Open bobeal opened 1 month ago
I was working on those tutorials to improve the execution and resolve some issues. At the moment, I prefer to check the @context because I found some discrepancies.
Keep in mind that we are testing the tutorials not the functionality of the brokers.
I was working on those tutorials to improve the execution and resolve some issues. At the moment, I prefer to check the @context because I found some discrepancies.
Keep in mind that we are testing the tutorials not the functionality of the brokers.
The first two points of the PR are strictly about NGSI-LD compliance, nothing related with the brokers.
And you are testing the tutorials ... using context brokers. So it is a bit harsh to consider a broker is failing whereas it is just not using the same default version of the core context.
synced with last version on develop.
address
property (streetAddress
, ...) are not in ngsi-context.jsonld. thus, when they are created with this context, they are expanded using the default vocab from the core context (https://uri.etsi.org/ngsi-ld/default-context/streetAddress
and nothttps://schema.org/streetAddress
) and when compacting without specifying a context, they are "correctly" compacted (streetAddress
). See this link for a demo in the JSON-LD playground.https://schema.org/name
andhttps://uri.fiware.org/ns/dataModels#category
are respectively compacted toschema:name
andfiware:category
. See this link for a demo in the JSON-LD playground