- From: Jose Emilio Labra Gayo <jelabra@gmail.com>
- Date: Thu, 19 Feb 2015 04:46:40 +0100
- To: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
- Cc: RDF Data Shapes Working Group <public-data-shapes-wg@w3.org>
- Message-ID: <CAJadXX+++vf9a5x4Fn2TXnaOpvV1e0ef-i7gYu4Hz3HCoVC48Q@mail.gmail.com>
On Thu, Feb 19, 2015 at 2:30 AM, Peter F. Patel-Schneider <
pfpschneider@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I've been looking again at Shape Expressions and have come up with some
> cases that may not be defined well.
>
>
> Consider the following simple RDF graph
>
> @prefix ex: <http://ex.com/> .
> ex:a ex:p ex:b .
> ex:b ex:p ex:a .
>
> and the following simple shape expressions
>
> PREFIX ex: <http://ex.com/>
> <R> { ex:p @<R> }
>
In this case, from my point of view, both ex:a, and ex:b conform to shape
<R>
> <S> { ( ex:p @<S> | ex:p @<T> ) }
> <T> { ( ex:p @<S> | ex:p @<T> ) }
>
In this case, there are some alternatives. If you start by node ex:a, then
the system can match with the following typing
ex:a -> <S>, ex:b -> <S>
or
ex:a -> <S>, ex:b -> <S>, <T>
or
ex:a -> <S>, ex:b -> <S>, <T>
>
> What are the results of rule evaluation
> 1/ as they should be,
> 2/ according to Shape Expressions 1.0 Definition,
> 3/ according to other definitions for Shape Expressions,
> and
> 4/ from implementations?
>
I tested it in RDFShape and the result was:
http://bit.ly/1vjlxX9
Best regards, Labra
>
>
> peter
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEcBAEBAgAGBQJU5Ty+AAoJECjN6+QThfjzMgUH/ikMoL04+atFbWA8uoSUMZO4
> PuoXRfNzRrs88bpt6b9rVe7U+wTV90J03iL1cQpwkKUtlfAB5/jmPXVhkj00C4CY
> bt+FGe2jXM/XhwK8QM5NGjofo8NCh8n/hw19SO+nraBm752NzxHU42Y7qaCep/1E
> JVNDV0y1plkye02IgVGJIlWbz/GlBfkmWWOaC7n5ap9Jl6acSZ2pI2gcWUYsmieo
> +/RelOzQyEspnH8lFiA0cFj9rgOCQMFaCNoxKpYiyztMtKCr0UACEyDoZha27Hi8
> wpTiDv2Nzdu/OS+vMZZQwE96WLd75/xFxZzLLxluBKpIs9WVzbiAKYXB5fZ1oc8=
> =rMNZ
> -----END PGP SIGNATURE-----
>
>
--
Saludos, Labra
Received on Thursday, 19 February 2015 03:47:27 UTC