You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Dataset 'types' and 'keywords' properties are typed as sdo:keywords which are defined (by schema.org) as essentially free text fields with the suggestion of comma separated values. The values serialized in the files however include more complex structures (json array of json objects).
The text was updated successfully, but these errors were encountered:
Following up on this point, and considering that the new release will test the use of multiple context files, I've removed the aliasing for these two properties in the schema.org context and added them in the OBO Foundry context file.
It terms of schema.org domain and ranges, it might be useful to point out the flexible approach taken about conformance (see more details at the schema.org data model description).
I believe the upcoming v0.4 release should fix this, although I'm not sure that the example queries cover these specific properties. Leaving the issue open until I've had a chance to verify this.
The Dataset 'types' and 'keywords' properties are typed as
sdo:keywords
which are defined (by schema.org) as essentially free text fields with the suggestion of comma separated values. The values serialized in the files however include more complex structures (json array of json objects).The text was updated successfully, but these errors were encountered: