- From: Stéphane Corlosquet <scorlosquet@gmail.com>
- Date: Fri, 23 Dec 2011 01:10:25 -0500
- To: Patrick Logan <patrickdlogan@gmail.com>
- Cc: WebID XG <public-xg-webid@w3.org>
- Message-ID: <CAGR+nnGcF-gQTPL+Ej-JSgkBFMnHttQ0oBduVsJ+PjDf7=R=Kg@mail.gmail.com>
On Thu, Dec 22, 2011 at 1:42 PM, Patrick Logan <patrickdlogan@gmail.com>wrote: > Another spec-specific thread, this one for moving Turtle forward. > Again, please keep this thread focused on moving the spec forward in > support of Turtle. Longer, side conversations should go in a different > thread. > > Henry asked in that other v.long thread: > > "I wonder if the linked data crowd would prefer turtle support over > rdf/xml by now." > > My sense is the incremental cost for spec'ing, implementing, and > testing Turtle is fairly low. And my assumption is that use of Turtle > is on the upswing relative to RDF/XML. > > My preference is for Turtle to be included, because: > > * Given the RDF/XML requirement, the incremental cost for spec'ing, > implementing, and testing Turtle is presumably low. > > * Turtle provides a beneficial alternative to RDF/XML or other XML-ish > notations, as Turtle is more concise and less verbose than RDF/XML Note also it is possible to embed Turtle in HTML, see [1] and the more recent [2]. I don't think it's ready for prime time yet as it is not widely supported. It seems [3] is the only lib supporting it. This approach might be interesting for the case when the user does not want the public key to be displayed in the browser, as an alternative to using hidden RDFa markup in <body>. Something to investigate. Steph. [1] http://www.w3.org/wiki/N3inHTML [2] https://dvcs.w3.org/hg/htmldata/raw-file/default/html-data-guide/index.html#scope [3] http://search.cpan.org/dist/HTML-Embedded-Turtle/
Received on Friday, 23 December 2011 06:10:58 UTC