Changes between Version 6 and Version 7 of SerializationPerlModules
- Timestamp:
- 2010/02/22 11:49:12 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SerializationPerlModules
v6 v7 12 12 As the module page says, it doesn't care the node type. 13 13 You cannot declare whether a node is a URI or literal. 14 On the other hand, a serialized output (RDF/XML) is better organized than the other.14 On the other hand, a serialized output (RDF/XML) is better organized than RDF::Trine and RDF::Redland. 15 15 16 16 RDF::Trine doesn't provide a sufficient document, and I have a bit difficulty in making a code. … … 18 18 This module groups statements that share a same subject, and embraces them by "<rdf:Description>" tags. 19 19 It's OK, but declaration of user-defined namespaces is not at the first "<rdf:RDF>" tag, but at each rdf-description tag. 20 Also, nest level is one .20 Also, nest level is one, and you cannot define a QNAME of a name space as "foaf" or "rdfs", but the module defines arbitrarily. 21 21 Even so, it's more compact than that of REF::Redland. 22 22 … … 30 30 Redland-1.0.5.4/redland/raptor/src/.libs 31 31 }}} 32 33 RDF::Core is a bit old and cannot handle a blank node (rdf:nodeID), but a serialized output (RDF/XML) is better organized than the others. 34 As with RDF::Trine, you cannot define a QNAME of a name space.