Broken Links about data-models HOT 5 CLOSED

The version we are pushing of more reliable of @context is
http://smartdatamodels.org/context.jsonld

from data-models.

• https://github.com/smart-data-models/data-models/blob/master/context.jsonld is the versioned file held in the GitHub repository

• Since the GH-Pages branch for this project is master - https://smart-data-models.github.io/data-models/context.jsonld is the hosted version of the same file.

• GitHub's raw.githubusercontent.com domain is used to serve unprocessed versions of files stored in GitHub repositories, so https://raw.githubusercontent.com/smart-data-models/data-models/master/context.jsonld is a rendering of the same file.

• https://schema.lab.fiware.org/ld/context.jsonld is a completely different context file originally generated from deprecated FIWARE data models repo that Smart Data models is building on. It may be the case that the domain is now forwarding to one of the other locations defined above.

from data-models.

Which among these should be referred for FIWARE context.

https://smart-data-models.github.io/data-models/context.jsonld is probably the most stable URL, but personally I would host my own copy and refer to that:

• https://smart-data-models.github.io, https://raw.githubusercontent.com/smart-data-models and https://github.com/smart-data-models are all domains reliant on Microsoft ensuring that GitHub is available 24/7
• https://schema.lab.fiware.org requires that the FIWARE Foundation infrastructure is available 24/7

Neither of these are guaranteed.

Furthermore, changes could be made to these files at any moment (e.g. adding new attributes) which may conflict with your own custom @context file. Much better to copy the relevant sections instead and host them yourself.

from data-models.

The links(https://uri.fiware.org) referred within the context.jsonld are giving 404 error

According to the JSON-LD Spec :

a context is used to map terms to IRIs.

An IRI is not necessarily a URL - see here - it would be nice if the IRI resolved to a web page, but it is not essential.

Indeed, if you take the NGSI-LD Core @context

{
  "@context": {

    "ngsi-ld": "https://uri.etsi.org/ngsi-ld/",
    "geojson": "https://purl.org/geojson/vocab#",
    "id": "@id",
    "type": "@type",
...
    "@vocab": "https://uri.etsi.org/ngsi-ld/default-context/"
  }
}

You can see that any unresolved short-name for an attribute will be mapped onto the default context e.g.:

• xxx => https://uri.etsi.org/ngsi-ld/default-context/xxx

And that URL doesn't exist either.

from data-models.

Thank you for the clarification

from data-models.