W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > April 2011

comments re ISSUE-86 (prefixes and terms)

From: Nathan <nathan@webr3.org>
Date: Wed, 06 Apr 2011 01:50:26 +0100
Message-ID: <4D9BB8D2.4070804@webr3.org>
To: RDFA Working Group <public-rdfa-wg@w3.org>
RE: ISSUE-86 Determine if prefixes and terms can be collapsed into one 
concept in the RDFa API

minor edit: it's the RDF API

minor comment: they're combined (not collapsed) in to one, that's what 
the Profile interface is.

Issues:
1)
if one sets a mapping of:
   merged.member = "http://www.w3.org/ns/org#member";

then one does:
   merged.resolve('member:bar');

the result will be (by the rules of CURIE processing)
   "http://www.w3.org/ns/org#memberbar"

or if one does:
   merged.resolve('member:bar#foo');

the result will be (by the rules of CURIE processing)
   "http://www.w3.org/ns/org#memberbar#foo"

2)
Name collisions, it's simple, but I believe it's the biggest issue we 
face here, lending to unexpected functionality that's built in to the API.

3)
How to /always/ shrink to a CURIE for those that serializations that 
support only CURIEs/qnames?

4)
How to ensure that only prefixes (and not terms) make it out in to the 
serializations for those that support only prefixes/CURIEs?

I'd /really/ rather keep these two separate, I believe by joining them 
we're only opening a can of worms that need not be opened.

Best,

Nathan
Received on Wednesday, 6 April 2011 00:51:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:19:51 UTC