On Fri, Jul 24, 2015 at 6:51 AM, Holger Knublauch <holger@topquadrant.com>
wrote:
> As resolved in the call today, SHACL now supports
>
> - sh:maxExclusive
> - sh:maxInclusive
> - sh:minExclusive
> - sh:minInclusive
> (hopefully not including too many copy and paste errors)
>
> - sh:maxLength
> - sh:minLength
> - sh:pattern
>
> I have implemented the latter three so that they work with any datatype
> and even IRIs.
> Errors are reported on blank node values, because they cannot be turned
> into strings. Errors are also reported if the <, > comparisons fail.
>
I have some minor concerns on this as it might not be consistent with other
cases where a comparison fails and a user would expect an error report as
well.
I suggest we place a note that this is an exception for now.
Best,
Dimitris
>
> The two spec documents and the Turtle file should now be up to date, and I
> added some test cases too.
>
> Regards,
> Holger
>
> PS: Never place an iPad face-down on a pillow when you want to rely on its
> alarm clock. The pillow will hit "Tap to snooze" on your behalf...
>
>
--
Dimitris Kontokostas
Department of Computer Science, University of Leipzig & DBpedia Association
Projects: http://dbpedia.org, http://http://aligned-project.eu,
http://rdfunit.aksw.org
Homepage:http://aksw.org/DimitrisKontokostas
Research Group: http://aksw.org