W3C home > Mailing lists > Public > public-html-data-tf@w3.org > October 2011

Re: Draft response to ISSUE-105: @itemref support

From: Jeni Tennison <jeni@jenitennison.com>
Date: Fri, 14 Oct 2011 20:38:21 +0100
Cc: RDFa WG <public-rdfa-wg@w3.org>, public-html-data-tf@w3.org
Message-Id: <5DC29D67-B51E-47B5-B597-D38F3A941B1E@jenitennison.com>
To: Manu Sporny <msporny@digitalbazaar.com>
Hi Manu,

On 15 Sep 2011, at 20:27, Jeni Tennison wrote:
> On 14 Sep 2011, at 02:54, Manu Sporny wrote:
> [snippety snip]
>> So at this point, we need a compelling use case that would outweigh the fairly large implementation burden for a feature like @itemref. We are also very concerned that allowing multiple subjects in @about would be very confusing to authors.
>> 
>> What are your thoughts on this Jeni? @itemref is helpful in a few scenarios, but it seems as if the trade-offs are not worth it to the Working Group. Do you have anything else to add? If there is no new evidence, the WG will probably close the issue due to the technical complexity and the lack of compelling use cases.
> 
> I understand the trade-offs and appreciate you taking time to look at this. I'm going to try to find use cases for you, if there are some. I wonder if you could hold the issue open for a while? If I don't manage to dig any out, then obviously it's fine to close the issue, but I'd like to get some input from others rather than make up use cases myself that may be based on false assumptions.


I asked the HTML Data TF whether anyone there had any use cases for shared properties as supported by itemref, or was prepared to go hunting for them, but no one did. Given that, I'm quite happy to drop it.

Thanks again for taking the time to consider it,

Jeni
-- 
Jeni Tennison
http://www.jenitennison.com
Received on Friday, 14 October 2011 19:38:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 14 October 2011 19:38:57 GMT