- From: Jeremy Carroll <jjc@hplb.hpl.hp.com>
- Date: Mon, 25 Oct 2004 17:08:26 +0100
- To: Jeremy Carroll <jjc@hplb.hpl.hp.com>
- CC: "'public-rdf-in-xhtml task force''" <public-rdf-in-xhtml-tf@w3.org>
Friday I took an action to review RDF/A
http://www.formsplayer.com/notes/rdf-a.html
11 October 2004
to see whether it addresses the nodeID issue.
It seems to, but I felt there were still a few rough edges.
Two were:
1)
from section 5.2 the example
[[
<link nodeID="a" rel="foaf:mbox"
href="mailto:daniel.brickley@bristol.ac.uk" />
<link nodeID="b" rel="foaf:mbox" href="mailto:libby.miller@bristol.ac.uk" />
<link about="#bnode(a)" rel="foaf:knows" href="#bnode(b)" />
]]
the x-ppinter like notation #bnode(a) seems to confuse blank nodes and
URIref nodes. I think it is significantly cleaner not to provide such
syntax, but require, say:
<link nodeID="a" rel="foaf:knows">
<link nodeID="b"/>
</link>
which cannot be read as introducing URIref nodes.
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 ... :(
Jeremy
Received on Monday, 25 October 2004 16:08:46 UTC