Changes between Version 4 and Version 5 of StateOfPerlAndRdf

Timestamp:

2010/03/12 02:57:42 (15 years ago)

Author:

tkappler

Comment:

Integrated SerializationPerlModules by yy.

StateOfPerlAndRdf

@@ -36 +36 @@
 > situations where get_statements doesn't do as much as you need.
 
+'''yy's serialization notes:''' The output (RDF/XML) has some redundancies. The module groups statements that share the subject, and embraces them by "<rdf:Description>" tags. It's OK, but declaration of user-defined namespaces is not at the first "<rdf:RDF>" tag, but at each rdf-description tag. This will probably be configurable from the next release, though. Also, the nesting level is one, and you cannot define a QNAME of a name space as "foaf" or "rdfs", but the module defines arbitrarily.
+Even so, it's more compact than that of RDF::Redland.
 
-See the `trine-*.pl` files for code snippets.
 
 ==== RDF::TrineShortcuts ====
@@ -51 +52 @@
 
 I couldn't build it as I have the new version 0.9.17 of librasqal, the query library for Redland, which is API incompatible with its predecessor on which RDF::Redland apparently depends.
+
+Another hint for building it is that the test script assumes that libraries generated by swig are in the shared library paths.
+After taking care of it by adding the following paths to LD_LIBRARY_PAT, no problem occurred for yy:
+{{{
+Redland-1.0.5.4/redland/rasqal/src/.libs
+Redland-1.0.5.4/redland/raptor/src/.libs
+}}}
 
 
@@ -71 +79 @@
   "[http://kasei.us/archives/2006/09/23/perl_performance met with resistance, rejection, or frustratingly long delays]". Not
   good.
-  
+
+'''yy's serialization notes:''' RDF::Core is a bit old and cannot handle a blank node (rdf:nodeID), but the serialized output (RDF/XML) is better organized than the others. You cannot define a QNAME of a name space.
+
+
+=== RDF::Simple ===
+
+[http://search.cpan.org/~mthurn/RDF-Simple-0.415/ RDF::Simple (0.415)] - very basic.
+
+'''yy's serialization notes:''' RDF::Simple is literally "simple", so IMO it is useful only for understanding how serialization works, but not for a practical use. As the module page says, it doesn't care the node type. You cannot declare whether a node is a URI or literal. On the other hand, a serialized output (RDF/XML) is better organized (more nested and size is smaller) than RDF::Trine and RDF::Redland.
+
 
 === Onto-Perl ===