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

shapes-ISSUE-194 (valueStem): stems in value sets

From: RDF Data Shapes Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Tue, 08 Nov 2016 13:39:59 +0000
To: public-data-shapes-wg@w3.org
Message-Id: <E1c46d5-0007AL-Ow@nash.w3.org>
shapes-ISSUE-194 (valueStem): stems in value sets

http://www.w3.org/2014/data-shapes/track/issues/194

Raised by: Eric Prud'hommeaux
On product: 

The current SHACL definition for stem (see 4.5.4 sh:stem <http://w3c.github.io/data-shapes/shacl/#StemConstraintComponent>) treats them as a Parameter while ShEx uses them in value sets (see 4.4.6 Values Constraint <https://shexspec.github.io/spec/#values>). The SHACL definition use doesn't offer much value over an XSD pattern. It's pretty common for clinical value sets to require any value with starting with one of a number of base IRIs (e.g. terminologies like LOINC, SNOMED, CPT, ...).

Another diff is that ShEx value sets have exclusions which can in turn be stems (see 10 Value Sets <http://shex.io/primer/#h-value-sets>)
Received on Tuesday, 8 November 2016 13:40:05 UTC

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