- From: Simon Steyskal <simon.steyskal@wu.ac.at>
- Date: Wed, 17 Apr 2019 18:41:49 +0200
- To: Felix Sasaki <felix@sasakiatcf.com>, public-shacl@w3.org
- Message-ID: <E1hGndY-0000DP-Dg@mimas.w3.org>
Hi!have you tried combining sh:xone with two sh:and constraints?e.g. something along the lines of:sh:xone ( sh:and ( ex:hasAddress sh:datatype xsd:string ex:addrType sh:hasValue "simple" ) sh:and ( ex:hasAddress sh:class ex:complexAddr ex:addrType sh:hasValue "comolex" ))(I'm on mobile right now so just pseudocode)br simon -------- Original message --------From: Felix Sasaki <felix@sasakiatcf.com> Date: 4/17/19 18:26 (GMT+01:00) To: public-shacl@w3.org Subject: Question on value based constraints HI all,I have a question on how to model alternative constraints based on literal values.Let's assume the two alternatives ways to express an address:ALTERNATIVE 1:ex:person1 ex:hasAddress "Street xzy plz 12345 ..."ex:person1 ex:addressType "simpleAddress".ALTERNATIVE 2:ex:person1 ex:hasAddress ex:someComplexAddress1 # object is an instance of class ex:complexAddressex:person1 ex:addressType "complexAddress".I want to define two alternative shapes for addresses: one is simple, i.e. the literal value "Street xzy plz 12345 ...", and one is complex, i.e. an instance of ex:complexAddress.How do I model the choice between the two address' shapes based on the values "simpleAddress" vs. "complexAddress"?Regards,Felix
Received on Wednesday, 17 April 2019 16:42:19 UTC