Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

confusion about schema.org datatypes #176

Open
VladimirAlexiev opened this issue Aug 11, 2021 · 2 comments
Open

confusion about schema.org datatypes #176

VladimirAlexiev opened this issue Aug 11, 2021 · 2 comments

Comments

@VladimirAlexiev
Copy link

schemaorg/schemaorg#1781 argues that schema.org datatypes should never be used, in favor of XSD datatypes.

https://github.com/ESIPFed/science-on-schema.org/blob/master/validation/shapegraphs/soso_common_v1.2.2.ttl shows confusion about such datatypes, using eg sh:class SO:Number.
See schemaorg/schemaorg#1781 (comment) for details.

@smrgeoinfo
Copy link
Contributor

smrgeoinfo commented Sep 23, 2021

so the recommendation would be that that shape should perhaps look like this:

sh:or (
        [    sh:nodeKind sh:Literal ;  ]
        [  sh:datatype xsd:decimal;  ]
    );

SHACL spec seems to indicate a Literal is a value with a declared datatype that could be any rdf datatype (iri, URL, number string, etc.), so isn't 'or sh:datatype xsd:decimal' redundant?

@VladimirAlexiev
Copy link
Author

@smrgeoinfo

  • Your example means the same as merely sh:nodeKind sh:Literal because sh:datatype xsd:decimal is a more specialized condition (all decimals are also Literals)
  • I think that SO:Dataset-version should be xsd:string only, because versions are identifiers not numbers. Version 2.0 may look like a number to someone... until 2.0.1 is released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants