Explore chapters and articles related to this topic
Semantic Technologies as Enabler
Published in Sarika Jain, Understanding Semantics-Based Decision Support, 2021
The foundations of the semantic technologies stack are web technologies. We rely on all the technologies of the World Wide Web. Everything on the web (whether abstract or physical), from living through non-living to web pages, is uniquely identified by a string of characters called the Uniform Resource Identifier (URI). Unicode and URI sit on the very bottom of Figure 2.1 and form the base of semantic technologies. Unicode gives a computer number to every existing character of every written language. URI, the naming convention, has two specializations: Uniform Resource Locator (URL; a means of locating the resource on the network) and Uniform Resource Name (URN; a persistent, location-independent identifier of a resource). Every URL and every URN is a URI. A URI is sufficient to retrieve a complete description of the resource on the web. A machine can unambiguously fetch RDF data (which is machine understandable), and a human can get the HTML version (which is human understandable when displayed by a browser). The International Resource Identifier (IRI) is the international variant of the URI. As compared to URIs that use only the ASCII character set, IRIs use the ISO/Unicode universal character set [Berners-Lee et al. 2001, Shadbolt et al. 2006]. IRIs thus allow non-Latin characters like Arabic and Japanese.
IoT and edge computing in the construction site
Published in Pieter Pauwels, Kris McGlinn, Buildings and Semantics, 2023
A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. A URI can be further classified as a locator (URL), a name (URN), or both. A more commonly known version of a URI is a Uniform Resource Locator (URL), which in addition to identifying a resource, provides a means of locating the resource by describing its primary access mechanism (e.g., its network “location”). A ucode is an identifier to be stored in many types of tags (RFID tags, optical code, infrared markers, and even sound sources), specified by the Ubiquitous ID Centre. Its use is to identify objects and places where existing standards do not fit the application needs. Applications that use ucode take advantage of the Internet extensively.
Hypertext Transfer Protocol
Published in Giovanni Bartolomeo, Tatiana Kováčiková, Identification and Management of Distributed Data: NGN, Content-Centric Networks and the Web, 2016
Giovanni Bartolomeo, Tatiana Kováčiková
The web uses global identifiers to allow a client to find and access a specific resource. Historically two different schemas have been created, the Uniform Resource Name (URN; RFC 1737 [Sollins and Masinter 1994] and RFC 2141 [Moats 1997]) and the Uniform Resource Locator (URL; RFC 1738 [Berners-Lee, Masinter, and McCahill 1994] and RFC 1808 [Fielding 1995]). The aim of a URN is to provide persistent and immutable names for a resource, independent of where the resource is located. In contrast, a URL provides a (not necessarily persistent) address where the resource can be accessed.
A Blockchain Based Decentralized Identifiers for Entity Authentication in Electronic Health Records
Published in Cogent Engineering, 2022
Manoj T, Krishnamoorthi Makkithaya, Narendra V G
Decentralized Identifiers (DIDs) are a new kind of globally unique, portable and cryptographically verifiable identifier that does not rely on any centralized authority and can never be taken away (Hughes et al., 2019). The DIDs are characterized by four core properties: permanent/persistent, resolvable, decentralized, and verifiable cryptographically. The DIDs can be assigned to any entity such as human, organization or thing. Currently, efforts are done by W3C DID working group for standardizing the DIDs. The format of DID is somewhat similar to the Uniform Resource Name (URN) so that it can be adapted to work with multiple blockchain. The DID is composed of three components, namely Schema, DID method and DID method specification, as shown in Figure 1.