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

Re: status of non-prefixed values in @rel

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Tue, 15 Jan 2008 18:58:53 -0500
Message-ID: <478D48BD.4010707@digitalbazaar.com>
To: RDFa <public-rdf-in-xhtml-tf@w3.org>

Mark Birbeck wrote:
> Anyway, it's unfortunate that despite plenty of airing of opinions, in
> this case we _didn't_ schedule a vote. Which means that all of the
> work that was done at the time has been wasted

Not so, the discussion has been coming back to me over the past several
days and I'm in very strong support of back-burnering this issue again.

IMHO, we have other more pressing issues that aren't being resolved
(@href/@resource does/doesn't complete hanging triples) while we spend
time on this.

Not having rel="next" generate a triple in the default graph isn't a
deal-breaker as far as I see it, especially since we leave it up to the
parsers to generate those triples in other graphs, if necessary.

If we had to vote on this right now, I'd vote to back-burner the issue
by adopting Mark's 'rel="XHTML_RESERVED" doesn't generate a triple in
the default graph, but can in another graph' approach.

As Mark described, the problem is more complex than it seems and we have
two glaring issues with the Syntax document that need to be resolved:

1. @href/@resource does/doesn't complete hanging triples
2. @src does/doesn't set the subject.

-- manu

-- 
Manu Sporny
President/CEO - Digital Bazaar, Inc.
blog: Intro to the Semantic Web in 6 minutes (video)
http://blog.digitalbazaar.com/2007/12/26/semantic-web-intro
Received on Tuesday, 15 January 2008 23:59:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 15 January 2008 23:59:05 GMT