– DRAFT –
Data Shapes WG

Phase 1 deliverables

elianaP: no updates on phase 1 or 2

Review old PRss

ajnelson-nist: will get to old PR review today

Task Force reports

holger: case of constraint for a limiting values to a value in a hierarchy

ajnelson-nist: I'm unclear on the intent

holger: value must be a class or subclass

<ieben> ASK { $value rdf:type/rdfs:subClassOf* $class . } VS ASK { $value rdfs:subClassOf* $class . }

holger: similar concept in SKOS

<ajnelson-nist> ieben: Thank you.

<simonstey> AndyS: it was unclear in some of your comments whether you are including or excluding the topclass of the hierarchy

<simonstey> ... depending on which, ancestor doesnt really work because you are not an ancestor of yourself

<simonstey> ... clade would fit

<simonstey> ... although this might be a bit to wacky

<TallTed> urClass

elianaP: show of hands on naming

<simonstey> ... ancestorClass, rootClass, cladeClass

elianaP: rootClass -- 6

<simonstey> rootClass +1

elianaP: ancestor -- no support shown

<AndyS> s/rootClaass -- 6/rootClass -- 6/

<HolgerK> w3c/data-shapes#786

holger: PR 787
… subset or equal to another property path
… (chatGPT suggestions)
… my preference valuesFromPath

<ajnelson-nist> valuesFromPath - seems a little incongruous with sh:equals not being sh:equalsPath

simonstey: hints at nodes on the path
… one of subsetof or other subset name

ajnelson-nist: conflict with path in name

mgberg: Is the intent a property path or inc node expressions?

<simonstey> +1 subsetof

holger: property path
… can use sh:in node-expr

<ajnelson-nist> +1 subsetOf

elianaP: list of options only posted 2 hours ago
… a bit early to decide

<DavidHabgood> +1 subsetOf

nicholascar: profiling
… resolved comment on one PR, doing the other now.
… next go through use cases to check the doc aligns

edmond: UI
… going though PR that was in draft since Dec'25.
… DASH integration into SHACL

Meeting tomorrow

w3c/data-shapes#787

<edmond> w3c/data-shapes#700

w3c/data-shapes#722

zkim, close item 4

General Business

nicholascar: reusable property shape but can it inherit message from the node space?

holgerK: no propagation