ServiceURI is the identifier of an Entity into the Knowledge Base and thus also of all the Entity Instances. References are established via the so-called ServiceURI in the Knowledge Base to refer to: IoT Devices, Entity Instances, POI, etc.
Please note that the ServiceURI of a given data model / Device / city entity / knowledge base entity can be recovered from a number of tools: Data Inspector (from healthiness button, red/green), ServiceMap, SuperServiceMap, Dashboard Wizard (from healthiness button, red/green), IoT Directory.
In Snap4City, ServiceURI, also called SURI, is defined a Snap4City Entity/Service URI (also called in IoT Directory Device URI) into some Km4City Knowledge Base.
For example as: http://www.disit.org/km4city/resource/iot/orionUNIFI/DISIT/METRO759
ServiceURI is an URI identifier defined according to the standard: https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
If you put the SURI on a browser, and the SURI refers to a public entity, its definition appears on browser as in the figure aside, since it is compliant with the Linked Data standard. You can see how the entities are identified in terms of URIs.
Please note that:
- The identifiers of other HLT are not based on SURI, for example for:
- consult the Data Inspector on the platform to identify the corresponding shape to identify each kind of HLT. The identifiers are used by the