hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.4.3 Specializing tasks | SAREF extensions may define a taxonomy of tasks using skos:broader and skos:narrower. The identifier, the label, and the comment of an instance of saref:Task should explicit its position in the taxonomy of tasks. EXAMPLE: ex:AmbianceLighting and ex:SecurityLighting are specializations of ex:Lighting. ex:SecurityLightin... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.4.4 Categorizing tasks | SAREF extensions and applications may define categories of tasks by creating sub-classes of saref:Task. The identifier, the label, and the comment of a sub-class of saref:Task should explicit its position in the hierarchy of task classes. The identifier should end with "Task". EXAMPLE: The class ex:SafetyTask groups ta... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.4.5 Specializing OPs and DPs related to tasks | SAREF extensions and applications shall not define sub-properties of the following properties: • saref:accomplishes • saref:isAccomplishedBy |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.5 SAREF pattern for commodities | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.5.1 Introduction | Class saref:Commodity represents marketable items which may be supplied without qualitative differentiation. Commodities may be consumed, produced, or stored, by some feature of interest or device. Figure 4 illustrates the main classes and properties in the SAREF Core patterns for Commodities. Figure 4: SAREF Core patt... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.5.2 Creating commodities | SAREF extensions should reuse or create specific instances of the class saref:Commodity. The identifier and the label of an instance of commodity should start with a capital letter and should not contain "Commodity". The comment may mention "commodity". EXAMPLE: ex:Electricity a saref:Commodity ; rdfs:label "Electricit... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.5.3 Specializing commodities | SAREF extensions may define a taxonomy of commodities using skos:broader and skos:narrower. The identifier, the label, and the comment of an instance of saref:Commodity should explicit its position in the taxonomy of commodities. EXAMPLE: ex:Propane is a specialization of ex:NaturalGas. ex:Propane a saref:Commodity ; s... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.5.4 Categorizing commodities | SAREF extensions and applications may define categories of commodities by creating sub-classes of saref:Commodity. The identifier, the label, and the comment of a sub-class of saref:Commodity should explicit its position in the hierarchy of commodity classes. The identifier should end with "Commodity". EXAMPLE: The cla... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.5.5 Specializing OPs and DPs related to commodities | SAREF extensions and applications shall not define sub-properties of the following properties: • saref:consumes • saref:isConsumedBy • saref:produces • saref:isProducedBy • saref:stores • saref:isStoredBy ETSI ETSI TS 103 548 V1.2.1 (2024-01) 18 |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.6 SAREF pattern for properties | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.6.1 Introduction | In SAREF, properties refer to the identifiable qualities of features of interest that can be acted upon by devices, such as observed or controlled. While properties can apply to different features of interest, properties of interest are specific to a feature of interest. Property values describe the value for a propert... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.6.2 Properties | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.6.2.1 Creating properties | SAREF extensions should create instances of the class saref:Property, such that they can be reused in different SAREF applications. SAREF applications may also create specific instances of the class saref:Property. The identifier and the label of an instance of property should not contain "property", and its comment ma... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.6.2.2 Specializing properties | SAREF extensions may define a taxonomy of properties using skos:broader and skos:narrower. The identifier, the label, and the comment of an instance of saref:Property should explicit its position in the taxonomy of properties. NOTE: Depending on the use case, the property can explicit the physical dimension its values ... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.6.2.3 Categorizing properties | SAREF extensions and applications may define categories of properties by creating sub-classes of saref:Property. The identifier, the label, and the comment of a sub-class of saref:Property should explicit its position in the hierarchy of property classes. The identifier, and the label of a property class should end wit... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.6.3 Properties of interest | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.6.3.1 Creating properties of interest | SAREF extensions should not create specific instances of the class saref:PropertyOfInterest, as they are meant to be specific to an application. The only exceptions to this provision are if the associated feature of interest is intended to be used by most applications of the SAREF extension. Given a property of interes... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.6.3.2 Categorizing properties of interest | SAREF extensions should not define sub-classes of saref:PropertyOfInterest, as this would duplicate information already part of the taxonomy of properties. |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.6.4 Creating or categorizing property values | SAREF extensions may create specific instances of the class saref:PropertyValue, only if they are used as the object of saref:hasPropertyValue. SAREF extensions should not define sub-classes of saref:PropertyValue, as this would duplicate information already part of the taxonomy of properties. ETSI ETSI TS 103 548 V1.2... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.6.5 Specializing OPs and DPs related to properties | SAREF extensions and applications shall not define sub-properties of the following properties: • saref:hasProperty • saref:isPropertyOf • saref:hasPropertyOfInterest • saref:isPropertyOfInterestOf • saref:hasPropertyKind • saref:hasPropertyValue • saref:isValueOfProperty • saref:hasValue • saref:isMeasuredIn NOTE: In s... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.7 SAREF pattern for states | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.7.1 Introduction | In SAREF, states refer to the identifiable conditions that features of interest are or may be in, and that can be acted upon by devices, such as observed and controlled. While states can apply to different features of interest, states of interest are specific to a feature of interest. Figure 6 illustrates the main clas... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.7.2 States | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.7.2.1 Creating states | SAREF extensions should create instances of the class saref:State, such that they can be reused in different SAREF applications. SAREF applications may also create specific instances of the class saref:State. The identifier and the label of an instance of state should not contain "state" and its comment may mention "st... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.7.2.2 Specializing states | SAREF extensions may define a taxonomy of states using skos:broader and skos:narrower. The identifier, the label, and the comment of an instance of saref:State should explicit its position in the taxonomy of states. NOTE: Depending on the use case, the state can explicit the physical dimension of the property it relate... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.7.2.3 Categorizing states | SAREF extensions and applications may define categories of states by creating sub-classes of saref:State. The identifier, the label, and the comment of a sub-class of saref:State should explicit its position in the hierarchy of state classes. The identifier, and the label of a state class should end with "State", and i... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.7.3 States of interest | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.7.3.1 Creating states of interest | SAREF extensions should not create specific instances of the class saref:StateOfInterest, as they are meant to be specific to an application. The only exceptions to this provision are if the associated feature of interest is intended to be used by most applications of the SAREF extension. Given a state of interest belo... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.7.3.2 Categorizing states of interest | SAREF extensions should not define sub-classes of saref:StateOfInterest, as this would duplicate information already part of the taxonomy of states. |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.7.4 Specializing OPs and DPs related to states | SAREF extensions and applications shall not define sub-properties of the following properties: • saref:hasState • saref:isStateOf • saref:hasStateOfInterest • saref:isStateOfInterestOf • saref:hasStateKind NOTE: In some SAREF extensions or application, it may be specified that features of interest of a specific categor... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.8 SAREF pattern for functions | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.8.1 Introduction | In SAREF, functions are logical groups of commands that devices support to accomplish their tasks. Function can act upon (OP saref:actsUpon and its sub-properties) features, properties or states. While functions are independent of any devices, functions of interest are functions actually supported by a device. Figure 7... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.8.2 Functions | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.8.2.1 Creating functions | SAREF extensions should create instances of the class saref:Function, such that they can be reused in different SAREF applications. SAREF applications may also create specific instances of the class saref:Function. The identifier and the label of an instance of function should end with "Function" and its comment may me... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.8.2.2 Specializing functions | SAREF extensions may define a taxonomy of functions using skos:broader and skos:narrower. The identifier, the label, and the comment of an instance of saref:Function should explicit its position in the taxonomy of functions. NOTE: The set of functions is specialized down the taxonomy of functions. The observed or contr... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.8.2.3 Categorizing functions | SAREF extensions and applications may define categories of functions by creating sub-classes of saref:Function. The identifier, the label, and the comment of a sub-class of saref:Function should explicit its position in the hierarchy of function classes. The identifier, and the label of a function class should end with... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.8.3 Functions of interest | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.8.3.1 Creating functions of interest | SAREF extensions should not create specific instances of the class saref:FunctionOfInterest, as they are meant to be specific to an application. The only exceptions to this provision are if the associated device is intended to be used by most applications of the SAREF extension. Given a function of interest belongs to ... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.8.3.2 Categorizing functions of interest | SAREF extensions should not define sub-classes of saref:FunctionOfInterest, as this would duplicate information already part of the taxonomy of functions. ETSI ETSI TS 103 548 V1.2.1 (2024-01) 25 |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.8.4 Specializing OPs and DPs related to functions | SAREF extensions and applications shall not define sub-properties of the following properties: • saref:hasFunction • saref:isFunctionOf • saref:hasFunctionOfInterest • saref:isFunctionOfInterestOf • saref:hasFunctionKind |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.9 SAREF pattern for commands | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.9.1 Introduction | In SAREF, commands represent the lowest-level directives a device supports and exposes to some network. Commands can act upon (OP saref:actsUpon and its sub-properties) features, properties, or states. While commands are independent of any function, commands of interest are commands actually supported by a function of ... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.9.2 Commands | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.9.2.1 Creating commands | SAREF extensions should create instances of the class saref:Command, such that they can be reused in different SAREF applications. SAREF applications may also create specific instances of the class saref:Command. ETSI ETSI TS 103 548 V1.2.1 (2024-01) 26 The identifier and the label of an instance of command should end ... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.9.2.2 Specializing commands | SAREF extensions may define a taxonomy of commands using skos:broader and skos:narrower. The identifier, the label, and the comment of an instance of saref:Command should explicit its position in the taxonomy of commands. NOTE: The set of commands is specialized down the taxonomy of functions. The observed or controlle... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.9.2.3 Categorizing commands | SAREF extensions and applications may define categories of commands by creating sub-classes of saref:Command. The identifier, the label and the comment of a sub-class of saref:Command should explicit its position in the hierarchy of function classes. The identifier, and the label of a command class should end with "Com... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.9.3 Commands of interest | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.9.3.1 Creating commands of interest | SAREF extensions should not create specific instances of the class saref:CommandOfInterest, as they are meant to be specific to an application. The only exception to this provision is if the associated function of interest is intended to be used by most applications of the SAREF extension. Given a command of interest b... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.9.3.2 Categorizing commands of interest | SAREF extensions should not define sub-classes of saref:CommandOfInterest, as this would duplicate information already part of the taxonomy of commands. ETSI ETSI TS 103 548 V1.2.1 (2024-01) 27 |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.9.4 Specializing OPs and DPs related to commands | SAREF extensions and applications shall not define sub-properties of the following properties: • saref:hasCommand • saref:isCommandOf • saref:hasMandatoryCommand • saref:hasOptionalCommand • saref:hasCommandOfInterest • saref:isCommandOfInterestOf • saref:hasCommandKind SAREF extensions and applications may define sub-... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.10 SAREF pattern for services and operations | A saref:Service is a digital representation of a function in a network, making it discoverable, registerable and remotely controllable in the network. A saref:Operation is the means of a service to communicate in a procedure-type manner over the network (i.e. transmit data to/from other devices). It is the -machine int... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.11 SAREF pattern for procedure executions | A saref:ProcedureExecution represents the act of carrying out a procedure. SAREF Core defines four sub-classes of saref:ProcedureExecution: • saref:CommandExecution describes the execution of a command. • saref:OperationExecution describes the execution of an operation in a network: the-machine interpretable- descripti... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 5.12 SAREF pattern for profiles | A device in SAREF can be characterized by profiles. A saref:Profile describes the money earned (negative values) or paid (positive values) for the use (production or consumption) of a commodity by a device in a certain context. Figure 11 illustrates the main classes and properties in the SAREF Core patterns for Profile... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.1 Ontology and semantics | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.1.1 Introduction | The present clause is the technical specification of SAREF4SYST, a generic extension of ETSI TS 103 264 [1] SAREF to represent the topology of systems and how they are connected or interact. ETSI ETSI TS 103 548 V1.2.1 (2024-01) 30 SAREF4SYST defines Systems, Connections between systems, and Connection Points at which ... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.1.2 Application example 1: Smart Energy | The present clause illustrates how SAREF4SYST can be used to homogeneously represent knowledge that is relevant for use cases in the Smart Energy domain: • Electric power systems can exchange electricity with other electric power systems. The electric energy can flow both ways in some cases (from the Public Grid to a P... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.1.3 Application example 2: Smart Building | The present clause illustrates how SAREF4SYST can be used to homogeneously represent knowledge that is relevant for use cases in the Smart Building domain: • Buildings, Storeys, Spaces, are different sub-types of Zones. Zones can contain sub-zones. Zones can be adjacent or intersect with other zones. • Two zones may sh... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.1.4 Namespaces | In addition to prefixes and namespaces defined in Table 1, clause 5 uses those in Table 2. Table 2: Prefixes and namespaces used in clause 5 Prefix Namespace s4syst-ex https://saref.etsi.org/saref4syst/v1.1.2/example/example/ ETSI ETSI TS 103 548 V1.2.1 (2024-01) 31 |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.2 Core Ontology | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.2.1 General overview | A graphical overview of the SAREF4SYST ontology is provided in Figure 12. Four pairs of properties are inverse one of the other; the property s4syst:connectedTo is symmetric, and properties s4syst:hasSubSystem and s4syst:hasSubSystem are transitive. Clauses 6.2.2 to 6.2.4 describe the different parts of the SAREF4SYST ... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.2.2 Systems and sub-systems | A s4syst:System, is defined as a part of the universe that is virtually isolated from the environment. NOTE: The system properties are typically state variables (e.g. consumed or stored energy, agent population, temperature, volume, humidity). Figure 13 illustrates classes and properties that can be used to define conn... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.2.3 Connections between systems | A connection between two s4syst:Systems, modelled by s4syst:connectedTo, describes the potential interactions between connected s4syst:Systems. A connection can be qualified using class s4syst:Connection. EXAMPLE 1: One can associate a s4syst:Connection with properties (saref:Property) that describe the interactions be... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.2.4 Connection Points of systems | A s4syst:System connects to other s4syst:Systems at connection points. A connection point belongs to one and only one s4syst:System, and can be described using the class s4syst:ConnectionPoint. Figure 15 illustrates the classes and the properties that can be used to describe connection points of a s4syst:System. EXAMPL... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.3 Pattern application to verticals | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.3.1 Introduction | Applications of the SAREF4SYST pattern are subsets of ontologies that define sub-classes and/or sub-properties of the classes and properties defined in clause 6. SAREF or SAREF extensions should contain applications of the SAREF4SYST pattern. Clauses 6.3.2 to 6.3.4 define how such applications are made. |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.3.2 Systems and sub-systems | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.3.2.1 Sub-classes of s4syst:System | A specialization of the SAREF4SYST pattern may define a sub-class of the s4syst:System class. If defined, it shall have an English-tagged label (rdfs:label) ending with "System". The local name of its IRI shall be a camel case form of its English-tagged label. ETSI ETSI TS 103 548 V1.2.1 (2024-01) 37 EXAMPLE: s4syst-ex... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.3.2.2 Sub-properties of s4syst:hasSubSystem and s4syst:subSystemOf | A specialization of the SAREF4SYST pattern may define a sub-property of the s4syst:hasSubSystem property or the s4syst:subSystemOf property. If defined, it shall have an English-tagged label (rdfs:label), and the local name of its IRI shall be a mixed case form of its English-tagged label. The label of the sub-property... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.3.2.3 Sub-properties of s4syst:connectedTo | A specialization of the SAREF4SYST pattern may define a sub-property of the s4syst:connectedTo property. If defined, it shall have an English-tagged label (rdfs:label), and the local name of its IRI shall be a mixed case form of its English-tagged label. EXAMPLE 1: s4syst-ex:exchangesElectricityWith has English-tagged ... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.3.3 Connections between systems | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.3.3.1 Sub-classes of s4syst:Connection | A specialization of the SAREF4SYST pattern may define a sub-class of the s4syst:Connection class. If defined, it shall have an English-tagged label (rdfs:label) ending with "Connection". The local name of its IRI shall be a camel case form of its English-tagged label. EXAMPLE 1: s4syst-ex:ThreePhasePowerBusConnection h... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.3.3.2 Sub-properties of s4syst:connectedThrough | A specialization of the SAREF4SYST pattern may define a sub-property of the s4syst:connectedThrough property. If defined, it shall have an English-tagged label (rdfs:label), and the local name of its IRI shall be a mixed case form of its English-tagged label. The label of the sub-property should use the same morpho-syn... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.3.3.3 Sub-properties of s4syst:connectsSystem | A specialization of the SAREF4SYST pattern may define a sub-property of the s4syst:connectsSystem property. If defined, it shall have an English-tagged label (rdfs:label), and the local name of its IRI shall be a mixed case form of its English-tagged label. The label of the sub-property should use the same morpho-synta... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.3.4 Connection Points of systems | |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.3.4.1 Sub-classes of s4syst:ConnectionPoint | A specialization of the SAREF4SYST pattern may define a sub-class of the s4syst:ConnectionPoint class. If defined, it shall have an English-tagged label (rdfs:label) ending with "Connection Point". The local name of its IRI shall be a camel case form of its English-tagged label. EXAMPLE 1: s4syst-ex:ThreePhaseConnectio... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.3.4.2 Sub-properties of s4syst:connectionPointOf | A specialization of the SAREF4SYST pattern may define a sub-property of the s4syst:connectionPointOf property. If defined, it shall have an English-tagged label (rdfs:label), and the local name of its IRI shall be a mixed case form of its English-tagged label. The label of the sub-property should use the same morpho-sy... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.3.4.3 Sub-properties of s4syst:connectsAt | A specialization of the SAREF4SYST pattern may define a sub-property of the s4syst:connectsAt property. If defined, it shall have an English-tagged label (rdfs:label), and the local name of its IRI shall be a mixed case form of its English-tagged label. The label of the sub-property should use the same morpho-syntactic... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.3.4.4 Sub-properties of s4syst:connectsSystemThrough | A specialization of the SAREF4SYST pattern may define a sub-property of the s4syst:connectsSystemThrough property. If defined, it shall have an English-tagged label (rdfs:label), and the local name of its IRI shall be a mixed case form of its English-tagged label. The label of the sub-property should use the same morph... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.3.4.5 Sub-properties of s4syst:connectsSystemAt | A specialization of the SAREF4SYST pattern may define a sub-property of the s4syst:connectsSystemAt property. If defined, it shall have an English-tagged label (rdfs:label), and the local name of its IRI shall be a mixed case form of its English-tagged label. The label of the sub-property should use the same morpho-syn... |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 6.3.5 Examples for the Smart Grid domain and the Smart Building domain | Different examples of applications of the SAREF4SYST pattern can be found at https://saref.etsi.org/saref4syst/v1.1.2/example/, including for the Smart Grid domain and the Smart Building domain. The sources of the ontology and the examples can be found at https://saref.etsi.org/sources/saref4syst. |
2c54959eca6295ae8d7bf6b30e18b432 | 103 548 | 7 Conclusion | The present document specifies 11 SAREF reference ontology patterns in SAREF Core and 3 in SAREF4SYST. Each sheds light on a specific subset of entities, and provides detailed instructions on how it may or should be be used and specialized in SAREF extensions and SAREF applications. The overall goal is to facilitate th... |
eb7538c5f21aa9112a5c264d96982f52 | 103 544-29 | 1 Scope | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, whi... |
eb7538c5f21aa9112a5c264d96982f52 | 103 544-29 | 2 References | |
eb7538c5f21aa9112a5c264d96982f52 | 103 544-29 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
eb7538c5f21aa9112a5c264d96982f52 | 103 544-29 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
eb7538c5f21aa9112a5c264d96982f52 | 103 544-29 | 3 Definition of terms, symbols and abbreviations | |
eb7538c5f21aa9112a5c264d96982f52 | 103 544-29 | 3.1 Terms | Void. ETSI ETSI TS 103 544-29 V1.3.1 (2019-10) 6 |
eb7538c5f21aa9112a5c264d96982f52 | 103 544-29 | 3.2 Symbols | Void. |
eb7538c5f21aa9112a5c264d96982f52 | 103 544-29 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: EMail Electronic Mail SBP Service Binary Protocol |
eb7538c5f21aa9112a5c264d96982f52 | 103 544-29 | 4 Data Service Definition | |
eb7538c5f21aa9112a5c264d96982f52 | 103 544-29 | 4.1 Schedule Data Service Version 1.0 | /** The present document defines data objects for the Schedule data * service to be carried over by SBP. By receiving this data, the * schedule data sink can provide schedule information to the * driver through instrument cluster display panel. The Schedule * Source may be implemented in a Mirrorlink Client or a Mirror... |
eb7538c5f21aa9112a5c264d96982f52 | 103 544-29 | 5 SBP Binding | A SBP Sink endpoint shall be able to access the schedule object using SBP Subscribe and Get commands. A SBP Source endpoint shall support the ON_CHANGE SBP subscription type. The schedule object stores the next upcoming schedule and is updated 15 minutes before the actual schedule time. If the SBP Source endpoint is no... |
eb7538c5f21aa9112a5c264d96982f52 | 103 544-29 | 6 Theory of Operations | |
eb7538c5f21aa9112a5c264d96982f52 | 103 544-29 | 6.1 Getting Schedule Information | Figure 1 shows how a schedule data sink retrieves metadata about the current schedules from the schedule data source. ETSI ETSI TS 103 544-29 V1.3.1 (2019-10) 9 SBP Server (Schedule Source) SBP Client (Schedule Sink) User ICD Execute steps as defined in [2] SBP::SUBSCRIBE ( Schedule ) SBP::Response ( Ok ) SBP::GET ( Sc... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 1 Scope | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, whi... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 2 References | |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 3 Definition of terms, symbols and abbreviations | |
606439e911d3f67ed36fc9b73becc04d | 103 544-13 | 3.1 Terms | For the purposes of the present document, the following terms apply: pointer event: touch screen action in which the user touches the screen with one (virtual) finger only at a single location touch event: touch screen action in which the user touches the screen with two or more separate fingers at different locations ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.