W3C home > Mailing lists > Public > public-shex@w3.org > March 2017

Re: ShEx 2.0 Candidate Release

From: Lukas Rosenstock <lukas@cloudobjects.io>
Date: Wed, 29 Mar 2017 12:25:03 +0200
Message-Id: <49FEB9A2-3B47-471E-B05B-B4B2A14C527A@cloudobjects.io>
Cc: W3C Semantic Web IG <semantic-web@w3.org>, public-rdf-shapes@w3.org, public-shex@w3.org
To: Gregg Kellogg <gregg@greggkellogg.net>
Hello!
ShEx looks interesting and seems to fill a gap in terms of defining constraints for RDF documents!

I have a quick question in terms of understanding the semantics and how they relate to existing RDF, apologies in advance if it’s a dumb question.

I’m basing this on the example in the Quick Start of the Primer.

There is inst:Student1. Where is it defined that inst:Student1 is to be validated against ex:Enrollee?

My understanding would be that it would have to be stated that inst:Student1 rdf:type ex:Enrollee.,
which implies that ex:Enrollee rdf:type rdfs:Class, shex:Shape. or even shex:Shape rdfs:subClassOf rdfs:Class..

Does that make any sense or am I going in a wrong direction with my thinking?

Regards,

Lukas Rosenstock

> Am 28.03.2017 um 10:43 schrieb Gregg Kellogg <gregg@greggkellogg.net>:
> 
> he ShEx Community Group would like to invite public review of three deliverables:
> 
>  Shape Expressions (ShEx) Primer http://shex.io/shex-primer/
>  Shape Expressions Language 2.0 http://shex.io/shex-semantics/
>  Shape Expressions Test Suite https://github.com/shexSpec/shexTest/ including:
>  * 337 schemas in three representations:
>      ShExC: compact syntax
>      ShExJ: JSON-LD 1.0 syntax
>      ShExR: Turtle syntax
>  * 927 validation tests.
>  * 101 ShExC negative syntax tests
>  * 7 negative structure tests.
> 
> The test suite has a Implementation Report including 4 of the 5 implementations:
>  http://shexspec.github.io/shexTest/reports/
> 
> For feature requests please note the features in the 2.1 milestone:
>  https://github.com/shexSpec/shex/issues?q=is%3Aopen+is%3Aissue+milestone%3A2.1
> 
> Many of these have been implemented and tested but are not in this version of
> the specification. We invite feedback from the community on issues with the
> documents or tests, new feature prioritization and new feature use cases.
> 
> Comments are welcome on the ShEx Community Group mailing list (archived):
>  public-shex@w3.org
> 
> Readers may also wish to join the ShEx Community Group:
>  https://www.w3.org/community/shex/join
> 
> Sincerely,
>  Andra Waagmeester
>  Dimitris Kontokostas
>  Eric Prud'hommeaux
>  Gregg Kellogg
>  Harold Solbrig
>  Iovka Boneva
>  Jose Emilio Labra Gayo 
>  Karen Coyle
>  Katherine Thornton
>  Tom Baker
> 
Received on Wednesday, 29 March 2017 10:28:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 29 March 2017 10:28:07 UTC