Title: Message Title
|
|
Hi João, I agree that we should fix this in the easiest way possible. I just thought it would be easier to use an existing schema than publish our own. In case of oai-identifier.xsd, I think we could easily pre-fill the repository URL in description.xml by filtering during the ant step (so no dynamic generation or manual editing should be necessary). I don't disagree, it's just a suggestion. Hilton: No, that is the schema for all PMH responses. We need a schema for the contents of the <description> element.
|
|
|
|
|
Check the OAI-PMH endpoint with a validator (eg. http://oval.base-search.net/) it reports an error: "ERROR: Identify response well-formed but invalid: Element '{http://www.lyncode.com/XOAIConfiguration}XOAIDescription': No matching global element declaration available, but demanded by the strict wildcard., line 11" This is basically a configuration ...
|
|
|
|
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel