Paul; The two are equivalent. I believe the story is that a few years back the Jena team wrote a Turtle serializer. Since N3 was a hot topic then, they used the .n3 extension, thinking that the Turtle serializer would be extended. Since then the alignment of Turtle and SPARQL has become stronger - even stronger in the RDF 1.1 WC - and N3 has had little uptake, no work beyond the Turtle serializer/parser is forthcoming. In addition, Turtle will become one of the standard RDF serializations (along with N-Triples, RDF/XML, and perhaps JSON) in the 1.1 recommendation.
For TBS, .n3 and .ttl files are the same Turtle serialization. You can use either extension, but to avoid confusion, we recommend .ttl, and Composer now enforces this for new file wizards, etc. -- Scott On Sep 25, 2012, at 7:51 AM, PaulZH <[email protected]> wrote: > I remember that in one of the previous versions of TBC turtle has been > favored over the n3 serialisation. > I do not seem able to find the text back explaining the rationale of this > move. > > Anyone having this pointer? > > > Thanks. > -- > -- You received this message because you are subscribed to the Google > Group "TopBraid Suite Users", the topics of which include Enterprise > Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, > TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN. > To post to this group, send email to > [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/topbraid-users?hl=en > > -- -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
