Replies: 2 comments 2 replies
-
Comunica doesn't do any kind of coercion/reasoning (at the moment), and it also does not do any special conversions for schema.org. This seems to be confimed when looking at the raw parsing of the two files:
FYI, the JSON-LD context of schema.org (https redirects to http) uses |
Beta Was this translation helpful? Give feedback.
-
The Schema.org JSON-LD context probably contains a
Then one of the following will probably be needed:
|
Beta Was this translation helpful? Give feedback.
-
When querying JSON-LD documents, any Schema.org date field is coerced to a
schema:Date
automatically. For example aschema:dateCreated
value becomes aschema:Date
:When querying other serialization formats, however, this is not the case:
I’ve seen that for JSON-LD documents, Comunica fetches the Schema.org vocabulary and apparently uses that to coerce values. Should this be the case for other serializations, too?
It may also be interesting to note that both source documents use
https://schema.org
(nothttp://schema.org
) but the JSON-LD is returned as HTTP; I assume this is because Comunica redirects tohttp://schema.org
.Beta Was this translation helpful? Give feedback.
All reactions