W3C home > Mailing lists > Public > public-data-shapes-wg@w3.org > May 2016

Re: Simplification of scopes section (see also ISSUE-148)

From: Dimitris Kontokostas <kontokostas@informatik.uni-leipzig.de>
Date: Sun, 15 May 2016 17:04:14 +0300
Message-ID: <CA+u4+a092in1YbiucjnmUQB_o44dixn4axsgKDDqTWV41urX4w@mail.gmail.com>
To: Holger Knublauch <holger@topquadrant.com>
Cc: public-data-shapes-wg <public-data-shapes-wg@w3.org>
On Sun, May 15, 2016 at 3:59 AM, Holger Knublauch <holger@topquadrant.com>
wrote:

>
>
> On 14/05/2016 22:07, Dimitris Kontokostas wrote:
>
>> Another gap that sh:AllSubjectsScope came to fill is sh:scopeClass
>> rdfs:Resource that was available in very early versions of SHACL
>> In general this scope gives shacl core the flexibility to define complex
>> focus nodes using all subjects + filters that will not be easy otherwise
>> so I would be keen on keeping this in core
>>
>
> Do you have a specific example?


Karen's example is a good one, e.g. I have a set of general properties that
apply to all resources e.g. dct:title must be a string with max length x
and dct:Description must be a string with min length z

another one is all resources must have at least one dct:title and at least
one dct:description

or more complex ones like resources that have rdfs:label or dct:title must
have the following constraints



-- 
Dimitris Kontokostas
Department of Computer Science, University of Leipzig & DBpedia Association
Projects: http://dbpedia.org, http://rdfunit.aksw.org,
http://aligned-project.eu
Homepage: http://aksw.org/DimitrisKontokostas
Research Group: AKSW/KILT http://aksw.org/Groups/KILT
Received on Sunday, 15 May 2016 14:05:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:30:33 UTC