W3C home > Mailing lists > Public > www-rdf-interest@w3.org > May 2001

#rdf-ns-prefix-confusion

From: Jason Diamond <jason@injektilo.org>
Date: Tue, 8 May 2001 08:46:51 -0700
To: "www-rdf-interest" <www-rdf-interest@w3.org>
Message-ID: <LAEMKGDBDFAKFNKPFEKLEEIBDMAA.jason@injektilo.org>
Hi.

I noticed in the minutes from the last teleconfierence [1] that the
unprefixed attribute issues [2] has been "RESOLVED". I'd just like to get
some clarification on this. Does it mean that all unprefixed attributes will
"assume" the prefix of their owner element for the purposes of which
predicate will be used or which RDF syntactic "keyword" is desired?

The following is legal according to the grammar:

<eg:Class about="http://foo">
  <eg:property>bar</eg:property>
</eg:Class>

but I've seen parsers report:

<#genid1> rdf:type eg:Class.
<#genid1> eg:about "http://foo".
<#genid1> eg:property "bar".

rather than:

<http://foo> rdf:type eg:Class.
<http://foo> eg:property "bar".

(Did I get my N3 right?)

Under the new resolution, which one is correct? I'm assuming the first but
would personally prefer the second.

Thanks,
Jason.

[1]
http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2001May/att-0017/01-2001-
04-27.html
[2]
http://www.w3.org/2000/03/rdf-tracking/Overview.html#rdf-ns-prefix-confusion
Received on Tuesday, 8 May 2001 11:54:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:51:49 GMT