- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Mon, 5 Feb 2024 12:35:28 +0100
- To: Nicolas Chauvat <nicolas.chauvat@logilab.fr>
- Cc: Han Wammes <han.wammes@dataincontext.org>, Simon Grant <asimong@gmail.com>, public-solid <public-solid@w3.org>
- Message-ID: <CAKaEYh+9K55pSymSEnLFj4vat1UpxGb62DGpRMRxEC3mZ8PeWA@mail.gmail.com>
po 5. 2. 2024 v 12:29 odesílatel Nicolas Chauvat <nicolas.chauvat@logilab.fr> napsal: > Hi, > > Le Sun, Feb 04, 2024 at 06:46:29PM +0100, Han Wammes a écrit : > > To support the discussion, have a look at the article on Datascience > from Kurt Cagle: > https://www.datasciencecentral.com/why-json-users-should-learn-turtle/ > > +1 > > As the article states: > > Turtle is the Language of the Semantic Web. > Turtle Underlies SPARQL, SHACL and other languages. > Turtle is Human Readable. > Turtle Is A True Streaming Language. > RDF automatically deduplicates. > Turtle is unambiguous, JSON is not. > Semantics Matter. > Turtle represents complex structures better than JSON. > > to me readability is high on the list and the fact that it looks the > same in Sparql and in Turtle is important. Others point are good too. > Hi Nicolas, thanks for the summary. You're preaching to the converted here, I've been a turtle evangelist for about a decade. I guess the only challenge is the network effect around turtle is much smaller than around JSON. All of those points made sense to me, though one I struggled to fully understand: "Turtle is unambiguous, JSON is not. JSON-LD emerged as a standard to work with the semantic web, but it currently has four different profiles, is surprisingly difficult to write well for larger data structures, and as often as not is rejected primarily because it fails to conform to any of the profiles. Turtle has two profiles that have very clear syntax (Turtle and Turtle-Star), with Turtle-star being only slightly less clear because of a few edge cases that haven’t been fully resolved. Additionally, when people refer to Turtle, they are usually actually talking about TRIG, which extends the turtle language to incorporate named graphs (TRIG is backwards compatible with Turtle)." The word that interests me here is "unambiguous", partly because we are currently trying to (re)define WebID in the CG as an HTTP URI that "unambiguously" denotes an agent. The term unambiguous comes up a lot in sem web discussions, and I'm not really sure I've fully grasped its meaning and how it differs from uniqueness and universality. > > -- > Nicolas Chauvat > > logilab.fr - services en informatique scientifique et gestion de > connaissances >
Received on Monday, 5 February 2024 11:35:45 UTC