Bug #4225
Do not parse any RDF object as an ORE object
100%
Description
I've been working with the CN indexing libraries and noticed that the ResourceMapSubprocessor is "handling" both these formatIds:
http://www.openarchives.org/ore/terms
http://www.w3.org/TR/rdf-syntax-grammar
But I believe it should only be handling the first one since many assumptions are made about the object and the triples it contains.
Also, I am trying to make a more generalized RDF/XML processor that would allow us to pick off concepts for indexing and when two subprocessors claim to handle the same formatId, only one of them can consume the stream - the next one gets an error. We could consider reconstructing the stream to support multiple parsers for the same document format to support this as well.
Related issues
History
#1 Updated by Skye Roseboom over 10 years ago
- Status changed from New to In Progress
#2 Updated by Skye Roseboom over 10 years ago
- Tracker changed from Story to Bug
- Status changed from In Progress to Testing
Moved configuration correction to build out on trunk/unstable for testing.
#3 Updated by Skye Roseboom over 10 years ago
- Status changed from Testing to Closed
Update to configuration of the ResourceMapSubProcessor has been updated to only handle 'http://www.openarchives.org/ore/terms'
