- From: Eric Prud'hommeaux <eric@w3.org>
- Date: Thu, 14 Feb 2013 09:19:36 -0500
- To: Andy Seaborne <andy.seaborne@epimorphics.com>
- Cc: public-rdf-wg@w3.org
* Andy Seaborne <andy.seaborne@epimorphics.com> [2013-02-14 12:27+0000] > > > On 13/02/13 22:58, RDF Working Group Issue Tracker wrote: > >RDF-ISSUE-115: LC Comment: Unsetting @base and @prefix [RDF Turtle] > > > >http://www.w3.org/2011/rdf-wg/track/issues/115 > > > >Raised by: Guus Schreiber > >On product: RDF Turtle > > > >See: http://lists.w3.org/Archives/Public/public-rdf-comments/2012Sep/0076.html > > If the TTL files are legal standalone, nothing needs to be done for > @prefix as the prefix must be defined in the file for the file to be > valid standalone. > > For @base, which might propagate from one file to the next, it only > makes a difference if the second file has no @base, making it > sensitive to location. > > In that case it is better to define @base: e.g. > > #!/usr/bin/env bash > for file in *.ttl; do > echo -e "\n @base <$file>\n" >> out.ttl > cat $file >> out.ttl > done > > so defining the base when the content is put in out.ttl. FYI, I mentioned this to the commenter in the WG response: http://www.w3.org/mid/20130214044715.GD15692@w3.org > If the files are fragments of Turtle undefining would be nice if it > were earlier in the WG lifecycle. > > Andy > -- -ericP
Received on Thursday, 14 February 2013 14:20:09 UTC