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
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:
On 10/3/13 11:59 AM, "Farrukh Najmi" <farr...@wellfleetsoftware.com>
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
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.