- From: Han Wammes <han.wammes@dataincontext.org>
- Date: Sun, 4 Feb 2024 18:46:29 +0100
- To: Simon Grant <asimong@gmail.com>
- Cc: Melvin Carvalho <melvincarvalho@gmail.com>, public-solid <public-solid@w3.org>
- Message-Id: <E667FFDE-75C1-44C8-B425-0F0251278CB7@dataincontext.org>
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/ Greeting, Han Wammes > Op 4 feb 2024, om 16:18 heeft Simon Grant <asimong@gmail.com> het volgende geschreven: > > Simple question, putting on my naive hat here in the hope it may contribute ... How about specifying a serialisation in JSON-LD with enough constraints so that it can be easily and accurately converted into Turtle? > Would there be any problems with that? And would that not allow people to work with whichever serialisation that suits their needs? > > I can imagine the problems if the interconvertibility was not completely solid, but are there real problems in specifying enough to ensure that it is? > > Simon > > > On Sun, 4 Feb 2024 at 14:57, Melvin Carvalho <melvincarvalho@gmail.com <mailto:melvincarvalho@gmail.com>> wrote: >> Back in 2013 we decided to base WebID on the mandatory serialization using Turtle. Soon after this Solid became the first project to take WebID and use it to create a functioning social web. >> >> Since then JSON-LD has grown in popularity. In the WebID there has been an ongoing discussion on how it can be used in conjunction with WebID. >> >> Most recently, an idea has been floated that JSON-LD could replace Turtle in the longer-term, with turtle eventually deprecated after the eco system has moved. >> >> While this offers many advantages, such as JSON-LD's wide adoption, I had personally assumed it to be a non-starter, since Turtle seems popular in solid and is used in a lot of tooling. But I realize that my knowledge on Solid might not be 100% up to date, and it would be better to see what the CG thinks (if anything). >> >> Let me say a few things that Turlte does, that JSON-LD does not: >> - comments >> - does not require async @context lookup >> - upgrade path to TriG/n3 >> >> I dont know if any of these things, or other things >> >> So I'd like to do an informal straw poll: >> >> Would there be strong objection to deprecating Turlte, in favour of JSON-LD, in the longer-term? >> >> On a long timeline that gives everyone a chance to upgrade, with conneg used in the transition period. >> >> Would be great to hear if anyone has views on Turtle vs JSON-LD. It would be helpful in the WebID group to know if there's opinions on this in the Solid CG, for our ongoing modernization efforts. > > > -- > from Simon Grant +32 485821368 (+44 7710031657 – "asimong" with many services)
Received on Sunday, 4 February 2024 17:48:25 UTC