Re: Use of SHACL for profiles

Ah, thanks Rob - I didn't look closely at the origins. In any case, what
this brings up for me beyond the interesting curiosity of a two-part
SHACL solution is:

1. Are these (taken together) an example of "publication of an AP" as
defined in our charter? with the emphasis on "publication"

2. Are we defining "application profile" in a way that an RDF vocabulary
list alone is not sufficient, or must other constraints (cardinality,
specific value constraints) must be included?

3. To what extent should our deliverable enter into the details of the
content/components of an application profile? meaning: are we being
asked to describe what are the elements of an application profile? (Our
use cases tend in this direction.)

kc

On 7/7/18 4:19 PM, Robert Sanderson wrote:
> 
> I would say that this is the library community, looking at the art world
> through a very bibliographic lens. Steven Folsom talked about the work
> at US2TS, notably as a way to build web forms.
> 
> See: https://twitter.com/sf433/status/968663830451679232  I can ask him
> for more details if there's interest?
> 
> Rob
> 
> 
> 
> 
> 
> On Sat, Jul 7, 2018 at 1:08 PM, Dan Brickley <danbri@google.com
> <mailto:danbri@google.com>> wrote:
> 
>     On Sat, 7 Jul 2018 at 12:47, Karen Coyle <kcoyle@kcoyle.net
>     <mailto:kcoyle@kcoyle.net>> wrote:
> 
>         I ran across an interesting use of SHACL for profiles, done by
>         the art
>         and museum community. The profiles are defined in SHACL, such as
>         this
>         example[1], and there is a separate SHACL graph for validation[2],
>         presumably validation of instance data. This is a case I hadn't
>         considered: separation of profile declaration and instance
>         validation,
>         both using SHACL. (There are other examples if you pop up in the
>         repo.)
> 
> 
>     Interesting! Is anyone collecting these already into a list (shex
>     too)? There are a few others on Github
>     e.g. https://github.com/BlueBrain/nexus-prov
>     <https://github.com/BlueBrain/nexus-prov> (see
>     also https://bbp-nexus.epfl.ch/dev/schema-documentation/documentation/shacl-schemas.html#namespaces-and-context
>     <https://bbp-nexus.epfl.ch/dev/schema-documentation/documentation/shacl-schemas.html#namespaces-and-context>
>     ) whose origins were apparently https://github.com/INCF/neuroshapes
>     <https://github.com/INCF/neuroshapes> 
> 
>     Dan
> 
>         kc
>         [1]
>         https://github.com/LD4P/arm/blob/master/application_profiles/art/shacl/artframe_art_form.ttl
>         <https://github.com/LD4P/arm/blob/master/application_profiles/art/shacl/artframe_art_form.ttl>
>         [2]
>         https://github.com/LD4P/arm/blob/master/core/validation/shacl/arm_core_property_shapes.ttl
>         <https://github.com/LD4P/arm/blob/master/core/validation/shacl/arm_core_property_shapes.ttl>
>         -- 
>         Karen Coyle
>         kcoyle@kcoyle.net <mailto:kcoyle@kcoyle.net> http://kcoyle.net
>         m: 1-510-435-8234 (Signal)
>         skype: kcoylenet/+1-510-984-3600
> 
> 
> 
> 
> -- 
> Rob Sanderson
> Semantic Architect
> The Getty Trust
> Los Angeles, CA 90049

-- 
Karen Coyle
kcoyle@kcoyle.net http://kcoyle.net
m: 1-510-435-8234 (Signal)
skype: kcoylenet/+1-510-984-3600

Received on Monday, 9 July 2018 14:31:27 UTC