W3C home > Mailing lists > Public > public-rdf-wg@w3.org > December 2013

Re: Turtle += Note explaining @prefix and PREFIX

From: Sandro Hawke <sandro@w3.org>
Date: Sun, 15 Dec 2013 12:04:58 -0500
Message-ID: <52ADE13A.6040109@w3.org>
To: Eric Prud'hommeaux <eric@w3.org>, Gavin Carothers <gavin@carothers.name>
CC: RDF Working Group WG <public-rdf-wg@w3.org>
On 12/15/2013 11:38 AM, Eric Prud'hommeaux wrote:
> * Eric Prud'hommeaux <eric@w3.org> [2013-12-14 19:23-0500]
>> On Dec 14, 2013 11:44 PM, "Gavin Carothers" <gavin@carothers.name> wrote:
>>> The changes to resolve the feature at risk were the last ones I was aware
>> of. Hopefully everyone finds them acceptable. Will create the PR
>> Overview.html(s) for everything this weekend.
>>
>> It looks good to me but I recall there being some text associated with the
>> resolution to the effect of "use @prefix until the RDF 1.1 Turtle parsers
>> are deployed." I'll dig that up in the morning unless someone else in the
> Done. please see:
>    https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#sec-iri
> and the changeset at:
>    https://dvcs.w3.org/hg/rdf/rev/551b4b75eff0
>
> [[
> Note
>
> The Turtle language originally permitted only the syntax including the
> '@' character for writing prefix and base directives. The
> case-insensitive 'PREFIX' and 'BASE' forms were added to align
> Turtle's syntax with that of SPARQL. It is advisable to serialize RDF
> using the '@prefix' and '@base' forms until RDF 1.1 Turtle parsers are
> widely deployed.
> ]]

Can we also point people to 
https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/reports/index.html or 
maybe a www.w3.org proxy/snapshot of it, so people have a better chance 
of knowing when that is?

Or is that misleading, because even if the software is updated, the 
people using the software will still be using old copies? Hrm.     I 
guess no advice is better than bad advice.   :-(

          -- Sandro


> ...
> [[
> This can be written using either the original Turtle syntax for prefix
> declarations:
>
> Example 7
> ┌
> │@prefix somePrefix: <http://www.perceive.net/schemas/relationship/> .
> │
> │<http://example.org/#green-goblin> somePrefix:enemyOf <http://example.org/#spiderman> .
> └				
> or SPARQL's syntax for prefix declarations:
>
> Example 8
> ┌
> │PREFIX somePrefix: <http://www.perceive.net/schemas/relationship/>
> │
> │<http://example.org/#green-goblin> somePrefix:enemyOf <http://example.org/#spiderman> .
> └				
> ]]
>
>
>> WG finds it first. The W3C HTML diff tool worked with the draft as of
>> Wednesday so ideally that will go smoothly. I don't recall there being any
>> agreed upon text for the SOTD but I can draft some in about 10 hours.
>>
>>> On Fri, Dec 13, 2013 at 8:38 PM, Eric Prud'hommeaux <eric@w3.org> wrote:
>>>> On Dec 12, 2013 5:03 PM, "Gavin Carothers" <gavin@carothers.name> wrote:
>>>>> I've updated Turtle to include PREFIX/BASE as not At Risk features.
>>>>>
>>>>> https://dvcs.w3.org/hg/rdf/rev/7153257b5d27 is the complete change
>> set. Please provide any feedback you may have ASAP.
>>>> You spoke of a list of pending Turtle issues on Wed. Are there remaining
>> issues that you know of?
>>>>> Cheers,
>>>>> Gavin
>>>
Received on Sunday, 15 December 2013 17:05:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:04:37 UTC