Re: ISSUE-83: CURIEs must require colon

+0.5 from me - that's only because I don't fully understand the 
requirement to not force the presence of a colon in CURIEs and feel they 
may be better with colons (colon as part of the prefix or just a requred 
separator) - but then I don't need to (and can't) understand everything :-)

It fixes the issue @about/@resource="#me" issue, that's good enough for me.

Agree w/ Ivan re using these things for test cases, good call.

Best,

Nathan

Ivan Herman wrote:
> +1 for me, too.
> 
> But... once we are over the LC comment round, we will have to have a look at our test cases. All these cases that we discussed should be reflected in real tests...
> 
> Ivan
> 
> On Feb 9, 2011, at 16:45 , Manu Sporny wrote:
> 
>> On 02/09/11 07:05, Toby Inkster wrote:
>>>> The solution to this problem must not create backward
>>>> incompatibilities and must allow the usage of @vocab.
>>> Proposed solution - which is probably the same as what Shane
>>> suggested...
>> A very big +1 from me for Shane/Toby's proposal. I had done a rough
>> draft proposal of something equivalent to this last night, but when I
>> went to review/send it this morning, Toby had already beat me to the
>> punch (and said it much more concisely than I did). So, yay and +1. :)
>>
>> -- manu
>>
>> -- 
>> Manu Sporny (skype: msporny, twitter: manusporny)
>> President/CEO - Digital Bazaar, Inc.
>> blog: Towards Universal Web Commerce
>> http://digitalbazaar.com/2011/01/31/web-commerce/
>>
> 
> 
> ----
> Ivan Herman, W3C Semantic Web Activity Lead
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> PGP Key: http://www.ivan-herman.net/pgpkey.html
> FOAF: http://www.ivan-herman.net/foaf.rdf
> 
> 
> 
> 
> 

Received on Wednesday, 9 February 2011 17:26:47 UTC