W3C home > Mailing lists > Public > semantic-web@w3.org > June 2021

Re: Chartering work has started for a Linked Data Signature Working Group @W3C

From: Ivan Herman <ivan@w3.org>
Date: Fri, 4 Jun 2021 17:32:39 +0200
Cc: Manu Sporny <msporny@digitalbazaar.com>, semantic-web@w3.org
Message-Id: <CE532C5A-44F7-4484-BB18-FF2458DBCA0C@w3.org>
To: Dan Brickley <danbri@danbri.org>


> On 4 Jun 2021, at 16:16, Dan Brickley <danbri@danbri.org> wrote:
> 
> 
> 
> That does sound really really bad. Perhaps the WG charter should cover only use of self-contained Linked Data / RDF format, eg Turtle/TRiG? And then try to secure hypertext / multi-stakeholder RDF syntaxes (json-ld, grddl, ...) as a stretch goal rather than core business? 

Dan,

I do not understand what you mean. What do you mean by "multi stakeholder RDF Syntax" that seems to characterize JSON-LD as opposed to Turtle or RDF/XML? This is the first time I meet this type of expression with regards to RDF syntaxes. In view, JSON-LD is not fundamentally different from Turtle or RDF/XML. 

I suspect you are referring to the problems that arise with the context file, although I am not sure why that is a "multi stakeholder syntax" - but we have already made a change on the charter by making it explicit that the WG will deal with the specific context issue separately, see

https://w3c.github.io/lds-wg-charter/#ig-other-deliverables <https://w3c.github.io/lds-wg-charter/#ig-other-deliverables>

Ivan

P.S. We can forget about GRDDL, which I would not call a a syntax.



> 
> Dan
> 
> 
> 
> -- manu
> 
> -- 
> Manu Sporny - https://www.linkedin.com/in/manusporny/ <https://www.linkedin.com/in/manusporny/>
> Founder/CEO - Digital Bazaar, Inc.
> blog: Veres One Decentralized Identifier Blockchain Launches
> https://tinyurl.com/veres-one-launches <https://tinyurl.com/veres-one-launches>
> 
> 


----
Ivan Herman, W3C 
Home: http://www.w3.org/People/Ivan/
mobile: +33 6 52 46 00 43
ORCID ID: https://orcid.org/0000-0003-0782-2704


Received on Friday, 4 June 2021 15:33:56 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:42:16 UTC