- From: Pierre-Antoine Champin via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Dec 2022 08:09:43 +0000
- To: public-dxwg-wg@w3.org
@jakubklimek strictly speaking `xsd:integer` is derived from `xsd:decimal` (see [spec](https://www.w3.org/TR/xmlschema11-2/#integer)), so having an `xsd:integer` where an `xsd:decimal` is perfectly legal semantically. OWL inference engines, for example, will not treat it as a contradiction. Now, SHACL and ShEX are only concerned with syntax, and a shape requiring `xsd:decimal` will indeed choke on an `xsd:integer` value... A pragmatic approach would be for such shape to allow `xsd:decimal` OR `xsd:integer` whenever the domain is `xsd:decimal`. Note that this is an incomplete workaround, because `xsd:decimal` has many more derived datatype that could semantically be used, but `xsd:integer` is probably by far the most used. I have added a comment (bcb5990) explaining this in the note below the definition of `dcat:spatialResolutionInMeters`. NB: this issue with `xsd:integer` is not specific to JSON-LD. The same problem exists with Turtle... -- GitHub Notification of comment by pchampin Please view or discuss this issue at https://github.com/w3c/dxwg/pull/1543#issuecomment-1350597102 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 December 2022 08:09:45 UTC