RDF & XML Literals: Intro

The RDF specification shows how labelled graphs can be encoded in XML.

e.g. the graph


is encoded as


It permits the use of well-balanced fragments of XML as one sort of label,
and refers to these as "XML Literals".

A typical example is:

  <dc:Title rdf:parseType="Literal"><!-- Relevant text start. -->
  <!-- Relevant text end. --></dc:Title>

Many users may omit the default xmlns declaration.

It is unclear precisely what the label in the RDF graph is.
There is agreement that the relevant text in the input file lies between the
two comments.

Some RDF APIs provide a string, others provide a means of accessing the SAX
This is the content of the issue

As will be familiar to the C14N people, there are specific issues to do with
namespace processing.

These are identified in:
and also present in an example in the spec.

Other problems relate to inconsistent treatment of character references etc.
which, for instance, the HP team found problematic when upgrading Jena to
work with ARP instead of RDFFilter. The two parsers had taken different
choices with respect to the exact representation of xml literals and the
regression tests then failed.

A large part of RDF Core WG's work has been making RDF more formal.
Particularly the RDF test cases and RDF model theory depend upon a well
defined equality over node labels.

These goals are in conflict with the current spec. that explicitly ducks the
issue of equality.

This specification does not state a mechanism for determining equivalence
between literals that contain markup, nor whether such a mechanism is
guaranteed to exist
RDF Model Theory
RDF Test Cases

Hence, a resolution of these issues will give:
- a set of representation for XML Literals,
- a means for turning a specific well balanced XML fragment into such a
- a means for comparing two such representations for equality

The RDF Core is currently agreed that C14N will be the basis of addressing
these issues.

Received on Monday, 4 March 2002 07:43:21 UTC