valueType
Another idea which may help with NGSI-v2 interoperability. Now that we have defined objectType for Relationships, should we define valueType for Properties?
{
"id": "urn:ngsi-ld:Store:001",
"type": "Store",
"address": {
"type": "Property",
"value": {
"streetAddress": "Bornholmer Straße 65",
"addressRegion": "Berlin",
"addressLocality": "Prenzlauer Berg",
"postalCode": "10439"
},
"valueType": "PostalAddress"
},
"name": {
"type": "Property",
"value": "Bösebrücke Einkauf",
"valueType": "Text"
}
}
the alternative is:
"value": {
"@type": "PostalAddress",
"@value" : {
"streetAddress": "Main Street 65",
"addressRegion": "Metropolis",
"addressLocality": "Duck Village",
"postalCode": "42000" }
}
valueType would just defined as an @vocab, so User context includes:
{
@context: {
"schema": "http://schema.org/",
"Text": "schema:Text",
"PostalAddress "schema"PostalAddress"
}