rdfs:comment"A relationship to determine the supported network technologies of the lift. Examples of technologies are 2G, 3G,4G, 5G and fixed line."@en;
rdfs:comment"A relationship identifying the manufacturer of an entity (e.g., device). The value is expected to be a string or a string with language tag.";
rdfs:comment"A relationship identifying the manufacturer of an entity (e.g., device). The value is expected to be a string or a string with language tag."@en;
rdfs:isDefinedBysaref:;
rdfs:label"has manufacturer".
rdfs:label"has manufacturer"@en.
### https://saref.etsi.org/core/hasTimestamp
saref:hasTimestamprdf:typeowl:DatatypeProperty;
rdfs:comment"A relationship stating the timestamp of an entity (e.g. a measurement).";
rdfs:comment"A relationship stating the timestamp of an entity (e.g. a measurement)."@en;
rdfs:label"Status of the door. TRUE indicates that indicates that the corresponding port identified by the array index is open at the given stop. FALSE indicates that the port is closed.",
rdfs:label"Status of the door. TRUE indicates that indicates that the corresponding port identified by the array index is open at the given stop. FALSE indicates that the port is closed."@en,
rdfs:comment"This class represents the top-level feature type. This class is equivalent to GFI_Feature defined in ISO 19156:2011, and it is superclass of all feature types.";
rdfs:comment"This class represents the top-level feature type. This class is equivalent to GFI_Feature defined in ISO 19156:2011, and it is superclass of all feature types."@en;
rdfs:comment"The class represents the top-level geometry type. This class is equivalent to the UML class GM_Object defined in ISO 19107, and it is superclass of all geometry types.";
rdfs:comment"The class represents the top-level geometry type. This class is equivalent to the UML class GM_Object defined in ISO 19107, and it is superclass of all geometry types."@en;
rdfs:comment"A directive that a device must support to perform a certain function. A command may act upon a state, but does not necessarily act upon a state. For example, the ON command acts upon the ON/OFF state, but the GET command does not act upon any state, it simply gives a directive to retrieve a certain value";
rdfs:comment"A directive that a device must support to perform a certain function. A command may act upon a state, but does not necessarily act upon a state. For example, the ON command acts upon the ON/OFF state, but the GET command does not act upon any state, it simply gives a directive to retrieve a certain value"@en;
rdfs:isDefinedBysaref:;
rdfs:label"Command".
rdfs:label"Command"@en.
### https://saref.etsi.org/core/Device
saref:Devicerdf:typeowl:Class;
rdfs:comment"A tangible object designed to accomplish a particular task. In order to accomplish this task, the device performs one or more functions. For example, a washing machine is designed to wash (task) and to accomplish this task it performs a start and stop function.";
rdfs:comment"A tangible object designed to accomplish a particular task. In order to accomplish this task, the device performs one or more functions. For example, a washing machine is designed to wash (task) and to accomplish this task it performs a start and stop function."@en;
rdfs:isDefinedBy<https://saref.etsi.org/core>;
rdfs:label"Device".
rdfs:label"Device"@en.
### https://saref.etsi.org/core/FeatureOfInterest
saref:FeatureOfInterestrdf:typeowl:Class;
rdfs:comment"A feature of interest represents any real world entity from which a property is measured.";
rdfs:comment"A feature of interest represents any real world entity from which a property is measured."@en;
rdfs:isDefinedBy"https://saref.etsi.org/core/";
rdfs:label"FeatureOfInterest".
rdfs:label"FeatureOfInterest"@en.
### https://saref.etsi.org/core/Function
saref:Functionrdf:typeowl:Class;
rdfs:comment"The functionality necessary to accomplish the task for which a device is designed. A device can be designed to perform more than one function. Functions can be structured in categories (subclasses) that reflect different points of view, for example, considering the specific application area for which a function can be used (e.g., light, temperature, motion, heat, power, etc.), or the capability that a function can support (e.g., receive, reply, notify, etc.), and so forth.";
rdfs:comment"The functionality necessary to accomplish the task for which a device is designed. A device can be designed to perform more than one function. Functions can be structured in categories (subclasses) that reflect different points of view, for example, considering the specific application area for which a function can be used (e.g., light, temperature, motion, heat, power, etc.), or the capability that a function can support (e.g., receive, reply, notify, etc.), and so forth."@en;
rdfs:comment"Represents the measured value made over a property. It is also linked to the unit of measure in which the value is expressed and the timestamp of the measurement.";
rdfs:comment"Represents the measured value made over a property. It is also linked to the unit of measure in which the value is expressed and the timestamp of the measurement."@en;
rdfs:isDefinedBysaref:;
rdfs:label"Measurement".
rdfs:label"Measurement"@en.
### https://saref.etsi.org/core/Power
saref:Powerrdf:typeowl:Class;
rdfs:subClassOfsaref:Property;
rdfs:comment"A saref:Property related to some measurements that are characterized by a certain value that is measured in a power unit (such as watt or kilowatt). Further specializations of the saref:Power class can be found in the SAREF4ENER extension, where classes such as PowerMax, PowerMin and PowerExpected are defined.";
rdfs:comment"A saref:Property related to some measurements that are characterized by a certain value that is measured in a power unit (such as watt or kilowatt). Further specializations of the saref:Power class can be found in the SAREF4ENER extension, where classes such as PowerMax, PowerMin and PowerExpected are defined."@en;
rdfs:isDefinedBy<https://saref.etsi.org/core>;
rdfs:label"Power".
rdfs:label"Power"@en.
### https://saref.etsi.org/core/Property
saref:Propertyrdf:typeowl:Class;
rdfs:comment"A quality of a feature of interest that can be measured; an aspect of a feature of interest that is intrinsic to and cannot exist without the feature";
rdfs:comment"A quality of a feature of interest that can be measured; an aspect of a feature of interest that is intrinsic to and cannot exist without the feature"@en;
rdfs:isDefinedBysaref:;
rdfs:label"Property".
rdfs:label"Property"@en.
### https://saref.etsi.org/core/Time
saref:Timerdf:typeowl:Class;
rdfs:comment"A class that allows to specify the time concept.";
rdfs:comment"A class that allows to specify the time concept."@en;
rdfs:isDefinedBysaref:;
rdfs:label"Time".
rdfs:label"Time"@en.
### https://saref.etsi.org/core/UnitOfMeasure
saref:UnitOfMeasurerdf:typeowl:Class;
rdfs:comment"The unit of measure is a standard for measurement of a quantity, such as a Property. For example, Power is a property and Watt is a unit of power that represents a definite predetermined power: when we say 10 Watt, we actually mean 10 times the definite predetermined power called \\\"watt\\\". Our definition is based on the definition of unit of measure in the Ontology of units of Measure (OM). We propose here a list of some units of measure that are relevant for the purpose of the Smart Appliances ontology, but this list can be extended.";
rdfs:comment"The unit of measure is a standard for measurement of a quantity, such as a Property. For example, Power is a property and Watt is a unit of power that represents a definite predetermined power: when we say 10 Watt, we actually mean 10 times the definite predetermined power called \\\"watt\\\". Our definition is based on the definition of unit of measure in the Ontology of units of Measure (OM). We propose here a list of some units of measure that are relevant for the purpose of the Smart Appliances ontology, but this list can be extended."@en;
rdfs:comment"A Smart Lift Edge Component is dedicated to the hosting of smar lift additional modules in the case that they are not hosted directly in the Smart Lift Edge Control Unit. An example could be the case of an additional earthquake sensor added after the lift deployment and not controlled by the Smart Lift Edge Control Unit.";
rdfs:label"Smart Lift Edge Component".
s4syst:System;
rdfs:comment"A Smart Lift Edge Component is dedicated to the hosting of smar lift additional modules in the case that they are not hosted directly in the Smart Lift Edge Control Unit. An example could be the case of an additional earthquake sensor added after the lift deployment and not controlled by the Smart Lift Edge Control Unit."@en;
rdfs:comment"A Smart Lift Edge Control Unit is the main element of a Smart Lift installation and it is typically associated with the lift control cabinet";
rdfs:label"Smart Lift Edge Control Unit".
s4syst:System;
rdfs:comment"A Smart Lift Edge Control Unit is the main element of a Smart Lift installation and it is typically associated with the lift control cabinet"@en;
rdfs:comment"A Smart Lift Group represents the correlation of multiple Smart Lifts Installation and it is supported by the introduction of a Smart Lift Group identifier common each Smart Lifts Installation belonging to the same Smart Lift Group. Such kind of installations usually presents control units connected one each other to coordinate the movement and position of the different lifts, where the common commands (e.g. the call buttons) are given to one of these control units that acts as a principal master and coordinates the other installations or is composed by peer installations that coordinates one each othe";
rdfs:label"Smart Lift Group".
s4syst:System;
rdfs:comment"A Smart Lift Group represents the correlation of multiple Smart Lifts Installation and it is supported by the introduction of a Smart Lift Group identifier common each Smart Lifts Installation belonging to the same Smart Lift Group. Such kind of installations usually presents control units connected one each other to coordinate the movement and position of the different lifts, where the common commands (e.g. the call buttons) are given to one of these control units that acts as a principal master and coordinates the other installations or is composed by peer installations that coordinates one each othe"@en;
rdfs:comment"The class of systems, i.e., systems virtually isolated from the environment, whose behaviour and interactions with the environment are modeled. Systems can be connected to other systems. Connected systems interact in some ways. Systems can also have subsystems. Properties of subsystems somehow contribute to the properties of the supersystem.";
s4syst:Systemrdf:typeowl:Class;
rdfs:comment"The class of systems, i.e., systems virtually isolated from the environment, whose behaviour and interactions with the environment are modeled. Systems can be connected to other systems. Connected systems interact in some ways. Systems can also have subsystems. Properties of subsystems somehow contribute to the properties of the supersystem."@en;