Re: ISSUE-143 (Prefixes too complicated): Use of prefixes is too complicated for a Web technology [RDFa 1.1 in HTML5]

Does no one have a proposal that both continues to support "the use of
multiple open-ended vocabularies" and also addresses the problems raised?
What is the attitude of list members to problem number 3 raised by TJ?

I am naively curious, but would be excited by a more durable resolution,
with an even greater consensus, on this long-running issue.

Simon

On 6 November 2012 02:02, Shane McCarron <ahby@aptest.com> wrote:

> [...]
> On Mon, Nov 5, 2012 at 7:10 PM, Sebastian Heath <sebastian.heath@gmail.com
> > wrote:
>
>> I believe both proposals would be detrimental to my work by way of
>> limiting the vocabularies I can use.
>> [...]
>>  I'll phrase that another way: it is not the role of the W3 to
>> determine which vocabularies I can use. Instead, I expect the W3 to
>> support the use of multiple open-ended vocabularies and to provide a
>> mechanism that eases such use. The existing prefix mechanism does both
>> so I move that it be retained as is.
>>
>>  Sebastian Heath.
>>
>> On Mon, Nov 5, 2012 at 7:16 PM, Tab Atkins Jr. <jackalmage@gmail.com>
>> wrote:
>> [...]
>> > 3. In addition to the theoretical interop problem above, we have a
>> > real interop problem already - many consumers will happily consume
>> > pages that don't declare their prefix, as long as they use a
>> > "well-known" prefix for it.  A conformant consumer, on the other hand,
>> > would *not* do so, and would find no valid data on the pages.  You
>> > have to reverse-engineer the web to find out which prefixes need to be
>> > supported without a declaration, and what URL they should be bound to.
>> >  This is an obvious failure mode of a standard.
>> [...]
>> > ~TJ
>>
>
-- 
Simon Grant
+44 7710031657
http://www.simongrant.org/home.html

Received on Tuesday, 6 November 2012 06:45:26 UTC