 |
|
|
The Jena RDF/XML Parser
ARP Features
- Java based RDF parser.
- Compliant with the last call candidate
syntax and
test cases
editors' working drafts.
- Compliant with following standards and recommendations:
- daml:collection
-
rdf:parseType='daml:collection' is supported.
- xml:lang
- xml:lang
is fully supported, both in RDF/XML and any
document embedding RDF/XML.
Moreover, the language tags are checked against
RFC1766,
RFC3066, ISO639-1,
ISO3166.
- xml:base
- xml:base
is fully supported, both in RDF/XML and any
document embedding RDF/XML.
- URI
- All URI references are checked
against RFC2396.
The treatment of international URIs follows the approach of anyURI in
XML Schema Datatypes.
- XML Names
- All rdf:ID and rdf:BagID's are checked against
the XML Names specification.
- International URI refs
- rdf:about, rdf:ID and rdf:BagID's are processed according to
the Character Model working draft.
- Unicode Normal Form C
- String literals and URIs are checked for conformance with
an early uniform normalization processing model.
- XML Literals
rdf:parseType='Literal' is processed respecting
namespaces, processing instructions and XML comments. This follows
the XML exclusive canonicalizations recommendation with comments, and
treating namespace (re)declarations as visible uses of the namespace.- Relative Namespace URI references
- Namespace URI references are checked in light of
the W3C XML Plenary
decision.
- aboutEach
- Is no longer supported, in line with working group decisions.
- Command-line as RDF/XML to N-Triple filter.
- Command-line RDF/XML error checking.
- Can be used independently of Jena, with customizable StatementHandler.
- Highly configurable error processing.
- Xerces based XML parsing.
- Processes both standalone and embedded RDF/XML.
- Streaming parser, suitable for large files.
Differences from ARP1
- Uses Xerces 2 (not configurable, even by hacking the source)
- Single threaded
- RDF datatype supported
- Significantly faster
|
