atom feed2 messages in org.oasis-open.lists.regrepRe: FW: [regrep] Proposal for PDF Pro...
FromSent OnAttachments
Reagan MooreOct 3, 2013 11:32 am 
Farrukh NajmiOct 3, 2013 12:22 pm 
Subject:Re: FW: [regrep] Proposal for PDF Profile
From:Farrukh Najmi (
Date:Oct 3, 2013 12:22:08 pm

Good point. How do you envision such a crosswalk to be used?

One possibility is to map indexes from various extension profiles of regrep to standard metadata indexes whenever possible. For example map PDF title index to dc.title instead of pdf.title.

Another possibility is to simply define equivalence crosswalk to relevant standards where possible and require that profiles treat the equivalent indexes synonymously. So if dc.title is used as index to search PDF documents it should match any entries that have pdf.title as cataloged slot.

Does this seems to be a more global issue than one specific to PDF prpfile?

On 10/03/2013 02:32 PM, Reagan Moore wrote:

There is always the issue of a crosswalk to standard metadata schemas. Pertinent schemas include:

Dublin Core METS

On 10/3/13 11:59 AM, "Farrukh Najmi" <> wrote:

Dear Colleagues,

I have been working on supporting the publish, management and discovery of PDF resources in an ebXML RegRep. I have written the initial outline of a extension profile specification with the proposed title "ebXML RegRep Profile for PDF Resources" in our wiki at.

You will see close similarities between the ImageProfile specification outline and this new PDF Profile specification outline. They both define a CQL Context Set and use CQL queries to query for their respective resources. This simplifies the profile by not requiring parameterized queries to be defined by the profile. I expect this CQL based approached to become the dominant means to query a RegRep server in future extension profiles of ebXML RegRep.

Please share any comments on the outline specification.

Thank you.