W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > October 2004

Nested mark-up and XML literals [was RE: comments on nodeID in RDF/A]

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Mon, 25 Oct 2004 17:59:19 +0100
To: "'Jeremy Carroll'" <jjc@hplb.hpl.hp.com>
Cc: "'public-rdf-in-xhtml task force''" <public-rdf-in-xhtml-tf@w3.org>
Message-ID: <009e01c4bab3$fc3d3ac0$6701a8c0@W100>

Jeremy,

> 2)
> I am unclear how the object rules determine whether XML 
> content within 
> an element without an href or content attribute is:
> - further metadata markup
> or
> - the literal object of the triple
> 
> e.g.
> 
> in
> 
> <link rel="foaf:mbox" href="mailto:daniel.brickley@bristol.ac.uk">
>      <link rel="foaf:knows">
>          <link rel="foaf:mbox" 
> href="mailto:libby.miller@bristol.ac.uk" />
>      </link>
> </link>
> 
> what stops the output being, roughly
> 
> _:a foaf:mbox mailto:daniel.brickley@bristol.ac.uk.
> _:a foaf:knows "<link rel='foaf:mbox' 
> href='mailto:libby.miller@bristol.ac.uk' />"^^rdf:XMLLiteral.
> 
> (XMLLiteral modulo excl XML c14n)
> 
> Such a reading would seemed forced if say there was a typo 
> using <linx> 
> instead of <link> as the innermost element tag ... :(


The difference is dictated by the use of the @rel/@rev attributes, versus
the @property attribute. The latter says that its object is *always* a
literal, the former that it is *always* a URIref.

Regards,

Mark


Mark Birbeck
CEO
x-port.net Ltd.

e: Mark.Birbeck@x-port.net
t: +44 (0) 20 7689 9232
w: http://www.formsPlayer.com/

Download our XForms processor from
http://www.formsPlayer.com/
Received on Monday, 25 October 2004 16:59:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:14:59 GMT