Cross-industry semantic interoperability: Glossary
June 21, 2017
"When we define a word we are merely inviting others to use it as we would like it to be used; that the purpose of definition is to focus argument upo...
“When we define a word we are merely inviting others to use it as we would like it to be used; that the purpose of definition is to focus argument upon fact, and that the proper result of a good definition is to transform argument over terms into disagreements about fact, and thus open arguments to further inquiry.”
– C. Wright Mills
This glossary describes terms utilized in the article series, “Cross-industry semantic interoperability,” including object classes, their relationships, and containments.
Navigate to other parts of the series here:
- Cross-industry semantic interoperability, part one
- Cross-industry semantic interoperability, part two: Application-layer standards and open-source initiatives
- Cross-industry semantic interoperability, part three: The role of a top-level ontology
- Cross-industry semantic interoperability, part four: The intersection of business and device ontologies
- Cross-industry semantic interoperability, part five: Towards a common data format and API
For each object class, the glossary incorporates the following formatting:
- Alias [data model using alias] – Description
- Alias [data model using alias] – Description
(e.g., door lock, fire alarm, sprinkler)
A top-level object class.
(e.g., equipment, inventory)
- Asset [ARTS ODM] – A fixture or equipment (including electronic equipment) used by retailers to support their business operations.
- Resource [O-DEF] – A source or supply from which benefit is produced. Typically, resources are materials, energy, services, knowledge, or other assets that are transformed, used, or consumed to produce bene-fit and in the process may be consumed or made unavailable.
Note: A resource as defined here is not the same as a resource as defined in the W3C RDF standard.
Attribute (Property, Tag)
A data characteristic of an object class.
(e.g., birth date)
- Attribute [GS1] – A piece of information associated with an entity. An attribute may be recognized if one can construct a sentence of the following form: “The [attribute name] of [entity] is [attribute value].”
- Property [O-DEF] – A characteristic applicable to all members of an object class.
- Property [schema.org] – A property, used to indicate attributes and relationships of some Thing; equivalent to rdf:Property.
- Tag [Project Haystack] – A name/value pair applied to an entity. A tag defines a fact or attribute about an entity. For example, if we apply the site tag to an entity, then we are declaring that the entity represents a building.
A type of system that eliminates the need for human intervention to complete a task by incorporating a collection of sensors, actuators, controllers, communication networks, and user-interface devices that interpret, process, and distribute data.
(e.g., Building Automation System, Home Automation System, Warehouse Automation System)
A system of digital message formats and rules for exchanging messages in or between computing systems (e.g., in telecommunications). Protocols may include signaling, authentication, error detection capabilities, and/or correction capabilities. Each message has an exact meaning intended to provoke a defined response by the receiver. The nature of the communication, the actual data exchanged, and any state-dependent behaviors are defined by a technical specification or communication protocol standard.
(e.g., HTTP, HTTP Secure (HTTPS), Simple Mail Transfer Protocol (SMTP), Constrained Application Protocol (CoAP))
A chip, an expansion card, or a stand-alone device that interfaces with a peripheral device.
An identifiable unit of data in a dataset.
(e.g., a database field, an RDF triple, an XML attribute or atomic element, a program variable or array element, or a JSON value)
- Data Element [O-DEF] – A unit of data that is considered in context to be indivisible. [ISO 2382]. Data elements can be stored in databases, exchanged in messages, and manipulated by software programs. A data element can be of any size; for example, a bit containing a binary value, or a large file of unstructured data.
- Data Element [GS1] – A unit of data for which the identification, description and value representation have been specified.
An individual instance of a data element.
A type of process for reducing data to a canonical form to facilitate interoperability. For instance, data element normalization is the process of organizing data elements within a data store to minimize redundancy and dependency.
(e.g., database, dataset, flat file, firmware)
Data Type (Kind)
A classification identifying one of various types of data that determines possible values, processes that can be performed, the meaning of the data, and the way values can be stored.
(e.g., Boolean, number, string, temperature, pressure, speed, electric power, currency, duration)
- Kind [Project Haystack] – A permitted value type of a tag.
A type of information model that comprises a collection of data elements represented in tabular form. Each column in a dataset may represent a particular variable. Each row in a dataset may correspond to a given object. A dataset may comprise data elements for one or more objects, corresponding to the number of rows.
(e.g., database table, file, array)
An element or term that has the function of describing, identifying, or indexing, in particular.
A type of equipment made for a particular purpose, especially a mechanical or electrical one.
(e.g., sensor, actuator, thermostat, smartphone, appliance)
A realm of administrative autonomy, authority, or control.
(e.g., knowledge domain, network domain, web domain)
A top-level object class.
(e.g., home, building, store, hospital, factory, city)
- Environment [O-DEF] – The natural or man-made surroundings of someone or something.
- Weather [Project Haystack]
(e.g., AHU, boiler, chiller, chiller plant)
- Equipment [Project Haystack] – A physical asset or logical grouping of assets associated with a site.
A top-level object class.
(e.g., time series event, concert)
- Event [O-DEF) – An occurrence happening at a determinable time or times, with or without the participation of human agents.
- Event [schema.org] – An event happening at a certain time and location, such as a concert, lecture, or festival. Repeated events may be structured as separate Event objects.
A type of value for naming any object with an unambiguous persistent name within a namespace.
(e.g., human-generated name, machine-generated UUID)
(e.g., meta model, metadata model)
- Information-Set [O-DEF] – A collection of information, whether in physical form (such as a book), machine-readable form (such as a file on disc), or human-based form (such as a person’s recollection or an oral tradition).
Location (Place, Site, Zone)
A top-level object class.
(e.g., campus, building, floor, city)
- Location [O-DEF] – A place or position. Typically, locations provide geographic context that characterizes a data element.
- Place [schema.org] – Entities that have a somewhat fixed, physical extension.
- Place [GS1] – Entities that have a somewhat fixed, physical location.
- Site [Project Haystack] – A “Site” entity models a single facility. A good rule of thumb is to model any building with its own street address as its own site. For example, a campus is better modeled with each building as a site, versus treating the entire campus as one site.
- Zone [Project Haystack) – A conditioned space in a building
Metadata (Data Semantics)
A type of dataset that comprises data about data.
Object (Entity, Record, Row)
A data representation of a unique instance of an object class. Attributes of an object can be stored as data elements within a data store. Every object of an object class has a minimal set of uniquely identifying attributes, including a unique identifier.
(e.g., Floor #4, Order #1234)
- Entity [Project Haystack] – An abstraction for some physical object in the real world. Entities include sites, equipment, sensor points, weather stations, etc. In software systems, an entity might be a modeled as a record in a database, an object in a building automation system, or maybe just a row in a CSV file.
Object Class (Class, Entity Class, Table, Type)
A category of like things or objects which are each recognized as being capable of an independent existence and which can be uniquely identified. Non-limiting examples of an entity include physical objects such as houses or cars, events such as house sales or car services, concepts such as customer transactions or orders, personal information such as contacts, messages, events, and tasks, and object schema including entities, reflectively.
(e.g., Floor, Order)
- Object Class [O-DEF] – A set of ideas, abstractions, or things in the real world that are identified with explicit boundaries and meaning and whose properties and behavior follow the same rules. An object class is similar to an entity used by the data modeling community. An example object class is person. Any attribute applicable to an object class is a valid attribute for all instances of this object class.
- Class [GS1] – A class describes a set of objects that share the same attributes, relationships and semantics.
- Type [schema.org] – Equivalent to rdfs:Class.
(e.g., business, institution, association)
- Organization [GS1] – any legal or physical entity involved at any point in any supply chain and upon which there is a need to retrieve predefined information. An Organization is uniquely identified by a Global Location Number (GLN).
- Organization [schema.org] – An organization such as a school, NGO, corporation, club, etc.
- Enterprise [O-DEF] – A collection of people organized to achieve a common set of goals.
(e.g., S-MART, John Smith)
- Party [GS1] – A Party (or) Location is any legal or physical entity involved at any point in any supply chain and upon which there is a need to retrieve predefined information. A Party is uniquely identified by a Global Location Number (GLN).
- Party [ARTS]
A type of party that represents a human being.
(e.g., John Smith)
- Person [O-DEF] – A human being, whether man, woman, or child.
- Person [schema.org] – A person (alive, dead, undead, or fictional).
An attribute of a sensor or actuator that represents a value within a system. For example, an electric meter might have two points: Kw value and KwH value. A temperature sensor might have one point: current temperature value.
(e.g., analog input, discrete input, analog output, discrete output)
- Point [Project Haystack] – Points are typically a digital or analog sensor or actuator entity (sometimes called hard points). Points can also represent a configuration value such as a setpoint or schedule log (sometimes called soft points). Point entities are tagged with the point tag. All points are further classified as sensors, commands, or setpoints
- Product [O-DEF] – The result of a process. Product [schema.org] – Any offered product or service.
- Product [GS1] – Any item (product or service) upon which there is a need to retrieve pre-defined information and that may be priced, or ordered, or invoiced at any point in any supply chain.
- Item [ARTS ODM] – A tangible product or intangible service that may be offered for sale and/or may be consumed by the retailer as supplies.
- Process [O-DEF] – A series of actions, changes, or functions bringing about a result.
- Action [schema.org] – An action performed by a direct agent and indirect participants upon a direct object. Optionally happens at a location with the help of an inanimate instrument. The execution of the action may produce a result. Specific action sub-type documentation specifies the exact expectation of each argument/role.
A top-level object class comprising a many-to-many association between two objects or classes
(e.g., Party Role, Order Item, Product Component)
(e.g., customer, parent, dishwasher)
- Role [O-DEF] – A function that can be performed by an object in a particular context.
- Role [schema.org] – A role can be used to associate a person, as a “member” role, to a sports team or an “actor” role to a movie.
- PartyRole [ARTS ODM]
Rule (Law, Condition)
(e.g., event trigger)
- Law-Rule [O-DEF] – A law (natural or man-made) or policy that governs a process.
A type of device that can provide ubiquitous, always on (real-time) observation capabilities to supplement human senses and detect changes in temperature, humidity, motion, moisture, location, weight and other important physical phenomena (or state).
(e.g., temperature sensor)
Smart Device (Connected Device)
A smart device is an electronic device, generally connected to other devices or networks via different wireless protocols such as Bluetooth, NFC, Wi-Fi, 3G, etc., that can operate to some extent interactively and autonomously. Several notable types of smart devices are smartphones, phablets and tablets, smartwatches, smart bands and smart key chains. The term can also refer to a device that exhibits some properties of ubiquitous computing, including—although not necessarily—artificial intelligence.
Smart devices can be designed to support a variety of form factors, a range of properties pertaining to ubiquitous computing and to be used in three main system environments: physical world, human-centered environments and distributed computing environments.
A top-level object class that comprises a regularly interacting or interdependent group of objects forming a unified whole. Every system is delineated by its spatial and temporal boundaries, surrounded and influenced by its environment, described by its structure and purpose and expressed in its processes.
(e.g., automation system, weather system, domain name system)
A type of dataset that comprises a series of data points indexed in time order.
(e.g., order, shipment, payment)
- Transaction [ARTS ODM] – A complete, self-contained record of business activity
Unit of Measurement (Measurement Unit, Unit)
(e.g., degrees Celsius, rotations per minute)