Page 806 - 2015 Security in Telecommunications and Information Technology
P. 806
5 Unleashing the potential of the Internet of Things
NOTE 2 – In a broad perspective, the IoT can be perceived as a vision with technological and societal
implications.
3.1.4 metadata [ITU-T M.3030]: Data that describes other data.
3.1.5 resource [b-IETF RFC 3986]: This specification does not limit the scope of what might be
a resource; rather, the term "resource" is used in a general sense for whatever might be identified by
a URI. Familiar examples include an electronic document, an image, a source of information with a
consistent purpose (e.g., "today's weather report for Los Angeles"), a service (e.g., an HTTP-to-
SMS gateway), and a collection of other resources. A resource is not necessarily accessible via the
Internet; e.g., human beings, corporations, and bound books in a library can also be resources.
Likewise, abstract concepts can be resources, such as the operators and operands of a mathematical
equation, the types of a relationship (e.g., "parent" or "employee"), or numeric values (e.g., zero,
one, and infinity).
3.1.6 server [b-W3C WACterms]: The role adopted by an application when it is supplying
resources.
3.1.7 service provider [ITU-T Y.2232]: An entity that provides services.
3.1.8 SOAP [b-W3C SOAP 1]: The formal set of conventions governing the format and
processing rules of a SOAP message. These conventions include the interactions among SOAP
nodes generating and accepting SOAP messages for the purpose of exchanging information along a
SOAP message path.
3.1.9 SOAP intermediary [b-W3C SOAP 1]: A SOAP intermediary is both a SOAP receiver
and a SOAP sender and is targetable from within a SOAP message. It processes the SOAP header
blocks targeted at it and acts to forward a SOAP message towards an ultimate SOAP receiver.
3.1.10 the World Wide Web (WWW, or simply web) [b-W3C webarch]: An information space
in which the items of interest, referred to as resources, are identified by global identifiers called
Uniform Resource Identifiers (URI).
3.1.11 thing [ITU-T Y.4000]: In the Internet of things, object of the physical world (physical
things) or of the information world (virtual things), which is capable of being identified and
integrated into the communication networks.
3.1.12 URI [b-IETF RFC 3986]: A URI is an identifier consisting of a sequence of characters
matching the syntax rule named <URI> in Section 3 of [b-IETF RFC 3986]. It enables uniform
identification of resources via a separately defined extensible set of naming schemes (Section 3.1 of
[b-IETF RFC 3986]). How that identification is accomplished, assigned, or enabled is delegated to
each scheme specification.
3.1.13 web of things [ITU-T Y.4400]: A way of realization of the IoT where (physical and
virtual) things are connected and controlled through the World Wide Web.
3.1.14 web resource [b-W3C WACterms]: A resource, identified by a URI.
3.1.15 web services [ITU-T Y.2232]: Web services is a service provided using web services
systems.
3.1.16 web services gateway (WSG) [ITU-T Y.2232]: A gateway which handles the web services
message between the WSP and WSR.
3.1.17 web services provider (WSP) [ITU-T Y.2232]: A service provider that exposes a
capability for use to create web services.
3.1.18 web services registry [ITU-T Y.2232]: An entity that stores web services information
(e.g., WSDL).
3.1.19 Web services requester (WSR) [ITU-T Y.2232]: Client software that makes use of the
services provided by a WSP.
792 Rec. ITU-T Y.4414/H.623 (11/2015)