Closed amiika closed 2 years ago
Thanks for reporting this, the JSON-LD context is automatically generated from the UML class diagram, sure that quality has to be checked.
The JSON-LD has been regenerated and I can test it with valid JSON-LD:
{
"@id" : "http://mytest.com",
"@type": "http://www.w3.org/ns/locn#Address",
"@context": "https://semiceu.github.io/Core-Person-Vocabulary/releases/2.00/context/core-person-ap.jsonld",
"Address.administrativeUnitLevel1 (country)" : {
"@value": "France",
"@language": "fr"
}
}
that works with EasyRDF and RDF Blue Mix
Use case name
JSON-LD Context validation and examples
Please insert the status of the use case
No response
Use case creator
Miika Alonen
Stakeholders
Everyone using JSON-LD and SEMIC vocabularies
Problem statement
Current release of the JSON-LD Context is invalid. Missing type on a property. There is also multiple occurrences of @id where it should be string. Some property names (like "Address.administrativeUnitLevel1 (country)" also seems very odd.
Publishing non-functioning vocabulary (even if draft) is a big credibility problem.
Existing approaches
No response
Links
No response
Requirements
Create example JSON-LD documents and validation process for the JSON-LD context.
Related use cases
No response
Comments
No response