The develop of ShEx continues, and the site http://shex.io/ is kept
fairly up-to-date (although I'm sure it lags behind github). There is a
translator from ShEx to SHACL Core that is not quite done but appears to
be close. It will be tested on the ShEx test suite to show that the
statements are equivalent.
Note that ShEx only covers SHACL Core, not the extension, and, most
importantly, ShEx does not have the target and filter mechanisms that
are in SHACL. What that means is that ShEx begins with previously
selected graphs that are intended for validation, while SHACL includes a
mechanism to select those graphs.
I have to say that the ShEx "primer" looks to me to be more of a "user
documentation" [1], and is already more formal than the SHACL
specification.[2] This makes it very hard to compare them, but I'm
hoping that the translate will be able to provide equivalent coded
versions that we can look at.
kc
[1] http://shexspec.github.io/primer/
[2] http://w3c.github.io/data-shapes/shacl/
On 10/20/16 6:47 AM, Gregg Kellogg wrote:
>> On Oct 20, 2016, at 3:22 PM, Thomas Baker <[log in to unmask]> wrote:
>>
>> Recent minutes of the Data Shapes Working Group [1] refer to what looks
>> like a new description of Shapes Expression Language (ShEx) [2].
>
> Eric and I are together at a workshop, and he disappeared a while yesterday to work on this, apparently. It seems that ShEx is not compatible with SHACL, and can produce SHACL directly, making the two shape models consistent, although it still retains it’s direct JSON representation that can be used to validate directly.
>
> Gregg
>
>> Tom
>>
>> [1] https://www.w3.org/2016/10/11-shapes-minutes
>> [2] https://shexspec.github.io/spec/
>>
>> --
>> Tom Baker <[log in to unmask]>
>
--
Karen Coyle
[log in to unmask] http://kcoyle.net
m: 1-510-435-8234
skype: kcoylenet/+1-510-984-3600
|