W3C home > Mailing lists > Public > public-rdf-shapes@w3.org > July 2014

Re: Shapes/ShEx or the worrying issue of yet another syntax and lack of validated vision.

From: Jerven Bolleman <jerven.bolleman@isb-sib.ch>
Date: Fri, 18 Jul 2014 22:40:30 +0200
Cc: Dimitris Kontokostas <kontokostas@informatik.uni-leipzig.de>, Jose Emilio Labra Gayo <jelabra@gmail.com>, "Dam, Jesse van" <jesse.vandam@wur.nl>, "public-rdf-shapes@w3.org" <public-rdf-shapes@w3.org>
Message-Id: <D0CB5DC0-074D-4485-A055-DE120553786B@isb-sib.ch>
To: Kendall Clark <kendall@clarkparsia.com>
I completely agree with Kendall.

A standard would look at the similarities between Resource Shapes, ICV and SPIN and see if a common syntax can be achieved.
What seems to be happening instead is that a 4th independent option is being designed.
Which means that the real standard will then need to look into standardising Shex, Resource Shapes, ICV and SPIN. 
Giving standard number 5, which is how WGs become inspiration for XKCD and Dilbert comics

ShEX currently reuses practically nothing of the earlier work or existing W3C standards.

And a lot is being said about usability but no one recalls the sad joke.

   Some people, when confronted with a problem, think 
   I know, I'll use regular expressions.   Now they have two problems.

ASCII art is not a requirement any more.
Saving bits is a goal of compression algorithms. 
Code should strive for readability, especially validation code.

E.g. this SPARQL pseudo style of using
{ [] foaf:name xsd:string }
{ [] foaf:givenName xsd:string }

Is a much better idea than
{ foaf:name xsd:string ;
  | foaf:givenName xsd:string }
Where we started using the binary OR symbol to mean XOR and that is rather similar to || or the normal OR people are exposed to.

For the rest I saw the UniProt ShEX example and it is not at all representative for what a database like UniProt really needs.

Attached to this e-mail is PDF/poster about how SPIN is actually looked at in the UniProt consortium.

All in all I really encourage the Charter writers to really look at what is out there being used in the semweb world.
And look at standardising that instead of looking to the XML and Regex planets, which we thankfully left behind.


On 18 Jul 2014, at 18:24, Kendall Clark <kendall@clarkparsia.com> wrote:

> On Fri, Jul 18, 2014 at 12:20 PM, Dimitris Kontokostas <kontokostas@informatik.uni-leipzig.de> wrote:
> Instead of criticizing what ShEx can't do we should all try to see what ShEx should do.
> Why? Standards bodies should be about standardizing existing systems. This is one thing the W3C has consistently gotten wrong in the semantic web space: too much speculative research done in the guise of standardization.
> I think we all agree that a compact human syntax (with equivalent RDF representation) that covers common validations cases and SPARQL extensions is something we all want.
> SPIN, IBM Resource Shapes, and Stardog ICV already provide that. You can't get any more compact human syntax than, say, Manchester OWL syntax for constraints: see http://docs.stardog.com/icv for many *real* examples from shipping code.
> I too don't like some parts of ShEx but I think it's a good initiative to bootstrap a standard.
> That isn't how standardization works best.
> I already raised some issues in the mailing list and have a few more from my experience with RDFUnit - but will raise them later since the maintainers are now too busy replying.
> Those are all valid, interesting points for ShEx, which is at this point an interesting proof of concept or prototype of an idea. That work should be carried out in an R&D context. W3C Working Groups are not R&D contexts.
> Cheers,
> Kendall Clark 

Jerven Bolleman                        Jerven.Bolleman@isb-sib.ch
SIB Swiss Institute of Bioinformatics      Tel: +41 (0)22 379 58 85
CMU, rue Michel Servet 1               Fax: +41 (0)22 379 58 58
1211 Geneve 4,
Switzerland     www.isb-sib.ch - www.uniprot.org
Follow us at https://twitter.com/#!/uniprot

Received on Friday, 18 July 2014 20:41:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:02:39 UTC