PREFIX ecseldr: <http://www.w3id.org/ecsel-dr/>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>

<http://www.w3id.org/ecsel-dr-AT#NetworkLayerModel> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution_ElectricPowerMax200> a rdfs:Class ;
  rdfs:label "Motor Control and Drive Solution With Electric Power Max 200.0" ;
  rdfs:comment "Motor control and drive solution with maximum electric power equal to 200.0." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasChipCountSmartDriver> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> ;
  rdfs:range xsd:integer ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasChipCount> .

<http://www.w3id.org/ecsel-dr-OOSMP#couldContainSensor> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#Sensor> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#containsProduct> .

<http://www.w3id.org/ecsel-dr-OOSMP#containsAdditionalPowerManagement> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#AdditionalPowerManagement> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#containsProduct> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaDiscretePowerStage> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> ;
  rdfs:range xsd:double ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaProductFamily> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasChipCountGateDriver> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> ;
  rdfs:range xsd:integer ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasChipCount> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasPriceIndication> a rdf:Property ;
  rdfs:comment "BOM" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#PriceIndication> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasDCLinkVoltageCharacteristic> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range xsd:double .

<http://www.w3id.org/ecsel-dr-OOSMP#hasSensingType> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#SensingType> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasMotorType> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MotorType> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaProductFamily> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> ;
  rdfs:range xsd:double ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintArea> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasChipCount> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-OOSMP#hasIntegrationLevel> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#IntegrationLevel> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaSmartDriver> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> ;
  rdfs:range xsd:double ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaProductFamily> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasTopology> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#Topology> .

<http://www.w3id.org/ecsel-dr-OOSMP#containsProduct> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Solution> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#Product> .

<http://www.w3id.org/ecsel-dr-OOSMP#containsDiscretePowerStage> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#DiscretePowerStage> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#containsProduct> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaIntelligentPowerModule> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> ;
  rdfs:range xsd:double ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaProductFamily> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasQualification> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#Qualification> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasDCLinkVoltageMin> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range xsd:double ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasDCLinkVoltageCharacteristic> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaGateDriver> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> ;
  rdfs:range xsd:double ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaProductFamily> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasMainPowerDeviceType> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MainPowerDeviceType> .

<http://www.w3id.org/ecsel-dr-OOSMP#identifier_solution> a rdf:Property ;
  rdfs:label "Solution ID" ;
  rdfs:comment "Any identifier (ID) of a solution" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Solution> ;
  rdfs:range xsd:string ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#identifier> .

<http://www.w3id.org/ecsel-dr-OOSMP#containsIntelligentPowerModule> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#IntelligentPowerModule> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#containsProduct> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintArea> a rdf:Property ;
  rdfs:range xsd:double .

<http://www.w3id.org/ecsel-dr-OOSMP#hasElectricPower> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range xsd:double .

<http://www.w3id.org/ecsel-dr-OOSMP#hasElectricPowerMin> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range xsd:double ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasElectricPower> .

<http://www.w3id.org/ecsel-dr-OOSMP#containsMicrocontroller> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#Microcontroller> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#containsProduct> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasChipCountIntelligentPowerModule> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> ;
  rdfs:range xsd:integer ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasChipCount> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaMicrocontroller> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> ;
  rdfs:range xsd:double ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaProductFamily> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasDCLinkVoltageMax> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range xsd:double ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasDCLinkVoltageCharacteristic> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasDCLinkVoltage> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range xsd:double ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasDCLinkVoltageCharacteristic> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasElectricPowerMax> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range xsd:double ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasElectricPower> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasSolutionQualification> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#Qualification> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasQualification> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasDesignTarget> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#DesignTarget> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasChipCountMicrocontroller> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> ;
  rdfs:range xsd:integer ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasChipCount> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasChipCountDiscretePowerStage> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> ;
  rdfs:range xsd:integer ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasChipCount> .

<http://www.w3id.org/ecsel-dr-OOSMP#canBeAppliedIn> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> .

<http://www.w3id.org/ecsel-dr-OOSMP#containsSmartDriver> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#SmartDriver> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#containsProduct> .

<http://www.w3id.org/ecsel-dr-OOSMP#containsGateDriver> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#GateDriver> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#containsProduct> .

<http://www.w3id.org/ecsel-dr-AT#AutomationML> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#MarkupLanguage> .

<http://www.w3id.org/ecsel-dr-AT#TransportRobot> a rdfs:Class ;
  rdfs:label "Transportroboter"@de ;
  rdfs:comment """neuere Version von fahrerlosem Transportfahrzeug. 
Im Gegensatz zu traditionellen FTF verfügen Transportroboter über die Fähigkeit der freien Navigation im Raum. 
D.h. sie bewegen sich nicht nur entlang vorgegebener physischer (z.B. optimscher oder magnetischer) oder virtueller Fahrspuren, sondern navigieren frei im Raum unter Nutzung eigener Sensorik zur Umgebungserkennung und Positionierung."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ActuatorDevice> .

<http://www.w3id.org/ecsel-dr-AT#usedInISA-95_Layer> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AT#Device> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer> .

<http://www.w3id.org/ecsel-dr-AT#Frame> a rdfs:Class ;
  rdfs:comment """Data transmission unit of ISO/OSI layer 2 (Data Link Layer). 
\"Envelope\", contain MAC addresses (Media Access Control)."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#DataTransmissionUnit> .

<http://www.w3id.org/ecsel-dr-AT#dataTransmissionUnitOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AT#DataTransmissionUnit> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AT#CPF3_Profibus_ProfiNet> a rdfs:Class ;
  rdfs:comment "Die Communication Protocol Family Profibus und Profinet ist eine Familie von Feldbus-Systemen."@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3id.org/ecsel-dr-PRIMA#Training> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PRIMA#isTrainingLevelOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#Training> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PRIMA#ProjectManager> .

<http://www.w3id.org/ecsel-dr-PRIMA#Certification> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PRIMA#isCertificationLevelOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#Certification> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> .

<http://www.w3id.org/ecsel-dr-AT#WAP> a rdfs:Class ;
  rdfs:label "Wireless Access Point" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#CommunicationDevice> .

<http://www.w3id.org/ecsel-dr-AT#isDeviceOfOSILayer> a rdf:Property ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer4_ERP> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer> .

<http://www.w3id.org/ecsel-dr-AH#AH_service> a rdfs:Class ;
  rdfs:comment "Arrowhead compliant service - service that is provided within an Arrowhead environment (i.e., service that is provided by an Arrowhead compliant software system that runs on a device within an Arrowhead local cloud; service is registered at the AH service registry system via its method for service registration and can be discovered and consumed by other Arrowhead compliant software systems."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Service> .

<http://www.w3id.org/ecsel-dr-AH#isAHServiceDocumentedBy> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#AH_service> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#AH_service_documentation> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#isServiceDocumentedBy> .

<http://www.w3id.org/ecsel-dr-AH#usesCommTech> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Service> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AH#usesSecurityMechanism> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Service> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Communication_security_mechanism> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#usesCommTech> .

<http://www.w3id.org/ecsel-dr-AH#isServiceDocumentedBy> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Service> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Service_documentation> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#isDocumentedBy> .

<http://www.w3id.org/ecsel-dr-AH#hasMethod> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Service> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Method> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#hasArchitecturalPart> .

<http://www.w3id.org/ecsel-dr-AH#isDocumentedBy> a rdf:Property ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AH#usesDataFormat> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Service> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Data_format> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#usesCommTech> .

<http://www.w3id.org/ecsel-dr-AH#producedBy> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Service> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Software_system> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#isArchitecturalPartOf> .

<http://www.w3id.org/ecsel-dr-AH#usesTransferProtocol> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Service> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Transfer_protocol> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#usesCommTech> .

<http://www.w3id.org/ecsel-dr-AH#hasInformationModel> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Service> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#InformationModel> .

<http://www.w3id.org/ecsel-dr-SO#Fab> a rdfs:Class ;
  rdfs:comment "The “Fab” entity depicts the fab as a technological and physical production unit. (master entity)"@en .

<http://www.w3id.org/ecsel-dr-SO#hasLotSize> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Lot_Size> .

<http://www.w3id.org/ecsel-dr-SO#hasFabType> a rdf:Property ;
  rdfs:comment "Fab: Front End, Wafer Testing, Back End Assembly, Back End Final Test, …"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Fab> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasEquipmentGroup> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Equipment_Group> .

<http://www.w3id.org/ecsel-dr-SO#hasEventCalendar> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Event_Calendar> .

<http://www.w3id.org/ecsel-dr-SO#hasDemand> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Product> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Demand_Snapshot> .

<http://www.w3id.org/ecsel-dr-SO#hasPlantID> a rdf:Property ;
  rdfs:comment "Fab: FK; Geographical location"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Fab> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasFabPseudonym> a rdf:Property ;
  rdfs:comment "FK; Name of the facility"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Release_Plan> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasMaxWIP> a rdf:Property ;
  rdfs:comment "Fab: Hard capacity restriction of process units (NULL if no restriction)"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Fab> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-SO#hasFabInternal> a rdf:Property ;
  rdfs:comment "Fab: Does the fab belong to the company or to an external partner"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Fab> ;
  rdfs:range xsd:boolean .

<http://www.w3id.org/ecsel-dr-SO#hasWorkshop> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Workshop> .

<http://www.w3id.org/ecsel-dr-AT#MQTT_nonTCPIP_based> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#MQTT> .

<http://www.w3id.org/ecsel-dr-AT#implementsOSILayer> a rdf:Property ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AT#usedInISA-95_Communication> a rdf:Property ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SCP#StandardOrders> a rdfs:Class ;
  rdfs:label "StandardOrders"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#Orders> .

<http://www.w3id.org/ecsel-dr-SCP#constitute> a rdf:Property ;
  rdfs:label "constitute"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#Orders> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#SalesDemands> .

<http://www.w3id.org/ecsel-dr-SCP#enterTo> a rdf:Property ;
  rdfs:label "enterTo"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#Orders> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#CLM> .

<http://www.w3id.org/ecsel-dr-SCP#contribute> a rdf:Property ;
  rdfs:label "contribute"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#Orders> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#PrioritizedOrders> .

<http://www.w3id.org/ecsel-dr-SCP#sortTo> a rdf:Property ;
  rdfs:label "sortTo"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#Orders> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#OrderLineItem> .

<http://www.w3id.org/ecsel-dr-AT#CPF9_HART> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3id.org/ecsel-dr-PWR#DrainCurrent> a rdfs:Class ;
  rdfs:label "Drain Current" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Property> .

<http://www.w3id.org/ecsel-dr-PMV#ProcessType> a rdfs:Class ;
  rdfs:label "Process Type" ;
  rdfs:comment "A set of core and enabler processes of Infineon on Level 0 (highest level). This level helps helps organizing project work/ development and represents a single track in the oneSAP project. It is based on a Deloitte standard which was adapted to Infineon's needs." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#StructuralFunctionObject> .

<http://www.w3id.org/ecsel-dr-PMV#diagramedOn> a rdf:Property ;
  rdfs:label "diagramedOn" ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Model> .

<http://www.w3id.org/ecsel-dr-PRIMA#ProjectOwner> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PRIMA#Role> .

<http://www.w3id.org/ecsel-dr-PRIMA#isRoleOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#Role> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> .

<http://www.w3id.org/ecsel-dr-PRIMA#hasContributor> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#Role> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AT#ANSI_X12-Specification> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#EDI_Specification> .

<http://www.w3id.org/ecsel-dr-AH#Interface_Design_Description_IDD> a rdfs:Class ;
  rdfs:comment "Provides a detailed description of how a service is implemented/realized including defining protocols, encoding and semantics. When more than one service is using the same protocols, encoding or semantics, this is broken out to Communication profiles (CP) and Semantic profiles (SP) and referred to from the IDD’s. (Source: Arrowhead Framework Definitions V2.4)"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_service_documentation_document> .

<http://www.w3id.org/ecsel-dr-AH#refersToSP> a rdf:Property ;
  rdfs:comment """an Interface Design Description (IDD) can refer to a Semantic Profile (SP). 
No other documentation document can refer to a SP. Hence the domain of this object property is the class of IDDs. 
An IDD can refer to a SP, but this is not mandatory. SPs are intended to be used in cases in which several services use the same SP. Then the SCP information should be extracted to an SP document and the IDDs of all services that use this SP shall refer to this SP. 
If the SP is unique for a specific service, the SP information can directly be included in the IDD.
References to SPs are not necessarily unique for an IDD. That is, different methods of the service documented by the IDD can use different Semantic Profiles."""@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Interface_Design_Description_IDD> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Semantic_Profile_SP> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#refersTo> .

<http://www.w3id.org/ecsel-dr-AH#refersToCP> a rdf:Property ;
  rdfs:comment """an Interface Design Description (IDD) can refer to a Communication Profile (CP). 
No other documentation document can refer to a CP. Hence the domain of this object property is the class of IDDs. 
An IDD can refer to a CP, but this is not mandatory. CPs are intended to be used in cases in which several services use the same CP. Then the CP information should be extracted to an CP document and the IDDs of all services that use this CP shall refer to this CP. 
If the CP is unique for a specific service, the CP information can directly be included in the IDD.
If the IDD refers to a CP, this must be a unique reference. That is, one IDD must not refer to different CPs. Hence this object property is functional. (If the service could be implemented using different communication technologies, each implementation would need an own IDD!!)."""@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Interface_Design_Description_IDD> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Communication_Profile_CP> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#refersTo> .

<http://www.w3id.org/ecsel-dr-AH#documentsAHServiceMethod> a rdf:Property ;
  rdfs:comment """Relation between an Interface Design Description document (of a specific service) and a method of this service. 
The relation expresses that the IDD document documents the methods of the service the IDD belongs to. 
With this, a consistency check would be possible: 
IF a service S has a method M AND the IDD IDD_S is part of the service documentation of S (i.e. IDD_S is the IDD of S) 
THEN IDD_S should contain a documentation of M."""@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Interface_Design_Description_IDD> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Method> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#documentsServicePart> .

<http://www.w3id.org/ecsel-dr-AH#isPartOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Documentation_document> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AH#isReferredToBy> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Documentation_document> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Documentation_document> .

<http://www.w3id.org/ecsel-dr-AH#isPartOfServiceDoc> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#AH_service_documentation_document> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#AH_service_documentation> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#isPartOf> .

<http://www.w3id.org/ecsel-dr-AH#refersToSD> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Interface_Design_Description_IDD> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Service_Description_SD> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#refersTo> .

<http://www.w3id.org/ecsel-dr-AH#documentsAHServiceCommSecurityMechanism> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Documentation_document> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Communication_security_mechanism> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#documentsAHServiceCommTech> .

<http://www.w3id.org/ecsel-dr-AH#refersTo> a rdf:Property ;
  rdfs:comment """describes the relation between two documentation documents that one document refers to another document.
To our best knowledge, the following relations hold between different types of documentation documents: 
- an IDD refers to exactly one SD.
- an SD is referred to by one or more IDD (each stating a way of implementing the service with a specific technolopgy (Source: Arrowhead Framework Definitions V2.4))
- an IDD refers to at most one CP (if it not refers to a CP, then the IDD contains all CP information by itself)
- an IDD refers to n SP, 0 <= n (if it not refers to a SP, then the IDD contains all SP information by itself)
- a SySD refers to one or more IDDs (that is, a system produces one or more services).
- a SySDD refers to one or more SySD's. (Remark HB: I don't understand this. How can one concrete white box description of a system fulfill (support / implement) different black box descriptions of systems? The other way around seems to be possible as between SDs and IDDs). 
- an SoSD refers to n SySD's.
- an SoSDD refers to n SoSD's. 
- an SoSDD refers to n SySD's. 
- an SoSDD refers to n SySDDs."""@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Documentation_document> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Documentation_document> .

<http://www.w3id.org/ecsel-dr-AH#documentsAHServiceDataFormat> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Documentation_document> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Data_format> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#documentsAHServiceCommTech> .

<http://www.w3id.org/ecsel-dr-AH#documentsAHServiceCommTech> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Documentation_document> ;
  rdfs:range <https://w3id.org/linkml/Any> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#documentsServicePart> .

<http://www.w3id.org/ecsel-dr-AH#documentsAHServiceTransferProtocol> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Documentation_document> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Transfer_protocol> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#documentsAHServiceCommTech> .

<http://www.w3id.org/ecsel-dr-AH#documentsAHServiceInformationModel> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Documentation_document> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#InformationModel> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#documentsServicePart> .

<http://www.w3id.org/ecsel-dr-AH#documentsServicePart> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Documentation_document> ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-OOSMP#Sensor> a rdfs:Class ;
  rdfs:label "Sensor" ;
  rdfs:comment "A semiconductor product which is used as sensor" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasTemperature> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Sensor> ;
  rdfs:range xsd:double .

<http://www.w3id.org/ecsel-dr-OOSMP#hasSupplyVoltageMax> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Sensor> ;
  rdfs:range xsd:double ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasSupplyVoltage> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasTemperatueMax> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Sensor> ;
  rdfs:range xsd:double ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasTemperature> .

<http://www.w3id.org/ecsel-dr-OOSMP#uniformResourceLocator_productPicture> a rdf:Property ;
  rdfs:label "Product Picture URL" ;
  rdfs:comment "The uniform resource locator (URL) of the picture of a product" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Product> ;
  rdfs:range xsd:string ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#uniformResourceLocator> .

<http://www.w3id.org/ecsel-dr-OOSMP#ownedBy> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Product> ;
  rdfs:range <http://www.w3.org/ns/org#OrganizationalUnit> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasTemperatureMin> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Sensor> ;
  rdfs:range xsd:double ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasTemperature> .

<http://www.w3id.org/ecsel-dr-OOSMP#uniformResourceLocator_productPage> a rdf:Property ;
  rdfs:label "Product Page URL" ;
  rdfs:comment "The uniform resource locator (URL) of the page of a product" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Product> ;
  rdfs:range xsd:string ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#uniformResourceLocator> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasApplicationCharacteristic> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-OOSMP#hasRoHSCompliantStatus> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#RoHSCompliantStatus> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasSemiconductorProductStatus> .

<http://www.w3id.org/ecsel-dr-OOSMP#partOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Product> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#Solution> .

<http://www.w3id.org/ecsel-dr-OOSMP#partOfAsPotentialSensor> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Sensor> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#partOf> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasMountingStyle> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Sensor> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MountingStyle> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasBudgetaryPrice> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range xsd:double .

<http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaProduct> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range xsd:double ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintArea> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasBenefit> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range xsd:string ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasApplicationCharacteristic> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasPackingType> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#PackingType> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasOPNStatus> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#OPNStatus> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasSemiconductorProductStatus> .

<http://www.w3id.org/ecsel-dr-OOSMP#identifier_product> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Product> ;
  rdfs:range xsd:string ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#identifier> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasChannelStructure> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range xsd:string ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasHierarchyInformation> .

<http://www.w3id.org/ecsel-dr-OOSMP#identifier_product_orderablePartNumber> a rdf:Property ;
  rdfs:label "Orderable Part Number" ;
  rdfs:comment "The orderable part number (OPN) of a product" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range xsd:string ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#identifier_product> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasPackageName> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range xsd:string ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasHierarchyInformation> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasSemiconductorProductStatus> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProductStatus> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasProductFamilyName> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range xsd:string ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasHierarchyInformation> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasPackingSize> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OOSMP#hasProductQualification> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#Qualification> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasQualification> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasSupplyVoltage> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Sensor> ;
  rdfs:range xsd:double .

<http://www.w3id.org/ecsel-dr-OOSMP#hasHierarchyInformation> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-OOSMP#hasCompletelyLeadFreeStatus> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#CompletelyLeadFreeStatus> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasSemiconductorProductStatus> .

<http://www.w3id.org/ecsel-dr-OOSMP#identifier_product_internetSalesProductNumber> a rdf:Property ;
  rdfs:label "Internet Sales Product Number" ;
  rdfs:comment "The internet sales product number (ISPN) of a product" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range xsd:string ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#identifier_product> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasHalogenFreeStatus> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#HalogenFreeStatus> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasSemiconductorProductStatus> .

<http://www.w3id.org/ecsel-dr-OOSMP#uniformResourceLocator_productDatasheet> a rdf:Property ;
  rdfs:label "Product Datasheet URL" ;
  rdfs:comment "The uniform resource locator (URL) of the datasheet of a product" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Product> ;
  rdfs:range xsd:string ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#uniformResourceLocator> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasTargetApplication> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range xsd:string ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasApplicationCharacteristic> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasFeature> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:range xsd:string ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasApplicationCharacteristic> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasSupplyVoltageMin> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Sensor> ;
  rdfs:range xsd:double ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasSupplyVoltage> .

<http://www.w3id.org/ecsel-dr-AT#Proxy> a rdfs:Class ;
  rdfs:comment """Proxies are also referred to as Application Layer Gateways. 
A proxy examines and modifies the content of the packets without translating them into another protocol."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#CommunicationDevice> .

<http://www.w3.org/2006/time#TemporalDuration> a rdfs:Class ;
  rdfs:label "Temporal duration"@en ;
  rdfs:comment "Time extent; duration of a time interval separate from its particular start position"@en .

<http://www.w3id.org/ecsel-dr-AT#DNS> a rdfs:Class ;
  rdfs:label "Domain Name Service"@de ;
  rdfs:comment """Das DNS ist ein weltweit auf Tausenden von Servern verteilter hierarchischer Verzeichnisdienst, der den Namensraum des Internets verwaltet. Dieser Namensraum ist in so genannte Zonen unterteilt, für die jeweils unabhängige Administratoren zuständig sind. Für lokale Anforderungen – etwa innerhalb eines Firmennetzes – ist es auch möglich, ein vom Internet unabhängiges DNS zu betreiben.

Hauptsächlich wird das DNS zur Umsetzung von Domainnamen in IP-Adressen („forward lookup“) benutzt. Dies ist vergleichbar mit einem Telefonbuch, das die Namen der Teilnehmer in ihre Telefonnummer auflöst. Das DNS bietet somit eine Vereinfachung, weil Menschen sich Namen weitaus besser merken können als Zahlenketten. So kann man sich einen Domainnamen wie example.org in der Regel leichter merken als die dazugehörende IP-Adresse 192.0.32.10. Dieser Punkt gewinnt im Zuge der Einführung von IPv6 noch mehr an Bedeutung, denn dann werden einem Namen jeweils IPv4- und IPv6-Adressen zugeordnet. So löst sich beispielsweise der Name www.kame.net in die IPv4-Adresse 203.178.141.194 und die IPv6-Adresse 2001:200:dff:fff1:216:3eff:feb1:44d7 auf.

Ein weiterer Vorteil ist, dass IP-Adressen – etwa von Web-Servern – relativ risikolos geändert werden können. Da Internetteilnehmer nur den (unveränderten) DNS-Namen ansprechen, bleiben ihnen Änderungen der untergeordneten IP-Ebene weitestgehend verborgen. Da einem Namen auch mehrere IP-Adressen zugeordnet werden können, kann sogar eine einfache Lastverteilung per DNS (Load Balancing) realisiert werden.

Mit dem DNS ist auch eine umgekehrte Auflösung von IP-Adressen in Namen (reverse lookup) möglich. In Analogie zum Telefonbuch entspricht dies einer Suche nach dem Namen eines Teilnehmers zu einer bekannten Rufnummer, was innerhalb der Telekommunikationsbranche unter dem Namen Inverssuche bekannt ist.

Das DNS wurde 1983 von Paul Mockapetris entworfen und in RFC 882 und RFC 883 (RFC = Request for Comments) beschrieben. Beide wurden inzwischen von RFC 1034 und RFC 1035 abgelöst und durch zahlreiche weitere Standards ergänzt. Ursprüngliche Aufgabe war es, die lokalen hosts-Dateien abzulösen, die bis dahin für die Namensauflösung zuständig waren und der enorm zunehmenden Zahl von Neueinträgen nicht mehr gewachsen waren. Aufgrund der erwiesenermaßen hohen Zuverlässigkeit und Flexibilität wurden nach und nach weitere Datenbestände in das DNS integriert und so den Internetnutzern zur Verfügung gestellt (siehe unten: Erweiterung des DNS).

DNS zeichnet sich aus durch:

    dezentrale Verwaltung,
    hierarchische Strukturierung des Namensraums in Baumform,
    Eindeutigkeit der Namen,
    Erweiterbarkeit."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-SO#Productive> a rdfs:Class ;
  rdfs:comment "[Priority Class] The standard lots, also referred to as Productive (Prod) lots, are the most common lot type and have no priority."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Priority_Classes> .

<http://www.w3id.org/ecsel-dr-PRIMA#CentralFunction> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PRIMA#isContributorOf> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PRIMA#Role> .

<http://www.w3id.org/ecsel-dr-AT#Hub> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#CommunicationDevice> .

<http://www.w3id.org/ecsel-dr-AT#BI-System> a rdfs:Class ;
  rdfs:label "Business Intelligence System"@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-AT#isPartOf-IT-Suite> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AT#IT-System> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-AT#has-IT-ModuleOrPart> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AT#IT-System> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-AT#belongsToISA-95-Layer> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AT#IT-System> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer> .

<http://www.w3id.org/ecsel-dr-AT#hasVendor> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AT#IT-System> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AT#IT-Vendor> .

<http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution_IndustrialQualification> a rdfs:Class ;
  rdfs:label "Motor Control and Drive Solution With Industrial Qualification" ;
  rdfs:comment "Motor control and drive solution with a industrial qualification." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> .

<http://www.w3id.org/ecsel-dr-AT#CAD-System> a rdfs:Class ;
  rdfs:label "Computer Aided Design System"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-AH#System_Design_Description_SySDD> a rdfs:Class ;
  rdfs:comment "Provides a description of Arrowhead Systems’ technological implementations, i.e. a “White Box” view of a system. Includes which components are used to implement the system and shows their internal interactions. A system described by a SySDD refers to one or more SySDs. (Source: Arrowhead Framework Definitions V2.4)"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_system_documentation_document> .

<http://www.w3id.org/ecsel-dr-AH#isPartOfSystemDoc> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#AH_system_documentation_document> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#AH_system_documentation> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#isPartOf> .

<http://www.w3id.org/ecsel-dr-AH#refersToSySD> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Documentation_document> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#System_Description_SySD> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#refersTo> .

<http://www.w3id.org/ecsel-dr-PWR#Operating_Property> a rdfs:Class ;
  rdfs:label "Operating Property" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Property> .

<http://www.w3id.org/ecsel-dr-AT#Ontology> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L5_DataSemantics> .

<http://www.w3id.org/ecsel-dr-OOSMP#AdditionalPowerManagement> a rdfs:Class ;
  rdfs:label "Additional Power Management" ;
  rdfs:comment "A semiconductor product which is used within the context of additional power management" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> .

<http://www.w3id.org/ecsel-dr-OOSMP#partOfAsAdditionalPowerManagement> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#AdditionalPowerManagement> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#partOf> .

<http://www.w3id.org/ecsel-dr-AT#RDFa> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L2_DataSyntax> .

<http://www.w3.org/2006/time#MonthOfYear> a rdfs:Class ;
  rdfs:label "Month of year"@en ;
  rdfs:comment "The month of the year"@en ;
  rdfs:subClassOf <http://www.w3.org/2006/time#DateTimeDescription> .

<http://www.w3.org/2006/time#monthOfYear> a rdf:Property ;
  rdfs:label "month of year"@en ;
  rdfs:comment "The month of the year, whose value is a member of the class time:MonthOfYear"@en ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDateTimeDescription> ;
  rdfs:range <http://www.w3.org/2006/time#MonthOfYear> .

<http://www.w3.org/2006/time#unitType> a rdf:Property ;
  rdfs:label "temporal unit type"@en ;
  rdfs:comment "The temporal unit which provides the precision of a date-time value or scale of a temporal extent"@en ;
  rdfs:range <http://www.w3.org/2006/time#TemporalUnit> .

<http://www.w3.org/2006/time#dayOfWeek> a rdf:Property ;
  rdfs:label "day of week"@en ;
  rdfs:comment "The day of week, whose value is a member of the class time:DayOfWeek"@en ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDateTimeDescription> ;
  rdfs:range <http://www.w3.org/2006/time#DayOfWeek> .

<http://www.w3.org/2006/time#minute> a rdf:Property ;
  rdfs:label "minute"@en ;
  rdfs:comment "Minute position in a calendar-clock system."@en ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDateTimeDescription> ;
  rdfs:range xsd:nonNegativeInteger .

<http://www.w3.org/2006/time#year> a rdf:Property ;
  rdfs:label "year"@en ;
  rdfs:comment """Year position in a calendar-clock system.

The range of this property is not specified, so can be replaced by any specific representation of a calendar year from any calendar. """@en ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDateTimeDescription> ;
  rdfs:range xsd:gYear , <https://w3id.org/linkml/Any> .

<http://www.w3.org/2006/time#hour> a rdf:Property ;
  rdfs:label "hour"@en ;
  rdfs:comment "Hour position in a calendar-clock system."@en ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDateTimeDescription> ;
  rdfs:range xsd:nonNegativeInteger .

<http://www.w3.org/2006/time#week> a rdf:Property ;
  rdfs:label "week"@en ;
  rdfs:comment "Week number within the year."@en ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDateTimeDescription> ;
  rdfs:range xsd:nonNegativeInteger .

<http://www.w3.org/2006/time#second> a rdf:Property ;
  rdfs:label "second"@en ;
  rdfs:comment "Second position in a calendar-clock system."@en ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDateTimeDescription> ;
  rdfs:range xsd:decimal .

<http://www.w3.org/2006/time#hasTRS> a rdf:Property ;
  rdfs:label "Temporal reference system used"@en ;
  rdfs:comment "The temporal reference system used by a temporal position or extent description. "@en ;
  rdfs:range <http://www.w3.org/2006/time#TRS> .

<http://www.w3.org/2006/time#month> a rdf:Property ;
  rdfs:label "month"@en ;
  rdfs:comment """Month position in a calendar-clock system.

The range of this property is not specified, so can be replaced by any specific representation of a calendar month from any calendar. """@en ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDateTimeDescription> ;
  rdfs:range xsd:gMonth , <https://w3id.org/linkml/Any> .

<http://www.w3.org/2006/time#dayOfYear> a rdf:Property ;
  rdfs:label "day of year"@en ;
  rdfs:comment "The number of the day within the year"@en ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDateTimeDescription> ;
  rdfs:range xsd:nonNegativeInteger .

<http://www.w3.org/2006/time#day> a rdf:Property ;
  rdfs:label "day"@en ;
  rdfs:comment """Day position in a calendar-clock system.

The range of this property is not specified, so can be replaced by any specific representation of a calendar day from any calendar. """@en ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDateTimeDescription> ;
  rdfs:range xsd:gDay , <https://w3id.org/linkml/Any> .

<http://www.w3.org/2006/time#timeZone> a rdf:Property ;
  rdfs:label "in time zone"@en ;
  rdfs:comment "The time zone for clock elements in the temporal position"@en ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDateTimeDescription> ;
  rdfs:range <http://www.w3.org/2006/time#TimeZone> .

<http://www.w3id.org/ecsel-dr-PWR#N-Channel_Configuration> a rdfs:Class ;
  rdfs:label "N-Channel Configuration" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Device_Configuration> .

<http://www.w3id.org/ecsel-dr-AH#AH_DeviceRegistrySystem_SySDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system_SySDD> .

<http://www.w3.org/2006/time#TimePosition> a rdfs:Class ;
  rdfs:label "Time position"@en ;
  rdfs:comment "A temporal position described using either a (nominal) value from an ordinal reference system, or a (numeric) value in a temporal coordinate system. "@en ;
  rdfs:subClassOf <http://www.w3.org/2006/time#TemporalPosition> .

<http://www.w3.org/2006/time#numericPosition> a rdf:Property ;
  rdfs:label "Numeric value of temporal position"@en ;
  rdfs:comment "The (numeric) value indicating position within a temporal coordinate system "@en ;
  rdfs:domain <http://www.w3.org/2006/time#TimePosition> ;
  rdfs:range xsd:decimal .

<http://www.w3.org/2006/time#nominalPosition> a rdf:Property ;
  rdfs:label "Name of temporal position"@en ;
  rdfs:comment "The (nominal) value indicating temporal position in an ordinal reference system "@en ;
  rdfs:domain <http://www.w3.org/2006/time#TimePosition> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AT#ISO-Standard> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Standard> .

<http://www.w3id.org/ecsel-dr-AT#standardOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AT#Standard> ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-AT#SOSA> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Ontology> .

<http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-RAMI40#UsedDate> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-RAMI40#Date> .

<http://www.w3id.org/ecsel-dr-RAMI40#hasDate> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#Date> ;
  rdfs:range xsd:dateTime .

<http://www.w3id.org/ecsel-dr-AT#OSI_L1_PhysicalLink> a rdfs:Class ;
  rdfs:label "Datenübertragungsschicht"@de ;
  rdfs:comment """Concerned with the transmission and reception of unstructured raw bit stream over the physical medium. 
Physical structure can be wired (cables, hubs) or wireless (radio wave technologies with antennas, base stations etc.). 
Topics: Data encoding, Physical medium attachment, Transmission technique, Baseband or Broadband, physical medium transmission: Bits and Volts.
Central device: Hub."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_DetailedLayer> .

<http://www.w3id.org/ecsel-dr-AT#hasDataTransmissionUnit> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AT#DataTransmissionUnit> .

<http://www.w3id.org/ecsel-dr-AT#OSI_AL4_ApplicationLayer> a rdfs:Class ;
  rdfs:label "Aggregated Application Layer"@en , "Anwendungsschicht"@de ;
  rdfs:comment """Corresponds to ISO/OSI layers 5, 6 and 7. 
Contains all protocols which cooperate with application programs and use the network infrastructure for exchange of application-specific data."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_AggregatedLayer> .

<http://www.w3id.org/ecsel-dr-AT#containsOSILayer> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AT#OSI_AggregatedLayer> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AT#OSI_DetailedLayer> .

<http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution_WithSensor> a rdfs:Class ;
  rdfs:comment "Motor control and drive solution with sensor" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> .

<http://purl.org/ontology/is/core#InfoService> a rdfs:Class ;
  rdfs:subClassOf <http://purl.org/dc/dcmitype/Service> .

<http://www.w3id.org/ecsel-dr-PMV#isOutputOf> a rdf:Property ;
  rdfs:label "isOutputOf" ;
  rdfs:comment "Physical or non-physical output is produced by a function in a process flow." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Output> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Function> .

<http://www.w3id.org/ecsel-dr-PMV#isInputOf> a rdf:Property ;
  rdfs:label "isInputFor" ;
  rdfs:comment "An external physical or non-physical input is used in a function in a process flow and is therefore input of it." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Input> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Function> .

<http://www.w3.org/2006/time#January> a rdfs:Class ;
  rdfs:label "January" ;
  rdfs:subClassOf <http://www.w3.org/2006/time#DateTimeDescription> .

<http://www.w3id.org/ecsel-dr-SCP#SSO_Stocks> a rdfs:Class ;
  rdfs:label "SSO_Stocks"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#OperationalDemand> .

<http://www.w3id.org/ecsel-dr-SCP#transferTo> a rdf:Property ;
  rdfs:label "transferTo"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#OperationalDemand> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#PrioritizedDemand> .

<http://www.w3id.org/ecsel-dr-AH#Arrowhead> a rdfs:Class ;
  rdfs:label "AH"@en ;
  rdfs:comment """The Arrowhead Framework specifies an overall system architecture with at least 6 hierarchy levels. These levels are (bottom up): 
Level 1: Method  
Level 2: Service 
Level 3: System 
Level 4: Device 
Level 5: Local Cloud
Level 6: Network of Local Clouds. 
These hierarchy relations are reflected by specific object properties (e.g. hasMethod, containsDevice) and their inverses (isMethodOf, isDeviceIn). In addition, a super property for all these specific hierarchy relations and its inverse exists: isArchitecturalPartOf and hasArchitecturalPart. This super properties are intended to make the structural similarity between the hierarchical object properties visible: the define the relations between entities of neighbored levels of the system architecture. 
Level 6 may further be divided into several sub-levels like network of local clouds at a plant, network of plants of a company, network of companies in a supply chain, network of supply chains in an industry etc. 
Author: H. Baumgaertel, 2019-03-25"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Service-oriented_Architecture> .

<http://www.w3id.org/ecsel-dr-AH#hasProperty> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Service-oriented_Architecture> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#SoA_property> .

<http://www.w3id.org/ecsel-dr-AH#definesCompliantService> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Service-oriented_Architecture> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Service> .

<http://www.w3id.org/ecsel-dr-AH#definesCompliantSystem> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Service-oriented_Architecture> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Software_system> .

<http://www.w3id.org/ecsel-dr-AH#definesCompliantSystemArchitecture> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Service-oriented_Architecture> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#System-of-Systems> .

<http://www.w3id.org/ecsel-dr-AH#definesCompliantDocumentation> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Service-oriented_Architecture> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#ProcessGroupMap> a rdfs:Class ;
  rdfs:label "Process Group Map" ;
  rdfs:comment "A set of a processes covering a single business area. Usually under the ownership of one business process owner and aligning with a function." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#Model> .

<http://www.w3id.org/ecsel-dr-PMV#contains> a rdf:Property ;
  rdfs:label "contains" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Model> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#connectedTo> a rdf:Property ;
  rdfs:label "connectedTo" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Model> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Model> .

<http://www.w3id.org/ecsel-dr-SO#Furnace> a rdfs:Class ;
  rdfs:comment "each furnace consists of two chambers with one tool in each chamber."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Tool> .

<http://www.w3id.org/ecsel-dr-SO#hasRobotLoadingTime> a rdf:Property ;
  rdfs:comment "length of, or element of the length of, a temporal extent expressed in hours"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Tool> ;
  rdfs:range xsd:decimal .

<http://www.w3id.org/ecsel-dr-SO#hasMeanTimeOffLine> a rdf:Property ;
  rdfs:comment "length of, or element of the length of, a temporal extent expressed in hours"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Tool> ;
  rdfs:range xsd:decimal .

<http://www.w3id.org/ecsel-dr-SO#hasToolAvailability> a rdf:Property ;
  rdfs:comment "is tool available? boolean YES/NO"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Tool> ;
  rdfs:range xsd:boolean .

<http://www.w3id.org/ecsel-dr-SO#hasRobotUnloadingTime> a rdf:Property ;
  rdfs:comment "length of, or element of the length of, a temporal extent expressed in hours"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Tool> ;
  rdfs:range xsd:decimal .

<http://www.w3id.org/ecsel-dr-SO#isPreceededBy> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Tool> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Timecoupling> .

<http://www.w3id.org/ecsel-dr-SO#needsPurge> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Tool> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Purge> .

<http://www.w3id.org/ecsel-dr-SO#hasEquipment> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Tool> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Equipment> .

<http://www.w3id.org/ecsel-dr-PWR#Software&Services> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#InformationTechnology> .

<http://www.w3id.org/ecsel-dr-SCP#BottleneckResource> a rdfs:Class ;
  rdfs:label "BottleneckResource"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#ResourceCapacity> .

<http://www.w3id.org/ecsel-dr-SCP#useIn> a rdf:Property ;
  rdfs:label "useIn"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#BottleneckResource> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#ResourceCapacity> .

<http://www.w3id.org/ecsel-dr-SCP#resultTo> a rdf:Property ;
  rdfs:label "resultTo"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#BottleneckResource> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#CapacityBottleneck> .

<http://www.w3id.org/ecsel-dr-SCP#matchTO> a rdf:Property ;
  rdfs:label "matchTO"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#AggregatedCapacity> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#MarketingDemands> .

<http://www.w3id.org/ecsel-dr-AT#IMAP> a rdfs:Class ;
  rdfs:label "Internet Message Access Protocol"@en ;
  rdfs:comment """The Internet Message Access Protocol (IMAP), originally Interactive Mail Access Protocol, is a network protocol that provides a network file system for e-mail.
IMAP was designed in the 1980s with the advent of personal computers to resolve in mail communication dependencies of individual client computers. To do this, IMAP extends Post Office Protocol (POP) features and procedures so that users can store and leave their mail, folder structures, and settings on their (mail) servers. The (PC) clients access the information directly on the servers directly online and may need to accommodate copies of it. While a user of POP either has lost all emails or has already deleted emails after losing his PC, an IMAP user keeps his emails on the servers and, even across several and different clients, unified access."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-AT#ControlDevice> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Device> .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer0_PhysicalProcess> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer> .

<http://www.w3id.org/ecsel-dr-AT#W3C_L4_SemanticsRepresentation> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#SMQTT> a rdfs:Class ;
  rdfs:comment """Abstract:
Rapid innovations in the area of digital things and Information Communication Technology are driving rapid deployment of Internet of Things (IoT) around the globe. Device to Device communications (D2D) in IoT are envisaged through various protocols such as Constrained Access Protocol (CoAP), Message Queue Telemetry Transport (MQTT) and MQTT-SN (for sensor networks). One of the major concerns in the deployment of IoT is to ensure the security of devices and D2D communications. Besides, existing communication protocols for IoT are devoid of security features. To address this, we propose a secure version of MQTT and MQTT-SN protocols (SMQTT and SMQTT-SN) in which security feature is augmented to the existing MQTT protocol based on Key/Cipher text Policy-Attribute Based Encryption(KP/CP-ABE) using lightweight Elliptic Curve Cryptography. Further we demonstrate feasibility of SMQTT and SMQTT-SNprotocols for various IoT requirements through simulations and evaluate their performance.
Published in: Communication Systems and Network Technologies (CSNT), 2015 Fifth International Conference on"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#MQTT_TCPIP_based> .

<http://www.w3id.org/ecsel-dr-AT#XHTML> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L2_DataSyntax> .

<http://www.w3id.org/ecsel-dr-AH#AH_GatekeeperSystem_SySDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system_SySDD> .

<http://www.w3id.org/ecsel-dr-AT#WIMAX_802_16> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> .

<http://www.w3id.org/ecsel-dr-SO#Product_Group> a rdfs:Class ;
  rdfs:comment "A (main) product group is a grouping of products for calculation or sales purposes. The scope includes finished and unfinished products of one product line."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Product> .

<http://www.w3id.org/ecsel-dr-SO#hasOperation> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Product> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Operation> .

<http://www.w3.org/ns/sosa/Actuator> a rdfs:Class ;
  rdfs:label "Actuator"@en ;
  rdfs:comment "A device that is used by, or implements, an (Actuation) Procedure that changes the state of the world."@en ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/System> .

<http://www.w3.org/ns/sosa/isHostedBy> a rdf:Property ;
  rdfs:label "is hosted by"@en ;
  rdfs:comment "Relation between a Sensor, Actuator, Sampler, or Platform, and the Platform that it is mounted on or hosted by."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Sampler> ;
  rdfs:range <http://www.w3.org/ns/sosa/Platform> .

<http://www.w3.org/ns/ssn/forProperty> a rdf:Property ;
  rdfs:label "for property"@en ;
  rdfs:comment "A relation between some aspect of an entity and a Property."@en ;
  rdfs:range <http://www.w3.org/ns/sosa/ActuatableProperty> , <http://www.w3.org/ns/ssn/Property> .

<http://www.w3.org/ns/ssn/systems/hasOperatingRange> a rdf:Property ;
  rdfs:label "has operating range" ;
  rdfs:comment "Relation from a System to an OperatingRange describing the normal operating environment of the System." ;
  rdfs:domain <http://www.w3.org/ns/ssn/System> ;
  rdfs:range <http://www.w3.org/ns/ssn/systems/OperatingRange> ;
  rdfs:subPropertyOf <http://www.w3.org/ns/ssn/hasProperty> .

<http://www.w3.org/ns/ssn/systems/hasSystemCapability> a rdf:Property ;
  rdfs:label "has system capability" ;
  rdfs:comment "Relation from a System to a SystemCapability describing the capabilities of the System under certain Conditions." ;
  rdfs:domain <http://www.w3.org/ns/ssn/System> ;
  rdfs:range <http://www.w3.org/ns/ssn/systems/SystemCapability> ;
  rdfs:subPropertyOf <http://www.w3.org/ns/ssn/hasProperty> .

<http://www.w3.org/ns/ssn/implements> a rdf:Property ;
  rdfs:label "implements"@en ;
  rdfs:comment "Relation between an entity that implements a Procedure in some executable way and the Procedure (an algorithm, procedure or method)."@en ;
  rdfs:range <http://www.w3.org/ns/sosa/Procedure> .

<http://www.w3.org/ns/sosa/madeActuation> a rdf:Property ;
  rdfs:label "made actuation"@en ;
  rdfs:comment "Relation between an Actuator and the Actuation it has made."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Actuator> ;
  rdfs:range <http://www.w3.org/ns/sosa/Actuation> .

<http://www.w3.org/ns/ssn/hasDeployment> a rdf:Property ;
  rdfs:label "has deployment"@en ;
  rdfs:comment "Relation between a System and a Deployment, recording that the System is deployed in that Deployment."@en ;
  rdfs:domain <http://www.w3.org/ns/ssn/System> ;
  rdfs:range <http://www.w3.org/ns/ssn/Deployment> .

<http://www.w3.org/ns/ssn/hasSubSystem> a rdf:Property ;
  rdfs:label "has subsystem"@en ;
  rdfs:comment "Relation between a System and its component parts."@en ;
  rdfs:domain <http://www.w3.org/ns/ssn/System> ;
  rdfs:range <http://www.w3.org/ns/ssn/System> .

<http://www.w3.org/ns/ssn/systems/hasSurvivalRange> a rdf:Property ;
  rdfs:label "has survival range" ;
  rdfs:comment "Relation from a System to SurvivalRange." ;
  rdfs:domain <http://www.w3.org/ns/ssn/System> ;
  rdfs:range <http://www.w3.org/ns/ssn/systems/SurvivalRange> ;
  rdfs:subPropertyOf <http://www.w3.org/ns/ssn/hasProperty> .

<http://www.w3.org/2006/time#Instant> a rdfs:Class ;
  rdfs:label "Time instant"@en ;
  rdfs:comment "A temporal entity with zero extent or duration"@en ;
  rdfs:subClassOf <http://www.w3.org/2006/time#TemporalEntity> .

<http://www.w3.org/2006/time#inTimePosition> a rdf:Property ;
  rdfs:label "Time position"@en ;
  rdfs:comment "Position of a time instant expressed as a TimePosition"@en ;
  rdfs:domain <http://www.w3.org/2006/time#Instant> ;
  rdfs:range <http://www.w3.org/2006/time#TimePosition> ;
  rdfs:subPropertyOf <http://www.w3.org/2006/time#inTemporalPosition> .

<http://www.w3.org/2006/time#inXSDDateTimeStamp> a rdf:Property ;
  rdfs:label "in XSD Date-Time-Stamp"@en ;
  rdfs:comment "Position of an instant, expressed using xsd:dateTimeStamp"@en ;
  rdfs:domain <http://www.w3.org/2006/time#Instant> ;
  rdfs:range xsd:dateTimeStamp .

<http://www.w3.org/2006/time#hasTemporalDuration> a rdf:Property ;
  rdfs:label "has temporal duration"@en ;
  rdfs:comment "Duration of a temporal entity."@en ;
  rdfs:domain <http://www.w3.org/2006/time#TemporalEntity> ;
  rdfs:range <http://www.w3.org/2006/time#TemporalDuration> .

<http://www.w3.org/2006/time#after> a rdf:Property ;
  rdfs:label "after"@en ;
  rdfs:comment "Gives directionality to time. If a temporal entity T1 is after another temporal entity T2, then the beginning of T1 is after the end of T2."@en ;
  rdfs:domain <http://www.w3.org/2006/time#TemporalEntity> ;
  rdfs:range <http://www.w3.org/2006/time#TemporalEntity> .

<http://www.w3.org/2006/time#inXSDgYear> a rdf:Property ;
  rdfs:label "in XSD g-Year"@en ;
  rdfs:comment "Position of an instant, expressed using xsd:gYear"@en ;
  rdfs:domain <http://www.w3.org/2006/time#Instant> ;
  rdfs:range xsd:gYear .

<http://www.w3.org/2006/time#inDateTime> a rdf:Property ;
  rdfs:label "in date-time description"@en ;
  rdfs:comment "Position of an instant, expressed using a structured description"@en ;
  rdfs:domain <http://www.w3.org/2006/time#Instant> ;
  rdfs:range <http://www.w3.org/2006/time#GeneralDateTimeDescription> ;
  rdfs:subPropertyOf <http://www.w3.org/2006/time#inTemporalPosition> .

<http://www.w3.org/2006/time#inXSDDateTime> a rdf:Property ;
  rdfs:label "in XSD Date-Time"@en ;
  rdfs:comment "Position of an instant, expressed using xsd:dateTime"@en ;
  rdfs:domain <http://www.w3.org/2006/time#Instant> ;
  rdfs:range xsd:dateTime .

<http://www.w3.org/2006/time#hasXSDDuration> a rdf:Property ;
  rdfs:label "has XSD duration"@en ;
  rdfs:comment "Extent of a temporal entity, expressed using xsd:duration"@en ;
  rdfs:domain <http://www.w3.org/2006/time#TemporalEntity> ;
  rdfs:range xsd:duration .

<http://www.w3.org/2006/time#before> a rdf:Property ;
  rdfs:label "before"@en ;
  rdfs:comment "Gives directionality to time. If a temporal entity T1 is before another temporal entity T2, then the end of T1 is before the beginning of T2. Thus, \"before\" can be considered to be basic to instants and derived for intervals."@en ;
  rdfs:domain <http://www.w3.org/2006/time#TemporalEntity> ;
  rdfs:range <http://www.w3.org/2006/time#TemporalEntity> .

<http://www.w3.org/2006/time#inXSDgYearMonth> a rdf:Property ;
  rdfs:label "in XSD g-YearMonth"@en ;
  rdfs:comment "Position of an instant, expressed using xsd:gYearMonth"@en ;
  rdfs:domain <http://www.w3.org/2006/time#Instant> ;
  rdfs:range xsd:gYearMonth .

<http://www.w3.org/2006/time#hasEnd> a rdf:Property ;
  rdfs:label "has end"@en ;
  rdfs:comment "End of a temporal entity."@en ;
  rdfs:domain <http://www.w3.org/2006/time#TemporalEntity> ;
  rdfs:range <http://www.w3.org/2006/time#Instant> ;
  rdfs:subPropertyOf <http://www.w3.org/2006/time#hasTime> .

<http://www.w3.org/2006/time#inXSDDate> a rdf:Property ;
  rdfs:label "in XSD date"@en ;
  rdfs:comment "Position of an instant, expressed using xsd:date"@en ;
  rdfs:domain <http://www.w3.org/2006/time#Instant> ;
  rdfs:range xsd:date .

<http://www.w3.org/2006/time#hasBeginning> a rdf:Property ;
  rdfs:label "has beginning"@en ;
  rdfs:comment "Beginning of a temporal entity."@en ;
  rdfs:domain <http://www.w3.org/2006/time#TemporalEntity> ;
  rdfs:range <http://www.w3.org/2006/time#Instant> ;
  rdfs:subPropertyOf <http://www.w3.org/2006/time#hasTime> .

<http://www.w3.org/2006/time#inTemporalPosition> a rdf:Property ;
  rdfs:label "Temporal position"@en ;
  rdfs:comment "Position of a time instant"@en ;
  rdfs:domain <http://www.w3.org/2006/time#Instant> ;
  rdfs:range <http://www.w3.org/2006/time#TemporalPosition> .

<http://www.w3id.org/ecsel-dr-AH#AH_system> a rdfs:Class ;
  rdfs:label "Arrowhead component"@en ;
  rdfs:comment "An Arrowhead compliant system (implemented in software and executed in a device) is what is providing and/or consuming Arrowhead Framework services."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Software_system> .

<http://www.w3id.org/ecsel-dr-AH#isAHSystemDocumentedBy> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#AH_system> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#AH_system_documentation> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#isSystemDocumentedBy> .

<http://www.w3id.org/ecsel-dr-AH#isSystemDocumentedBy> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Software_system> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#System_documentation> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#isDocumentedBy> .

<http://www.w3id.org/ecsel-dr-AH#produces> a rdf:Property ;
  rdfs:comment """Relation expressing that a software system produces a service. 
Equivalent names for this relation include
- offers
- provides 
- isServiceProducerOf 
Since Arrowhead uses the pair produce / consume and corresponding service producer / service consumer adressing the relations and the software systems, this ontology uses these names for the relations too. 
If it is needed, object properties with other names can be added and stated to be equivalent to these ones."""@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Software_system> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Service> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#hasArchitecturalPart> .

<http://www.w3id.org/ecsel-dr-AH#runsOn> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Software_system> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Device> .

<http://www.w3id.org/ecsel-dr-AH#isServiceProducerOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Software_system> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Service> .

<http://www.w3id.org/ecsel-dr-AH#isHostedBy> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Software_system> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Device> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#isArchitecturalPartOf> .

<http://www.w3id.org/ecsel-dr-AH#AH_DeviceDiscoveryService_IDD> a rdfs:Class ;
  rdfs:comment "Interface Design Description of the Arrowhead non-mandatory core service (automation supporting service) DeviceDiscovery, provided by the AH system DeviceRegistry."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service_IDD> .

<http://www.w3id.org/ecsel-dr-PWR#Electric_Vehicle_Charging> a rdfs:Class ;
  rdfs:label "Electric Vehicle Charging" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#ApplicationArea> .

<http://www.w3.org/ns/ssn/systems/Resolution> a rdfs:Class ;
  rdfs:label "Resolution" ;
  rdfs:comment "As an actuator capability: The closeness of agreement between replicate Actuations for an unchanged or similar command: i.e., a measure of an Actuator's ability to consistently reproduce an Actuations, under the defined Conditions." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/systems/SystemProperty> .

<http://www.w3.org/ns/ssn/isPropertyOf> a rdf:Property ;
  rdfs:label "is property of"@en ;
  rdfs:comment "Relation between a Property and the entity it belongs to."@en ;
  rdfs:domain <http://www.w3.org/ns/ssn/Property> ;
  rdfs:range <http://www.w3.org/ns/sosa/FeatureOfInterest> .

<http://www.w3id.org/ecsel-dr-OOSMP#Solution> a rdfs:Class ;
  rdfs:label "Solution" ;
  rdfs:comment "A solution is a combination of products which is produced or assembled by an organization. Further, a solution is sold to a customer and solves a specific problem / fulfills a specific need." .

<http://www.w3id.org/ecsel-dr-AT#MachineSimulationSystem> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Simulation-System> .

<http://www.w3id.org/ecsel-dr-AT#Digital-Factory-System> a rdfs:Class ;
  rdfs:comment """The term \"Digital Factory\" is used in different meanings today and should hence not longer be used. 
It should be replaced by more specific terms like \"Digital Factory Planning system\" or \"Digital Factory Twin\". 
Originally, Digital Factory referred to software tools for computer-aided planning, design, engineering and simulation of production, manufacturing, or assembly systems. These tools supplemented CAD-based tools for factory layout planning and tools for computer-aided tools for production engineering (work plan preparation, production process planning) and were glued together with them to PLM software suites. 
As today even CAD-based layout planning and process planning tools are \"digital\" and refer to the factory, the terms \"Digital Factory tool\" and \"Production Engineering tool\" more and more converge. 
At the same time, automation vendors start to use the concept \"Digital Factory\" to address online monitoring and control tools for production systems. In this meaning, the term is a synonym for \"Digital Factory Twin\" or \"Digital Twin of a Factory\". 
The important difference between these two meanings is the phase in the life cycle in which the tool is used: Manufacturing Planning / Eingineering is conducted mainly in the first two lifecycle phases in which the product (type, class) is created, designed, and engineered, as well as the corresponding production system. 
The online monitoring and control is conducted during the third phase, in which the product individuals are produced on the existing production system. 
Hartwig Baumgaertel, 2018-11-12"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-AT#PLM1_Vendor> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#PLM-System-FirstGeneration> .

<http://www.w3id.org/ecsel-dr-PMV#Role> a rdfs:Class ;
  rdfs:label "Role" ;
  rdfs:comment "Business Role (Person) that performs task." ;
  rdfs:subClassOf <http://xmlns.com/foaf/0.1/Person> .

<http://www.w3id.org/ecsel-dr-PMV#mustBeInformedAbout> a rdf:Property ;
  rdfs:label "mustBeInformedAbout" ;
  rdfs:comment "Role(s) to be informed after/ during the process step is carried out (one-way-communication) (equivalent to I in RACI notation)" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Role> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Task> .

<http://www.w3id.org/ecsel-dr-PMV#contributesTo> a rdf:Property ;
  rdfs:label "contributesTo" ;
  rdfs:comment "Role(s) that contribute(s) to a process step during it is carried out." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Role> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Task> .

<http://www.w3id.org/ecsel-dr-PMV#hasKnowledge> a rdf:Property ;
  rdfs:label "has Knwoledge" ;
  rdfs:comment "Describes the knowledge that is required." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Role> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#carriesOut> a rdf:Property ;
  rdfs:label "carriesOut" ;
  rdfs:comment "Role(s) or Organizational unit(s) that carrries (carry) out the process step (equivalent to R in RACI notation)" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Role> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Task> .

<http://www.w3id.org/ecsel-dr-PMV#hasExperience> a rdf:Property ;
  rdfs:label "has Experience" ;
  rdfs:comment "Describes the experience that is required." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Role> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AT#AppleTalk> a rdfs:Class ;
  rdfs:comment "Outdated, replaced by IP-based service system by Apple, cf. Bonjour."@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_3_4_NetworkTechnology> .

<http://www.w3id.org/ecsel-dr-PWR#Variable_Resistance> a rdfs:Class ;
  rdfs:label "Variable Resistance" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Resistance> .

<http://www.w3id.org/ecsel-dr-AT#AssemblyLinePlanning> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#PLM1_Module> .

<http://www.w3id.org/ecsel-dr-PWR#Information_Object> a rdfs:Class ;
  rdfs:label "Information Object" ;
  rdfs:comment "A piece of information, such as a musical composition, a text, a word, a picture, independently from how it is concretely realized." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#InformationEntity> .

<http://www.w3id.org/ecsel-dr-SCP#ConsignmentOrders> a rdfs:Class ;
  rdfs:label "ConsignmentOrders"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#Orders> .

<http://www.w3id.org/ecsel-dr-PMV#Function> a rdfs:Class ;
  rdfs:label "Function" ;
  rdfs:comment "They are the active elements of an EPC that represent the activities of a modelled process and again raise events upon completion. The extended event driven process chain expands the semantic of functions, since they may be associated with the organizational unit performing the function or the data needed and created as output by the function." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#ModelElement> .

<http://www.w3id.org/ecsel-dr-PMV#executes> a rdf:Property ;
  rdfs:label "executes" ;
  rdfs:comment "A function in a process flow excutes software." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Function> ;
  rdfs:range <http://purl.org/dc/dcmitype/Software> .

<http://www.w3id.org/ecsel-dr-PMV#uses> a rdf:Property ;
  rdfs:label "uses" ;
  rdfs:comment "A function in a process flow uses external resources like machines or computer hardware during its execution." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Function> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#isUnderResponsibilityOf> a rdf:Property ;
  rdfs:label "isUnderResponsibilityOf" ;
  rdfs:comment "The execution of a function in a process flow is under the responsibility of an organizational unit." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Function> ;
  rdfs:range <http://www.w3.org/ns/org#OrganizationalUnit> .

<http://www.w3id.org/ecsel-dr-PMV#hasOutput> a rdf:Property ;
  rdfs:label "hasOutput" ;
  rdfs:comment "A function in a process flow produces a physical or non-physical output." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Function> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Output> .

<http://www.w3id.org/ecsel-dr-PMV#hasSubModel> a rdf:Property ;
  rdfs:label "hasSubModel" ;
  rdfs:comment "Denotes to which instance of \"Process\" an instance of a \"Process Element\" belongs." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Function> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Model> .

<http://www.w3id.org/ecsel-dr-PMV#flow> a rdf:Property ;
  rdfs:label "flow" ;
  rdfs:comment "Enables the modelling of the process flow by logically connecting the different process elements. Therefore, the domain and the range are set to a \"Process Element\"." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#ModelElement> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#ModelElement> .

<http://www.w3id.org/ecsel-dr-PMV#isProcessedBy> a rdf:Property ;
  rdfs:label "isProcessedBy" ;
  rdfs:comment "The execution of a function in a process flow is processed by a person (human output)." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Function> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#HumanOutput> .

<http://www.w3id.org/ecsel-dr-PMV#isControlledBy> a rdf:Property ;
  rdfs:label "isControlledBy" ;
  rdfs:comment "The result of a function in a process flow is controlled by a goal." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Function> ;
  rdfs:range <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Goal> .

<http://www.w3id.org/ecsel-dr-PMV#relevantFor> a rdf:Property ;
  rdfs:label "relevantFor" ;
  rdfs:comment "An object is relevant for EPCs and value-added chain diagrams." ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#transforms> a rdf:Property ;
  rdfs:label "transforms" ;
  rdfs:comment "A function in a process flow transforms environmental data like work schedules." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Function> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#EnvironmentalData> .

<http://www.w3id.org/ecsel-dr-PMV#belongsTo> a rdf:Property ;
  rdfs:label "belongsTo" ;
  rdfs:comment "Denotes the connection between a \"Function\" and another \"Process\" as this process may deliver an output used in this function." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#ModelElement> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Model> .

<http://www.w3id.org/ecsel-dr-AT#ActuatorDevice> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Device> .

<http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitectureImplementation> a rdfs:Class ;
  rdfs:comment """Implementations or Realizations of Service-oriented Architectures.

This class contains existing implementations, i.e. software systems, which are designed as Service-oriented Architectures. That is, these systems realize service-oriented communication between their participants / components. (2018-08-04 HB)."""@en .

<http://www.w3id.org/ecsel-dr-AH#AH_OrchestrationSystem_SySD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_system_SySD> .

<http://www.w3id.org/ecsel-dr-AH#refersToIDD> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#System_Description_SySD> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Interface_Design_Description_IDD> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#refersTo> .

<http://www.w3id.org/ecsel-dr-AT#ERP-System> a rdfs:Class ;
  rdfs:label "Enterprise Resource Planning System" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-SO#Deposition> a rdfs:Class ;
  rdfs:comment "the deposition process, or chemical vapor deposition (CVD) is a process whereby a fiolm is deposited by reacting chemicals together in the gaseous or vapor phase to form a film. The gases or vapors utilized for CVD are compounds that contain the element to be deposited and that may be inducted to react with a substrate or other gas(es) to deposit a film. The CVD reactoin may be thermally activated, plasma induced, plasma enhanced CVD or activated by light in photon induced CVD."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Workshop> .

<http://www.w3id.org/ecsel-dr-AT#RDF> a rdfs:Class ;
  rdfs:label "Resource Description Framework"@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#DataLanguage_SemanticWebStackBased> .

<http://www.w3id.org/ecsel-dr-AH#System_documentation> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AH#documents> a rdf:Property ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AH#hasPart> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Documentation_document> .

<http://www.w3id.org/ecsel-dr-OOSMP#ProductLine> a rdfs:Class ;
  rdfs:comment "A product line is an organizational unit that can be assigned to a business line and directly owns/is responsible for products." ;
  rdfs:subClassOf <http://www.w3.org/ns/org#OrganizationalUnit> .

<http://www.w3id.org/ecsel-dr-OOSMP#owns> a rdf:Property ;
  rdfs:domain <http://www.w3.org/ns/org#OrganizationalUnit> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#Product> .

<http://www.w3id.org/ecsel-dr-OOSMP#responsibleForApplicationArea> a rdf:Property ;
  rdfs:domain <http://www.w3.org/ns/org#OrganizationalUnit> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> .

<http://www.w3.org/ns/org#unitOf> a rdf:Property ;
  rdfs:domain <http://www.w3.org/ns/org#OrganizationalUnit> ;
  rdfs:range <http://www.w3.org/ns/org#Organization> .

<http://www.w3id.org/ecsel-dr-OOSMP#subUnitOfBusinessLine> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#ProductLine> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#BusinessLine> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#subUnitOf> .

<http://www.w3id.org/ecsel-dr-OOSMP#identifier_organizationalUnit> a rdf:Property ;
  rdfs:label "Unit ID" ;
  rdfs:comment "Any identifier (ID) of an organizational unit" ;
  rdfs:domain <http://www.w3.org/ns/org#OrganizationalUnit> ;
  rdfs:range xsd:int ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#identifier> .

<http://www.w3id.org/ecsel-dr-OOSMP#subUnitOf> a rdf:Property ;
  rdfs:domain <http://www.w3.org/ns/org#OrganizationalUnit> ;
  rdfs:range <http://www.w3.org/ns/org#OrganizationalUnit> .

<http://www.w3id.org/ecsel-dr-OOSMP#responsibleForApplicationArea_ProductLine> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#ProductLine> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#responsibleForApplicationArea> .

<http://www.w3id.org/ecsel-dr-PMV#isResponsibleFor> a rdf:Property ;
  rdfs:label "isResponsibleFor" ;
  rdfs:comment "An organizational unit is responible for a function in a process flow." ;
  rdfs:domain <http://www.w3.org/ns/org#OrganizationalUnit> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Function> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasSubUnit> a rdf:Property ;
  rdfs:domain <http://www.w3.org/ns/org#OrganizationalUnit> ;
  rdfs:range <http://www.w3.org/ns/org#OrganizationalUnit> .

<http://www.w3id.org/ecsel-dr-SO#Diffusion> a rdfs:Class ;
  rdfs:comment "diffusion is a process whereby a substance redistributes from an area of relatively high concentration to an area of relatively low concentration due to random thermal motion. The larger the concentration gradient the faster diffusion occurs for a given temperature, conversely, the higher the temperature the faster diffusion occurs for a given concentration gradient."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Workshop> .

<http://www.w3id.org/ecsel-dr-OOSMP#AngleSensor> a rdfs:Class ;
  rdfs:label "Angle Sensor" ;
  rdfs:comment "Infineon offers a family of angle sensors based on integrated Magneto Resistive (ixMR) technologies. Technologies include today iGMR and AMR. The sensors detect the orientation of an applied magnetic field by measuring sine and cosine angle components with monolithically integrated magneto resistive elements. ixMR technology is now widely used in automotive and industrial applications and provides a wide range of benefits. Our iAMR sensors are ideal for applications with the highest accuracy requirements. Our iAMR technology offers best performance over temperature, lifetime and magnetic field range. They are pre-calibrated and ready to use." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#MagneticPositionSensor> .

<http://www.ontologydesignpatterns.org/cp/owl/informationrealization.owl#InformationObject> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PMV#OR> a rdfs:Class ;
  rdfs:label "OR" ;
  rdfs:comment "At least one of the possible process paths must be followed." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#Connector> .

<http://www.w3id.org/ecsel-dr-AT#MQTT-SN> a rdfs:Class ;
  rdfs:label "MQTT for Sensor Networks"@en , "MQTT für Sensorgeräte"@de ;
  rdfs:comment """Specification of MQTT-SN (formerly MQTT-S), Version 1.2
Designed for embedded devices on non-TCP / IP networks, such as ZigBee. MQTT-SN is a message protocol according to the observer pattern for sensor networks. It extends MQTT (which is originally designed on top of TCP / IP infrastructure) and is optimized for use with sensor and actuator solutions. The original name was MQTT-S. However, this generated misunderstandings (s for secure?), So that in 2013 a renaming was initiated in MQTT-SN (SN for Sensor Networks).

Protocol
MQTT is a client-server protocol. Clients send messages to the server (\"broker\") after connection with a topic that hierarchically classifies the message; for example kitchen/fridge/temperature or car/wheel/3/barometric_pressure. Clients can subscribe to these topics, with the server passing the received messages to the appropriate subscribers.

Messages always consist of a topic and the message content. Messages are sent with a definable Quality of Service: at most once (the message is sent once and may not arrive when the connection is lost), at least once (the message is sent until receipt is acknowledged and can be repeated at the recipient arrive) and exactly once (this ensures that the message arrives exactly once even when the connection is interrupted). In addition, the server can be instructed with the retain flag to cache the message for this topic. Clients who subscribe to this topic are the first to receive the cached message.

When establishing a connection, clients can define a \"last will\" in the form of a message. If the connection to the client is lost, this message is published and sent to the appropriate subscribers."""@en , """Spezifikation von MQTT-SN (ehemals MQTT-S), Version 1.2 
    Ausgelegt für eingebettete Geräte in non-TCP/IP-Netzwerken, wie zum Beispiel ZigBee. MQTT-SN ist ein Nachrichtenprotokoll nach dem Beobachter-Muster für Sensornetze. Es erweitert MQTT für die Nutzung über TCP/IP-Infrastruktur hinaus und ist besonders optimiert für die Nutzung mit Sensor- und Aktor-Lösungen. Der ursprüngliche Name war MQTT-S. Dieser erzeugte jedoch Missverständnisse (s für secure?), so dass 2013 eine Umbenennung in MQTT-SN angestoßen wurde (SN für Sensor Networks).

Protokoll
MQTT ist ein Client-Server-Protokoll. Clients senden dem Server (“Broker”) nach Verbindungsaufbau Nachrichten mit einem Topic, welches die Nachricht hierarchisch einstuft; zum Beispiel Küche/Kühlschrank/Temperatur oder Auto/Rad/3/Luftdruck. Clients können diese Topics abonnieren, wobei der Server die empfangenen Nachrichten an die entsprechenden Abonnenten weiterleitet.

Nachrichten bestehen immer aus einem Topic und dem Nachrichteninhalt. Nachrichten werden mit einem definierbaren Quality of Service versendet: at most once (die Nachricht wird einmal gesendet und kommt bei Verbindungsunterbrechung möglicherweise nicht an), at least once (die Nachricht wird so lange gesendet, bis der Empfang bestätigt wird, und kann beim Empfänger mehrfach ankommen) und exactly once (hierbei wird sichergestellt, dass die Nachricht auch bei Verbindungsunterbrechung genau einmal ankommt). Außerdem kann mit dem Retain-Flag der Server angewiesen werden, die Nachricht zu diesem Topic zwischenzuspeichern. Clients, die neu auf dieses Thema abonnieren, bekommen als erstes die zwischengespeicherte Nachricht zugestellt.

Beim Verbindungsaufbau können Clients einen „letzten Willen“ in Form einer Nachricht definieren. Falls die Verbindung zum Client verloren geht, wird diese Nachricht publiziert und dabei an die entsprechenden Abonnenten gesendet."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#MQTT_nonTCPIP_based> .

<http://www.w3id.org/ecsel-dr-AT#W3C_L1_WebPlatform> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#SMTP> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-SO#Operator> a rdfs:Class ;
  rdfs:comment "a user that interacts with the equipment only to the degree necessary for the equipment to perform its intended function."@en .

<http://www.w3id.org/ecsel-dr-SO#manuallyLoads> a rdf:Property ;
  rdfs:comment "the operator will load the wafer into the wip station and then the robot will load the wafers from the wip station to the tool" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operator> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#WIP_Station> .

<http://www.w3id.org/ecsel-dr-SO#hasLoadTimeWait> a rdf:Property ;
  rdfs:comment "length of, or element of the length of, a temporal extent expressed in hours"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operator> ;
  rdfs:range xsd:decimal .

<http://www.w3id.org/ecsel-dr-SO#isResponsibleFor> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operator> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Planning_Work_Center> .

<http://www.w3id.org/ecsel-dr-SO#unloads> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operator> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Tool> .

<http://www.w3id.org/ecsel-dr-PWR#ApplicationArea> a rdfs:Class ;
  rdfs:comment "The different application ares that the product can be used." .

<http://www.w3id.org/ecsel-dr-AT#EDI_Specification> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L5_DataSemantics> .

<http://www.w3id.org/ecsel-dr-AT#IEC> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#StandardisationOrganization> .

<http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_system_SySDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_core_system_SySDD> .

<http://www.w3id.org/ecsel-dr-AT#OSI_TransportProtocol> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PWR#Interface> a rdfs:Class ;
  rdfs:comment "A common boundary or interconnection between systems, equipment, concepts, or human beings" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Physical_Object> .

<http://www.w3id.org/ecsel-dr-AT#OSI_AL1_NetworkAccessLayer> a rdfs:Class ;
  rdfs:label "Network Access Layer"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_AggregatedLayer> .

<http://www.w3id.org/ecsel-dr-SO#Planning_Work_Center> a rdfs:Class ;
  rdfs:comment "Semiconductor wafers arrive at the planning work center according to a Poisson process in lots with a certain unit size. The planning work center X48- can process three different products which arrive in four different classes."@en .

<http://www.w3id.org/ecsel-dr-SO#consistsOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Planning_Work_Center> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Tool> .

<http://www.w3id.org/ecsel-dr-SO#belongsTo> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Planning_Work_Center> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Furnace_Process> .

<http://www.w3id.org/ecsel-dr-PRIMA#Task> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PRIMA#isTaskOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#Task> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AT#HTTP> a rdfs:Class ;
  rdfs:label "Hypertext Transfer Protocol"@en ;
  rdfs:comment """The Hypertext Transfer Protocol (HTTP) is an application protocol for distributed, collaborative, and hypermedia information systems. HTTP is the foundation of data communication for the WWW.
  – Hypertext is structured text that uses logical links (hyperlinks) between nodes containing text (e.g. HTML, XHTML). HTTP is the protocol to exchange or transfer hypertext.
• HTTP functions as a request–response protocol in the client–server computing model.
  – A web browser, for example, may be the client and an application running on a computer hosting a website may be the server.
  – The client submits an HTTP request message to the server. The server, which provides resources such as HTML files and other content, or performs other functions on behalf of the client, returns a response message to the client.
  – The response contains completion status information about the request and may also contain requested content in its message body.
• HTTP properties (design rationales) include
  – Enable intermediate network elements (hosts) to improve communication, e.g. web cache servers
  – Facilitate communication for clients which do not have a globally routable address, e.g. proxy servers at the boundaries of private networks (cf. local WLAN network with 192.168.2.xxx IPv4 addresses)."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-OOSMP#ApplicationLevel1> a rdfs:Class ;
  rdfs:label "Application Level 1" ;
  rdfs:comment "The top application level which can have several sub application levels (application level 2)" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> .

<http://www.w3id.org/ecsel-dr-OOSMP#subApplicationAreaOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasApplicationLevel2> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationLevel1> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationLevel2> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasSubApplicationArea> .

<http://www.w3id.org/ecsel-dr-OOSMP#belongsToOrganizationalUnit> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> ;
  rdfs:range <http://www.w3.org/ns/org#OrganizationalUnit> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasSubApplicationArea> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> .

<http://www.w3id.org/ecsel-dr-OOSMP#belongsToProductLine> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#ProductLine> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#belongsToOrganizationalUnit> .

<http://www.w3id.org/ecsel-dr-OOSMP#findsApplicationThrough> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AT#DataLanguage_SemanticWebStackBased> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L3_KnowledgeRepresentation> .

<http://www.w3id.org/ecsel-dr-OOSMP#GateDriver> a rdfs:Class ;
  rdfs:label "Gate Driver" ;
  rdfs:comment "A semiconductor product which is used as a gate driver" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> .

<http://www.w3id.org/ecsel-dr-OOSMP#partOfAsGateDriver> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#GateDriver> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#partOf> .

<http://www.w3id.org/ecsel-dr-PWR#Leakage_Current> a rdfs:Class ;
  rdfs:label "Leakage Current" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Property> .

<http://www.w3id.org/ecsel-dr-AT#PLM-System> a rdfs:Class ;
  rdfs:label "Product Lifecycle Management System" ;
  rdfs:comment """General term for software systems which are used during the first phases of a product lifecycle, namely in 
- product design and engineering (e.g. CAD systems, PDM systems) 
- work plan design and optimization 
- manufacturing system design and engineering (factory layout planning, machine, line, workcell, robot design and engineering, process planning, tool engineering, material flow, worker, and robot simulation, ...) 
- automation (system) planning and programming 
- Computer-aided manufacturing preparation (CNC programming, ...) 

First phases of the product lifecycle refers here to the first two of the four phases of a product lifecycle according to the standard IEC62890 (life cycle value stream) which is also one dimension in the RAMI 4.0 model. In these phases, the product is treated as type or class. In the latter phases, product individuals (instances) are treated as they are produced, shipped and sold to a customer. In these phases, the ERP systems are the \"leading systems\" in the companies. 

The relations and communication between PLM and ERP systems are crucial in companies IT architectures. 
H. Baumgaertel, 2018-11-12"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-AT#IT-System> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#ZigBee_RF4CE> a rdfs:Class ;
  rdfs:label "Radio Frequency for Consumer Electronics"@en ;
  rdfs:comment """ZigBee RF4CE
RF4CE ist ein Akronym für radio frequency for consumer electronics. ZigBee-RF4C ist eine weitere auf dem IEEE-802.15.4-Standard aufbauende Spezifikation der ZigBee-Allianz. Sie ist im Jahr 2010 erschienen und ist eine eigenständige Spezifikation. Sie spezifiziert einfache und kostengünstige drahtlose Netzwerke zur Steuerung von Geräten wie etwa Homeentertainment und Lichtsteuerung. Routing wird in diesen Netzwerken nicht unterstützt. Ein fernzusteuerndes Gerät bildet ein eigenes PAN (Personal Area Network). Die Fernsteuerung tritt diesem Netzwerk bei. Um mehrere Geräte zu steuern, partizipiert die Fernsteuerung im Allgemeinen an mehreren PANs. Auch ein fernzusteuerndes Gerät kann Mitglied eines zweiten PANs sein, wenn es selbst fernzusteuernde Aufgaben erfüllt. Wenn der DVD-Player von der Fernbedienung gestartet wird, soll der DVD-Player gleichzeitig den Kanal des Fernsehers wechseln."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_3_4_NetworkTechnology> .

<http://www.w3id.org/ecsel-dr-PWR#ElectronicComponents> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#ElectronicEquipment,Instruments&Components> .

<http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProductStatus> a rdfs:Class ;
  rdfs:label "Semiconductor Product Status" ;
  rdfs:comment "A semiconductor product can have different product states which describe the product characteristics more closely." .

<http://www.w3id.org/ecsel-dr-OOSMP#semiconductorProductStatusOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProductStatus> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> .

<http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service_SD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_core_service_SD> .

<http://www.w3id.org/ecsel-dr-PMV#BP> a rdfs:Class ;
  rdfs:label "Business Process" ;
  rdfs:comment "A Business Process consists of a series of value-creating activities that reach the performance expected by customers and fulfill goals derived from the business strategy." .

<http://www.w3id.org/ecsel-dr-AT#SMQTT-SN> a rdfs:Class ;
  rdfs:comment """Abstract:
Rapid innovations in the area of digital things and Information Communication Technology are driving rapid deployment of Internet of Things (IoT) around the globe. Device to Device communications (D2D) in IoT are envisaged through various protocols such as Constrained Access Protocol (CoAP), Message Queue Telemetry Transport (MQTT) and MQTT-SN (for sensor networks). One of the major concerns in the deployment of IoT is to ensure the security of devices and D2D communications. Besides, existing communication protocols for IoT are devoid of security features. To address this, we propose a secure version of MQTT and MQTT-SN protocols (SMQTT and SMQTT-SN) in which security feature is augmented to the existing MQTT protocol based on Key/Cipher text Policy-Attribute Based Encryption(KP/CP-ABE) using lightweight Elliptic Curve Cryptography. Further we demonstrate feasibility of SMQTT and SMQTT-SNprotocols for various IoT requirements through simulations and evaluate their performance.
Published in: Communication Systems and Network Technologies (CSNT), 2015 Fifth International Conference on"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#MQTT_nonTCPIP_based> .

<http://www.w3id.org/ecsel-dr-AT#PLM2_Module> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#PLM-System-SecondGeneration> .

<http://www.w3id.org/ecsel-dr-AT#Fieldbus_Car_Airplane> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#ManufacturingSimulationSystem> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Simulation-System> .

<http://www.w3.org/ns/sosa/sampling/RelationshipNature> a rdfs:Class ;
  rdfs:comment "Nature of a relationship (between samples) - Members of this class indicate the nature of a relationship between two samples." .

<http://www.w3id.org/ecsel-dr-SO#Cycle_Time_Committment> a rdfs:Class ;
  rdfs:comment """The “Cycle Time Commitment” entity helps controlling the WIP
via the release plan. (strategy entity)"""@en .

<http://www.w3id.org/ecsel-dr-SO#hasProductLevel3Pseudonym> a rdf:Property ;
  rdfs:comment "Product Level 4: FK; Assignment of product to first product aggregation level"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Release_Plan> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasCycleTimeCommittment> a rdf:Property ;
  rdfs:comment "Cycle Time Commitment: Committed overall supply chain cycle time"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Cycle_Time_Committment> ;
  rdfs:range xsd:dateTime .

<http://www.w3id.org/ecsel-dr-SO#hasCycleTimeCommitmentID> a rdf:Property ;
  rdfs:comment "Cycle Time Commitment: FK; Name of the product level 3"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Cycle_Time_Committment> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-OOSMP#Microcontroller> a rdfs:Class ;
  rdfs:label "Microcontroller" ;
  rdfs:comment "A semiconductor product which is used as microcontroller" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> .

<http://www.w3id.org/ecsel-dr-OOSMP#partOfAsMicrocontroller> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Microcontroller> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#partOf> .

<http://www.w3id.org/ecsel-dr-PMV#ProcessGroup> a rdfs:Class ;
  rdfs:label "Process Group" ;
  rdfs:comment "A set of a processes covering a single business area. Usually under the ownership of one business process owner and correlates to one module. E.g. Procurement" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#StructuralFunctionObject> .

<http://www.w3id.org/ecsel-dr-AT#B2MML> a rdfs:Class ;
  rdfs:label "Business to Manufacturing Markup Language"@en ;
  rdfs:comment """B2MML is an XML implementation of the ANSI/ISA-95, Enterprise-Control System Integration, family of standards (ISA-95), known internationally as IEC/ISO 62264. B2MML consists of a set of XML schemas written using the World Wide Web Consortium's XML Schema language (XSD) that implement the data models in the ISA-95 standard. 
Companies interested in following ISA-95 for integration projects may use B2MML to integrate business systems such as ERP and supply chain management systems with manufacturing systems such as control systems and manufacturing execution systems. B2MML is a complete implementation of ISA-95. Any company may use B2MML royalty free, provided credit is given to MESA. 
B2MML V0600 is the latest version. Earlier versions are still available; however, we recommend new users use the latest version which contains enhancements based upon user feedback.
New in V0600:
Support for ISA-95 Part 4 which was released by ISA in 2012. 
Support for the soon to be released updates to ISA-95 Parts 3 and 5. These updates were completed by the committee in March 2013 and will be released by ISA shortly. These updates are to make Parts 3 and 5 match the new Part 4. 
All B2MML V0500 errata items have been included. 
B2MML V0600 is up to date with the latest updates to the ISA-95 standard: 

ANSI/ISA-95.00.01-2010 Models and Terminology 
ANSI/ISA-95.00.02-2010 Object Model Attributes 
ANSI.ISA- 95.00.03-2013 Activity Models of Manufacturing Operations Management (approved by the ISA-95 committee, soon to be released) 
ANSI.ISA- 95.00.04-2012 Objects and attributes for manufacturing operations management integration 
ANSI/ISA- 95.00.05-2013 Business-to-Manufacturing Transactions (approved by the ISA-95 committee, soon to be released) 
The release notes provide more details on the changes in this release. 
Starting with V0401, the BatchML schemas were integrated into the B2MML namespace and BatchML now uses the B2MML common and extension files. Therefore B2MML schema and documentation downloads include BatchML files.
The MESA XML Committee maintains B2MML and BatchML. It is fully staffed by volunteers and is open to all interested parties. To join the committee or to send feedback on B2MML or BatchML, send a request to b2mml@mesa.org.
(http://www.mesa.org/en/B2MML.asp)"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#MarkupLanguage> .

<http://www.w3id.org/ecsel-dr-PMV#SubprocessDiagram> a rdfs:Class ;
  rdfs:label "Subprocess Diagram" ;
  rdfs:comment "The second and lowest level of process decomposition that is comprised of tasks that depict the role-based activities of the subprocess." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#Model> .

<http://www.w3id.org/ecsel-dr-PMV#hasPersonResponsible> a rdf:Property ;
  rdfs:label "hasPersonResponsible" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#SubprocessDiagram> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AT#HTTPS> a rdfs:Class ;
  rdfs:label "Hypertext Transfer Protocol Secure"@en ;
  rdfs:comment """HTTPS adds an additional layer between the transport protocol (TCP) and the application protocols: SSL/TLS. 
Syntactically, HTTPS is identical to the scheme for HTTP, the additional encryption of the data is done via SSL / TLS: Using the SSL handshake protocol, a protected identification and authentication of the communication partners takes place first. Subsequently, a common symmetric session key is exchanged using asymmetric encryption or the Diffie-Hellman key exchange. This is finally used to encrypt the user data.
The default port for HTTPS connections is 443.
In addition to server certificates, signed client certificates can also be created after X.509.3. This allows clients to authenticate to the server but is rarely used.
An older protocol variant of HTTPS was S-HTTP."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-SCP#ResourceCapacity> a rdfs:Class ;
  rdfs:label "ResourceCapacity"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#AggregatedCapacity> .

<http://www.w3id.org/ecsel-dr-SO#Lot> a rdfs:Class ;
  rdfs:comment "The Lot represents manufacturing unit (e.g. in the semicondutor industry in Frontend this often consists of 25 or 50 wafers)."@en .

<http://www.w3id.org/ecsel-dr-SO#hasLotEvent> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Lot_Event> .

<http://www.w3id.org/ecsel-dr-SO#hasRoute> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Product_Level_3> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Route> .

<http://www.w3id.org/ecsel-dr-SO#hasLotOwner> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Lot_Event> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasLotDueDate> a rdf:Property ;
  rdfs:comment "Lot: Date customer needs the lot delivered (DD.MM.YYYY hh:mm:ss)"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Lot> ;
  rdfs:range xsd:dateTime .

<http://www.w3id.org/ecsel-dr-SO#hasProductLevel3> a rdf:Property ;
  rdfs:comment "Lot: FK; Name of product level 3 lot belongs to"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Lot_Event> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasPriority> a rdf:Property ;
  rdfs:comment "Current WIP: Priority of the lot"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Lot_Event> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-SO#hasLotID> a rdf:Property ;
  rdfs:comment "Lot ID: PK; Name of the lot"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Current_WIP> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasLeaveState> a rdf:Property ;
  rdfs:comment "Lot Event: Time state is finished"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Lot_Event> ;
  rdfs:range xsd:dateTime .

<http://www.w3id.org/ecsel-dr-SO#hasLotSizeAmount> a rdf:Property ;
  rdfs:comment "Lot Event: Amount of units in the lot"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Lot_Event> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-SO#hasRoutePosition> a rdf:Property ;
  rdfs:comment "Lot: FK; Sequential number of the operation lot has entered"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Lot_Event> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-SO#hasEnterState> a rdf:Property ;
  rdfs:comment "Lot State: Time state is entered"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Lot_Event> ;
  rdfs:range xsd:dateTime .

<http://www.w3id.org/ecsel-dr-PWR#P-channel_Configuration> a rdfs:Class ;
  rdfs:label "P-Channel Configuration" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Device_Configuration> .

<http://purl.org/dc/dcmitype/Software> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PMV#isExecutedBy> a rdf:Property ;
  rdfs:label "isExectuedBy" ;
  rdfs:comment "Software is executed by a function in a process flow." ;
  rdfs:domain <http://purl.org/dc/dcmitype/Software> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Function> .

<http://www.w3.org/ns/sosa/ActuatableProperty> a rdfs:Class ;
  rdfs:label "Actuatable Property"@en ;
  rdfs:comment "An actuatable quality (property, characteristic) of a FeatureOfInterest."@en ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/Property> .

<http://www.w3.org/ns/sosa/isActedOnBy> a rdf:Property ;
  rdfs:label "is acted on by"@en ;
  rdfs:comment "Relation between an ActuatableProperty of a FeatureOfInterest and an Actuation changing its state."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/ActuatableProperty> ;
  rdfs:range <http://www.w3.org/ns/sosa/Actuation> .

<http://www.w3id.org/ecsel-dr-RAMI40#SensorMeasurement> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-RAMI40#Submodel> .

<http://www.w3id.org/ecsel-dr-RAMI40#hasSemanticExpression> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#Submodel> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-RAMI40#Expression_Semantic> .

<http://www.w3id.org/ecsel-dr-RAMI40#hasDataType> a rdf:Property ;
  rdfs:comment "Points to the datatypes of the Submodels" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#Submodel> ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-RAMI40#inAccordanceWith> a rdf:Property ;
  rdfs:comment "The Submodel is in accordance with a given standard specified in the STO ontology" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#Submodel> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-RAMI40#Standard> .

<http://www.w3id.org/ecsel-dr-RAMI40#hasReference> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#Submodel> ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-AT#RackFeeder> a rdfs:Class ;
  rdfs:label "Regalbediengerät"@de ;
  rdfs:comment "Gerät zur Materialbewegung in einem automatisierten Hochregallager."@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ActuatorDevice> .

<http://www.w3id.org/ecsel-dr-OM#CustomerPlantData> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-OM#hasPlantAddress> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#CustomerPlantData> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-OM#describesCustomerPlant> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#CustomerPlantData> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#CustomerPlant> .

<http://www.w3id.org/ecsel-dr-SO#Event_Calendar> a rdfs:Class ;
  rdfs:comment "In the “Event Calendar” tracing entity, certain events like planned facility shutdowns, etc. can be scheduled"@en .

<http://www.w3id.org/ecsel-dr-SO#hasCurrentWIP> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Current_WIP> .

<http://www.w3id.org/ecsel-dr-SO#hasMeanTimeToFailure> a rdf:Property ;
  rdfs:comment "mean time to failure - MTTF"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Event_Calendar> ;
  rdfs:range xsd:decimal .

<http://www.w3id.org/ecsel-dr-SO#hasFab> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Fab> .

<http://www.w3id.org/ecsel-dr-SO#hasMeanTimeToFailureDistribution> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Event_Calendar> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasEventCalendarType> a rdf:Property ;
  rdfs:comment "Event Calendar: Type of event"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Event_Calendar> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasMeanTimeToRepair> a rdf:Property ;
  rdfs:comment "mean time to repair - MTTR"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Event_Calendar> ;
  rdfs:range xsd:decimal .

<http://www.w3id.org/ecsel-dr-SO#hasMeanTimeToRepairDistribution> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Event_Calendar> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasCapacityLoss> a rdf:Property ;
  rdfs:comment "Calendar: Facility capacity loss in percent"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Event_Calendar> ;
  rdfs:range xsd:double .

<http://www.w3id.org/ecsel-dr-RAMI40#MESConnection> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-RAMI40#Submodel> .

<http://www.w3id.org/ecsel-dr-AH#AH_DeviceRegistrySystem_SySD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system_SySD> .

<http://www.w3id.org/ecsel-dr-PWR#Voltage> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PMV#Input> a rdfs:Class ;
  rdfs:label "Input" ;
  rdfs:comment "Item external to a system (such as a process) that is transformed by the system (usually together with one or more other items) to become an output." .

<http://www.w3id.org/ecsel-dr-AT#XML> a rdfs:Class ;
  rdfs:label "Extended Markup Language" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L2_DataSyntax> .

<http://www.w3id.org/ecsel-dr-SO#Sputtering> a rdfs:Class ;
  rdfs:comment "The sputtering process, or physical vapor deposition (PVD) is the most used layering process today. Here gas atoms, mostly argon, strike out atoms from the cathode I an electric field which then form a thin film on the wafer surface."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Workshop> .

<http://www.w3.org/2006/time#Duration> a rdfs:Class ;
  rdfs:label "Time duration"@en ;
  rdfs:comment "Duration of a temporal extent expressed as a number scaled by a temporal unit"@en ;
  rdfs:subClassOf <http://www.w3.org/2006/time#TemporalDuration> .

<http://www.w3.org/2006/time#numericDuration> a rdf:Property ;
  rdfs:label "Numeric value of temporal duration"@en ;
  rdfs:comment "Value of a temporal extent expressed as a decimal number scaled by a temporal unit"@en ;
  rdfs:domain <http://www.w3.org/2006/time#Duration> ;
  rdfs:range xsd:decimal .

<http://www.w3id.org/ecsel-dr-OOSMP#BusinessLine> a rdfs:Class ;
  rdfs:label "Business Line" ;
  rdfs:comment "A business line is an organizational unit that can be assigned to a division and can have one or more product lines." ;
  rdfs:subClassOf <http://www.w3.org/ns/org#OrganizationalUnit> .

<http://www.w3id.org/ecsel-dr-OOSMP#subUnitOfDivision> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#BusinessLine> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#Division> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#subUnitOf> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasProductLine> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#BusinessLine> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#ProductLine> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasSubUnit> .

<http://www.w3id.org/ecsel-dr-AH#AH_AuthorizationSystem_SysDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_system_SySDD> .

<http://www.w3.org/ns/ssn/systems/OperatingPowerRange> a rdfs:Class ;
  rdfs:label "Operating Power Range" ;
  rdfs:comment "Power range in which System is expected to operate in the specified." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/systems/OperatingProperty> .

<http://www.w3id.org/ecsel-dr-AH#AH_system_of_systems_documentation> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#System_documentation> .

<http://www.w3id.org/ecsel-dr-AT#Packet> a rdfs:Class ;
  rdfs:comment """Data transmission unit of ISO/OSI Layer 3 (Network Layer). 
\"Letter\", contains IP address"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#DataTransmissionUnit> .

<http://www.w3id.org/ecsel-dr-SO#Process_Line> a rdfs:Class ;
  rdfs:comment "A Process Line is the forth hierarchy level in the Technology Catalogue and is a subset of Process Group. A Process Line is defined by WHAT is produced in detail"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Process> .

<http://www.w3id.org/ecsel-dr-SO#hasPart> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Simulation_Part> .

<http://www.w3id.org/ecsel-dr-SO#usesOneOrMoreTechnology> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Process> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Workshop> .

<http://www.w3id.org/ecsel-dr-PWR#InformationEntity> a rdfs:Class ;
  rdfs:label "Information Entity" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Entity> .

<http://www.w3id.org/ecsel-dr-AT#SensML> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#MarkupLanguage> .

<http://www.w3id.org/ecsel-dr-AH#Communication_security_mechanism> a rdfs:Class ;
  rdfs:comment "corresponds to a part of OSI layer 5" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Communication_technology> .

<http://www.w3id.org/ecsel-dr-PMV#TechnicalTermOutputElement> a rdfs:Class ;
  rdfs:label "Technical Term Output Element" ;
  rdfs:comment "Denotes the output element of a function in the process flow." .

<http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_service_IDD> a rdfs:Class ;
  rdfs:comment """Class of all Interface Design Descriptions (IDDs) of mandatory Arrowwhead core services.
While the class AH_mandatory_core_service contains the mandatory core services only as instances, this class contains classes of the IDDs of each single mandatory core service as subclasses (not only as instances). Since each AH Local Cloud runs one instance of each mandatory core service, each of these services has to be documented by an AH service documentation, i.e. at least by a SD and a IDD. So the IDD is an individual document for each mandatory core service in each single Local Cloud. Hence, all IDDs of a certain mandatory core service will be individuals of the corresponding IDD class."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_core_service_IDD> .

<http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> a rdfs:Class ;
  rdfs:label "Semiconductor Solution" ;
  rdfs:comment "A semiconductor solution is combination of semiconductor products and is sold within the seminconductor industry." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#Solution> .

<http://www.w3id.org/ecsel-dr-AT#ElectricDrive> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ActuatorDevice> .

<http://www.w3id.org/ecsel-dr-SCP#MarketingDemands> a rdfs:Class ;
  rdfs:label "MarketingDemands"@iri-based .

<http://www.w3id.org/ecsel-dr-SCP#calculateBasedOn> a rdf:Property ;
  rdfs:label "calculateBasedOn"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#MarketingDemands> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#SalesDemands> .

<http://www.w3id.org/ecsel-dr-SCP#hasResult> a rdf:Property ;
  rdfs:label "hasResult"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#MarketingDemands> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#OperationalDemand> .

<http://www.w3id.org/ecsel-dr-SO#Equipment> a rdfs:Class ;
  rdfs:comment "The entity “Equipment” describes the semiconductor equipment of any equipment model. It allocates it to higher level entities and describes the behavior of the equipment. (master entity)"@en .

<http://www.w3id.org/ecsel-dr-AT#IETF-Standard> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Standard> .

<http://www.w3.org/2003/11/swrl#Variable> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AH#Documentation_document> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-SO#Development> a rdfs:Class ;
  rdfs:comment "[Priority Class] these lots have the same maxium waiting time as standard lots, however they are put before the standard lots."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Priority_Classes> .

<http://www.w3id.org/ecsel-dr-SO#hasDevelopmentTimeout> a rdf:Property ;
  rdfs:comment "length of, or element of the length of, a temporal extent expressed in hours"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Development> ;
  rdfs:range xsd:decimal .

<http://www.w3id.org/ecsel-dr-AT#SenML> a rdfs:Class ;
  rdfs:comment "Sensor Modelling Language" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#MarkupLanguage> .

<http://www.w3id.org/ecsel-dr-AT#5G> a rdfs:Class ;
  rdfs:label "5G"@en ;
  rdfs:comment """5G uses a scalable orthogonal frequency-division multiplexing (OFDM) framework with different numerologies. Within a 1ms time duration, six separate slot configurations are available, e.g. 1, 2, 4, 8, 16, and 32 slots. The minimum size of a transport block could be reduced to a minimum of 0.03125ms
based on the new configuration:
To reduce the waste of periodically allocated resources, 5G enables multiple devices to share the periodic resources, called a configured grant (Type 1). The configured grant is based on the LTE SPS feature. A base station can allocate
the configured grant resources to multiple vehicles, and the vehicles randomly utilize the resources when they have data to transmit. By assigning the configured grant resources, the 5G network eliminates the packet transmission delay for a scheduling request procedure and increases the utilization
ratio of allocated periodic radio resources.
Source: https://www.edn.com/electronics-blogs/5g-waves/4460644/How-5G-reduces-data-transmission-latency"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> .

<http://www.w3id.org/ecsel-dr-AT#X400> a rdfs:Class ;
  rdfs:label "X.400"@de ;
  rdfs:comment """X.400, often called Message Handling System (MHS), is an e-mail system based on the OSI model and an alternative to Internet e-mail. The standard was published in 1984 by the CCITT (now ITU) and expanded in 1988. The ISO refers to the system as its Message Oriented Text Interchange System (MOTIS) in its ISO 10021 standard based on X.400 (1988).

In Germany, X.400 is often still known under the old brand name Telebox400 the German Federal Post. Meanwhile, the successor Deutsche Telekom called it BusinessMail X.400. EDI systems often use X.400 for data transfer.

Access to the message store is from X.400 (1988) via the P7 protocol defined in X.419 from the user agent (UA) to the message store (MS). The message exchange takes place by means of a message transfer system (MTS), which can consist of one or more message transfer agents (MTA) and gateways to non-X.400 systems. Telekom Deutschland GmbH also offers a client for the transmission of messages, which can transmit messages based on the protocol P7. This client software is called Filework for Windows (all versions) and is now available in version 5.1.1. Filework also has a script interface, with which the program independently transmits messages in both directions and processes them accordingly.

The MTA is the central component for messaging with other X.400 systems. By means of pre-configured routing information, the MTA uses the X.400 destination address to decide via which route the messages are forwarded to the recipient. An X.400 address has a hierarchical structure and uniquely identifies sender and recipient. Since 1 July 2012, SMTP MTAs can also be networked with the BusinessMail X.400 system. Thus, the connectivity to current, popular e-mail server such. For example, \"sendmail\" or \"postfix\", which are part of any Linux system, has been greatly enhanced. This increases compatibility with other systems while reducing customer service costs.

Unlike Internet e-mail, the X.400 network only has well-known domain operators and traceable ways in which messages move through the network. For this reason, when using X.400, some of the messages are not encrypted.

For the transmission of EDI messages, for example in the European food trade, X.400 is frequently used.

X.400 is next to AS2 one of the most common forms of communication used in professional electronic data exchange. Whether a company uses X.400 or AS2 depends on how the company weights certain operating costs and which EDI infrastructure it owns. With AS2, the fees for the provider for the X.400 service can be saved. This saving is offset by a higher expenditure in-house for the administration of the regularly to be renewed, partner-individual certificates and the operation of an uninterruptible own EDI system. With X.400, the X.400 provider stands between two EDI systems, so that both partners do not communicate directly with each other. Likewise, connection tests with new partner connections or the elimination of connection problems with X.400 are simpler because they are abstracted from the direct communication partner. Since the beginning of 2014, there is a free pilot operation for the introduction of the Odette File Transfer Protocol (OFTP). OFTP is used as a transmission protocol above all in the electronic business data exchange in the automotive industry, ie between the car manufacturers and their suppliers, as well as banks. As of October 1, 2015, OFTP access was officially transferred to production and also offered."""@en , """X.400, oft auch Message Handling System (MHS) genannt, ist ein E-Mail-System auf Basis des OSI-Modell und eine Alternative zu Internet-E-Mail. Der Standard wurde 1984 durch die CCITT (heute ITU) herausgegeben und 1988 erweitert. Die ISO bezeichnet das System in ihrer Norm ISO 10021, die auf X.400 (1988) basiert, als Message Oriented Text Interchange System (MOTIS).

In Deutschland ist X.400 häufig noch unter dem alten Markennamen Telebox400 der Deutschen Bundespost bekannt. Inzwischen bezeichnet die Nachfolgerin Deutsche Telekom es als BusinessMail X.400. EDI-Systeme verwenden häufig X.400 für die Übertragung der Daten.

Der Zugang zu dem Message Store erfolgt ab X.400 (1988) über das in X.419 definierte P7 Protokoll vom User Agent (UA) zum Message Store (MS). Der Mitteilungsaustausch erfolgt mittels eines Message Transfer System (MTS), welches aus einem oder mehreren Message Transfer Agent (MTA) und Gateways zu Nicht-X.400-Systemen bestehen kann. Die Telekom Deutschland GmbH bietet zur Übermittlung der Nachrichten auch einen Client an, der auf dem Protokoll P7 basierend Messages übermitteln kann. Diese Client-Software nennt sich Filework für Windows (alle Versionen) und liegt mittlerweile in der Version 5.1.1 vor. Ebenso hat Filework eine Script-Schnittstelle, mit der das Programm selbständig Nachrichten in beide Richtungen übermittelt und entsprechend verarbeitet.

Der MTA ist die zentrale Komponente für den Mitteilungsaustausch mit anderen X.400-Systemen. Mittels vorab konfigurierter Routinginformationen entscheidet der MTA anhand der X.400-Zieladresse, über welchen Weg die Mitteilungen an den Empfänger weitergeleitet werden. Eine X.400-Adresse hat eine hierarchische Struktur und identifiziert Absender und Empfänger eindeutig. Seit dem 1. Juli 2012 können auch SMTP-MTA's mit dem BusinessMail X.400-System vernetzt werden. Damit wird die Konnektivität auf aktuelle, gängige E-Mailserver wie z. B. \"sendmail\" oder \"postfix\", die Bestandteil eines jeden Linux-Systems sind, erheblich erweitert. Das steigert die Kompatibilität zu anderen Systemen und senkt gleichzeitig die Servicekosten beim Kunden.

Im Gegensatz zu Internet-E-Mail gibt es im weltweiten X.400-Netz nur namentlich bekannte Domänenbetreiber und nachvollziehbare Wege, auf denen die Nachrichten durch das Netz bewegt werden. Aus diesem Grund wird bei der Verwendung von X.400 teilweise auf eine Verschlüsselung der Nachrichten verzichtet.

Für die Übertragung von EDI-Nachrichten, zum Beispiel im europäischen Lebensmittelhandel, wird X.400 häufig eingesetzt.

X.400 ist neben AS2 eine der häufigsten Kommunikationsformen, die im professionellen elektronischen Datenaustausch verwendet werden. Ob ein Unternehmen X.400 oder AS2 einsetzt, entscheidet sich danach, wie das Unternehmen bestimmte Betriebskosten gewichtet und welche EDI-Infrastruktur es besitzt. Mit AS2 lassen sich die Gebühren beim Provider für den X.400-Service einsparen. Dieser Einsparung steht ein höherer Aufwand im eigenen Hause für die Verwaltung der regelmäßig zu erneuernden, partnerindividuellen Zertifikate und der Betrieb eines unterbrechungsfreien eigenen EDI-Systems gegenüber. Bei X.400 steht der X.400-Provider zwischen zwei EDI-Systemen, so dass beide Partner nicht direkt miteinander kommunizieren. Ebenso sind Verbindungstests bei neuer Partneranbindung oder auch die Behebung von Verbindungsstörungen bei X.400 einfacher, weil diese abstrahiert ist vom direkten Kommunikationspartner. Seit Beginn des Jahres 2014 gibt es einen kostenlosen Pilotbetrieb für die Einführung des Odette File Transfer Protokolls (OFTP). OFTP wird als Übertragungsprotokoll vor allem beim elektronischen Geschäftsdatenaustausch in der Automobilindustrie, also zwischen den Automobilherstellern und deren Zulieferern, sowie Banken benutzt. Ab dem 1. Oktober 2015 wurde der OFTP-Zugang offiziell in den Produktivbetrieb überführt und auch angeboten."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-PMV#Event> a rdfs:Class ;
  rdfs:label "Event" ;
  rdfs:comment "An event illustrates the fact that a process object has taken on a business relevant state influencing the further procedure of a process. Unlike a function, which is a time consuming occurrence, an event is related to one point in time. Therefore, it is used to describe an event or status in the process flow. The object is mandatory for: EPC start and EPC end or after x (xor), v (or)." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#ModelElement> .

<http://www.w3id.org/ecsel-dr-PMV#activatesFunction> a rdf:Property ;
  rdfs:label "activatesFunction" ;
  rdfs:comment "Specialization of the activates property that links the class Event with Task and Process Interface in the course of the process flow." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Event> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#ModellingFunctionObject> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-PMV#activates> .

<http://www.w3id.org/ecsel-dr-PMV#isCreatedBy> a rdf:Property ;
  rdfs:label "isCreatedBy" ;
  rdfs:comment "An event is created by a process step. The connector is used to represent the chronological order in an EPC." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Event> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#isEvaluatedBy> a rdf:Property ;
  rdfs:label "isEvaluatedBy" ;
  rdfs:comment "An event is evaluated by a rule. The connector is used to represent the chronological order in an EPC." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Event> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#JoinRule> .

<http://www.w3id.org/ecsel-dr-PMV#activates> a rdf:Property ;
  rdfs:label "activates" ;
  rdfs:comment "The connector is used to represent the chronological order in an EPC, where an Event or a Rule activate a Task or Process Interface. " ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#ModellingFunctionObject> .

<http://www.w3id.org/ecsel-dr-PMV#isDependentOn> a rdf:Property ;
  rdfs:label "isDependentOn" ;
  rdfs:comment "An event is dependent on a rule. The connector is used to represent the chronological order in an EPC." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Event> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Rule> .

<http://www.w3id.org/ecsel-dr-AH#AH_ServiceDiscoveryService_IDD> a rdfs:Class ;
  rdfs:comment "Interface Design Description (IDD) of the Arrowhead mandatory core service Service Discovery Service which is provided by the mandatory core system Service Registry."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_service_IDD> .

<http://www.w3id.org/ecsel-dr-AT#OSI_AL2_InternetLayer> a rdfs:Class ;
  rdfs:label "Internet Layer"@en , "Internetschicht"@de ;
  rdfs:comment """Corresponds 1:1 to ISO/OSI layer 3: Network Layer. 
conducts transmission of data packets and choice of the net node (routing), i.e. determines the next intermediate node for received data packets and transmits the data packet there. 
Handles point-to-pint (node-to-node) transmissions, no transmission paths. 
Examples: Internet Protocol Version 4 (IPv4), IPv6."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_AggregatedLayer> .

<http://www.w3id.org/ecsel-dr-AH#AH_AuthorizationControlService_IDD> a rdfs:Class ;
  rdfs:comment "Interface Design Description (IDD) of the Arrowhead mandatory core service Authorization Control Service which is provided by the mandatory core system Authorization System."@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_service_IDD> .

<http://www.w3id.org/ecsel-dr-PWR#Solar_Energy> a rdfs:Class ;
  rdfs:label "Solar Energy" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#ApplicationArea> .

<http://www.w3id.org/ecsel-dr-AT#CPF10_VNET_IP> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3id.org/ecsel-dr-OM#OpenOrder> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-OM#isPartOfOpenOrderBook> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OpenOrder> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#OpenOrderBook> .

<http://www.w3id.org/ecsel-dr-OM#hasPONumberOO> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OpenOrder> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#isDeliveredToCustomerPlant> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OpenOrder> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#CustomerPlant> .

<http://www.w3id.org/ecsel-dr-OM#consistsOfOrderLineItem> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OpenOrder> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#OrderLineItem> .

<http://www.w3id.org/ecsel-dr-PWR#TechnologyHardware&Equipment> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#InformationTechnology> .

<http://www.w3id.org/ecsel-dr-SO#Priority_Classes> a rdfs:Class ;
  rdfs:comment "Each lot is characterized by a product type and a priority class. The priority classes are listed as follows: development, hot, productive, rocket and timecoupling."@en .

<http://www.w3id.org/ecsel-dr-PMV#ProcessInterface> a rdfs:Class ;
  rdfs:label "Process Interface" ;
  rdfs:comment "Process Interfaces connect several process models on the same Process hierarchical levelby linking the EPCs according to their shared events (also known as \"horizontal navigation\"). They thus facilitate process structuring and navigation by keeping models concise" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#Function> , <http://www.w3id.org/ecsel-dr-PMV#ModelElement> , <http://www.w3id.org/ecsel-dr-PMV#ModellingFunctionObject> .

<http://www.w3id.org/ecsel-dr-PMV#follows> a rdf:Property ;
  rdfs:label "follows" ;
  rdfs:comment "A process step follows a process step. The connector is used to represent the chronological order in an EPC." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#ModellingFunctionObject> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#ModellingFunctionObject> .

<http://www.w3id.org/ecsel-dr-PMV#creates> a rdf:Property ;
  rdfs:label "creates" ;
  rdfs:comment "A process step creates an event. The connector is used to represent the chronological order in an EPC." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#ModellingFunctionObject> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Event> .

<http://www.w3id.org/ecsel-dr-PMV#isActivatedBy> a rdf:Property ;
  rdfs:label "isActivatedBy" ;
  rdfs:comment "A process step is activated by an event or a rule. The connector is used to represent the chronological order in an EPC." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#ModellingFunctionObject> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#isPredecessorOf> a rdf:Property ;
  rdfs:label "isPredecessorOf" ;
  rdfs:comment "The connector is used to represent the chronological order of value chain elements." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#ModellingFunctionObject> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#ModellingFunctionObject> .

<http://www.w3id.org/ecsel-dr-PMV#isActivatedByFunction> a rdf:Property ;
  rdfs:label "isActivatedByFunction" ;
  rdfs:comment "Represents the inverse property of activatesFunction." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#ModellingFunctionObject> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Event> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-PMV#isActivatedBy> .

<http://www.w3id.org/ecsel-dr-PMV#leadsToRule> a rdf:Property ;
  rdfs:label "leadsToRule" ;
  rdfs:comment "A process step leads to a rule. The connector is used to represent the chronological order in an EPC." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#ModellingFunctionObject> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Rule> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-PMV#leadsTo> .

<http://www.w3id.org/ecsel-dr-AH#AH_StoreManagementService_SD> a rdfs:Class ;
  rdfs:comment "Service Description (SD) of the Arrowhead mandatory core service Store Management Service which is provided by the mandatory core system Orchestrator."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_service_SD> .

<http://www.w3id.org/ecsel-dr-AT#DocumentTypeDescription> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#DataLanguage_XML-based> .

<http://www.w3id.org/ecsel-dr-AT#JSON> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L2_DataSyntax> .

<http://www.w3id.org/ecsel-dr-RAMI40#TransportInterface> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-RAMI40#Submodel> .

<http://www.w3id.org/ecsel-dr-AT#W3C> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#StandardisationOrganization> .

<http://www.w3id.org/ecsel-dr-SCP#AP_FCST> a rdfs:Class ;
  rdfs:label "AP_FCST"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#Forecast> .

<http://www.w3id.org/ecsel-dr-SCP#isPartOf> a rdf:Property ;
  rdfs:label "isPartOf"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#Forecast> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#OperationalDemand> .

<http://www.w3id.org/ecsel-dr-SCP#obtainFrom> a rdf:Property ;
  rdfs:label "obtainFrom"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#Forecast> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#SalesDemands> .

<http://www.w3.org/ns/sosa/Platform> a rdfs:Class ;
  rdfs:label "Platform"@en ;
  rdfs:comment "A Platform is an entity that hosts other entities, particularly Sensors, Actuators, Samplers, and other Platforms."@en .

<http://www.w3.org/ns/sosa/hosts> a rdf:Property ;
  rdfs:label "hosts"@en ;
  rdfs:comment "Relation between a Platform and a Sensor, Actuator, Sampler, or Platform, hosted or mounted on it."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Platform> ;
  rdfs:range <http://www.w3.org/ns/ssn/System> .

<http://www.w3.org/ns/ssn/inDeployment> a rdf:Property ;
  rdfs:label "in deployment"@en ;
  rdfs:comment "Relation between a Platform and a Deployment, meaning that the deployedSystems of the Deployment are hosted on the Platform."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Platform> ;
  rdfs:range <http://www.w3.org/ns/ssn/Deployment> .

<http://www.w3id.org/ecsel-dr-AT#CPF17_RAPINet> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3id.org/ecsel-dr-PWR#Device_Configuration> a rdfs:Class ;
  rdfs:label "Device Configuration" .

<http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service_IDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_core_service_IDD> .

<http://www.w3id.org/ecsel-dr-AT#CPF6_INTERBUS> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3id.org/ecsel-dr-AT#Ethernet_802_3> a rdfs:Class ;
  rdfs:comment """cf. https://de.wikipedia.org/wiki/Ethernet 

Dort zwei schöne Grafiken von Technologie-Stacks auf Basis von Ethernet: der TCP/IP-Stack und der AppleTalk-Stack. 
Letzterer ist wegen DNS-SD für Arrowhead und P 4.0 relevant."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> .

<http://www.w3id.org/ecsel-dr-PWR#Length> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#GeometricDimension> .

<http://www.w3id.org/ecsel-dr-SCP#SafetyStock> a rdfs:Class ;
  rdfs:label "SafetyStock"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#SSO_Stocks> .

<http://www.w3id.org/ecsel-dr-SCP#SupplyDemandMatch> a rdfs:Class ;
  rdfs:label "SupplyDemandMatch"@iri-based .

<http://www.w3id.org/ecsel-dr-SCP#calculate> a rdf:Property ;
  rdfs:label "calculate"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#SupplyDemandMatch> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#SupplyPicture> .

<http://www.w3id.org/ecsel-dr-AT#UDS> a rdfs:Class ;
  rdfs:label "Unified Diagnostic Services"@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3.org/ns/ssn/Condition> a rdfs:Class ;
  rdfs:label "Condition" ;
  rdfs:comment "Used to specify ranges for qualities that act as Condition on a Systems' operation." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/Property> .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_1_4> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ISA-95_CrossLayerCommunication> .

<http://www.w3id.org/ecsel-dr-AT#CPF3_2_Profibus_PA> a rdfs:Class ;
  rdfs:comment """PROFIBUS (Process Field Bus) ist ein Standard für die Feldbus-Kommunikation in der Automatisierungstechnik und wurde anfangs (1989) vom BMBF gefördert. Er ist nicht zu verwechseln mit dem Profinet-Standard für Industrial Ethernet.
PROFIBUS existiert in drei Varianten, wobei DP die meistgenutzte ist:

1. PROFIBUS DP (Dezentrale Peripherie) 
2. PROFIBUS PA (Prozess-Automation) wird zur Kommunikation zwischen Mess- und Prozessgeräten, Aktoren und Prozessleitsystem bzw. SPS/DCS in der Prozess- und Verfahrenstechnik eingesetzt. PROFIBUS PA ist eine PROFIBUS-Variante mit für die Prozessautomation geeignetem Physical Layer (Übertragungsschicht), bei welcher an PROFIBUS DP über sogenannte Koppler mehrere Segmente (PA-Segmente) mit Feldgeräten angeschlossen werden können. Die zweiadrige Busleitung dieser Segmente übernimmt nicht nur die Kommunikation, sondern auch die Energieversorgung der Teilnehmer (MBP Übertragungstechnik). PROFIBUS PA stellt eine digitale Alternative zur klassischen analogen Verbindung von Geräten (4- bis 20-mA-Technik) dar und bietet zusätzliche Funktionen durch die bidirektionale Kommunikation. PROFIBUS PA ist durch Leistungsbegrenzung auch für explosionsgefährdete Bereiche geeignet. Je nach Einsatzbereich kommen unterschiedliche Explosionsschutzarten zum Einsatz. Besonders etabliert ist die Schutzart Eigensicherheit. Sie erlaubt einen Zugang zum Feldgerät im laufenden Betrieb ohne einen Heißarbeitserlaubnisschein (FISCO-Spezifikation). Die Datenübertragungsrate von PROFIBUS PA liegt bei 31,25 kbit/s, was für eine hohe Immunität gegen elektromagnetische Interferenzen sorgt und lange Kabelwege ermöglicht. Diese Geschwindigkeit ist für verfahrenstechnische Applikationen völlig ausreichend. Eine weitere Besonderheit von PROFIBUS PA ist das weit verbreitete Geräteprofil „PA Devices“ (PA-Profil), in welchem die wichtigsten Funktionen der Feldgeräte herstellerübergreifend standardisiert sind, was für den Anwender von erheblichem Nutzen ist.""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#CPF3_Profibus_ProfiNet> .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer3_MES_LES> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer> .

<http://www.w3id.org/ecsel-dr-AT#MarkupLanguage> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L5_DataSemantics> .

<http://www.w3id.org/ecsel-dr-SCP#EDIForecast> a rdfs:Class ;
  rdfs:label "EDIForecast"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#Orders> .

<http://www.w3id.org/ecsel-dr-RAMI40#Submodel> a rdfs:Class ;
  rdfs:comment "Describe the different types of Data related to the I4.0 Asset" .

<http://www.w3id.org/ecsel-dr-SCP#PrivateCustomers> a rdfs:Class ;
  rdfs:label "PrivateCustomers"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#Customers> .

<http://www.w3id.org/ecsel-dr-SCP#CustomerLocation> a rdf:Property ;
  rdfs:label "CustomerLocation"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#Customers> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SCP#isPlaceOrders> a rdf:Property ;
  rdfs:label "isPlaceOrders"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#Customers> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#Orders> .

<http://www.w3id.org/ecsel-dr-SCP#Granularity> a rdf:Property ;
  rdfs:label "Granularity"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#Customers> ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SCP#CustomersID> a rdf:Property ;
  rdfs:label "CustomersID"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#Customers> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-AT#Standard> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#OSI_3_4_NetworkTechnology> a rdfs:Class ;
  rdfs:comment "Technologie, die die mittleren Schichten des OSI-Schichtenmodells abdeckt, z.B. TCP/IP, ZigBee, UDP usw."@de .

<http://www.w3id.org/ecsel-dr-AH#AH_Historian_SySD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system_SySD> .

<http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_system> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_core_system> .

<http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-OM#belongsToOpenOrder> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#OpenOrder> .

<http://www.w3id.org/ecsel-dr-OM#hasCustomerReferenceNo> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#hasResponseDate> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range xsd:dateTime .

<http://www.w3id.org/ecsel-dr-OM#hasUnitPrice> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-OM#hasTotalConfirmedQuantity> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#hasTotalOpenQuantity> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#hasCustomerPartNumber> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#containsOrderLineItem> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#OrderLineItem> .

<http://www.w3id.org/ecsel-dr-OM#containsContactPersonData> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#ContactPersonData> .

<http://www.w3id.org/ecsel-dr-OM#hasSupplierReferenceNo> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#hasTotalDeliveredQuantity> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#hasIcoterms> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-OM#hasTotalUnconfirmedOpenQuantity> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#containsCustomerData> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#CustomerData> .

<http://www.w3id.org/ecsel-dr-OM#hasItemPrice> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-OM#hasItemNo> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#hasModeOfTransport> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-OM#containsCustomerPlantData> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#CustomerPlantData> .

<http://www.w3id.org/ecsel-dr-OM#hasTotalConfirmedOpenQuantity> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#containsSupplierData> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#SupplierData> .

<http://www.w3id.org/ecsel-dr-OM#hasTotalRequestedQuantity> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#hasRequestedQuantity> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderConfirmation> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-SCP#Stocks> a rdfs:Class ;
  rdfs:label "Stocks"@iri-based .

<http://www.w3id.org/ecsel-dr-SCP#hasInput> a rdf:Property ;
  rdfs:label "hasInput"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#Stocks> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#SupplyDemandMatch> .

<http://www.w3id.org/ecsel-dr-AH#Service-oriented_Architecture> a rdfs:Class ;
  rdfs:label "SoA"@en .

<http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_core_service> .

<http://www.w3.org/ns/ssn/systems/SurvivalProperty> a rdfs:Class ;
  rdfs:label "Survival Property" ;
  rdfs:comment "An identifiable characteristic that represents the extent of the System's useful life under the specified Conditions. May describe for example total battery life or number of recharges, or, for Sensors that are used only a fixed number of times, the number of Observations that can be made before the sensing capability is depleted." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/Property> .

<http://purl.org/dc/terms/PhysicalResource> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#OSI_DetailedLayer> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-SO#Product_Line> a rdfs:Class ;
  rdfs:comment "The product line is one of the most prominent grouping of products. It is used in reporting as well as for structuring organizations."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Product> .

<http://www.w3id.org/ecsel-dr-PMV#TechnicalTerm> a rdfs:Class ;
  rdfs:label "Technical Term" ;
  rdfs:comment "Set up with connection to a function or activity or VAC. It can be either input or output, where the direction of the arrow describes whether it is an input or an output. Set up of a connection is not mandatory." ;
  rdfs:subClassOf <http://xmlns.com/foaf/0.1/Document> .

<http://www.w3id.org/ecsel-dr-PMV#isInputFor> a rdf:Property ;
  rdfs:label "isInputFor" ;
  rdfs:comment "A software independent business object or product/services may be input for a process step." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#TechnicalTerm> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Task> .

<http://www.w3id.org/ecsel-dr-AH#Service_Description_SD> a rdfs:Class ;
  rdfs:comment "Provides an abstract description of the purpose and behaviour of a specific service, including what information it is aiming to distribute. It is referred to by one or more IDD (each stating a way of implementing the service with a specific technology) (Source: Arrowhead Framework Definitions V 2.4)"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_service_documentation_document> .

<http://www.w3id.org/ecsel-dr-AT#W3C-Standard> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Standard> .

<http://www.w3id.org/ecsel-dr-SO#Simulation_Part> a rdfs:Class ;
  rdfs:comment "A simulation part helps to identify the same product in different locations. They are visible in Product Structures. This is a simulation entity and not a form of production/planning."@en .

<http://www.w3id.org/ecsel-dr-AT#PL_Phase1_Development> a rdfs:Class ;
  rdfs:comment """First general phase of a product lifecycle: 
the product (and in many industries also the production system, production equipment, production process etc.) is developed, i.e. designed, engineered, computed, virtually tested, simulated etc. 
\"Product\" refers in this phase to a product type, i.e. a class of products. It may consist of several product variants."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ProductLifecyclePhase> .

<http://www.w3id.org/ecsel-dr-AH#AH_service_documentation_document> a rdfs:Class ;
  rdfs:comment """Document belonging to the documentation of an Arrowhead Service. 
There are four types of documents for Arrowhead service documentations: 
- Service Description
- Interface Design Description
- Communication Profile
- Semantic Profile. 
The central documents are IDDs. They document the implementation of a certain service based on a certain communication technology (communication, encoding, data format) and a certain information model. 
The Service Description contains a more general description of the service, without the link to a specific communication technology or information model. 
Communication Profiles and Semantic Profiles are optional documents for a service documentation. They can be seen as modules of an IDD, since they can describe the communication technolopgy and the information model of a service implementation as external documents. If they exist, the IDD refers to them instead of declaring these contents by themselfes. 
That is, CP and SP are useful if different service implementations use the same CP and SP - then their IDDs can refer to one and the same CP or SP document."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Documentation_document> .

<http://www.w3id.org/ecsel-dr-AT#OSI_L5_SessionLayer> a rdfs:Class ;
  rdfs:label "Session layer"@en , "Sitzungsschicht"@de ;
  rdfs:comment """Allows session establishment between processes running on different stations (hosts). 
Provides Sync and Send-to ports (logical ports). 
Topics: Session establishment, maintenance and termination; Session support; perform security, name recognition, logging etc. 
Central elements: logical ports
Example protocols: RPC (Remote Procedure Call), SQL, NFS, NetBIOS names,"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_DetailedLayer> .

<http://www.w3id.org/ecsel-dr-AT#CPF2_ControlNet> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3id.org/ecsel-dr-AH#Data_model> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AH#Device> a rdfs:Class ;
  rdfs:comment "A device in the context of Service-oriented architectures (that is, in the context of Information Technology (IT) and Automation / Operations Technology (OT)) is an technical artefact that fulfills the basic definition of a \"computer\". That is, a device must be able to host (run) software systems. For this, it needs at least a processing unit (processor), a memory and a communication interface, which can be either wired or wireless."@en .

<http://www.w3id.org/ecsel-dr-AH#DeviceName> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Device> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AH#DeviceID> a rdf:Property ;
  rdfs:comment """Data property of each device in Arrowhead context. Needed by Device Discovery service.
Purpose: provides an unique identifier for a device."""@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Device> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AH#isDeviceIn> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Device> ;
  rdfs:range <https://w3id.org/linkml/Any> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#isArchitecturalPartOf> .

<http://www.w3id.org/ecsel-dr-AH#hosts> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Device> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Software_system> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#hasArchitecturalPart> .

<http://www.w3id.org/ecsel-dr-AH#MAC_address> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Device> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AH#IP_address> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Device> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#Product_Class> a rdfs:Class ;
  rdfs:comment "the product class is an entity used for planning and reporting. This helps create stable brand/name architectures to enable highest possible product portfolio transparency, true value creation ad to prevent from product TM overload."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Product> .

<http://www.w3id.org/ecsel-dr-AH#AH_SessionEstablishService_SD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service_SD> .

<http://www.w3id.org/ecsel-dr-PWR#Infineon_Device> a rdfs:Class ;
  rdfs:label "Amplication (switching) Device" ;
  rdfs:comment """Should defined as its function for example:

-Sensor
-Power Converter 
-Microcontroller 

Then must be defined what the device it is, for exmaple:
-A sensing device is a device that implments sensing.""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Device> .

<http://www.w3id.org/ecsel-dr-PWR#hasIndustrySector> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Infineon_Device> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Semiconductors> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-PWR#are> .

<http://www.w3id.org/ecsel-dr-PWR#has_Properties> a rdf:Property ;
  rdfs:label "has Properties" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Infineon_Device> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Property> .

<http://www.w3id.org/ecsel-dr-PWR#has_The_Elements> a rdf:Property ;
  rdfs:label "has The Elements" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Infineon_Device> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Device_Elements> .

<http://www.w3id.org/ecsel-dr-PWR#has_information_object> a rdf:Property ;
  rdfs:label "has information object" ;
  rdfs:comment "States that the devices have ona or more information objects, which can be a sensor data sheet for the sensors." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Infineon_Device> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#SemiconductorProduct(its_name)_DataSheet> .

<http://www.w3id.org/ecsel-dr-PWR#has_a_Configuration> a rdf:Property ;
  rdfs:label "has a Configuration" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Infineon_Device> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Device_Configuration> .

<http://www.w3id.org/ecsel-dr-PWR#made_(the_method_name,_e.g.:_observation,_and_amlification)> a rdf:Property ;
  rdfs:label "Makes Switching" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Infineon_Device> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#The_method_of_the_device_function> .

<http://www.w3id.org/ecsel-dr-PWR#The_Temperature_Must_Not_Exceed> a rdf:Property ;
  rdfs:label "The Temperature Must Not Exceed" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Infineon_Device> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Maximum_Junction_Temperature> .

<http://www.w3id.org/ecsel-dr-PWR#has_an_Operation_Modes> a rdf:Property ;
  rdfs:label "has an Operation Modes" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Infineon_Device> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Enhancement> .

<http://www.w3id.org/ecsel-dr-PWR#has_an_Operation_Region> a rdf:Property ;
  rdfs:label "has an Operation Region" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Infineon_Device> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Region_of_Operation> .

<http://www.w3id.org/ecsel-dr-PWR#has_A_Configuration> a rdf:Property ;
  rdfs:label "has A Configuration" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Infineon_Device> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Device_Configuration> , <http://www.w3id.org/ecsel-dr-PWR#P-channel_Configuration> .

<http://www.w3id.org/ecsel-dr-PWR#hasControlMethod> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Infineon_Device> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Control_Method> .

<http://www.w3id.org/ecsel-dr-PWR#has_deployment> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#System> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Deployment> .

<http://www.w3id.org/ecsel-dr-AT#TTP_A> a rdfs:Class ;
  rdfs:label "Time Triggered Protocol Class A"@de ;
  rdfs:comment """TTP/A (Time-Triggered Protocol Class A) ist ein weiteres zeitgesteuertes Protokoll der Time-Triggered Architecture, welches für die echtzeitfähige Ansteuerung von Sensoren, Aktuatoren und nicht sicherheitskritischen Steuergeräten konzipiert ist.

Wie TTP/C verwendet TTP/A ein TDMA-Schema für die kollisionsfreie Übertragung von Nachrichten. TTP/A ist ein Master-Slave-System, das für Low-Cost Feldbussystemanwendungen entwickelt worden ist. TTP/A kann auf einem Standard 8-bit Mikrocontroller mit einer Standard UART (Universal Asynchronous Receiver Transmitter) implementiert werden; dieser Physical Layer ist aber im Prinzip austauschbar. In der Standardimplementierung verwendet TTP/A eine UART-Kodierung mit einem Startbit, 8 Datenbits, einem Paritybit und einem Stopbit. Die Kommunikation ist in Runden und Slots unterteilt, in einem Slot wird genau ein UART-Wort gesendet. Eine Runde setzt sich aus einer festen Abfolge von Slots zusammen, wobei jeder Slot fix einer bestimmten Nachricht zugeordnet ist. Man spricht in diesem Zusammenhang auch von einem Nachrichtenfahrplan oder Round Description List (RODL). Nachrichten werden somit periodisch mit einem vorhersagbaren Zeitverhalten übertragen. TTP/A unterstützt acht verschiedene RODL, sodass schnell zwischen verschiedenen Zusammenstellungen von Daten gewechselt werden kann.

TTP/A garantiert eine feste Antwortzeit, wenn keine Übertragungsfehler auftreten. Treten hingegen Fehler auf, so verzögert sich die Übertragung der Nachricht um eine Periode. Dies ist bei Sensordaten im Allgemeinen kein Problem, bei gesendeten Befehlen müssen diese jedoch idempotent sein, um ein fehlertolerantes Verhalten im Zeitbereich zu garantieren.

TTP/A bietet ein Adressierungsschema namens Interface File System (IFS) für bis zu 256 Knoten mit je 64 Files. Ein File besteht aus bis zu 256 Records zu je 4 Bytes. Das IFS bietet eine einheitliche Adressierung von Datenwörtern bei der Erstellung von Nachrichtenfahrplänen."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_Car_Airplane> .

<http://www.w3id.org/ecsel-dr-PWR#Process_Output> a rdfs:Class ;
  rdfs:label "Process Output" ;
  rdfs:comment "Any information that is reported from a Procedure." .

<http://www.w3id.org/ecsel-dr-AT#Enocean> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_3_4_NetworkTechnology> .

<http://www.w3id.org/ecsel-dr-AH#AH_SystemRegistrySystem_SySD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system_SySD> .

<http://www.w3id.org/ecsel-dr-OM#OpenOrderBook> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PWR#PowerConverters> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Semiconductors> .

<http://www.w3id.org/ecsel-dr-PWR#are> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Semiconductors> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Products> .

<http://www.w3id.org/ecsel-dr-PMV#VACD> a rdfs:Class ;
  rdfs:label "Value-added chain diagram" ;
  rdfs:comment """A Value-Added Chain is a process that represents an element of the process chain. A process hierarchy can be realized by hierarchically structuring value chains, thus modeling business areas, process groups, business processes and business process variants using the sam notation.
House: represents enabler processes.""" .

<http://www.w3id.org/ecsel-dr-PMV#hasSuperiorVACD> a rdf:Property ;
  rdfs:label "hasSuperiorVACD" ;
  rdfs:comment "Value-added chain diagrams have another value-added chain diagram as superior. The connector is used to represent the hierarchical order." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#VACD> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#VACD> .

<http://www.w3id.org/ecsel-dr-PMV#isRepresentedBy> a rdf:Property ;
  rdfs:label "isRepresentedBy" ;
  rdfs:comment "Represents the inverse property of represents." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Task> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Screen> .

<http://www.w3id.org/ecsel-dr-PMV#hasSubordinateVACD> a rdf:Property ;
  rdfs:label "hasSubordinateVACD" ;
  rdfs:comment "Value-added chain diagrams have value-added chain diagrams as subordinates. The connector is used to represent the hierarchical order." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#VACD> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#VACD> .

<http://www.w3id.org/ecsel-dr-PMV#hasObject> a rdf:Property ;
  rdfs:label "hasObject" ;
  rdfs:comment "EPCs and Value-added chain diagrams consist of objects." ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#hasSubordinate> a rdf:Property ;
  rdfs:label "hasSubordinate" ;
  rdfs:comment "Value-added chain diagrams have EPCs as subordinates. The connector is used to represent the hierarchical order." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#VACD> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#BPFlow> .

<http://www.w3id.org/ecsel-dr-AT#MES> a rdfs:Class ;
  rdfs:label "Maufacturing Execution System" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-PWR#SemiconductorProduct(its_name)_DataSheet> a rdfs:Class ;
  rdfs:label "SiC MOSFET DataSheet" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Documents> .

<http://www.w3id.org/ecsel-dr-PWR#has_The_Propeties_of> a rdf:Property ;
  rdfs:label "has The Propeties of" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#SemiconductorProduct(its_name)_DataSheet> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Infineon_Device> .

<http://www.w3id.org/ecsel-dr-OOSMP#IntegratedPressureSensor> a rdfs:Class ;
  rdfs:label "Integrated Pressure Sensor" ;
  rdfs:comment "Infineon offers a different range of barometric air pressure sensor for automotive and industrial applications. The barometric air pressure (BAP) is an important parameter to compute the air-fuel ratio provided to the engine and for controlling spark advance to optimize engine efficiency. In automotive applications where high production volumes are common there is substantial interest in precision, low-cost and fully integrated sensors." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#PressureSensor> .

<http://www.w3id.org/ecsel-dr-PROD#SKU> a rdfs:Class ;
  rdfs:comment "finished product by storage location; called DC BauNumber" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PROD#Product> .

<http://www.w3id.org/ecsel-dr-PROD#isSimilarTo> a rdf:Property ;
  rdfs:comment """other variant after a product change, in case the customer wants to order old and new variant over a longer period
separate SalesProductNumber""" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#Product> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PROD#Product> .

<http://www.w3id.org/ecsel-dr-PROD#additionalProperty> a rdf:Property ;
  rdfs:comment "A property-value pair representing an additional characteristics of the entitity, e.g. a product feature or another characteristic for which there is no matching property in schema.org." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#Product> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PROD#location> a rdf:Property ;
  rdfs:comment "A Location within Infineon’s internal supply chain is a local area where products are manufactured or stored." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#Product> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PWR#Width> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#GeometricDimension> .

<http://www.w3id.org/ecsel-dr-AT#PLM1_System_Suite> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#PLM-System-FirstGeneration> .

<http://www.w3.org/ns/ssn/systems/OperatingRange> a rdfs:Class ;
  rdfs:label "Operating Range" ;
  rdfs:comment """\"Describes normal OperatingProperties of a System under some specified Conditions. For example, to the power requirement or maintenance schedule of a System under a specified temperature range.
In the absence of OperatingProperties, it simply describes the Conditions in which a System is expected to operate.\"""" ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/Property> .

<http://www.w3.org/ns/ssn/systems/inCondition> a rdf:Property ;
  rdfs:label "in condition" ;
  rdfs:comment "Describes the prevailing environmental Conditions for SystemCapabilities, OperatingRanges and SurvivalRanges." ;
  rdfs:domain <http://www.w3.org/ns/ssn/systems/OperatingRange> ;
  rdfs:range <http://www.w3.org/ns/ssn/Condition> .

<http://www.w3.org/ns/ssn/systems/hasOperatingProperty> a rdf:Property ;
  rdfs:label "has operating property" ;
  rdfs:comment "Relation from an OperatingRange of a System to an OperatingProperty describing the operating range of the System." ;
  rdfs:domain <http://www.w3.org/ns/ssn/systems/OperatingRange> ;
  rdfs:range <http://www.w3.org/ns/ssn/systems/OperatingProperty> ;
  rdfs:subPropertyOf <http://www.w3.org/ns/ssn/hasProperty> .

<http://www.w3id.org/ecsel-dr-SO#Product_Number> a rdfs:Class ;
  rdfs:comment "The product number is a unique identifier of a product. The scope is limited to finished products only."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Product> .

<http://www.w3id.org/ecsel-dr-AT#RobotCellPlanning> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#PLM1_Module> .

<http://www.w3id.org/ecsel-dr-PRIMA#Role> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PWR#Materials> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#IndutrialSector> .

<http://www.w3id.org/ecsel-dr-SO#Bottlenecks> a rdfs:Class ;
  rdfs:comment "A capacity Bottleneck is defined as an equipment or multiple equipment that reflect the capacity of the whole line (either a dedicated Line or Pool sharing)."@en .

<http://www.w3id.org/ecsel-dr-SO#hasProductLevel> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Product_Level> .

<http://www.w3id.org/ecsel-dr-SO#hasEquipmentGroupID> a rdf:Property ;
  rdfs:comment "Equipment: FK; technical equipment group affiliation; FK to FabID"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Equipment_Group> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-OOSMP#Division> a rdfs:Class ;
  rdfs:label "Division" ;
  rdfs:comment "A division is a administrative business unit that is smaller than the whole company, but it is self-contained and most often responsible for its own revenue, cost, and profit. It has one or more business lines." ;
  rdfs:subClassOf <http://www.w3.org/ns/org#OrganizationalUnit> .

<http://www.w3id.org/ecsel-dr-OOSMP#responsibleForApplicationLevel3_Division> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Division> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationLevel3> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#responsibleForApplicationArea> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasBusinessLine> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Division> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#BusinessLine> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasSubUnit> .

<http://www.w3id.org/ecsel-dr-SCP#AggregatedCapacity> a rdfs:Class ;
  rdfs:label "AggregatedCapacity"@iri-based .

<http://www.w3id.org/ecsel-dr-SO#Route> a rdfs:Class ;
  rdfs:comment "The master entity “Route” describes the structure of a workflow out of operations. Every product uses a specific route in its value stream, i.e. the complete sequence of operations with all mandatory and optional operations necessary to complete the product. A route makes use of the single operations. (workflow descriptive master entity)"@en .

<http://www.w3id.org/ecsel-dr-SO#hasSequenceNumber> a rdf:Property ;
  rdfs:comment "Route: PK; Sequential number of operations along the route"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Route> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-SO#hasRouteName> a rdf:Property ;
  rdfs:comment "Name of route (usually equals product names requiring the route)"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Route> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasOperationID> a rdf:Property ;
  rdfs:comment "FK; Name of operation"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Route> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PRIMA#Region> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AH#System-of-Systems_Description_SoSD> a rdfs:Class ;
  rdfs:comment "Is a high level view, describing the System of Systems main functionalities and architecture. In the context of the Arrowhead project this document can be used to provide a high level view of a pilot. The SoSD refers to a number of SySDs (which are the building blocks in the SoSD) and as such indirectly to how the included systems need to be implemented in order to be interoperable. (Source: Arrowhead Framework Definitions V2.4)"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_system_of_systems_documentation_document> .

<http://www.w3id.org/ecsel-dr-AH#isPartOfSoSDoc> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#AH_system_of_systems_documentation_document> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#AH_system_of_systems_documentation> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#isPartOf> .

<http://www.w3id.org/ecsel-dr-SO#Workshop> a rdfs:Class ;
  rdfs:comment "The overall organizational working structures within the fabs is described in the entity “Workshop”. (master entity)"@en .

<http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_service_SD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_core_service_SD> .

<http://www.w3id.org/ecsel-dr-PWR#Entity> a rdfs:Class ;
  rdfs:comment "Anything: real, possible, or imaginary, which some modeller wants to talk about for some purpose." .

<http://www.w3.org/ns/sosa/Procedure> a rdfs:Class ;
  rdfs:label "Procedure"@en ;
  rdfs:comment "A workflow, protocol, plan, algorithm, or computational method specifying how to make an Observation, create a Sample, or make a change to the state of the world (via an Actuator). A Procedure is re-usable, and might be involved in many Observations, Samplings, or Actuations. It explains the steps to be carried out to arrive at reproducible results."@en .

<http://www.w3.org/ns/ssn/hasInput> a rdf:Property ;
  rdfs:label "has input"@en ;
  rdfs:comment "Relation between a Procedure and an Input to it."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Procedure> ;
  rdfs:range <http://www.w3.org/ns/ssn/Input> .

<http://www.w3.org/ns/ssn/implementedBy> a rdf:Property ;
  rdfs:label "implemented by"@en ;
  rdfs:comment "Relation between a Procedure (an algorithm, procedure or method) and an entity that implements that Procedure in some executable way."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Procedure> ;
  rdfs:range <http://www.w3.org/ns/ssn/System> .

<http://www.w3.org/ns/ssn/hasOutput> a rdf:Property ;
  rdfs:label "has output"@en ;
  rdfs:comment "Relation between a Procedure and an Output of it."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Procedure> ;
  rdfs:range <http://www.w3.org/ns/ssn/Output> .

<http://www.w3id.org/ecsel-dr-AH#AH_application_system_SySD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#System_Description_SySD> .

<http://www.w3id.org/ecsel-dr-AT#TCP> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_TransportProtocol> .

<http://www.w3id.org/ecsel-dr-AT#OSI_L3_NetworkLayer> a rdfs:Class ;
  rdfs:label "Network Layer"@en , "Vermittlungsschicht"@de ;
  rdfs:comment """Controls the operations of the subnet, deciding which physical path the data takes. 
Transmits Packets: \"letters\" containing IP addresses. 
Topics: Routing, Subnet traffic control, Frame fragmentation, logical-physical address mapping, Subnet usage accounting. 
Central devices: Routers. 
Example protocols: IPv4, IPv6, IPX, ICMP"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_DetailedLayer> .

<http://www.w3id.org/ecsel-dr-AH#Transfer_protocol> a rdfs:Class ;
  rdfs:comment "corresponds to OSI layers 6 and 7" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Communication_technology> .

<http://www.w3id.org/ecsel-dr-OOSMP#SmartDriver> a rdfs:Class ;
  rdfs:label "Smart Driver" ;
  rdfs:comment "A semiconductor product which is used as smart driver" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> .

<http://www.w3id.org/ecsel-dr-OOSMP#partOfAsSmartDriver> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SmartDriver> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#partOf> .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_3_4> a rdfs:Class ;
  rdfs:comment "Communication between devices on ISA-95 level 3 and ISA-95 level 4 (inter-level-communication 3 - 4)"@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ISA-95_Communication> .

<http://www.w3id.org/ecsel-dr-PWR#Negative_(-)> a rdfs:Class ;
  rdfs:label "Negative (-)" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Voltage> .

<http://www.w3id.org/ecsel-dr-RAMI40#Version> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-SCP#SupplyPicture> a rdfs:Class ;
  rdfs:label "SupplyPicture"@iri-based .

<http://www.w3id.org/ecsel-dr-AT#PLC> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ControlDevice> .

<http://www.w3id.org/ecsel-dr-AT#RDFS> a rdfs:Class ;
  rdfs:label "Resource Description Framework Schema"@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L4_SemanticsRepresentation> .

<http://www.w3id.org/ecsel-dr-SO#EPA> a rdfs:Class ;
  rdfs:comment "The EPA is a product identifier referring to the associated process."@en .

<http://www.w3id.org/ecsel-dr-SO#hasPriorityClass> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#EPA> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Priority_Classes> .

<http://www.w3id.org/ecsel-dr-SO#isProcessedBy> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#EPA> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Tool> .

<http://www.w3id.org/ecsel-dr-SO#isDedicatedTo> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#EPA> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Tool> .

<http://www.w3id.org/ecsel-dr-SO#hasOwner> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#EPA> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Owner> .

<http://www.w3id.org/ecsel-dr-AT#SECS> a rdfs:Class ;
  rdfs:label "SEMI Equipment Communications Standard"@en ;
  rdfs:comment """The SECS/GEM is the semiconductor's equipment interface protocol for equipment-to-host data communications. In an automated fab, the interface can start and stop equipment processing, collect measurement data, change variables and select recipes for products. The SECS (SEMI Equipment Communications Standard)/GEM (Generic Equipment Model) standards do all this in a defined way.

Developed by the SEMI (Semiconductor Equipment and Materials International) organization,[1] the standards define a common set of equipment behaviour and communications capabilities.

The Generic Model for Communications and Control Of Manufacturing Equipment (GEM) standard is maintained and published by the non-profit organization Semiconductor Equipment and Materials International (SEMI). Generally speaking, the SECS/GEM standard defines messages, state machines and scenarios to enable factory software to control and monitor manufacturing equipment. The GEM standard is formally designated and referred to as SEMI standard E30, but frequently simply referred to as the GEM or SECS/GEM standard. GEM intends \"to produce economic benefits for both device manufacturers and equipment suppliers...\" by defining \"... a common set of equipment behavior and communications capabilities that provide the functionality and flexibility to support the manufacturing automation programs of semiconductor device manufacturers\" [SEMI E30, 1.3]. GEM is a standard implementation of the SECS-II standard, SEMI standard E5. Many equipment in semiconductor (front end and back end), surface mount technology, electronics assembly, photovoltaic, flat panel display and other manufacturing industries worldwide provide a GEM/SECS interface on the manufacturing equipment so that the factory host software can communicate with the machine for monitoring and/or controlling purposes. Because the GEM standard was written with very few semiconductor-specific features, it can be applied to virtually any automated manufacturing equipment in any industry.

All GEM compliant manufacturing equipment share a consistent interface and certain consistent behavior. GEM equipment can communicate with a GEM capable host using either TCP/IP (using the HSMS standard, SEMI E37) or RS-232 based protocol (using the SECS-I standard, SEMI E4). Often both protocols are supported. Each equipment can be monitored and controlled using a common set of SECS-II messages specified by GEM.

There are many additional SEMI standards and factory specifications that reference the GEM standard its features. These additional standards are either industry-specific or equipment-type specific. Following are a few examples.

Source: https://en.wikipedia.org/wiki/SECS/GEM"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-AT#OSI_AL3_TransportLayer> a rdfs:Class ;
  rdfs:label "Transport Layer"@en , "Transportschicht"@de ;
  rdfs:comment """Corresponds 1:1 to ISO/OSI layer 4: Transport Layer. 
takes care for end-to-end transmission of data. 
Mostly known protocol of this layer is the Transmission Control Protocol (TCP).
It realizes connections between two network hosts for ensured transmission of data streams."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_AggregatedLayer> .

<http://www.w3id.org/ecsel-dr-AT#auto-gration-Specification> a rdfs:Class ;
  rdfs:comment """XML Schema describing the Grammar of data content representing the content of a set of EDIFACT messages.
Relies on XML as data syntax, XML Schema as knowledge representation scheme and on EDIFACT message specifications (like ORDER, ORDRSP, DELFOR, DELJIT etc.). Has no Semantics representation.""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ServiceDataLanguage> .

<http://www.w3id.org/ecsel-dr-PWR#Constant_Resistance> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Resistance> .

<http://www.w3id.org/ecsel-dr-PWR#Deployment-related_Process> a rdfs:Class ;
  rdfs:label "Deployment-related Process" ;
  rdfs:comment "Place to group all the various Processes related to Deployment. For example, as well as Deployment, installation, maintenance, deployment of the further devices and the like would all be classified under DeploymentRelatedProcess." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Process> .

<http://www.w3id.org/ecsel-dr-PWR#has_input> a rdf:Property ;
  rdfs:label "has input" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Process> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Process_Input> .

<http://www.w3id.org/ecsel-dr-PWR#has_output> a rdf:Property ;
  rdfs:label "has output" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Process> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Process_Output> .

<http://www.w3id.org/ecsel-dr-OOSMP#MagneticPositionSensor> a rdfs:Class ;
  rdfs:label "Magnetic Position Sensor" ;
  rdfs:comment "A magnetic position sensor is a sensor which measures magnetic positions." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#Sensor> .

<http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Goal> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PMV#controls> a rdf:Property ;
  rdfs:label "controls" ;
  rdfs:comment "A goal controls the outcome of a function in a process flow." ;
  rdfs:domain <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Goal> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Function> .

<http://www.w3id.org/ecsel-dr-AH#AH_GatewaySystem_SySDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system_SySDD> .

<http://www.w3id.org/ecsel-dr-AT#StandardisationOrganization> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-SO#Product> a rdfs:Class ;
  rdfs:comment "A product is any tangible output or service that is a result of a process and that is intended for delivery to a customer or end user. A product is a work product that is delivered to the customer."@en .

<http://www.w3id.org/ecsel-dr-AH#End-to-End_communication_technology> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Communication_technology> .

<http://www.w3id.org/ecsel-dr-AT#SCADA-System> a rdfs:Class ;
  rdfs:label "Supervisory Control And Data Aquisision System" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-SO#Process_Group> a rdfs:Class ;
  rdfs:comment "A Process Group is the third hierarchy level in the Technology Catalogue and a subset of the Process Class. A Process Group is defined by the device type and its generation (eventually voltage class) or wafer diameter"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Process> .

<http://www.w3id.org/ecsel-dr-AT#ZigBee> a rdfs:Class ;
  rdfs:comment "https://de.wikipedia.org/wiki/ZigBee"@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_3_4_NetworkTechnology> .

<http://www.w3id.org/ecsel-dr-AH#AH_QoS-Manager_SySD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system_SySD> .

<http://www.w3id.org/ecsel-dr-AT#Computer> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Device> .

<http://www.w3id.org/ecsel-dr-AT#APS> a rdfs:Class ;
  rdfs:label "Advanced Planning System"@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_1_2> a rdfs:Class ;
  rdfs:comment "Communication between devices on ISA-95 level 1 and ISA-95 level 2 (inter-level-communication 1 - 2)"@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ISA-95_Communication> .

<http://www.w3id.org/ecsel-dr-AT#REST> a rdfs:Class ;
  rdfs:label "Representational State Transfer"@de ;
  rdfs:comment "REST is not a complete Service-oriented architecture, but an architecture style that enables systems to show SoA properties." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitecture> .

<http://www.w3id.org/ecsel-dr-AT#hasServiceDescriptionLanguage> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitecture> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AT#W3C_L5_DataSemantics> .

<http://www.w3id.org/ecsel-dr-PMV#Material> a rdfs:Class ;
  rdfs:label "Material" ;
  rdfs:comment "The matter from which something can be made. Material can include but is not limited to raw and processed material, components, parts, assemblies, sub-assemblies, fuels, lubricants, coolants, cleaning agents, and small tools and accessories that may be consumed directly or indirectly." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#Input> , <http://www.w3id.org/ecsel-dr-PMV#Output> , <http://purl.org/dc/terms/PhysicalResource> .

<http://www.w3id.org/ecsel-dr-AT#MQTT_TCPIP_based> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#MQTT> .

<http://www.w3id.org/ecsel-dr-PWR#Financial> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#IndutrialSector> .

<http://www.w3id.org/ecsel-dr-PWR#Switching_Frequency> a rdfs:Class ;
  rdfs:label "Switching Frequency" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Property> .

<http://www.w3id.org/ecsel-dr-OOSMP#SensorSubApplication> a rdfs:Class ;
  rdfs:label "Sensor Sub Application" ;
  rdfs:comment "An application area on lowest level (corresponing to application level 3) for sensors which can be assigned to super application levels (sensor main application)" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> .

<http://www.w3id.org/ecsel-dr-OOSMP#subApplicationAreaOfSensorMainApplication> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SensorSubApplication> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#SensorMainApplication> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#subApplicationAreaOf> .

<http://www.w3id.org/ecsel-dr-PROD#SalesProduct> a rdfs:Class ;
  rdfs:comment """sellable product; It can be identified by salesProductNumber

""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PROD#Product> .

<http://www.w3id.org/ecsel-dr-PROD#salesProductNumber> a rdf:Property ;
  rdfs:comment "A salesProductNumber is a unique identifier of a Sales Product" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#SalesProduct> ;
  rdfs:range xsd:string ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-PROD#salesProductName> .

<http://www.w3id.org/ecsel-dr-PROD#substituteProduct> a rdf:Property ;
  rdfs:comment """are finishedProductNumbers with different SalesProductNumber that meet the customer’s requirements on form – fit – function
A Sales Product SP2 that can be used instead of a Sales Product SP1 to promise an order to a customer 
""" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#SalesProduct> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PROD#SalesProduct> .

<http://www.w3id.org/ecsel-dr-PROD#halogeenFree> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#SalesProduct> ;
  rdfs:range xsd:boolean .

<http://www.w3id.org/ecsel-dr-PROD#hasFinishedProduct> a rdf:Property ;
  rdfs:comment "SalesProduct hasFinishedProduct FinishedProduct" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#SalesProduct> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PROD#FinishedProduct> .

<http://www.w3id.org/ecsel-dr-PROD#customerPartNumberSpecification> a rdf:Property ;
  rdfs:comment """contain relevant information including customer and CPN
Several CPNs can be linked to the same SP number 
'sold-to'""" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#SalesProduct> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PROD#CPNSpec> .

<http://www.w3id.org/ecsel-dr-PROD#salesProductName> a rdf:Property ;
  rdfs:comment """In verbal communication it is usually identified by Sales Product Name (SPN) which might not be sufficient for unique identification.
It reflects a product from customer view without differentiation of manufacturing route or storage location ( form – fit – function ).

 

""" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#SalesProduct> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PROD#hasProductFamily> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#SalesProduct> ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-PROD#orderablePartNumber> a rdf:Property ;
  rdfs:comment """Customers may use the OPN as their customer part number for ordering at Infineon 
based on product attributes""" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#SalesProduct> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PWR#InformationTechnology> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#IndutrialSector> .

<http://www.w3id.org/ecsel-dr-AT#KPI-ML> a rdfs:Class ;
  rdfs:comment """KPI-ML is an XML implementation of the ISO 22400 standard, Automation systems integration - Key performance indicators (KPIs) for manufacturing operations management.  KPI-ML consists of a set of XML schemas written using the World Wide Web Consortium's XML Schema language (XSD) that implement the data models in the ISO 22400 standard.
Companies interested in following ISO 22400 for integration projects may use KPI-ML to exchange KPI definitions and values between manufacturing systems such as control systems and manufacturing execution systems and IT systems, as well as visualization systems such as dashboards. Any company may use KPI-ML royalty free, provided credit is given to MESA.
V0100 is the first version of KPI-ML.
The MESA XML Committee maintains KPI-ML. It is fully staffed by volunteers and is open to all MESA members. To join the committee or to send feedback on KPI-ML, send a request to KPI-ML@mesa.org.
(http://www.mesa.org/en/KPIML.asp)"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#MarkupLanguage> .

<http://www.w3id.org/ecsel-dr-PRIMA#ProjectManager> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PRIMA#Role> .

<http://www.w3id.org/ecsel-dr-PRIMA#hasMinimumJobExperience> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#ProjectManager> ;
  rdfs:range xsd:integer ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-PRIMA#hasExperience> .

<http://www.w3id.org/ecsel-dr-PRIMA#hasMinimumProjectManagerExperience> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#ProjectManager> ;
  rdfs:range xsd:integer ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-PRIMA#hasExperience> .

<http://www.w3id.org/ecsel-dr-PRIMA#hasExperience> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#ProjectManager> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-PRIMA#hasTrainingLevel> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#ProjectManager> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PRIMA#Training> .

<http://www.w3id.org/ecsel-dr-AT#ISO> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#StandardisationOrganization> .

<http://www.w3.org/2006/time#Interval> a rdfs:Class ;
  rdfs:label "Time interval"@en ;
  rdfs:comment "A temporal entity with an extent or duration"@en ;
  rdfs:subClassOf <http://www.w3.org/2006/time#TemporalEntity> .

<http://www.w3.org/2006/time#inside> a rdf:Property ;
  rdfs:label "has time instant inside"@en ;
  rdfs:comment "An instant that falls inside the interval. It is not intended to include beginnings and ends of intervals."@en ;
  rdfs:domain <http://www.w3.org/2006/time#Interval> ;
  rdfs:range <http://www.w3.org/2006/time#Instant> .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_2_3> a rdfs:Class ;
  rdfs:comment "Communication between devices on ISA-95 level 2 and ISA-95 level 3 (inter-level-communication 2 - 3)"@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ISA-95_Communication> .

<http://www.w3id.org/ecsel-dr-AT#MaterialFlowSimulation> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#PLM1_Module> .

<http://www.w3id.org/ecsel-dr-OM#Supplier> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#ISA> a rdfs:Class ;
  rdfs:label "International Society of Automation (ISA)"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#StandardisationOrganization> .

<http://www.w3id.org/ecsel-dr-PRIMA#SubProject> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PRIMA#hasTask> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PRIMA#Task> .

<http://www.w3id.org/ecsel-dr-PRIMA#hasWorkPackage> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PRIMA#WorkPackage> .

<http://www.w3id.org/ecsel-dr-PRIMA#isSubProjectOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#SubProject> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> .

<http://www.w3id.org/ecsel-dr-AT#EDIFACT_ORDRSP> a rdfs:Class ;
  rdfs:label "Order response"@en ;
  rdfs:comment "EDIFACT message for Order Response."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#EDIFACT-Specification> .

<http://www.w3id.org/ecsel-dr-AT#WebAddress> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L1_WebPlatform> .

<http://www.w3id.org/ecsel-dr-AH#AH_SystemDiscoveryService_IDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service_IDD> .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer1_SensorsActuators> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer> .

<http://www.w3id.org/ecsel-dr-AT#W3C_L3_KnowledgeRepresentation> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#MESA> a rdfs:Class ;
  rdfs:comment "especially MESA XML Committee"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#StandardisationOrganization> .

<http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_core_system> .

<http://www.w3id.org/ecsel-dr-AT#IndustryPC> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ControlDevice> .

<http://www.w3id.org/ecsel-dr-PWR#Drain-Source_Voltage> a rdfs:Class ;
  rdfs:label "Drain-Source Voltage" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Property> .

<http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> a rdfs:Class ;
  rdfs:label "Application Area" ;
  rdfs:comment "A way in which something can be used for a particular purpose" .

<http://www.w3id.org/ecsel-dr-PROD#DREP> a rdfs:Class ;
  rdfs:comment "Die-Representative: supply element; where the package is not yet decided" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PROD#PlanningElement> .

<http://www.w3id.org/ecsel-dr-PROD#hasSKU_PD> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#DREP> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PROD#SKU> .

<http://www.w3id.org/ecsel-dr-PWR#Postive_(+)> a rdfs:Class ;
  rdfs:label "Positive (+)" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Voltage> .

<http://www.w3id.org/ecsel-dr-SO#Current_WIP> a rdfs:Class ;
  rdfs:comment "“Current WIP” entity describes the actual material distribution in the supply chain. (snapshot entity)"@en .

<http://www.w3id.org/ecsel-dr-SO#hasResidualTimeInFab> a rdf:Property ;
  rdfs:comment "Current WIP: Expected residual time lot spends in current Fab (FE/BE)"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Current_WIP> ;
  rdfs:range xsd:decimal .

<http://www.w3id.org/ecsel-dr-SCP#AATP> a rdfs:Class ;
  rdfs:label "AATP"@iri-based .

<http://www.w3id.org/ecsel-dr-SCP#NP_Forecast> a rdfs:Class ;
  rdfs:label "NP_Forecast"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#Forecast> .

<http://www.w3id.org/ecsel-dr-OOSMP#MagneticSpeedSensor> a rdfs:Class ;
  rdfs:label "Magnetic Speed Sensor" ;
  rdfs:comment "The  magnetic speed sensors are designed to measure speed in safety and powertrain applications such as speedometers, ABS, camshafts/crankshafts and automatic transmissions. They are also used in similar applications in the industrial sector. The sensors use a ferromagnetic gear tooth or encoder structure to measure linear or rotational speed and position." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#Sensor> .

<http://www.w3id.org/ecsel-dr-OOSMP#SubApplication> a rdfs:Class ;
  rdfs:label "Sub Application" ;
  rdfs:comment "An application area on lowest level (corresponing to application level 3) which can be assigned to super application levels (main application)" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> .

<http://www.w3id.org/ecsel-dr-OOSMP#subApplicationAreaOfMainApplication> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SubApplication> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MainApplication> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#subApplicationAreaOf> .

<http://www.w3id.org/ecsel-dr-PWR#Price> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Information_Object> .

<http://www.w3id.org/ecsel-dr-PMV#Rule> a rdfs:Class ;
  rdfs:label "Rule" ;
  rdfs:comment "Rules allow to model alternative, exclusive alternative and parallel process flows." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#ModelElement> .

<http://www.w3id.org/ecsel-dr-PMV#links> a rdf:Property ;
  rdfs:label "links" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Rule> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Rule> .

<http://www.w3id.org/ecsel-dr-PMV#leadsToEvent> a rdf:Property ;
  rdfs:label "leadsToEvent" ;
  rdfs:comment "A rule leads to an event. The connector is used to represent the chronological order in an EPC." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Rule> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Event> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-PMV#leadsTo> .

<http://www.w3id.org/ecsel-dr-PMV#activatesTask> a rdf:Property ;
  rdfs:label "activatesTask" ;
  rdfs:comment "Specialization of the activates property that links the class Rule with Task in the course of the process flow." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Rule> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Task> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-PMV#activates> .

<http://www.w3id.org/ecsel-dr-PMV#isAssignedTo> a rdf:Property ;
  rdfs:label "isAssignedTo" ;
  rdfs:comment "A rule is assigned to a process step. The connector is used to represent the chronological order in an EPC." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Rule> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#ModellingFunctionObject> .

<http://www.w3id.org/ecsel-dr-PMV#isLinkedBy> a rdf:Property ;
  rdfs:label "isLinkedBy" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Rule> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Rule> .

<http://www.w3id.org/ecsel-dr-AT#Database-System> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-AH#AH_core_service_IDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Interface_Design_Description_IDD> .

<http://www.w3id.org/ecsel-dr-AH#AH_core_system> a rdfs:Class ;
  rdfs:label "Arrowhead Core Component"@en ;
  rdfs:comment """Software system, that belongs to the \"standard\" components offered by Arrowhead framework. 
Arrowhead core systems can occur once in each Arrowhead Local Cloud. 
Arriwhead Core Systems can be distinguished in Arrowhead Mandatory Core Systems and Automation supporting systems. Mandatory core systems must exist in each Arrowhead Local Cloud, Automation supporting systems can occur in an Arrowhead Local Cloud."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_system> .

<http://www.w3id.org/ecsel-dr-PWR#Physical_Object> a rdfs:Class ;
  rdfs:label "Physical Object" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Object> .

<http://www.w3.org/ns/ssn/systems/Drift> a rdfs:Class ;
  rdfs:label "Drift" ;
  rdfs:comment "As a Sensor Property: a continuous or incremental change in the reported values of Observations over time for an unchanging Property under the defined Conditions. As an Actuator Property: a continuous or incremental change in the true value of the acted on ActuableProperty over time for an unchanging command under the defined Conditions." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/systems/SystemProperty> .

<http://www.w3id.org/ecsel-dr-PWR#Triode/Constant_Resistance_Region> a rdfs:Class ;
  rdfs:label "Triode/Constant Resistance Region" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#On-State_Region> .

<http://www.w3id.org/ecsel-dr-PWR#Acting_As> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Constant_Resistance> .

<http://www.w3id.org/ecsel-dr-SO#Plant> a rdfs:Class ;
  rdfs:comment "The “Plant” entity describes the plant as a physical location of one or more fabs. The Plant belongs to a supply chain and can either be internal or external. (master entity)"@en .

<http://www.w3id.org/ecsel-dr-SO#hasPlantInternal> a rdf:Property ;
  rdfs:comment "Plant: Does the plant belong to the company or to an external partner"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Plant> ;
  rdfs:range xsd:boolean .

<http://www.w3id.org/ecsel-dr-SO#hasPlantName> a rdf:Property ;
  rdfs:comment "Plant: Will generally refer to the geographical location of the plant"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Plant> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AT#FTP> a rdfs:Class ;
  rdfs:label "File Transfer Protocol"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-PWR#Threshold_Voltage> a rdfs:Class ;
  rdfs:label "Threshold Voltage" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Property> .

<http://www.w3id.org/ecsel-dr-PWR#The_Application_Voltage> a rdfs:Class ;
  rdfs:label "The Application Voltage" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Process_Input> .

<http://www.w3id.org/ecsel-dr-PWR#Has_Voltage> a rdf:Property ;
  rdfs:label "is a Volatge of" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#The_Application_Voltage> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Drain_Voltagea> .

<http://www.w3id.org/ecsel-dr-AH#Service_documentation> a rdfs:Class .

<http://www.w3.org/2006/time#TimeZone> a rdfs:Class ;
  rdfs:label "Time Zone"@en ;
  rdfs:comment """A Time Zone specifies the amount by which the local time is offset from UTC. 
\tA time zone is usually denoted geographically (e.g. Australian Eastern Daylight Time), with a constant value in a given region. 
The region where it applies and the offset from UTC are specified by a locally recognised governing authority."""@en .

<http://www.w3id.org/ecsel-dr-AT#SoA_Server> a rdfs:Class ;
  rdfs:comment """\"Role\" or function of an software (application) system that offers one or several services to other systems. 
Other names: Service Producer,"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitecture_FunctionPattern> .

<http://www.w3id.org/ecsel-dr-PWR#Off-State_Region> a rdfs:Class ;
  rdfs:label "Off-State Region" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Region_of_Operation> .

<http://www.w3id.org/ecsel-dr-OM#Allocation> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-OM#isAllocatedBy> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#Allocation> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#Supply> .

<http://www.w3id.org/ecsel-dr-OM#Allocates> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#Allocation> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#Supply> .

<http://www.w3id.org/ecsel-dr-AT#2G_GPRS> a rdfs:Class ;
  rdfs:label "General Packaged Radio Service"@en ;
  rdfs:comment """Second generation of Wireless Wide Area Data Transmission Networks. 
Uses GSM radio infrastructure."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> .

<http://www.w3id.org/ecsel-dr-AT#MicroController> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ControlDevice> .

<http://www.w3id.org/ecsel-dr-AT#DHCP> a rdfs:Class ;
  rdfs:label "Dynamic Host Configuration Protocol"@de ;
  rdfs:comment "Das Dynamic Host Configuration Protocol (DHCP) ist ein Kommunikationsprotokoll in der Computertechnik. Es ermöglicht die Zuweisung der Netzwerkkonfiguration an Clients durch einen Server."@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-AT#CSV> a rdfs:Class ;
  rdfs:label "Comma Separated Values" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L2_DataSyntax> .

<http://www.w3id.org/ecsel-dr-PWR#On-State_Region> a rdfs:Class ;
  rdfs:label "On-State Region" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Region_of_Operation> .

<http://www.w3id.org/ecsel-dr-AH#AH_GlobalServiceDiscoveryService_SD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service_SD> .

<http://www.w3.org/ns/sosa/Observation> a rdfs:Class ;
  rdfs:label "Observation"@en ;
  rdfs:comment "Act of carrying out an (Observation) Procedure to estimate or calculate a value of a property of a FeatureOfInterest. Links to a Sensor to describe what made the Observation and how; links to an ObservableProperty to describe what the result is an estimate of, and to a FeatureOfInterest to detail what that property was associated with."@en .

<http://www.w3.org/ns/sosa/observedProperty> a rdf:Property ;
  rdfs:label "observed property"@en ;
  rdfs:comment "Relation linking an Observation to the property that was observed. The ObservableProperty should be a property of the FeatureOfInterest (linked by hasFeatureOfInterest) of this Observation."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Observation> ;
  rdfs:range <http://www.w3.org/ns/sosa/ObservableProperty> .

<http://www.w3.org/ns/sosa/phenomenonTime> a rdf:Property ;
  rdfs:label "phenomenon time"@en ;
  rdfs:comment "The time that the Result of an Observation, Actuation or Sampling applies to the FeatureOfInterest. Not necessarily the same as the resultTime. May be an Interval or an Instant, or some other compound TemporalEntity."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Observation> ;
  rdfs:range <http://www.w3.org/2006/time#TemporalEntity> .

<http://www.w3.org/ns/ssn/systems/qualityOfObservation> a rdf:Property ;
  rdfs:label "quality of observation" ;
  rdfs:comment "Relation linking an Observation to the adjudged quality of the Result. This is complementary to the SystemCapability information recorded for the Sensor that made the Observation." ;
  rdfs:domain <http://www.w3.org/ns/sosa/Observation> ;
  rdfs:range <http://www.w3.org/ns/sosa/Result> ;
  rdfs:subPropertyOf <http://www.w3.org/ns/ssn/hasProperty> .

<http://www.w3.org/ns/ssn/oversamplingUsed> a rdf:Property ;
  rdfs:label "oversampling used" ;
  rdfs:comment "Link to the oversampling rate." ;
  rdfs:domain <http://www.w3.org/ns/sosa/Observation> ;
  rdfs:range <http://www.w3.org/ns/ssn/OversamplingRate> .

<http://www.w3.org/ns/ssn/wasOriginatedBy> a rdf:Property ;
  rdfs:label "was originated by"@en ;
  rdfs:comment "Relation between an Observation and the Stimulus that originated it."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Observation> ;
  rdfs:range <http://www.w3.org/ns/ssn/Stimulus> .

<http://www.w3.org/ns/sosa/resultTime> a rdf:Property ;
  rdfs:label "result time"@en ;
  rdfs:comment "The result time is the instant of time when the Observation, Actuation or Sampling activity was completed."@en ;
  rdfs:range xsd:dateTime .

<http://www.w3.org/ns/sosa/madeBySensor> a rdf:Property ;
  rdfs:label "made by sensor"@en ;
  rdfs:comment "Relation between an Observation and the Sensor which made the Observation."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Observation> ;
  rdfs:range <http://www.w3.org/ns/sosa/Sensor> .

<http://www.w3.org/ns/sosa/hasResult> a rdf:Property ;
  rdfs:label "has result"@en ;
  rdfs:comment "Relation linking an Observation or Actuation or act of Sampling and a Result or Sample."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Observation> ;
  rdfs:range <http://www.w3.org/ns/sosa/Result> , <http://www.w3.org/ns/sosa/Sample> .

<http://www.w3.org/ns/sosa/hasFeatureOfInterest> a rdf:Property ;
  rdfs:label "has feature of interest"@en ;
  rdfs:comment "A relation between an Observation and the entity whose quality was observed, or between an Actuation and the entity whose property was modified, or between an act of Sampling and the entity that was sampled."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Observation> ;
  rdfs:range <http://www.w3.org/ns/sosa/FeatureOfInterest> .

<http://www.w3.org/ns/sosa/usedProcedure> a rdf:Property ;
  rdfs:label "used procedure"@en ;
  rdfs:comment "A relation to link to a re-usable Procedure used in making an Observation, an Actuation, or a Sample, typically through a Sensor, Actuator or Sampler."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Observation> ;
  rdfs:range <http://www.w3.org/ns/sosa/Procedure> .

<http://www.w3id.org/ecsel-dr-AT#OSI_L2_DataLink> a rdfs:Class ;
  rdfs:label "Data Link Layer"@en , "Sicherungsebene"@de ;
  rdfs:comment """Provides error-free transfer of data frames from one node to another over the physical layer. 
Frames are \"envelopes\", contains MAC address (MAC: Media Access Control). 
Topics: establishes and terminates the logical link between nodes. Frame traffic control. Frame sequencing. Frame acknowledgement. Frame delimiting. Frame error checking. Media access control. 
Central devices: Switch, Bridge, WAP
Examples: PPP/SLIP"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_DetailedLayer> .

<http://www.w3id.org/ecsel-dr-PWR#GateDriver> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PWR#Energy> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#IndutrialSector> .

<http://www.w3id.org/ecsel-dr-OOSMP#Industry> a rdfs:Class ;
  rdfs:label "Industry" ;
  rdfs:comment "An application area on top level (corresponing to application level 1) which can have several sub application levels (main application)" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasMainApplication> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#Industry> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MainApplication> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasSubApplicationArea> .

<http://www.w3id.org/ecsel-dr-AH#AH_OrchestrationService_IDD> a rdfs:Class ;
  rdfs:comment "Interface Design Description (IDD) of the Arrowhead mandatory core service Orchestration Service which is provided by the mandatory core system Orchestration System (Orchestrator)."@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_service_IDD> .

<http://www.w3id.org/ecsel-dr-PWR#System> a rdfs:Class ;
  rdfs:comment "System is a unit of abstraction for pieces of infrastructure that implements procedure. A System may have components, its subsystems, which are other systems.\"" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Physical_Object> .

<http://www.w3id.org/ecsel-dr-SCP#OrdersReschedule> a rdfs:Class ;
  rdfs:label "OrdersReschedule"@iri-based .

<http://www.w3id.org/ecsel-dr-SCP#calculateBased> a rdf:Property ;
  rdfs:label "calculateBased"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#OrdersReschedule> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#SupplyPicture> .

<http://www.w3.org/2006/time#DayOfWeek> a rdfs:Class ;
  rdfs:label "Day of week"@en ;
  rdfs:comment "The day of week"@en .

<http://www.w3id.org/ecsel-dr-AT#SCTP> a rdfs:Class ;
  rdfs:comment """Es wurde von der Internet Engineering Task Force (IETF) als neues Transportprotokoll vorgeschlagen und im Oktober 2000 in dem Standarddokument RFC 2960 veröffentlicht und im September 2007 durch RFC 4960 erweitert. Eine Einführung findet sich auch in RFC 3286. Das zuständige Gremium bei der IETF ist die Arbeitsgruppe Signaling Transport, kurz SIGTRAN.

Als Transportprotokoll steht SCTP auf derselben Stufe des TCP/IP-Referenzmodells wie TCP und UDP (Schicht 4 des OSI-Modells).

SCTP realisiert das Konzept einer Association: Hier wird eine Verbindung aufgebaut, in der mehrere Nachrichten-Datenströme in sich reihenfolgenerhaltend (untereinander aber potentiell nicht-reihenfolgenerhaltend) transportiert werden. Zusätzlich können einzelne, zum Beispiel dringende, Datagramme separat und außer der Reihe verschickt werden, die dadurch eventuell die In-Order-Datenströme „überholen“.

SCTP kennt außerdem Multistreaming und Multihoming (ein Host mit mehreren gültigen IP-Adressen). Es werden Heartbeats verwendet, um aktiv auf Verbindungsabriss zu testen.

Anders als TCP zeigt sich SCTP resistent gegen SYN-Flooding, eine Denial-of-Service-Attacke, bei der durch halboffene Verbindungen die Ressourcen des Servers aufgebraucht werden. Dazu verwendet es einen sogenannten Vier-Wege-Handshake. Hierbei speichert der Server bei einer Verbindungsanfrage (INIT-Paket) keine Zustandsinformationen, sondern schickt diese in Form eines Cookies (INIT-ACK-Paket) an den Client. Der Client muss dieses Cookie in seine Antwort (COOKIE-ECHO-Paket) einfügen und wird damit vom Server als zum Verbindungsaufbau berechtigt erkannt, was dieser ihm bestätigt (COOKIE-ACK-Paket). Ein ähnliches Verfahren ist mit TCP ebenfalls möglich, siehe SYN-Cookies.

Ursprünglich wurde SCTP als Transportprotokoll definiert, um Zeichengabenachrichten (SS7) aus Telefonnetzen auch über IP-Netzwerke übertragen zu können. Bei der Entwicklung stand insbesondere die Zuverlässigkeit des Protokolls im Vordergrund. SCTP ist aber auch für andere Anwendungen geeignet, da es Vorteile von TCP und UDP vereint. Eine wichtige, auf SCTP aufbauende Anwendung ist Reliable Server Pooling (RSerPool).

SCTP verwendet für Fluss- und Überlastkontrolle ähnliche Algorithmen wie TCP, verhält sich also in einem gemischten Netz (SCTP und TCP) neutral.[1]

Auch Java bietet seit Version 7 eine eigene API für SCTP an."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_TransportProtocol> .

<http://www.w3id.org/ecsel-dr-SO#Furnace_Process> a rdfs:Class ;
  rdfs:comment "Sequence of interdependent and linked procedures which, at every stage, consume one or more resources (employee time, energy, machines, money) to convert inputs (data, material, parts, etc.) into outputs. These outputs then serve as inputs for the next stage until a known goal or end result is reached."@en .

<http://www.w3id.org/ecsel-dr-AT#ANSI> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#StandardisationOrganization> .

<http://www.w3id.org/ecsel-dr-AH#AH_GatewaySystem_SySD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system_SySD> .

<http://www.w3id.org/ecsel-dr-PWR#Gate> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Device_Elements> .

<http://www.w3id.org/ecsel-dr-AH#AH_GatekeeperSystem_SySD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system_SySD> .

<http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_service> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_core_service> .

<http://www.w3id.org/ecsel-dr-AT#OASIS> a rdfs:Class ;
  rdfs:label "Organization for the Advancement of Structured Information Standards"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#StandardisationOrganization> .

<http://www.w3id.org/ecsel-dr-AH#AH_SystemDiscoveryService_SD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service_SD> .

<http://www.w3id.org/ecsel-dr-AT#W3C_L2_DataSyntax> a rdfs:Class .

<http://www.w3.org/ns/ssn/systems/SystemCapability> a rdfs:Class ;
  rdfs:label "System Capability" ;
  rdfs:comment "Describes normal measurement, actuation, sampling properties such as accuracy, range, precision, etc. Of a System under some specified Conditions such as temperature range. The capabilities specified here are those that affect the primary purpose of the System, while those in OperatingRange represent the system's normal operating environment, including Conditions that don't affect the Observations or the Actuations." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/Property> .

<http://www.w3.org/ns/ssn/systems/hasSystemProperty> a rdf:Property ;
  rdfs:label "has system property" ;
  rdfs:comment "Relation from a SystemCapability of a System to a SystemProperty describing the capabilities of the System." ;
  rdfs:domain <http://www.w3.org/ns/ssn/systems/SystemCapability> ;
  rdfs:range <http://www.w3.org/ns/ssn/systems/SystemProperty> ;
  rdfs:subPropertyOf <http://www.w3.org/ns/ssn/hasProperty> .

<http://www.w3id.org/ecsel-dr-OM#SupplierData> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-OM#hasSupplierAddress> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#SupplierData> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-OM#describesSupplier> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#SupplierData> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#Supplier> .

<http://www.w3id.org/ecsel-dr-SO#Target_Revenue> a rdfs:Class ;
  rdfs:comment "The target revenue is the amount of income a company wants to generate for the current accounting period."@en .

<http://www.w3id.org/ecsel-dr-SO#hasRevenuePerUnit> a rdf:Property ;
  rdfs:comment "Target Revenue: Revenue per unit of a certain technology"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Target_Revenue> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-SO#hasTargetCosts> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Target_Costs> .

<http://www.w3id.org/ecsel-dr-SO#hasTechnologyID> a rdf:Property ;
  rdfs:comment "Technology ID: FK; Name of the technology"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Technology> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasTechnology> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Technology> .

<http://www.w3.org/ns/ssn/systems/Latency> a rdfs:Class ;
  rdfs:label "Latency" ;
  rdfs:comment "The time between a command for an Observation and the Sensor providing a Result, under the defined Conditions." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/systems/SystemProperty> .

<http://www.w3id.org/ecsel-dr-OM#Supply> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-OM#isAllocatedTo> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#Supply> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#OrderLineItem> .

<http://www.w3.org/ns/ssn/Deployment> a rdfs:Class ;
  rdfs:label "Deployment"@en ;
  rdfs:comment "Describes the Deployment of one or more Systems for a particular purpose. Deployment may be done on a Platform."@en .

<http://www.w3.org/ns/ssn/deployedSystem> a rdf:Property ;
  rdfs:label "deployed system"@en ;
  rdfs:comment "Relation between a Deployment and a deployed System."@en ;
  rdfs:domain <http://www.w3.org/ns/ssn/Deployment> ;
  rdfs:range <http://www.w3.org/ns/ssn/System> .

<http://www.w3.org/ns/ssn/deployedOnPlatform> a rdf:Property ;
  rdfs:label "deployed on platform"@en ;
  rdfs:comment "Relation between a Deployment and the Platform on which the Systems are deployed."@en ;
  rdfs:domain <http://www.w3.org/ns/ssn/Deployment> ;
  rdfs:range <http://www.w3.org/ns/sosa/Platform> .

<http://www.w3id.org/ecsel-dr-AT#CPF5_WorldFIP> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3id.org/ecsel-dr-PROD#Product> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PWR#Weight> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Information_Object> .

<http://www.w3id.org/ecsel-dr-AT#Z-Wave> a rdfs:Class ;
  rdfs:comment """Wireless communications protocol for home automation
– allowing for wireless control of residential appliances and other devices, such as lighting control, security systems, thermostats, windows, locks, swimming pools and garage door openers
• operates at 868.42 MHz in Europe, at 908.42 MHz in the North America
  – Depending on national regulations of countries
  – Better pervasion of walls and lower reflection than 2,4 GHz radio waves
• Reliable, low-latency transmission of small data packets at data rates up to 100kbit/s
• Realized as System-on-Chip (SoC)
• Accepted by many producers of home appliances etc.
  – Certified interoperable products: 2017: 1700, 2018: 2400
• Current owner: Silicon Labs (since April 2018)
  – Many companies involved before, origin: Zensys, Copenhagen, Danmark
• Supporting organization: Z-Wave Alliance
• Standards: Z-Wave PHY and MAC layer are one option in standard G.9959 for wireless devices under 1 GHz of International Telecommunications Union (ITU)"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_3_4_NetworkTechnology> .

<http://www.w3id.org/ecsel-dr-AT#OSI_AggregatedLayer> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-OOSMP#SensorMainApplication> a rdfs:Class ;
  rdfs:label "Sensor Main Application" ;
  rdfs:comment "An application area on medium level (corresponing to application level 2) for sensors which can have several sub application levels (sensor sub application)" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasSensorSubApplication> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#SensorMainApplication> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#SensorSubApplication> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasSubApplicationArea> .

<http://www.w3id.org/ecsel-dr-AH#AH_ServiceRegistrySystem_SysDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_system_SySDD> .

<http://www.w3id.org/ecsel-dr-SO#Delivery_Commitment> a rdfs:Class ;
  rdfs:comment "The \"Delivery Commitment\" directly corresponds to the release plans and cycle time commitments introduced in the corresponding entities."@en .

<http://www.w3id.org/ecsel-dr-SO#hasUnitsPerTimePeriod> a rdf:Property ;
  rdfs:comment "Release Plan: Quantity of release per time period (time period depends on company)"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Release_Plan> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-SO#hasDeliveryCommitmentID> a rdf:Property ;
  rdfs:comment "Delivery Commitment: FK; Name of the product level 3"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Delivery_Commitment> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasReleasePlan> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Delivery_Commitment> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Release_Plan> .

<http://www.w3id.org/ecsel-dr-SO#Demand_Snapshot> a rdfs:Class ;
  rdfs:comment "The “Demand” entity stores redundant demand at every product level. (snapshot entity)"@en .

<http://www.w3id.org/ecsel-dr-SO#hasDemandQuantity> a rdf:Property ;
  rdfs:comment "Demand: Demand amount"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Demand_Snapshot> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-SO#hasDemandDueDate> a rdf:Property ;
  rdfs:comment "Demand: PK; Due Date of the demand entry"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Demand_Snapshot> ;
  rdfs:range xsd:date .

<http://www.w3id.org/ecsel-dr-SO#hasDemandType> a rdf:Property ;
  rdfs:comment "Demand: PK; Demand forecast or real demand"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Demand_Snapshot> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasCustomerWishTime> a rdf:Property ;
  rdfs:comment "PK; customer wish time of the demand entry" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Demand_Snapshot> ;
  rdfs:range xsd:date .

<http://www.w3id.org/ecsel-dr-AT#AGV> a rdfs:Class ;
  rdfs:label "Autonomously Guided Vehicle"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ActuatorDevice> .

<http://www.w3id.org/ecsel-dr-PWR#SiC_MOSFET> a rdfs:Class ;
  rdfs:label "SiC MOSFET" ;
  rdfs:comment "Silicon Carbide Metal Oxide Semiconductor Field Effect Transistor (SiC MOSFET): It is a transistor: It is used for switching or amplifying the electronics signals or electric power." .

<http://www.w3id.org/ecsel-dr-PWR#has_an_Output_Current> a rdf:Property ;
  rdfs:label "has an Output Current" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#SiC_MOSFET> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#DrainCurrent> .

<http://www.w3id.org/ecsel-dr-PWR#is_a_Product_of> a rdf:Property ;
  rdfs:label "is a Product of" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#SiC_MOSFET> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Products> .

<http://www.w3.org/2006/time#Year> a rdfs:Class ;
  rdfs:label "Year"@en ;
  rdfs:comment "Year duration" ;
  rdfs:subClassOf <http://www.w3.org/2006/time#DurationDescription> .

<http://www.w3.org/2006/time#years> a rdf:Property ;
  rdfs:label "years duration"@en ;
  rdfs:comment "length of, or element of the length of, a temporal extent expressed in years"@en ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDurationDescription> ;
  rdfs:range xsd:decimal .

<http://www.w3.org/2006/time#weeks> a rdf:Property ;
  rdfs:label "weeks duration"@en ;
  rdfs:comment "length of, or element of the length of, a temporal extent expressed in weeks"@en ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDurationDescription> ;
  rdfs:range xsd:decimal .

<http://www.w3.org/2006/time#seconds> a rdf:Property ;
  rdfs:label "seconds duration"@en ;
  rdfs:comment "length of, or element of the length of, a temporal extent expressed in seconds"@en ;
  rdfs:seeAlso <http://www.bipm.org/en/publications/si-brochure/second.html> ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDurationDescription> ;
  rdfs:range xsd:decimal .

<http://www.w3.org/2006/time#minutes> a rdf:Property ;
  rdfs:label "minutes"@en ;
  rdfs:comment "length, or element of, a temporal extent expressed in minutes"@en ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDurationDescription> ;
  rdfs:range xsd:decimal .

<http://www.w3.org/2006/time#hours> a rdf:Property ;
  rdfs:label "hours duration"@en ;
  rdfs:comment "length of, or element of the length of, a temporal extent expressed in hours"@en ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDurationDescription> ;
  rdfs:range xsd:decimal .

<http://www.w3.org/2006/time#months> a rdf:Property ;
  rdfs:label "months duration"@en ;
  rdfs:comment "length of, or element of the length of, a temporal extent expressed in months"@en ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDurationDescription> ;
  rdfs:range xsd:decimal .

<http://www.w3.org/2006/time#days> a rdf:Property ;
  rdfs:label "days duration"@en ;
  rdfs:comment "length of, or element of the length of, a temporal extent expressed in days"@en ;
  rdfs:domain <http://www.w3.org/2006/time#GeneralDurationDescription> ;
  rdfs:range xsd:decimal .

<http://www.w3id.org/ecsel-dr-SO#Wet_Etching> a rdfs:Class ;
  rdfs:comment "Wet Etching is the process of removing material-etching, through the use of chemical activity."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Workshop> .

<http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PRIMA#Project> .

<http://www.w3id.org/ecsel-dr-PRIMA#hasResultingFactorAverage> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-PRIMA#hasImpactFactor> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-PRIMA#hasRole> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PRIMA#Role> .

<http://www.w3id.org/ecsel-dr-PRIMA#hasSubProject> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PRIMA#SubProject> .

<http://www.w3id.org/ecsel-dr-PRIMA#hasCertificationLevel> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PRIMA#Certification> .

<http://www.w3id.org/ecsel-dr-PRIMA#hasName> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PRIMA#hasInterfaceComplexityFactor> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-PRIMA#hasBudgetValue> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-PRIMA#hasBudgetFactor> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-PRIMA#hasGoal> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PRIMA#hasProjectStatus> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PRIMA#ProjectStatus> .

<http://www.w3id.org/ecsel-dr-PRIMA#hasCategoryLevel> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PRIMA#Category> .

<http://www.w3id.org/ecsel-dr-PWR#ConsumerDiscretionary> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#IndutrialSector> .

<http://www.w3id.org/ecsel-dr-SO#Chemical_Polishing> a rdfs:Class ;
  rdfs:comment "The chemical polishing process or chemical mechanical planarization (CMP) is a process whereby a chemical reaction increases the mechanical removal rate of a material. CMP is commonly used to polish off high spots on wafers or films deposited on wafers, flattening the film or wafer, referred to as planarization. The chemical reaction that increases the mechanical removal rate is commonly tailored to provide a higher removal rate of one material versus another material. The chemical action in CMP helps to achieve higher selectivity's of one material to another than a strictly mechanical process would provide."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Workshop> .

<http://www.w3.org/ns/ssn/OversamplingRate> a rdfs:Class ;
  rdfs:label "Oversampling Rate" ;
  rdfs:comment "Specifies the number of sensor measurements used internally to generate one sensor output result. (Oversampling rate = OSR)" ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/systems/SystemProperty> .

<http://www.w3id.org/ecsel-dr-AT#DeviceControlApp> a rdfs:Class ;
  rdfs:comment """A device control app is an app typically for a Smartphone (also usable on tablets, pocket PCs and other mobile devices) which offers control to a certain IoT device.
It can show and visualize the status of the device and offers control commands to the device to change it's status (e.g. switch it on or off), set new target values for measures which are influenced by the device (e.g. brightness - lamp or temperatur - heater) etc.""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-AH#AH_Historian_SysDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system_SySDD> .

<http://www.w3id.org/ecsel-dr-PMV#Model> a rdfs:Class ;
  rdfs:label "Model" ;
  rdfs:comment "To graphically depict functional and process decomposition, function objects are diagramed on models in IndustryPrint 5." .

<http://www.w3id.org/ecsel-dr-PWR#Property> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Quality> .

<http://www.w3id.org/ecsel-dr-AH#AH_TokenGenerationServcie_SD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_service_SD> .

<http://www.w3id.org/ecsel-dr-AH#AH_application_system> a rdfs:Class ;
  rdfs:label "Arrowhead Application Component"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_system> .

<http://www.w3id.org/ecsel-dr-PMV#TechnicalTermInputElement> a rdfs:Class ;
  rdfs:label "Technical Term Input Element" ;
  rdfs:comment "Denotes the input element to a function in the process flow." .

<http://www.w3id.org/ecsel-dr-PWR#Quality> a rdfs:Class ;
  rdfs:comment "Any aspect of an Entity (but not a part of it), which cannot exist without that Entity. For example, the way the surface of a specific PhysicalObject looks like is a Quality, while the encoding of that Quality into e.g. a PhysicalAttribute should be modeled as a Region. From the design viewpoint, the Quality-Region distinction is useful only when individual aspects of an Entity are considered in a domain of discourse. For example, in an automotive context, it would be irrelevant to consider the aspects of car windows for a specific car, unless the factory wants to check a specific window against design parameters (anomaly detection). On the other hand, in an antiques context, the individual aspects for a specific piece of furniture are a major focus of attention, and may constitute the actual added value, because the design parameters for old furniture are often not fixed, and may not be viewed as 'anomalies'." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Entity> .

<http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> a rdfs:Class ;
  rdfs:comment "A net access technology provides the physical link layer and the data link layer  of the OSI layer model (i.e. OSI layer 1 and 2)."@en .

<http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution_WithoutSensor> a rdfs:Class ;
  rdfs:label "Motor Control and Drive Solution Without Sensor" ;
  rdfs:comment "Motor control and drive solution without a sensor" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> .

<http://www.w3id.org/ecsel-dr-AT#EDIFACT_DELJIT> a rdfs:Class ;
  rdfs:label "Delivery Forecast for Just in Time and Just in Sequence parts"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#EDIFACT-Specification> .

<http://www.w3id.org/ecsel-dr-OM#CustomerPlant> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-SCP#MinStock> a rdfs:Class ;
  rdfs:label "MinStock"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#SSO_Stocks> .

<http://www.w3id.org/ecsel-dr-AH#AH_QoS-Manager_SySDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system_SySDD> .

<http://www.w3id.org/ecsel-dr-SCP#PrioritizedDemand> a rdfs:Class ;
  rdfs:label "PrioritizedDemand"@iri-based .

<http://www.w3id.org/ecsel-dr-SCP#matchIn> a rdf:Property ;
  rdfs:label "matchIn"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#PrioritizedDemand> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#SupplyDemandMatch> .

<http://purl.org/dc/dcmitype/Service> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#Input> , <http://www.w3id.org/ecsel-dr-PMV#Output> .

<http://www.w3id.org/ecsel-dr-AT#CPF18_SafetyNet_p> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3.org/ns/ssn/systems/MeasurementRange> a rdfs:Class ;
  rdfs:label "Measurement Range" ;
  rdfs:comment "The set of values that the Sensor can return as the Result of an Observation under the defined Conditions with the defined system properties." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/systems/SystemProperty> .

<http://www.w3id.org/ecsel-dr-AT#OPC_UA_BinaryProtocol> a rdfs:Class ;
  rdfs:label "Open Platform Communications Unified Architecture Binary Protocol"@en ;
  rdfs:comment """OPC UA supports two protocols. They can be stated in the URL:
• Binary protocol: opc.tcp://Server
• Web Service: http://Server
The binary protocol offers
• the best performance/least overhead,
• takes minimum resources (no XML Parser, SOAP and HTTP required, which is important for embedded devices),
• offers best interoperability (binary is explicitly specified and allows fewer degrees of freedom during implementation) and
• uses a single arbitrarily choosable TCP port for communication easing tunneling or easy enablement through a firewall.

The Web Service (SOAP) protocol is best supported from available tools, e.g., from Java or .NET environments, and is firewall-friendly, using standard HTTP(S) ports.
Binary is supported by all implementations, while only .NET implementation supports SOAP.

The protocol stack is: 

TCP/IP - UA-TCP - UA Secure Conversation - UA Binary Encoding. 

The standardized port for this protocol is 4840. 
That is, use of OPC-UA binary protocol requires to open only this one port at a firewall."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-PMV#Output> a rdfs:Class ;
  rdfs:label "Output" ;
  rdfs:comment "The amount of energy, work, goods, or services produced by a machine, factory, company, or an individual in a period." .

<http://www.w3id.org/ecsel-dr-AT#OSI_Layer_Model_aggregated> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#NetworkLayerModel> .

<http://www.w3id.org/ecsel-dr-AH#Communication_Profile_CP> a rdfs:Class ;
  rdfs:comment """Remark HB: the descriptions in the Arrowhead Framework Definitions V2.4 document and the Arrowhead WiKi are inconsistent!!
Description from Wiki seems to be more actual. Difference: the lower level communication technology is not included in the CP (should not be relevant for the service as with TCP/IP a unique layer above exists!), but the data format is included in the CP and not in the SP (as described by the definitions document)."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_service_documentation_document> .

<http://www.w3id.org/ecsel-dr-SO#Product_Level> a rdfs:Class ;
  rdfs:comment "In the \"product level\" entity, the aggregation of elements enables the grouping of products and defines the relationship between products and groups at different hierarchy levels. This supports planning, logistics, modeling, forecasting and reporting."@en .

<http://www.w3id.org/ecsel-dr-AT#CPF7_SwiftNet> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3id.org/ecsel-dr-PMV#EndEvent> a rdfs:Class ;
  rdfs:label "End Event" ;
  rdfs:comment "Denotes the event element that stands at the end of a branch in the process flow and thus, ends the process flow branch or the total process." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#Event> .

<http://www.w3id.org/ecsel-dr-PWR#Situation> a rdfs:Class ;
  rdfs:comment "A view, consistent with ('satisfying') a Description, on a set of entities. It can also be seen as a 'relational context' created by an observer on the basis of a 'frame' (i.e. a Description). For example, a PlanExecution is a context including some actions executed by agents according to certain parameters and expected tasks to be achieved from a Plan; a DiagnosedSituation is a context of observed entities that is interpreted on the basis of a Diagnosis, etc. Situation is also able to represent reified n-ary relations, where isSettingFor is the top-level relation for all binary projections of the n-ary relation. If used in a transformation pattern for n-ary relations, the designer should take care of creating only one subclass of Situation for each n-ary relation, otherwise the 'identification constraint' (Calvanese et al., IJCAI 2001) could be violated." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Social_Object> .

<http://www.w3id.org/ecsel-dr-SO#Timecoupling> a rdfs:Class ;
  rdfs:comment "[Priority Class] lots of this type are requested by the next machine in the production line in irregular intervals. Special chemical characteristics require the lot being further processed immediately after the furnace operation. Thus, the downstram machines keep capacity free for the resulting time slot. timecoupling can be turned on or off. if it is on all lots are processed no matter how many are waiting and if not they wait."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Priority_Classes> .

<http://www.w3id.org/ecsel-dr-SO#hasFrequency> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Timecoupling> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-SO#hasNumberOfProducts> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Timecoupling> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-AH#AH_local_cloud> a rdfs:Class ;
  rdfs:comment """Remark HB (2019-03-25): 
the relation between a local network and an AH local cloud should be discussed in more detail. 
Sample questions: 
- must all devices of an AH local cloud be part of one local network? Or can an AH local cloud be spread over different local networks? (Assumption: all devices must be part of the same local network. Justification??)
- Same question for subnets. Large automation systems are often devided into several subnets. Is it possible that an AH local cloud spreads over several subnets?
- What is the role of the domain in this context? What is the relation between domain (in sense of IP protocol) and a local network? Should the questions above better be asked for domains instead for local networks?"""@en .

<http://www.w3id.org/ecsel-dr-AH#containsDevice> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Device> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#hasArchitecturalPart> .

<http://www.w3id.org/ecsel-dr-SO#Operation> a rdfs:Class ;
  rdfs:comment "The master entity “Operation” depicts the generic behavior of a single process step. Each operation has a foreign key relation to equipment and to route which means that the operation is required by the specific routes and requires a specific equipment. (workflow descriptive master entity)"@en .

<http://www.w3id.org/ecsel-dr-SO#hasSplitLotChips> a rdf:Property ;
  rdfs:comment "split into lots with # chips, added due to data import" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-SO#hasReworkTest> a rdf:Property ;
  rdfs:comment "Operation: Are the processed lots tested for rework?"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range xsd:boolean .

<http://www.w3id.org/ecsel-dr-SO#hasTimeConstraints> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Time_Constraints> .

<http://www.w3id.org/ecsel-dr-SO#hasVariancePTime> a rdf:Property ;
  rdfs:comment "length of, or element of the length of, a temporal extent expressed in seconds"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range xsd:decimal .

<http://www.w3id.org/ecsel-dr-SO#hasReworkOperation> a rdf:Property ;
  rdfs:comment "Operation: [FK] Rework Operation, if needed"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasUnit> a rdf:Property ;
  rdfs:comment "unit, added due to data import" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasPTimePerUnit> a rdf:Property ;
  rdfs:comment "Operation: Capacity consuming / relevant equipment processing time"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range xsd:decimal .

<http://www.w3id.org/ecsel-dr-SO#hasOperationCritical> a rdf:Property ;
  rdfs:comment "Operation: Is the Operation critical in terms of SC planning (a Bottleneck) or not?"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range xsd:boolean .

<http://www.w3id.org/ecsel-dr-SO#hasReworkProbabilityWafers> a rdf:Property ;
  rdfs:comment "Operation: Probability of rework-tested wafers to be reworked"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range xsd:double .

<http://www.w3id.org/ecsel-dr-SO#hasScrappingProbabilityWafers> a rdf:Property ;
  rdfs:comment "Operation: Probability of scrapping-tested wafers to be scrapped"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range xsd:double .

<http://www.w3id.org/ecsel-dr-SO#hasScrappingProbabilityLots> a rdf:Property ;
  rdfs:comment "Operation: Probability of scrapping-tested full lots to be scrapped"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range xsd:double .

<http://www.w3id.org/ecsel-dr-SO#hasSamplingRate> a rdf:Property ;
  rdfs:comment "Sampling Rate: Execution rate of operation If operation is mandatory sampling rate is 1 (1- sampling rate = skipping rate of optional operation)"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range xsd:double .

<http://www.w3id.org/ecsel-dr-SO#hasReworkProbabilityLots> a rdf:Property ;
  rdfs:comment "Operation: Probability of rework-tested full lots to be reworked"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range xsd:double .

<http://www.w3id.org/ecsel-dr-SO#hasScrappingTest> a rdf:Property ;
  rdfs:comment "Operation: Are the processed lots tested for scrapping?"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range xsd:boolean .

<http://www.w3id.org/ecsel-dr-SO#hasProcessingTimeDistribution> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasOperationName> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasSplitLots> a rdf:Property ;
  rdfs:comment "Split into # lots, added due to data import" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Operation> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-OOSMP#MainApplication> a rdfs:Class ;
  rdfs:label "Main Application" ;
  rdfs:comment "An application area on medium level (corresponing to application level 2) which can have several sub application levels (sub application) and can be assigned to super application levels (industry)" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> .

<http://www.w3id.org/ecsel-dr-OOSMP#subApplicationAreaOfIndustry> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MainApplication> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#Industry> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#subApplicationAreaOf> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasSubApplication> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#MainApplication> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#SubApplication> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasSubApplicationArea> .

<http://www.w3id.org/ecsel-dr-OOSMP#DiscretePowerStage> a rdfs:Class ;
  rdfs:label "Discrete Power Stage" ;
  rdfs:comment "A semiconductor product which is used within a discrete power stage" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> .

<http://www.w3id.org/ecsel-dr-OOSMP#partOfAsDiscretePowerStage> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#DiscretePowerStage> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#partOf> .

<http://www.w3id.org/ecsel-dr-PMV#JoinRule> a rdfs:Class ;
  rdfs:label "Join Rule" ;
  rdfs:comment "Rule element that unites the control flow after being split into several branches. Has several incoming paths (at least two) and one outgoing." .

<http://www.w3id.org/ecsel-dr-PMV#evaluates> a rdf:Property ;
  rdfs:label "evaluates" ;
  rdfs:comment "A rule evaluates an event. The connector is used to represent the chronological order in an EPC." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#JoinRule> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Event> .

<http://www.w3id.org/ecsel-dr-AT#B2MML-based-Service> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitecture> .

<http://www.w3id.org/ecsel-dr-SCP#MaxStock> a rdfs:Class ;
  rdfs:label "MaxStock"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#SSO_Stocks> .

<http://www.w3id.org/ecsel-dr-PWR#On-State_Power_loss> a rdfs:Class ;
  rdfs:label "On-State Power Loss" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Property> .

<http://www.w3id.org/ecsel-dr-PWR#Power_loss_Calculated_by> a rdf:Property ;
  rdfs:label "has a Power Loss Calculated by Multiplicatoin of" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#On-State_Power_loss> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#DrainCurrent> .

<http://www.w3.org/ns/sosa/Sample> a rdfs:Class ;
  rdfs:label "Sample"@en ;
  rdfs:comment "Feature which is intended to be representative of a FeatureOfInterest on which Observations may be made."@en ;
  rdfs:subClassOf <http://www.w3.org/ns/sosa/FeatureOfInterest> , <http://www.w3.org/ns/sosa/Result> .

<http://www.w3.org/ns/sosa/isFeatureOfInterestOf> a rdf:Property ;
  rdfs:label "is feature of interest of"@en ;
  rdfs:comment "A relation between a FeatureOfInterest and an Observation about it, an Actuation acting on it, or an act of Sampling that sampled it."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/FeatureOfInterest> ;
  rdfs:range <http://www.w3.org/ns/sosa/Observation> .

<http://www.w3.org/ns/sosa/isSampleOf> a rdf:Property ;
  rdfs:label "is sample of"@en ;
  rdfs:comment "Relation from a Sample to the FeatureOfInterest that it is intended to be representative of."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Sample> ;
  rdfs:range <http://www.w3.org/ns/sosa/FeatureOfInterest> .

<http://www.w3.org/ns/sosa/hasSample> a rdf:Property ;
  rdfs:label "has sample"@en ;
  rdfs:comment "Relation between a FeatureOfInterest and the Sample used to represent it."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/FeatureOfInterest> ;
  rdfs:range <http://www.w3.org/ns/sosa/Sample> .

<http://www.w3.org/ns/sosa/sampling/hasSampleRelationship> a rdf:Property ;
  rdfs:label "has sample relationship" ;
  rdfs:comment "Links a sample to a Sample Relationship (which links to a related Sample)." ;
  rdfs:domain <http://www.w3.org/ns/sosa/Sample> ;
  rdfs:range <http://www.w3.org/ns/sosa/sampling/SampleRelationship> .

<http://www.w3.org/ns/ssn/hasProperty> a rdf:Property ;
  rdfs:label "has property"@en ;
  rdfs:comment "Relation between an entity and a Property of that entity."@en ;
  rdfs:range <http://www.w3.org/ns/ssn/Property> .

<http://www.w3.org/ns/sosa/isResultOf> a rdf:Property ;
  rdfs:label "is result of"@en ;
  rdfs:comment "Relation linking a Result to the Observation or Actuation or act of Sampling that created or caused it."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Result> ;
  rdfs:range <http://www.w3.org/ns/sosa/Sampling> , <http://www.w3.org/ns/sosa/Observation> .

<http://www.w3id.org/ecsel-dr-AT#DigitalFactoryTwin> a rdfs:Class ;
  rdfs:comment """Digital Twin of a Factory or a Manufacturing System. 
Most complex kind of Digital Twin: comprises complete manufacturing systems, like assembly lines, transfer lines, flexible manufacturing systems etc. 
(other types of digital twins are digital twins of single devices, ranging from sensors to tooling machines, household appliances, automated doors, controlled heaters, lights etc.,  i.e. devices which are sensors or actors which can be controlled; and primitive, passive things which could be tracked and traced).

A Digital Factory Twin should be aligned with the real system according to all of it's components which are involved in the physical process (ISA-95 level 0), sensing and acting on them (ISA-95 level 1) and basically control them (level 2) in real time and according to physical properties, location, conditions, states and software. 
To achieve this real-time alignment, the Digital Factory Twin should be connected via ISA-cross level communication with the real level 1 and 2 elements. 
A Digital Factory Twin can be the basis for simulations of the system, for that the twin data could be transferred to an simulation system e.g. for what-if analysis or simulation-based manufacturing control and optimization. 
Nevertheless, the simulated systems should be only \"clones\" of the digital factory twin as they change the system differently to the real system. 
(H. Baumgaertel, 2018-04-18)."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#PLM2_Module> .

<http://www.w3id.org/ecsel-dr-AT#ProductLifecyclePhase> a rdfs:Class ;
  rdfs:comment """Product Lifecycle Phases according to IEC 62890, which is used in RAMI 4.0 as product lifecycle dimension.

The phase model is a very general model and should be interpreted carefully. The \"phases\" occur in practise not sequentially, but overlap (except phase 1)."""@en .

<http://www.w3id.org/ecsel-dr-PWR#RealEstate> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#IndutrialSector> .

<http://www.w3.org/ns/sosa/Sampler> a rdfs:Class ;
  rdfs:label "Sampler"@en ;
  rdfs:comment "A device that is used by, or implements, a Sampling Procedure to create or transform one or more samples."@en ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/System> .

<http://www.w3.org/ns/sosa/madeSampling> a rdf:Property ;
  rdfs:label "made sampling"@en ;
  rdfs:comment "Relation between a Sampler (sampling device or entity) and the Sampling act it performed."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Sampler> ;
  rdfs:range <http://www.w3.org/ns/sosa/Sampling> .

<http://www.w3id.org/ecsel-dr-AT#CPF14_EPA> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3id.org/ecsel-dr-AH#AH_GlobalServiceDiscoveryService_IDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service_IDD> .

<http://www.w3id.org/ecsel-dr-AT#CPF3_1_Profibus_DP> a rdfs:Class ;
  rdfs:comment """PROFIBUS (Process Field Bus) ist ein Standard für die Feldbus-Kommunikation in der Automatisierungstechnik und wurde anfangs (1989) vom BMBF gefördert. Er ist nicht zu verwechseln mit dem Profinet-Standard für Industrial Ethernet.
PROFIBUS existiert in drei Varianten, wobei DP die meistgenutzte ist:

1. PROFIBUS DP (Dezentrale Peripherie) zur Ansteuerung von Sensoren und Aktoren durch eine zentrale Steuerung in der Fertigungstechnik. Hier stehen insbesondere auch die vielen Standarddiagnosemöglichkeiten im Vordergrund. Weitere Einsatzgebiete sind die Verbindung von „verteilter Intelligenz“, also die Vernetzung von mehreren Steuerungen untereinander (ähnlich PROFIBUS FMS). Es sind Datenraten bis zu 12 Mbit/s auf verdrillten Zweidrahtleitungen oder Lichtwellenleiter möglich. Der Einsatz mit Antriebsgeräten ist im Profil PROFIdrive festgelegt.
2. PROFIBUS PA (Prozess-Automation)  
3. PROFIBUS FMS (Fieldbus Message Specification) war vor allem für den Einsatz in komplexen Maschinen und Anlagen gedacht. Diese Protokollvariante wurde von DP abgelöst und ist heute nicht mehr Bestandteil der Internationalen Feldbusnorm.""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#CPF3_Profibus_ProfiNet> .

<http://www.w3id.org/ecsel-dr-SCP#OrderLineItem> a rdfs:Class ;
  rdfs:label "OrderLineItem"@iri-based .

<http://www.w3id.org/ecsel-dr-SCP#isTransferTo> a rdf:Property ;
  rdfs:label "isTransferTo"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#OrderLineItem> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#ordersScheduleLine> .

<http://www.w3id.org/ecsel-dr-SCP#consistOf> a rdf:Property ;
  rdfs:label "consistOf"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#OrderLineItem> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#OpenOrderBook> .

<http://www.w3id.org/ecsel-dr-SCP#useUp> a rdf:Property ;
  rdfs:label "useUp"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#OrderLineItem> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#AATP> .

<http://www.w3id.org/ecsel-dr-SCP#consume> a rdf:Property ;
  rdfs:label "consume"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#OrderLineItem> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#ATP> .

<http://www.w3id.org/ecsel-dr-SCP#goesTo> a rdf:Property ;
  rdfs:label "goesTo"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#OrderLineItem> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#ordersScheduleLine> .

<http://www.w3id.org/ecsel-dr-SCP#generate> a rdf:Property ;
  rdfs:label "generate"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#OrderLineItem> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#OpenOrderBook> .

<http://www.w3id.org/ecsel-dr-PROD#NonShippableProduct> a rdfs:Class ;
  rdfs:comment "NonShippableProduct are those finishedProductNumbers that are not allowed to be shipped to a given customer" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PROD#Product> .

<http://www.w3id.org/ecsel-dr-PWR#Maximum_Junction_Temperature> a rdfs:Class ;
  rdfs:label "Maximum Junction Temperature" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Junction_Temperature> .

<http://www.w3.org/ns/ssn/systems/BatteryLifetime> a rdfs:Class ;
  rdfs:label "Battery Lifetime" ;
  rdfs:comment "Total useful life of a System's battery in the specified Conditions." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/systems/SurvivalProperty> .

<http://www.w3id.org/ecsel-dr-SO#Purge> a rdfs:Class ;
  rdfs:comment "purge' is the application of an intert gas, or gas mixture, to the OD or ID surface of the weld joint to displace non-inert atmospheric gases. A block purge is a non-flowing purge with positive pressure."@en .

<http://www.w3id.org/ecsel-dr-SO#hasPurgeDuration> a rdf:Property ;
  rdfs:comment "length of, or element of the length of, a temporal extent expressed in hours"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Purge> ;
  rdfs:range xsd:decimal .

<http://www.w3id.org/ecsel-dr-AH#AH_core_service> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_service> .

<http://www.w3id.org/ecsel-dr-SO#Target_Costs> a rdfs:Class ;
  rdfs:comment "The \"target costs\" entity is the final cost of a product or service that must be achieved in order to generate the desired level of sales revenue and income or due to contractual agreements."@en .

<http://www.w3id.org/ecsel-dr-SO#hasFinishedProductCosts> a rdf:Property ;
  rdfs:comment "Target Costs: Costs of a finished unit of a certain technology"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Target_Costs> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-SO#hasTargetRevenue> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Target_Revenue> .

<http://www.w3id.org/ecsel-dr-SO#hasWIPCostsPerUnitAndTimeUnit> a rdf:Property ;
  rdfs:comment "Target Costs: Capital bounding costs + Storage costs + Mean production costs of a unit of a certain technology and time unit"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Target_Costs> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-SO#Rocket> a rdfs:Class ;
  rdfs:comment "[Priority Class] rocket lots are processed immediately if a machine has free capacity. The remaining furnace space is then filled up with lots of the same product."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Priority_Classes> .

<http://www.w3id.org/ecsel-dr-RAMI40#Admin_Shell> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-RAMI40#isDescribedWith> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#Admin_Shell> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-RAMI40#Standard> .

<http://www.w3id.org/ecsel-dr-RAMI40#hasSubmodel> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#Admin_Shell> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-RAMI40#Submodel> .

<http://www.w3id.org/ecsel-dr-RAMI40#hasData> a rdf:Property ;
  rdfs:comment "Connects the AdminShell with the different types of Data for the Object/Entity" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#Admin_Shell> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-RAMI40#Submodel> .

<http://www.w3id.org/ecsel-dr-RAMI40#isConnectedTo> a rdf:Property ;
  rdfs:comment "Connects the Admin Shell with the different RAMI4.0 Dimensions" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#Admin_Shell> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-RAMI40#Dimension> .

<http://www.w3id.org/ecsel-dr-RAMI40#describes> a rdf:Property ;
  rdfs:comment "Connect the Asset with the Administration Shell" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#Admin_Shell> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-RAMI40#Asset> .

<http://www.w3id.org/ecsel-dr-AT#LoRaWAN> a rdfs:Class ;
  rdfs:comment """Verfügbare LoRaWAN - Netze

In der Schweiz hat die Swisscom ein nahezu landesweit erreichbares Funknetz auf LoRa-Basis erfolgreich produktiv gesetzt.

Dem größten südkoreanischen Telekommunikationsunternehmen SK Telecom gelang Anfang Juli 2016 die landesweite Einführung von Low-Power Wide-Area Network (LPWAN) basierend auf der LoRa-Technologie für die IoT-Infrastruktur.[1] Die niederländische KPN meldete die landesweite Bereitstellung eines IoT-Netzwerkes mit LoRa-Technik. Damit gehören die Niederlande, die Schweiz und Südkorea zu den ersten Ländern mit flächendeckender LoRaWAN-Versorgung.[2]

Einen internationalen, community basierten, Ansatz verfolgt die niederländische Initiative The Things Network (TTN), welche seit 2015 am Markt aktiv ist. Bisher erfolgte die Etablierung in über 90 Ländern und in über 500 communities. Dort sind bereits knapp 3.000 LoRaWAN Gateways aktiv. Die führenden Standorte sind dabei Zürich, Bern, Amsterdam und Berlin. In Deutschland sind mehr als 300 gateways in über 40 Städten und Orten installiert. Führende Stadt in Deutschland mit den meisten Installationen ist Berlin[3]. Dort wurden in 9 Monaten bereits 50 IoT-Gateways installiert und zu einem, bereits jetzt voll nutzbaren, stadtweiten Netz verbunden. Dessen Nutzung ist kostenfrei und bedarf keiner vorherigen Erlaubnis.""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> .

<http://www.w3id.org/ecsel-dr-OOSMP#ApplicationLevel3> a rdfs:Class ;
  rdfs:label "Application Level 3" ;
  rdfs:comment "The lowest application level which can be assigned to super application levels (application level 2)" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> .

<http://www.w3id.org/ecsel-dr-OOSMP#belongsToDivision> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationLevel3> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#Division> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#belongsToOrganizationalUnit> .

<http://www.w3id.org/ecsel-dr-OOSMP#subApplicationAreaOfApplicationLevel2> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationLevel3> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationLevel2> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#subApplicationAreaOf> .

<http://www.w3.org/2006/time#TemporalPosition> a rdfs:Class ;
  rdfs:label "Temporal position"@en ;
  rdfs:comment "A position on a time-line"@en .

<http://www.w3id.org/ecsel-dr-AT#OWL> a rdfs:Class ;
  rdfs:label "Web Ontology Language"@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L4_SemanticsRepresentation> .

<http://www.w3id.org/ecsel-dr-AT#WebApplicationProtocol> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L1_WebPlatform> .

<http://www.w3id.org/ecsel-dr-AH#AH_AuthorizationSystem_SySD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_system_SySD> .

<http://www.w3id.org/ecsel-dr-SCP#HP_Forecast> a rdfs:Class ;
  rdfs:label "HP_Forecast"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#Forecast> .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_1_3> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ISA-95_CrossLayerCommunication> .

<http://www.w3id.org/ecsel-dr-PWR#The_method_of_the_device_function> a rdfs:Class ;
  rdfs:label "Switching" ;
  rdfs:comment """The function of the devices has a method ( Procedure to estimate or calculate a value), for example:
The Senor its function is the sensing, the sensing method is the observation
The Boost converter ( a type of the power converter) its function is boosting, the boosting method is the amplification.  

Act of carrying out an (the method) Procedure to estimate or calculate a value of a property of a FeatureOfInterest. Links to an the methodProperty to describe what the result is an estimate of, and to a FeatureOfInterest to detail what that proeprty was associated with.

Example: The activity of estimating the intensity of an earthquake using the Mercalli intensity scale is an Observation as is measuring the moment magnitude, i.e., the energy released by said earthquake.\"""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Situation> .

<http://www.w3id.org/ecsel-dr-PWR#amplified_by> a rdf:Property ;
  rdfs:label "The Act of The Switching" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#The_method_of_the_device_function> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Infineon_Device> .

<http://www.w3id.org/ecsel-dr-AT#OSI_L7_ApplicationLayer> a rdfs:Class ;
  rdfs:label "Application layer"@en , "Anwendungsschicht"@de ;
  rdfs:comment """Serves as the window for users and application processes to access the network services. 
End User Layer. Application system / process: program that opens what was sent or creates what is to be sent. 
Topics: resource sharing, remote file access, remote printer access, directory services, network management
Example protocols: HTTP, HTTPS, SMTP, FTP, CoAP, MQTT,"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_DetailedLayer> .

<http://www.w3id.org/ecsel-dr-AH#AH_system_documentation_document> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Documentation_document> .

<http://www.w3id.org/ecsel-dr-AT#IEEE-Standard> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Standard> .

<http://www.w3id.org/ecsel-dr-AT#IEC-Standard> a rdfs:Class ;
  rdfs:label "IEC standard"@en ;
  rdfs:comment "standard maintained and published by IEC."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Standard> .

<http://www.w3id.org/ecsel-dr-SCP#RampUpStock> a rdfs:Class ;
  rdfs:label "RampUpStock"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#SSO_Stocks> .

<http://www.w3id.org/ecsel-dr-AH#AH_Orchestrator_WADL> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#System_WebApplicationDescription_WADL> .

<http://www.w3id.org/ecsel-dr-AT#ProductDataManagement-Module> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#PLM1_Module> .

<http://www.w3id.org/ecsel-dr-SO#Target_Service_Level> a rdfs:Class ;
  rdfs:comment "The target service level is a performance indicator expressing the percentage of orders satisfied"@en .

<http://www.w3id.org/ecsel-dr-SO#hasStockOutProbability> a rdf:Property ;
  rdfs:comment "Target service level: Probability that customer demand cannot be fulfilled"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Target_Service_Level> ;
  rdfs:range xsd:double .

<http://www.w3id.org/ecsel-dr-SO#hasFillRate> a rdf:Property ;
  rdfs:comment "Target Service Level: Rate of demand that can be fulfilled"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Target_Service_Level> ;
  rdfs:range xsd:double .

<http://www.w3id.org/ecsel-dr-SO#hasTargetServiceLevelBeta> a rdf:Property ;
  rdfs:comment "Target Service Level: Target beta service level (Rate of demand to be fulfilled without delay)"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Target_Service_Level> ;
  rdfs:range xsd:double .

<http://www.w3id.org/ecsel-dr-AT#IndustrialEthernet> a rdfs:Class ;
  rdfs:comment """Im Rahmen von Industrial Ethernet werden Switches, Hubs und Medienkonverter geschaffen, die an industrielle Umgebungsbedingungen angepasst sind. Dazu gehören insbesondere die Befestigung auf einer 35-mm-DIN-Hutschiene (Tragschiene), Gleichspannungsversorgung (in der Regel 24 V DC), eine erhöhte EMV-Störsicherheit, ein erweiterter Betriebstemperaturbereich, eine erhöhte Schutzart (Schutz gegen Staub, Spritzwasser usw.), Beständigkeit gegen diverse Medien wie Öle, Schmierstoffe und Säuren, Rüttelfestigkeit und vielfach auch besondere Vorkehrungen zur Ausfallsicherheit.
Für die hohen Echtzeitanforderungen mit isochronen Zykluszeiten von weniger als 1 ms (z. B. für Motion-Control-Anwendungen) werden spezielle Protokolle definiert, die durch Hardware und spezielle Topologien unterstützt werden. Systeme wie SERCOS III, SafetyNET p, VARAN, Profinet, EtherNet/IP, Ethernet Powerlink oder EtherCAT erreichen bereits Buszyklen von rund 100 µs.
Da die Netzwerkverbindung im industriellen Umfeld häufig von Maschine zu Maschine in Reihe erfolgt, werden Industrial Ethernet Netze oftmals in einem Ring realisiert. Dadurch kann ein Störfall auf maximal einen Switch beschränkt werden. Fällt eine Leitung aus, kann das Netzwerk vollständig weiterarbeiten. Die Netzwerktrennung im Ring erfolgt entweder durch Rapid Spanning Tree oder durch ein nicht standardisiertes Protokoll, das eine schnellere Reaktionszeit ermöglicht.
Potentialfreie Meldekontakte ermöglichen eine schnelle Fehlererkennung. Über die Verwaltung kann ebenfalls das Netzwerk überwacht werden und ggf. eine Benachrichtigung des Operators erfolgen.
Trotz vieler Bemühungen hat man es nicht geschafft, einen einheitlichen Standard zu definieren, der es ermöglicht, Geräte verschiedener Systeme gemeinsam zu betreiben. Durch die höheren Datenraten werden Feldbussysteme nach EIA-485 trotz wesentlich höherer Kosten in einzelnen Anwendungen durch Industrial Ethernet ersetzt.

Besonderheiten bei der Infrastruktur
War das Ethernet als Standard für Datenverkabelungen früher nur in Büroumgebungen üblich, wird es heute vermehrt auch für industrielle Anwendungen genutzt. Hier trifft das Netzwerk aber auf Störfaktoren, die erheblichen Einfluss auf die Übertragungsqualität haben können. Vor allem an den Anschlusspunkten ist das Risiko von Störungen durch Vibrationen, Schmutz, Feuchtigkeit oder schädliche Substanzen hoch. Je nach Anforderung unterscheidet man zwischen verschiedenen Schutzarten. Anbieter von Steckverbindern haben daher spezielle Anschlusstechniken für Industrial Ethernet entwickelt. Sie sind den teils widrigen Bedingungen in der Leicht- und Schwerindustrie, in Eisenbahntunneln, auf Schiffen (Kreuzfahrtschiffen) oder auch anderen Umgebungen wie hoch hygienischen OP-Räumen gewachsen."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> .

<http://www.w3id.org/ecsel-dr-RAMI40#Asset> a rdfs:Class ;
  rdfs:comment "Clearly identifiable asset for the Administration Shell" .

<http://www.w3id.org/ecsel-dr-RAMI40#hasDescription> a rdf:Property ;
  rdfs:comment "Description of the Object/Entity" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#Asset> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-RAMI40#isPartOf> a rdf:Property ;
  rdfs:comment "A relation between any entities, in this case, the Asset can be part of other Asset(s)." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#Asset> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-RAMI40#Asset> .

<http://www.w3id.org/ecsel-dr-AT#CPF15_ModBus> a rdfs:Class ;
  rdfs:comment "Das Modbus-Protokoll ist ein Kommunikationsprotokoll, das auf einer Master/Slave- bzw. Client/Server-Architektur basiert. Es wurde 1979 von Gould-Modicon für die Kommunikation mit seinen speicherprogrammierbaren Steuerungen ins Leben gerufen. In der Industrie hat sich der Modbus zu einem De-facto-Standard entwickelt, da es sich um ein offenes Protokoll handelt. Seit 2007 ist die Version Modbus TCP Teil der Norm IEC 61158."@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3id.org/ecsel-dr-AT#SPARQL_protocol> a rdfs:Class ;
  rdfs:comment "Protocol for the transmission of SPARQL queries and SPARQL updates between a client and a RDF graph store on a server."@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitecture> .

<http://www.w3id.org/ecsel-dr-PWR#Social_Object> a rdfs:Class ;
  rdfs:label "Social Object" ;
  rdfs:comment """Act of carrying out an (Observation) Procedure to estimate or calculate a value of a property of a FeatureOfInterest. Links to an ObservableProperty to describe what the result is an estimate of, and to a FeatureOfInterest to detail what that proeprty was associated with.

Example: The activity of estimating the intensity of an earthquake using the Mercalli intensity scale is an Observation as is measuring the moment magnitude, i.e., the energy released by said earthquake.""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Object> .

<http://www.w3id.org/ecsel-dr-PMV#XOR> a rdfs:Class ;
  rdfs:label "XOR" ;
  rdfs:comment """One and only one of the incoming pathways is required to proceed along the flow
One and only one of the outgoing pathways can be taken
Divide should be made with yes/no question and lines labelled only with �yes� or �no�
Gateway must therefore be named with this Yes/No question""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#Connector> .

<http://www.w3.org/ns/ssn/systems/Precision> a rdfs:Class ;
  rdfs:label "Precision" ;
  rdfs:comment "As a sensor capability: The closeness of agreement between replicate Observations on an unchanged or similar quality value: i.e., a measure of a Sensor's ability to consistently reproduce an Observation, under the defined Conditions." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/systems/SystemProperty> .

<http://www.w3id.org/ecsel-dr-PMV#BPActivity> a rdfs:Class ;
  rdfs:label "Business Process Activity" ;
  rdfs:comment "A Business Process Activity is a part of a Business Process containing one or more sub Business Processes or a Process Flow." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#Function> .

<http://www.w3id.org/ecsel-dr-PMV#represents> a rdf:Property ;
  rdfs:label "represents" ;
  rdfs:comment "A aris:BPActivity is the graphical representation of a aris:VACD or aris:BPFlow in a aris:VACD." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Screen> ;
  rdfs:range xsd:string .

<http://purl.org/vocommons/voaf#Vocabulary> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#OCF-Standard> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Standard> .

<http://www.w3id.org/ecsel-dr-SCP#BufferStockOrders> a rdfs:Class ;
  rdfs:label "BufferStockOrders"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#Orders> .

<http://www.w3id.org/ecsel-dr-AH#AH_application_system_SySDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#System_Design_Description_SySDD> .

<http://www.w3id.org/ecsel-dr-AT#uPnP> a rdfs:Class ;
  rdfs:comment "UPnP (Universal Plug and Play) - Now managed by the Open Connectivity Foundation is a set of networking protocols that permits networked devices to seamlessly discover each other's presence on the network and establish functional network services for data sharing, communications, and entertainment."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-AT#EDIFACT-Specification> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#EDI_Specification> .

<http://www.w3id.org/ecsel-dr-RAMI40#Standard> a rdfs:Class ;
  rdfs:comment "Standards that are used to describe the actual I4.0 Asset. Defined in the STO ontology" .

<http://www.w3id.org/ecsel-dr-RAMI40#hasVersion> a rdf:Property ;
  rdfs:comment "The current version of Standard." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#Standard> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-RAMI40#StandardVersion> .

<http://www.w3id.org/ecsel-dr-RAMI40#IsUsedBy> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#Standard> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-RAMI40#Standard_Organisation> .

<http://www.w3id.org/ecsel-dr-RAMI40#hasUsedDate> a rdf:Property ;
  rdfs:comment "The date that standard has been used" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#Standard> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-RAMI40#UsedDate> .

<http://www.w3id.org/ecsel-dr-OOSMP#PhysicalProduct> a rdfs:Class ;
  rdfs:label "Physical Product" ;
  rdfs:comment "A physical product is something that is produced with effort (e.g. by mechanical or industrial processes) and sold to a customer. A physical product is tangible." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#Product> .

<http://www.w3id.org/ecsel-dr-PWR#The_process_name_of_the_device_function> a rdfs:Class ;
  rdfs:label "The Process used in the Device Function" ;
  rdfs:comment """It is a process that results in the estimation, or calculation, of the value of a device output. 
Usually it derived from the name of the device for example:
Sensor process: sensing: Sensing is a process that results in the estimation, or calculation, of the value of a phenomenon.

Boost Converter process: boosting: is a process that results in the estimation, or calculation, of the value of a amplified voltage.""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Process> .

<http://www.w3id.org/ecsel-dr-PROD#PPOS> a rdfs:Class ;
  rdfs:comment """Plan Position: capacity and demand planning element
""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PROD#PlanningElement> .

<http://www.w3id.org/ecsel-dr-PROD#hasRfP> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#PPOS> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PROD#RfP> .

<http://www.w3id.org/ecsel-dr-PROD#hasFPOS> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#PPOS> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PROD#FPOS> .

<http://www.w3.org/2006/time#DurationDescription> a rdfs:Class ;
  rdfs:label "Duration description"@en ;
  rdfs:comment "Description of temporal extent structured with separate values for the various elements of a calendar-clock system. The temporal reference system is fixed to Gregorian Calendar, and the range of each of the numeric properties is restricted to xsd:decimal"@en ;
  rdfs:subClassOf <http://www.w3.org/2006/time#GeneralDurationDescription> .

<http://www.w3id.org/ecsel-dr-PWR#Saturation_Region> a rdfs:Class ;
  rdfs:label "Saturation Region" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#On-State_Region> .

<http://www.w3id.org/ecsel-dr-PRIMA#Division> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_4_4> a rdfs:Class ;
  rdfs:comment "Communication between devices on ISA-95 level 4 (intra-level 4-communication)"@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ISA-95_Communication> .

<http://www.w3.org/2006/time#ProperInterval> a rdfs:Class ;
  rdfs:label "Proper interval"@en ;
  rdfs:comment "A temporal entity with non-zero extent or duration, i.e. for which the value of the beginning and end are different"@en ;
  rdfs:subClassOf <http://www.w3.org/2006/time#Interval> .

<http://www.w3.org/2006/time#intervalStartedBy> a rdf:Property ;
  rdfs:label "interval started by"@en ;
  rdfs:comment "If a proper interval T1 is intervalStarted another proper interval T2, then the beginning of T1 is coincident with the beginning of T2, and the end of T1 is after the end of T2."@en ;
  rdfs:domain <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:range <http://www.w3.org/2006/time#ProperInterval> .

<http://www.w3.org/2006/time#intervalFinishedBy> a rdf:Property ;
  rdfs:label "interval finished by"@en ;
  rdfs:comment "If a proper interval T1 is intervalFinishedBy another proper interval T2, then the beginning of T1 is before the beginning of T2, and the end of T1 is coincident with the end of T2."@en ;
  rdfs:domain <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:range <http://www.w3.org/2006/time#ProperInterval> .

<http://www.w3.org/2006/time#intervalBefore> a rdf:Property ;
  rdfs:label "interval before"@en ;
  rdfs:comment "If a proper interval T1 is intervalBefore another proper interval T2, then the end of T1 is before the beginning of T2."@en ;
  rdfs:domain <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:range <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:subPropertyOf <http://www.w3.org/2006/time#intervalDisjoint> , <http://www.w3.org/2006/time#before> .

<http://www.w3.org/2006/time#intervalEquals> a rdf:Property ;
  rdfs:label "interval equals"@en ;
  rdfs:comment "If a proper interval T1 is intervalEquals another proper interval T2, then the beginning of T1 is coincident with the beginning of T2, and the end of T1 is coincident with the end of T2."@en ;
  rdfs:domain <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:range <http://www.w3.org/2006/time#ProperInterval> .

<http://www.w3.org/2006/time#intervalIn> a rdf:Property ;
  rdfs:label "interval in"@en ;
  rdfs:comment "If a proper interval T1 is intervalIn another proper interval T2, then the beginning of T1 is after the beginning of T2 or is coincident with the beginning of T2, and the end of T1 is before the end of T2, or is coincident with the end of T2, except that end of T1 may not be coincident with the end of T2 if the beginning of T1 is coincident with the beginning of T2."@en ;
  rdfs:domain <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:range <http://www.w3.org/2006/time#ProperInterval> .

<http://www.w3.org/2006/time#intervalAfter> a rdf:Property ;
  rdfs:label "interval after"@en ;
  rdfs:comment "If a proper interval T1 is intervalAfter another proper interval T2, then the beginning of T1 is after the end of T2."@en ;
  rdfs:domain <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:range <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:subPropertyOf <http://www.w3.org/2006/time#intervalDisjoint> , <http://www.w3.org/2006/time#after> .

<http://www.w3.org/2006/time#intervalMetBy> a rdf:Property ;
  rdfs:label "interval met by"@en ;
  rdfs:comment "If a proper interval T1 is intervalMetBy another proper interval T2, then the beginning of T1 is coincident with the end of T2."@en ;
  rdfs:domain <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:range <http://www.w3.org/2006/time#ProperInterval> .

<http://www.w3.org/2006/time#intervalDisjoint> a rdf:Property ;
  rdfs:label "interval disjoint"@en ;
  rdfs:comment "If a proper interval T1 is intervalDisjoint another proper interval T2, then the beginning of T1 is after the end of T2, or the end of T1 is before the beginning of T2, i.e. the intervals do not overlap in any way, but their ordering relationship is not known."@en ;
  rdfs:domain <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:range <http://www.w3.org/2006/time#ProperInterval> .

<http://www.w3.org/2006/time#intervalContains> a rdf:Property ;
  rdfs:label "interval contains"@en ;
  rdfs:comment "If a proper interval T1 is intervalContains another proper interval T2, then the beginning of T1 is before the beginning of T2, and the end of T1 is after the end of T2."@en ;
  rdfs:domain <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:range <http://www.w3.org/2006/time#ProperInterval> .

<http://www.w3.org/2006/time#intervalStarts> a rdf:Property ;
  rdfs:label "interval starts"@en ;
  rdfs:comment "If a proper interval T1 is intervalStarts another proper interval T2, then the beginning of T1 is coincident with the beginning of T2, and the end of T1 is before the end of T2."@en ;
  rdfs:domain <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:range <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:subPropertyOf <http://www.w3.org/2006/time#intervalIn> .

<http://www.w3.org/2006/time#intervalOverlappedBy> a rdf:Property ;
  rdfs:label "interval overlapped by"@en ;
  rdfs:comment "If a proper interval T1 is intervalOverlappedBy another proper interval T2, then the beginning of T1 is after the beginning of T2, the beginning of T1 is before the end of T2, and the end of T1 is after the end of T2."@en ;
  rdfs:domain <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:range <http://www.w3.org/2006/time#ProperInterval> .

<http://www.w3.org/2006/time#intervalDuring> a rdf:Property ;
  rdfs:label "interval during"@en ;
  rdfs:comment "If a proper interval T1 is intervalDuring another proper interval T2, then the beginning of T1 is after the beginning of T2, and the end of T1 is before the end of T2."@en ;
  rdfs:domain <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:range <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:subPropertyOf <http://www.w3.org/2006/time#intervalIn> .

<http://www.w3.org/2006/time#intervalOverlaps> a rdf:Property ;
  rdfs:label "interval overlaps"@en ;
  rdfs:comment "If a proper interval T1 is intervalOverlaps another proper interval T2, then the beginning of T1 is before the beginning of T2, the end of T1 is after the beginning of T2, and the end of T1 is before the end of T2."@en ;
  rdfs:domain <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:range <http://www.w3.org/2006/time#ProperInterval> .

<http://www.w3.org/2006/time#intervalMeets> a rdf:Property ;
  rdfs:label "interval meets"@en ;
  rdfs:comment "If a proper interval T1 is intervalMeets another proper interval T2, then the end of T1 is coincident with the beginning of T2."@en ;
  rdfs:domain <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:range <http://www.w3.org/2006/time#ProperInterval> .

<http://www.w3.org/2006/time#intervalFinishes> a rdf:Property ;
  rdfs:label "interval finishes"@en ;
  rdfs:comment "If a proper interval T1 is intervalFinishes another proper interval T2, then the beginning of T1 is after the beginning of T2, and the end of T1 is coincident with the end of T2."@en ;
  rdfs:domain <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:range <http://www.w3.org/2006/time#ProperInterval> ;
  rdfs:subPropertyOf <http://www.w3.org/2006/time#intervalIn> .

<http://www.w3id.org/ecsel-dr-AT#Gateway> a rdfs:Class ;
  rdfs:comment """A gateway is a piece of networking hardware used in telecommunications for communications networks that allows data to flow from one discrete network to another. 
Gateways are distinct from routers or switches in that they communicate using more than one protocol and can operate at any of the 7 layers of the OSI model."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#CommunicationDevice> .

<http://www.w3.org/ns/ssn/systems/ResponseTime> a rdfs:Class ;
  rdfs:label "Response Time" ;
  rdfs:comment "As a Sensor Property: the time between a (step) change in the value of an observed ObservableProperty and a Sensor (possibly with specified error) 'settling' on an observed value, under the defined Conditions." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/systems/SystemProperty> .

<http://www.w3id.org/ecsel-dr-OOSMP#Microphone> a rdfs:Class ;
  rdfs:label "Microphone" ;
  rdfs:comment "The highly performing MEMS Microphones will enable the next performance level of voice user interfaces, audio recording and active noise cancellation. Infineon’s Dual Backplate (DBP) MEMS technology provides crystal clear (SNR), distortion free (THD) audio signals." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#Sensor> .

<http://www.w3id.org/ecsel-dr-AH#Software_system> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PWR#CommunicationServices> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#IndutrialSector> .

<http://www.w3.org/ns/ssn/systems/Accuracy> a rdfs:Class ;
  rdfs:label "Accuracy" ;
  rdfs:comment "The closeness of agreement between the Result of an Observation (resp. The command of an Actuation) and the true value of the observed ObservableProperty (resp. Of the acted on ActuableProperty) under the defined Conditions." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/systems/SystemProperty> .

<http://www.w3id.org/ecsel-dr-AT#RDF-GraphStore> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Database-System> .

<http://www.w3id.org/ecsel-dr-AH#Point-to-Point_communication_technology> a rdfs:Class ;
  rdfs:comment "corresponds to OSI layer 3, e.g. IPv4 or IPv6" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Communication_technology> .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_1_1> a rdfs:Class ;
  rdfs:comment "Communication between devices on ISA-95 level 1 (intra-level 1-communication)"@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ISA-95_Communication> .

<http://www.w3id.org/ecsel-dr-AT#WPAN_802_15_4> a rdfs:Class ;
  rdfs:comment """IEEE 802.15.4 is a standard which specifies the physical layer and media access control for low-rate wireless personal area networks (LR-WPANs). 
It is maintained by the IEEE 802.15 working group. 
It is the basis for the ZigBee, ISA100.11a, WirelessHART, and MiWi specifications, each of which further extends the standard by developing the upper layers which are not defined in IEEE 802.15.4. Alternatively, it can be used with 6LoWPAN and standard Internet protocols to build a wireless embedded Internet.
(https://www.postscapes.com/internet-of-things-protocols/)"""@en , "Der Standard IEEE 802.15.4 beschreibt ein Übertragungsprotokoll für Wireless Personal Area Networks (WPAN). Er definiert die untersten beiden Schichten des OSI-Modells, den Bitübertragungs- und den MAC-Layer. Höhere Protokollebenen mit Funktionen zum Routing und einer Anwendungsschnittstelle obliegen anderen Standards für Funknetze wie ZigBee. Wesentliche Entwicklungsziele für das Protokoll sind geringe Leistungsaufnahme für einen langen Betrieb über Batterieversorgung, kostengünstige Hardware, sichere Übertragung, Nutzung der lizenzfreien ISM-Bänder und Parallelbetrieb mit anderen Sendern auf diesen Frequenzen, insbesondere WLAN und Bluetooth. Durch diese Eigenschaften eignet sich der Standard IEEE 802.15.4 vor allem für drahtlose Sensornetze (WSN) und für direkt am Körper getragene Sensoren und Aktoren (WBAN, Wireless Body Area Network)."@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> .

<http://www.w3id.org/ecsel-dr-AT#Simulation-System> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-PWR#Process_Input> a rdfs:Class ;
  rdfs:label "Process Input" ;
  rdfs:comment "Any information that is provided a Procedure for its use." .

<http://www.w3id.org/ecsel-dr-OOSMP#MagneticCurrentSensor> a rdfs:Class ;
  rdfs:label "Magnetic Current Sensor" ;
  rdfs:comment "A magnetic current sensor is a sensor which measures magnetic current." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#Sensor> .

<http://www.w3id.org/ecsel-dr-AT#PLM-System-SecondGeneration> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#PLM-System> .

<http://www.w3id.org/ecsel-dr-PMV#ApplicationSystemType> a rdfs:Class ;
  rdfs:label "Application system type" ;
  rdfs:comment "An application system type classifies individual application systems which have exactly the same technological properties. Process steps might be supported by application systems. Object describe IT systems (library for IT systems available)." ;
  rdfs:subClassOf <http://purl.org/dc/dcmitype/Software> .

<http://www.w3id.org/ecsel-dr-PMV#hasRemarkOrExample> a rdf:Property ;
  rdfs:label "has remark or example" ;
  rdfs:comment "Denotes a remark or an example that is given specific to an element." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#ApplicationSystemType> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#supports> a rdf:Property ;
  rdfs:label "supports" ;
  rdfs:comment "A process step is supported by an Application system." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#ApplicationSystemType> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Task> .

<http://www.w3.org/ns/ssn/Input> a rdfs:Class ;
  rdfs:label "Input"@en ;
  rdfs:comment "Any information that is provided to a Procedure for its use."@en .

<http://www.w3id.org/ecsel-dr-AT#DPWS> a rdfs:Class ;
  rdfs:label "Device Profile for Web Services" ;
  rdfs:comment """The Device Profiles for Web Services (DPWS for short) specifies a standard that should enable Web services to be deployed on embedded systems, that is, on hardware with resources that may be severely constrained. For this, DPWS combines a selection of existing WS - * specifications together with some extensions or some new specifications into a profile based on network - capable embedded systems

    can communicate safely with each other,
    discover dynamically remote devices or services,
    can independently describe services and
    Trigger events or subscribe to events of other services.

In order to reach these goals the existing specifications WS-Addressing, WS-Policy, WS-Security and WS-Metadata Exchange respectively WS-Transfer are combined in the Devices Profiles for Web Services, especially for the dynamic discovery of services and for the event-based communication defines the new WS-Discovery and WS-Eventing specifications.

Originally, the Devices Profile for Web Services specification was developed by Microsoft, and an implementation of DPWS is also integrated with Windows Vista. Open source implementations of the DPWS specification have been developed, for example as part of the Web Services for Devices Initiative."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitecture> .

<http://www.w3.org/ns/ssn/System> a rdfs:Class ;
  rdfs:label "System"@en ;
  rdfs:comment "System is a unit of abstraction for pieces of infrastructure that implement Procedures. A System may have components, its subsystems, which are other systems."@en .

<http://www.w3id.org/ecsel-dr-AT#Segment> a rdfs:Class ;
  rdfs:comment """Data transmission unit of ISO/OSI Layer 4 (Transport Layer). 
A segment is a part of a message which is sent from an application system to another application system. The message is segmented on ISO/OSI Layer 4 to fit the end-to-end transport requirements of this layer."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#DataTransmissionUnit> .

<http://xmlns.com/foaf/0.1/Person> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#WADL> a rdfs:Class ;
  rdfs:comment """Die Web Application Description Language (WADL) ist ein XML-basiertes Dateiformat, das HTTP-basierte Anwendungen beschreibt, wie sie vorwiegend im WWW und in Intranets vorkommen. WADL unterstützt dabei vor allem die Beschreibung von REST-basierten Webservices und nimmt für diese Klasse von Anwendungen eine vergleichbare Rolle ein wie WSDL für SOAP-basierte Webservices.

WADL hat zum Ziel, Dienste im Internet (oder jedem anderen IP-basierten Netz) in maschinenlesbarer Form zu beschreiben und damit die Entwicklung von Anwendungen im Stil des Web 2.0 zu vereinfachen.""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#MarkupLanguage> .

<http://www.w3id.org/ecsel-dr-RAMI40#Structure> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-RAMI40#Submodel> .

<http://www.w3id.org/ecsel-dr-AT#PLM-System-FirstGeneration> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#PLM-System> .

<http://www.w3id.org/ecsel-dr-AT#CPF3_4_Profinet_IO_ClassA> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#CPF3_Profibus_ProfiNet> .

<http://www.w3id.org/ecsel-dr-AH#System-of-Systems> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#ServiceDataLanguage> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L5_DataSemantics> .

<http://www.w3id.org/ecsel-dr-AT#LES> a rdfs:Class ;
  rdfs:label "Logistics Execution System" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-AT#SoA_Subscriber> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitecture_FunctionPattern> .

<http://www.w3id.org/ecsel-dr-SCP#OP_Forecast> a rdfs:Class ;
  rdfs:label "OP_Forecast"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#Forecast> .

<http://www.w3id.org/ecsel-dr-PROD#RfP> a rdfs:Class ;
  rdfs:comment "Required for Plan: planning product being not capacity relevant" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PROD#PlanningElement> .

<http://www.w3id.org/ecsel-dr-PROD#hasSalesProduct> a rdf:Property ;
  rdfs:comment "FinishedProduct hasSalesProduct SalesProduct" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#RfP> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PROD#SalesProduct> .

<http://www.w3id.org/ecsel-dr-PWR#Source> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Device_Elements> .

<http://www.w3id.org/ecsel-dr-OOSMP#DigitalBarometricPressureSensor> a rdfs:Class ;
  rdfs:label "Digital Barometric Pressure Sensor" ;
  rdfs:comment "Infineon’s  DPS310 is a miniaturized digital barometric pressure sensor which offers high accuracy and low current consumption, and is capable of measuring both pressure and temperature. A sealed capacitive sensing element is used for pressure measurement, guaranteeing high precision and accuracy across temperature changes. The small package and low energy consumption make  DPS310 ideal for mobile applications and wearable devices." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#PressureSensor> .

<http://www.w3id.org/ecsel-dr-AT#SoA_Publisher> a rdfs:Class ;
  rdfs:comment "\"Role\" or function of a software (application) system that publishes data to a communication channel in a publish-subscribe communication pattern / process."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitecture_FunctionPattern> .

<http://www.w3id.org/ecsel-dr-AT#CPF12_EtherCAT> a rdfs:Class ;
  rdfs:comment "s. auch Beckhoff-Vortrag im Folder der Automatisierungstechnik-VL der TU München von 2008" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_2_2> a rdfs:Class ;
  rdfs:comment "Communication between devices on ISA-95 level 2 (intra-level 2-communication)"@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ISA-95_Communication> .

<http://www.w3id.org/ecsel-dr-OOSMP#LinearHallSensor> a rdfs:Class ;
  rdfs:label "Linear Hall Sensor" ;
  rdfs:comment """Measure the vertical component of a magnetic field and outputs a signal that is directly proportional to the magnetic field. These programmable linear Hall sensors come with different interface options. Our family of TLE499x linear Hall ICs is tailored to the needs of highly accurate angular and linear position detection and current measurement applications.
Each product measures the vertical component of a magnetic field and outputs a signal that is directly proportional to the magnetic field. These programmable linear Hall sensors come with different interface options.""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#MagneticPositionSensor> .

<http://www.w3id.org/ecsel-dr-AH#AH_service_documentation> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Service_documentation> .

<http://www.w3id.org/ecsel-dr-PWR#Object> a rdfs:Class ;
  rdfs:comment "Any physical, social, or mental object, or a substance" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Entity> .

<http://www.w3.org/ns/ssn/systems/SystemProperty> a rdfs:Class ;
  rdfs:label "System Property" ;
  rdfs:comment "An identifiable and observable characteristic that represents the system's ability to operate its primary purpose: a sensor to make Observations, an Actuator to make Actuations, or a Sampler to make Sampling." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/Property> .

<http://www.w3id.org/ecsel-dr-AT#IEEE> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#StandardisationOrganization> .

<http://www.w3id.org/ecsel-dr-PWR#Abstract> a rdfs:Class ;
  rdfs:comment """Any Entity that cannot be located in space-time.

Example: mathematical entities: formal semantics elements, regions within dimensional spaces, etc.\"""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Entity> .

<http://www.w3id.org/ecsel-dr-AT#MQTT_TCPIP> a rdfs:Class ;
  rdfs:label "Message Queue Telemetry Transport over TCP/IP infrastructure"@en ;
  rdfs:comment "https://de.wikipedia.org/wiki/MQTT" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#MQTT_TCPIP_based> .

<http://www.w3id.org/ecsel-dr-SCP#Customers> a rdfs:Class ;
  rdfs:label "Customers"@iri-based .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_3_3> a rdfs:Class ;
  rdfs:comment "Communication between devices on ISA-95 level 3 (intra-level 3-communication)"@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ISA-95_Communication> .

<http://www.w3id.org/ecsel-dr-AT#AMQP> a rdfs:Class ;
  rdfs:label "Advanced Message Queuing Protocol"@en ;
  rdfs:comment """Comment HB: this protocol seems to be usable in all ISA-level- and ISA-cross-level communications except 4-4. 
We exclude 4-4 from the list since AMQP claims to be a standard for a (message oriented) middleware. Communication between ISA Level 4 systems does typically not rely on a middleware. 
This statement should be further discussed!"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-SO#Lot_Event> a rdfs:Class ;
  rdfs:comment "the “Lot Event” tracing entity gives the history of lot events. e.g. Hold events, Split events, Merge events, etc. (tracing entities)"@en .

<http://www.w3id.org/ecsel-dr-SO#hasEventDate> a rdf:Property ;
  rdfs:comment "Lot Event: Date event occurred (DD.MM.YYYY hh:mm:ss)"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Lot_Event> ;
  rdfs:range xsd:dateTime .

<http://www.w3id.org/ecsel-dr-SO#hasEventName> a rdf:Property ;
  rdfs:comment "Lot Event: Name of event that occurred to lot (Hold, Split, Merge, Scrap, etc.)"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Lot_Event> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasLot> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Lot_Event> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Lot> .

<http://www.w3id.org/ecsel-dr-SO#hasParentLotEvent> a rdf:Property ;
  rdfs:comment "Lot Event: FK; Name of ancestor lot event (important to rebuild the lot history)"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Lot_Event> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasLeaveMainQuantity> a rdf:Property ;
  rdfs:comment "Lot Event: Number of units in the lot (wafers / chips) when left the event (Important for splits, merges and scraps)"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Lot_Event> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-SO#hasEnterMainQuantity> a rdf:Property ;
  rdfs:comment "Lot Event: Number of units in the lot (wafers / chips) when entered the event"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Lot_Event> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-PWR#Package> a rdfs:Class ;
  rdfs:comment "A package is the housing for a chip (or several chips) and provides electrical contacts. It is an interconnect in between chip-pads and the interface to the PCB board. A package is characterized by its outline (drawing) and its materials." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Physical_Object> .

<http://www.w3.org/ns/sosa/ObservableProperty> a rdfs:Class ;
  rdfs:label "Observable Property"@en ;
  rdfs:comment "An observable quality (property, characteristic) of a FeatureOfInterest."@en ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/Property> .

<http://www.w3.org/ns/sosa/isObservedBy> a rdf:Property ;
  rdfs:label "is observed by"@en ;
  rdfs:comment "Relation between an ObservableProperty and the Sensor able to observe it."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/ObservableProperty> ;
  rdfs:range <http://www.w3.org/ns/sosa/Sensor> .

<http://www.w3id.org/ecsel-dr-SO#Lithography> a rdfs:Class ;
  rdfs:comment "The lithography process is the key process in frontend. This consists of the following steps: a photo resisting layer is spun on a wafer, then exposed through the mask, then developed, then showing the effect on the open places, and then final deletion of the photo resisting material leaves only the remaining structure on the water. after some time for deposition, these steps are repeated up to 35 times."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Workshop> .

<http://www.w3id.org/ecsel-dr-SO#Release_Plan> a rdfs:Class ;
  rdfs:comment "The “Release Plan” entity shows the quantity planned to be released to a fab or facility. (strategy entity)"@en .

<http://www.w3id.org/ecsel-dr-SO#hasDeliveryCommitment> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Release_Plan> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Delivery_Commitment> .

<http://www.w3id.org/ecsel-dr-SO#hasReleasePlanID> a rdf:Property ;
  rdfs:comment "Release Plan: FK; Name of the product level 3"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Release_Plan> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AT#6LoWPAN> a rdfs:Class ;
  rdfs:label "IPv6 over Low Power Wireless Personal Area Network"@de ;
  rdfs:comment """6LoWPAN ist ein Akronym für „IPv6 over Low power Wireless Personal Area Network“ (engl.: IPv6 für WPAN mit niedrigem Energieverbrauch).[1] 6LoWPAN ist ein Kommunikationsprotokoll zur Funkdatenübertragung und eine Arbeitsgruppe der IETF, die für diesen Standard zuständig ist.

Der Standard umfasst dabei auch Header-Kompressionsverfahren, die es effizienter machen, IPv6-Pakete über IEEE-802.15.4-basierende Netzwerke zu übermitteln. Das Internet-Protokoll ist dabei Grundlage für die Netzstrukturen des Internets und für lokale Netze. 6LoWPAN verfolgt das Ziel, drahtlose PANs mit möglichst geringem Aufwand in bestehende Netze integrieren zu können.

Die Basisspezifikation des Protokolls, die von der 6LoWPAN-Arbeitsgruppe der IETF entwickelt wurde, ist im RFC 4944 festgehalten. Einige Probleme des 6LoWPAN sind im RFC 4919 aufgeführt. Da die Header-Komprimierung aus dem ursprünglichen Entwurf (HC1) nur in wenigen Fällen zu guten Ergebnissen führt, wurde in RFC 6282 eine neue Methode eingeführt (IPHC) und die alte soll nicht mehr verwendet werden."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_3_4_NetworkTechnology> .

<http://www.w3id.org/ecsel-dr-AT#FDDI> a rdfs:Class ;
  rdfs:label "Fiber Distributed Data Interface"@de ;
  rdfs:comment "Das Fiber Distributed Data Interface (FDDI, umgangssprachlich auch Lichtwellenleiter-Metro-Ring) ist eine Ende der 1980er Jahre entwickelte standardisierte 100-Mbit/s-Netzwerkstruktur für lokale Netzwerke (ANSI Standard X3T9.5). Als Medium werden Glasfaserkabel in einem doppelten, gegenläufigen Ring mit Token-Zugriffsmechanismus verwendet. 1994 wurde der FDDI-Standard erweitert und die Übertragung auch über geschirmte (STP) und ungeschirmte (UTP Typ 5) verdrillte Kupferleitungen standardisiert (CDDI, C für Copper). FDDI wurde nach und nach durch kostengünstige Ethernet-Technik verdrängt. Marktführende Hersteller von Netzwerkkomponenten bieten für ihre Produkte keine FDDI-Unterstützung mehr an, so dass die Technik als veraltet gilt" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> .

<http://www.w3id.org/ecsel-dr-AH#Raspberry_Pi> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Device> .

<http://www.w3id.org/ecsel-dr-SCP#RetainedStock> a rdfs:Class ;
  rdfs:label "RetainedStock"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#SSO_Stocks> .

<http://www.w3id.org/ecsel-dr-SO#Robot> a rdfs:Class ;
  rdfs:comment "the robot loads and unloads the lots from the WIP station into the furnace. Robot can load the furnace while another boat is processd by the tool."@en .

<http://www.w3id.org/ecsel-dr-SO#roboticallyLoads> a rdf:Property ;
  rdfs:comment "the operator will load the wafer into the wip station and then the robot will load the wafers from the wip station to the tool" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Robot> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Tool> .

<http://www.w3id.org/ecsel-dr-PWR#Drain_Voltagea> a rdfs:Class ;
  rdfs:label "Gate-Source Voltage" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Process_Input> , <http://www.w3id.org/ecsel-dr-PWR#Property> .

<http://www.w3id.org/ecsel-dr-OM#CustomerData> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-OM#hasCustomerAddress> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#CustomerData> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-OM#describesCustomer> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#CustomerData> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#Customer> .

<http://www.w3id.org/ecsel-dr-OM#hasCustomerNo> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#CustomerData> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-AT#OCF> a rdfs:Class ;
  rdfs:label "Open Connectivity Foundation"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#StandardisationOrganization> .

<http://www.w3.org/ns/sosa/Sensor> a rdfs:Class ;
  rdfs:label "Sensor"@en ;
  rdfs:comment "Device, agent (including humans), or software (simulation) involved in, or implementing, a Procedure. Sensors respond to a stimulus, e.g., a change in the environment, or input data composed from the results of prior Observations, and generate a Result. Sensors can be hosted by Platforms."@en ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/System> .

<http://www.w3.org/ns/sosa/observes> a rdf:Property ;
  rdfs:label "observes"@en ;
  rdfs:comment "Relation between a Sensor and an ObservableProperty that it is capable of sensing."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Sensor> ;
  rdfs:range <http://www.w3.org/ns/sosa/ObservableProperty> ;
  rdfs:subPropertyOf <http://www.w3.org/ns/ssn/forProperty> .

<http://www.w3.org/ns/ssn/detects> a rdf:Property ;
  rdfs:label "detects"@en ;
  rdfs:comment "A relation from a Sensor to the Stimulus that the Sensor detects. The Stimulus itself will be serving as a proxy for some ObservableProperty."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Sensor> ;
  rdfs:range <http://www.w3.org/ns/ssn/Stimulus> .

<http://www.w3.org/ns/sosa/madeObservation> a rdf:Property ;
  rdfs:label "made observation"@en ;
  rdfs:comment "Relation between a Sensor and an Observation made by the Sensor."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Sensor> ;
  rdfs:range <http://www.w3.org/ns/sosa/Observation> .

<http://www.w3.org/2006/time#TemporalEntity> a rdfs:Class ;
  rdfs:label "Temporal entity" ;
  rdfs:comment "A temporal interval or instant."@en .

<http://www.w3id.org/ecsel-dr-OM#Customer> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-OM#ownsCustomerPlant> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#Customer> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#CustomerPlant> .

<http://www.w3id.org/ecsel-dr-OM#requestsOrderChangeRequest> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#Customer> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#OrderChangeRequest> .

<http://www.w3id.org/ecsel-dr-PMV#ModellingFunctionObject> a rdfs:Class ;
  rdfs:label "Modelling Function Object" ;
  rdfs:comment "Function objects are used to model the decomposition of the process flow." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#FunctionObject> .

<http://www.w3id.org/ecsel-dr-SO#Tempering> a rdfs:Class ;
  rdfs:comment "The tempering process is a type of heat treatment applied by the furnace. The process has the effect of toughening by lessing brittleness and reducing internal stresses."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Furnace_Process> .

<http://www.w3id.org/ecsel-dr-PWR#Process> a rdfs:Class ;
  rdfs:label "Process" ;
  rdfs:comment "A process has an output and possibly inputs, and for a compositive process, describes the temporal and dataflow dependencies and relationships amongst its parts." .

<http://www.w3id.org/ecsel-dr-AT#OMG> a rdfs:Class ;
  rdfs:label "Object Management Group"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#StandardisationOrganization> .

<http://www.w3id.org/ecsel-dr-PRIMA#Project> a rdfs:Class .

<http://www.w3.org/ns/ssn/Output> a rdfs:Class ;
  rdfs:label "Output"@en ;
  rdfs:comment "Any information that is reported from a Procedure."@en .

<http://www.w3id.org/ecsel-dr-PMV#OtherServices> a rdfs:Class ;
  rdfs:label "Other Services" ;
  rdfs:comment "Collection of other services used as input to a production process or which are created during a production process." ;
  rdfs:subClassOf <http://purl.org/dc/dcmitype/Service> .

<http://www.w3id.org/ecsel-dr-AH#SoA_property> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AH#isPropertyOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#SoA_property> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Service-oriented_Architecture> .

<http://www.w3id.org/ecsel-dr-AH#Communication_technology> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#OMG-Standard> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Standard> .

<http://www.w3id.org/ecsel-dr-PMV#StartEvent> a rdfs:Class ;
  rdfs:label "Start Event" ;
  rdfs:comment "Denotes the event that stands at the beginning of a branch in the process flow and thus, triggers the execution of this branch or the total process." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#Event> .

<http://www.w3id.org/ecsel-dr-OOSMP#PackingType> a rdfs:Class ;
  rdfs:label "Packing Type" ;
  rdfs:comment "A packing type describes how products/solutions are packed for shipping. There are different packing types, like \"Ammo Pack\", \"Tape and Reel\", \"Tray\" and \"Tube\"." .

<http://www.w3id.org/ecsel-dr-OOSMP#packingTypeOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#PackingType> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> .

<http://www.w3id.org/ecsel-dr-PWR#Semiconductors&SemiconductorEquipment> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#InformationTechnology> .

<http://www.w3id.org/ecsel-dr-AH#AH_ServiceRegistrySystem_SySD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_system_SySD> .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_AutomationHierarchy> a rdfs:Class ;
  rdfs:comment """The original ISA-95 standard defined an information model for exchanges of information between business systems and manufacturing operations systems. The 2012 release of ISA-95 Part 4: Objects and Attributes for Manufacturing Operations Management Integration, and the planned 2016 release of the equivalent IEC 62264-4 standard, has added information models for data exchange between manufacturing execution systems (MESs), laboratory information management systems, warehouse management systems, tank farm systems, asset management systems, and other manufacturing operations
management systems. 
The MESA B2MML Version 6.0 2013 release provided an implementation of the ISA-95 Part 4 models.
(Source: Dennis Brandl)"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#NetworkLayerModel> .

<http://www.w3id.org/ecsel-dr-SCP#GeneralCustomers> a rdfs:Class ;
  rdfs:label "GeneralCustomers"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#Customers> .

<http://www.w3id.org/ecsel-dr-AH#AH_DeviceDiscoveryService_SD> a rdfs:Class ;
  rdfs:comment "Service Description of the Arrowhead non-mandatory core service (automation supporting service) DeviceDiscovery, provided by the AH system DeviceRegistry."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service_SD> .

<http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system_SySDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_core_system_SySDD> .

<http://www.w3id.org/ecsel-dr-AT#WirelessHART> a rdfs:Class ;
  rdfs:comment """In September 2007, the HCF (HART Communication Foundation) set and released the new WirelessHART standard. The radio transmission is based on the wireless communication standard IEEE 802.15.4 (ISM band) and uses TDMA as a transmission method. The communication provides encryption based on the Advanced Encryption Standard (AES 128) so that the data transfer and the parameterization of the field devices can not be changed without authorization.
WirelessHART is part of the new HART 7 specification and has been standardized as IEC 62591: 2010. Completion of the HART test specification is expected by mid-2008. Thus, the first WirelessHART-compliant measuring devices should still be available in 2008. 
Essential Features
The network builds itself up (meshed network). If a field device to be added to an existing network, only a kind of password must be entered, the topology is self-organizing. Outside, transmission distances of up to 3 km from subscriber to subscriber are possible. In spatially consecutive participants, therefore, significantly longer distances can be bridged, since the intermediate participants act as a kind of repeater.
Built-in redundancy: If a subscriber fails as a transmission path, the transmission is automatically established by another subscriber. The same information is transmitted as with the wired HART. The measured value transmission cycles depend on the particular system configuration and are typically between 15 seconds and several hours.""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_3_4_NetworkTechnology> .

<http://www.w3id.org/ecsel-dr-PMV#Connector> a rdfs:Class ;
  rdfs:label "Connector" ;
  rdfs:comment " A connector determines the behavior of the process in case its control ?ow is split up into or joined from several execution branches." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#ModelElement> .

<http://www.w3id.org/ecsel-dr-AT#AS2> a rdfs:Class ;
  rdfs:label "Applicability Statement 2"@de ;
  rdfs:comment """Applicability Statement 2 (AS2) ist ein Standard über einen gesicherten Nachrichtentransport über das Internet. Es ist detailliert beschrieben in RFC 4130.

Mit AS2 werden meist Nachrichten für Electronic Data Interchange (EDI) übertragen.

AS2 spezifiziert, wie man sich verbindet und Nachrichten validiert, versendet und bestätigt. Es erzeugt einen Umschlag für eine Nachricht, welche dann gesichert über das Internet versandt wird. Die Urheberschaft (nicht abstreitbare Nachricht) wird durch digitale Signaturen und die Datensicherheit durch Verschlüsselung gewährleistet. Der Absender erhält aus dem AS2-Protokoll eine digitale Empfangsquittung, in der AS-Sprache als Message Disposition Notification (MDN) bezeichnet, mit der der Absender die fristgerechte Zustellung beweisen kann.
Ablaufschema von AS2

AS2 ist ein Übertragungsstandard, der speziell für E-Commerce entwickelt wurde. Im Gegensatz zu anderen Übertragungsstandards wie etwa E-Mail, X.400, ISDN-FTP usw., die auch, aber nicht ausschließlich im geschäftlichen Kontext verwendet werden, ist AS2 von Grund auf nur für einen Geschäftseinsatz konzipiert. Charakteristischer Unterschied zu anderen Übertragungsstandards ist, dass der Anwender zum Beweis der Revisionssicherheit nicht auf technische Protokolle angewiesen ist (die bspw. Netzwerkspezialisten erst aus den Systemen hervorholen müssen), sondern mit der MDN den Beweis in Nachricht-Form besitzt."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-AH#AH_SystemRegistrySystem_SySDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system_SySDD> .

<http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitecture_FunctionPattern> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#IndustrialWLAN> a rdfs:Class ;
  rdfs:comment """Industrial Wireless Local Area Network bzw. Industrial WLAN kurz IWLAN ist eine Weiterentwicklung des bekannten WLAN für den industriellen Einsatz durch die Firma Siemens.

Der wesentliche Unterschied im Vergleich mit dem im Privatbereich stark verbreiteten WLAN liegt in der zeitgenauen Übertragung der Steuer- und Datensätze, was für den Einsatz in der Industrie zwingend erforderlich ist, um Maschinen sicher steuern zu können. Außerdem sind solche Geräte für einen größeren Temperaturbereich von −40 °C bis +70 °C ausgelegt.

Das Netz arbeitet mit einem speziellen Verschlüsselungsverfahren, um Manipulationen zu unterbinden."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> .

<http://www.w3id.org/ecsel-dr-PWR#Industrials> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#IndutrialSector> .

<http://www.w3id.org/ecsel-dr-OM#DemandFulfillement> a rdfs:Class .

<http://www.w3.org/2006/time#GeneralDurationDescription> a rdfs:Class ;
  rdfs:label "Generalized duration description"@en ;
  rdfs:comment "Description of temporal extent structured with separate values for the various elements of a calendar-clock system."@en ;
  rdfs:subClassOf <http://www.w3.org/2006/time#TemporalDuration> .

<http://www.w3id.org/ecsel-dr-AT#MQTT> a rdfs:Class ;
  rdfs:comment """MQTT[1] (Message Queuing Telemetry Transport) is an ISO standard (ISO/IEC PRF 20922)[2] publish-subscribe-based messaging protocol. It works on top of the TCP/IP protocol. It is designed for connections with remote locations where a \"small code footprint\" is required or the network bandwidth is limited. The publish-subscribe messaging pattern requires a message broker.

Andy Stanford-Clark of IBM and Arlen Nipper of Cirrus Link authored the first version of the protocol in 1999.[3]

The specification does not specify the meaning of \"small code footprint\" or the meaning of \"limited network bandwidth\". Thus, the protocol's availability for use depends on the context. In 2013, IBM submitted MQTT v3.1 to the OASIS specification body with a charter that ensured only minor changes to the specification could be accepted.[4] MQTT-SN[5] is a variation of the main protocol aimed at embedded devices on non-TCP/IP networks, such as ZigBee.

Historically, the \"MQ\" in \"MQTT\" came from IBM's MQ Series message queuing product line.[6] However, queuing itself is not required to be supported as a standard feature in all situations.[7]

Alternative protocols include the Advanced Message Queuing Protocol (AMQP), Streaming Text Oriented Messaging Protocol (STOMP), the IETF Constrained Application Protocol,[8] XMPP,[9][10] DDS,[11] OPC UA,[12] and Web Application Messaging Protocol (WAMP).
(https://en.wikipedia.org/wiki/MQTT)"""@en , """MQTT is not only application protocol. It's take layers 5-7 (App, Presentation and Session).
For example, you can see that MQTT has Persistent Session. It means MQTT contains Session Layer."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-AT#DSL> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> .

<http://www.w3id.org/ecsel-dr-AT#UDP> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_TransportProtocol> .

<http://www.w3id.org/ecsel-dr-OOSMP#IntelligentPowerModule> a rdfs:Class ;
  rdfs:label "Intelligent Power Module" ;
  rdfs:comment "A semiconductor product which is used as intelligent power module" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> .

<http://www.w3id.org/ecsel-dr-OOSMP#partOfAsIntelligentPowerModule> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#IntelligentPowerModule> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#partOf> .

<http://www.w3id.org/ecsel-dr-PROD#PlanningElement> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#PLM1_Module> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#PLM-System-FirstGeneration> .

<http://www.w3id.org/ecsel-dr-AT#N3_TURTLE> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L2_DataSyntax> .

<http://www.w3id.org/ecsel-dr-AH#AH_system_of_systems_documentation_document> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Documentation_document> .

<http://www.w3id.org/ecsel-dr-AH#AH_StoreManagementService_IDD> a rdfs:Class ;
  rdfs:comment "Interface Design Description (IDD) of the Arrowhead mandatory core service Store Management Service which is provided by the mandatory core system Orchestration System (Orchestrator)."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_service_IDD> .

<http://www.w3id.org/ecsel-dr-PWR#Junction_Temperature> a rdfs:Class ;
  rdfs:label "Junction Temperature" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Property> .

<http://www.w3id.org/ecsel-dr-AH#System_WebApplicationDescription_WADL> a rdfs:Class ;
  rdfs:comment """Description of an Arrowhead compliant software system in terms of the Web Application Description Language WADL. 
The Web Application Description Language (WADL) is a machine-readable XML description of HTTP-based web services. WADL models the resources provided by a service and the relationships between them. WADL is intended to simplify the reuse of web services that are based on the existing HTTP architecture of the Web. It is platform and language independent and aims to promote reuse of applications beyond the basic use in a web browser.
WADL is the REST equivalent of SOAP's Web Services Description Language (WSDL), which can also be used to describe REST web services.
Sources: 
https://en.wikipedia.org/wiki/Web_Application_Description_Language
 Sun Microsystems (31 August 2009). \"Web Application Description Language: W3C Member Submission 31 August 2009\". World Wide Web Consortium. Retrieved 12 August 2012.
World Wide Web Consortium (14 October 2009). \"Team Comment on the \"Web Application Description Language\" Submission\". World Wide Web Consortium. Retrieved 12 August 2012.
Lawrence Mandel (29 May 2008). \"Describe REST Web services with WSDL 2.0: A how-to guide\". IBM. Retrieved 12 August 2012."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_system_documentation_document> .

<http://www.w3id.org/ecsel-dr-SCP#SalesDemands> a rdfs:Class ;
  rdfs:label "SalesDemands"@iri-based .

<http://www.w3id.org/ecsel-dr-PMV#StructuralFunctionObject> a rdfs:Class ;
  rdfs:label "Structural Function Object" ;
  rdfs:comment "Function objects are used to model the decomposition of the structure of a process." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#FunctionObject> .

<http://www.w3id.org/ecsel-dr-SCP#nEWs> a rdfs:Class ;
  rdfs:label "nEWs"@iri-based .

<http://www.w3id.org/ecsel-dr-SCP#isResultOf> a rdf:Property ;
  rdfs:label "isResultOf"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#nEWs> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#OrdersReschedule> .

<http://www.w3id.org/ecsel-dr-SCP#sendTo> a rdf:Property ;
  rdfs:label "sendTo"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#nEWs> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#CLM> .

<http://www.w3id.org/ecsel-dr-AT#PLM2_Vendor> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#PLM-System-SecondGeneration> .

<http://www.w3id.org/ecsel-dr-SO#Material_Transfer> a rdfs:Class ;
  rdfs:comment "a material transfer matrix estimates the duration of material from on to another equipment."@en .

<http://www.w3id.org/ecsel-dr-SO#hasTransferTime> a rdf:Property ;
  rdfs:comment "Material Transfer: Duration of transfer from on to the other equipment"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Material_Transfer> ;
  rdfs:range xsd:decimal .

<http://www.w3id.org/ecsel-dr-SO#toEquipmentGroupID> a rdf:Property ;
  rdfs:comment "Material Transfer: FK; target EquipmentGroup of transfer"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Material_Transfer> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#fromEquipmentGroupID> a rdf:Property ;
  rdfs:comment "Material Transfer: FK; start Equipment Group of material transfer"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Material_Transfer> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasTransferMode> a rdf:Property ;
  rdfs:comment "Transfer Mode: Automation, AGV, milkrun or manual"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Material_Transfer> ;
  rdfs:range xsd:string .

<http://www.w3.org/ns/ssn/Stimulus> a rdfs:Class ;
  rdfs:label "Stimulus"@en ;
  rdfs:comment "An event in the real world that 'triggers' the Sensor. The properties associated to the Stimulus may be different to the eventual observed ObservableProperty. It is the event, not the object, that triggers the Sensor."@en .

<http://www.w3.org/ns/ssn/isProxyFor> a rdf:Property ;
  rdfs:label "is proxy for"@en ;
  rdfs:comment "A relation from a Stimulus to the Property that the Stimulus is serving as a proxy for."@en ;
  rdfs:domain <http://www.w3.org/ns/ssn/Stimulus> ;
  rdfs:range <http://www.w3.org/ns/sosa/ObservableProperty> .

<http://www.w3id.org/ecsel-dr-PWR#GeometricDimension> a rdfs:Class ;
  rdfs:label "Geometric Dimension" ;
  rdfs:comment "\"Describes the Dimensions of any Physical Object (Length, Wisth, Height)\"" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Information_Object> .

<http://www.w3id.org/ecsel-dr-AT#IETF> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#StandardisationOrganization> .

<http://www.w3id.org/ecsel-dr-AT#UML> a rdfs:Class ;
  rdfs:label "Unified Modelling Language" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#MarkupLanguage> .

<http://www.w3.org/ns/ssn/systems/SurvivalRange> a rdfs:Class ;
  rdfs:label "Survival Range" ;
  rdfs:comment """\"Describes SurvivalProperties of a System under some specified Conditions. For example, the lifetime of a System under a specified temperature range.
In the absence of SurvivalProperties, simply describes the Conditions a System can be exposed to without damage. For example, the temperature range a System can withstand before being considered damaged.\"""" ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/Property> .

<http://www.w3.org/ns/ssn/systems/hasSurvivalProperty> a rdf:Property ;
  rdfs:label "has survival property" ;
  rdfs:comment "Relation from a SurvivalRange of a System to a SurvivalProperty describing the survival range of the System." ;
  rdfs:domain <http://www.w3.org/ns/ssn/systems/SurvivalRange> ;
  rdfs:range <http://www.w3.org/ns/ssn/systems/SurvivalProperty> ;
  rdfs:subPropertyOf <http://www.w3.org/ns/ssn/hasProperty> .

<http://xmlns.com/foaf/0.1/Agent> a rdfs:Class ;
  rdfs:label "Agent" ;
  rdfs:comment """\"The Agent class is the class of agents; things that do stuff. A well known sub-class is Person, representing people. Other kinds of agents include Organization and Group.

The Agent class is useful in a few places in FOAF where Person would have been overly specific. For example, the IM chat ID properties such as jabberID are typically associated with people, but sometimes belong to software bots.\"""" .

<http://www.w3id.org/ecsel-dr-AH#Method> a rdfs:Class ;
  rdfs:comment "Method of a service: method that is provided by a service within a SoA."@en .

<http://www.w3id.org/ecsel-dr-AH#isMethodOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#Method> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Service> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#isArchitecturalPartOf> .

<http://www.w3.org/ns/ssn/systems/Selectivity> a rdfs:Class ;
  rdfs:label "Selectivity" ;
  rdfs:comment "As an Actuator Property: the time between a (step) change in the command of an Actuator and the 'settling' of the value of the acted on ActuatableProperty, under the defined Conditions." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/systems/SystemProperty> .

<http://www.w3id.org/ecsel-dr-RAMI40#Date> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#OSI_L6_PresentationLayer> a rdfs:Class ;
  rdfs:label "Presentation layer"@en , "Darstellungsschicht"@de ;
  rdfs:comment """formats the data to be presented to the application layer. It can be viewed as the \"translator\" for the network on the data syntax level. 
Syntax layer. Encrypt and Decrypt (if needed). 
Topics: Character code translation, Data conversion, Data compression, Data encryption, Character Set translation. 
Examples: ASCII, UTF-8, JPEG, TIFF, GIF, MPEG, ..."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_DetailedLayer> .

<http://www.w3id.org/ecsel-dr-AH#Service> a rdfs:Class ;
  rdfs:label "Service"@en ;
  rdfs:comment """In the context of the Arrowhead Framework a Service is the information exchanged from a providing system to a consuming system.
• is based on a number of service orientation principles derived from high level objectives and properties of the Arrowhead framework 
• can be realized by an arbitrary number of service producers and service consumers 
• a system can consume a number of services, process and provide other services to fulfil a more complex task 
• can only be provided by technical systems 
• can support operational activities within business processes 
• can support non-functional requirements, such as real-time 
• can have stakeholders, with an interest in business benefit, in one or more specific area of interest 
• can have an appointed stakeholder, responsible for the governance of the Service (definition, development). 
(Source: Arrowhead Framework Definitions V2.4 & Arrowhead Device Registry Presentation)"""@en .

<http://www.w3id.org/ecsel-dr-PWR#Device_Elements> a rdfs:Class ;
  rdfs:label "Device Elements" .

<http://www.w3id.org/ecsel-dr-AT#EDIFACT_ORDERS> a rdfs:Class ;
  rdfs:label "Orders"@en ;
  rdfs:comment "EDIFACT message for purchase order(s)."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#EDIFACT-Specification> .

<http://www.w3id.org/ecsel-dr-SCP#DC> a rdfs:Class ;
  rdfs:label "DC"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#Stocks> .

<http://www.w3id.org/ecsel-dr-RAMI40#StandardVersion> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-RAMI40#Version> .

<http://www.w3id.org/ecsel-dr-AT#Message> a rdfs:Class ;
  rdfs:comment """Most complex data grouping in M2M communication. Complete data set which is sent from one application system to another. 
A message contains meta information which is added by the protocols on the different ISO/OSI layers (like transport protocol, network protocol, data link protocol) and the original content, which is referred to as payload data."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#DataTransmissionUnit> .

<http://www.w3id.org/ecsel-dr-RAMI40#Machine> a rdfs:Class ;
  rdfs:comment "A machine is ordered, designed, commissioned, operated, serviced, converted and recycled." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-RAMI40#Asset> .

<http://www.w3id.org/ecsel-dr-AT#TTP_C> a rdfs:Class ;
  rdfs:label "Time Triggered Protocol Class C"@de ;
  rdfs:comment """TTP (Time-Triggered Protocol Class C oder kurz: TTP/C) ist ein feldbusbasierendes Übertragungsprotokoll, das fehlertolerante zeitgesteuerte Kommunikation zwischen elektronischen Komponenten regelt und harte Echtzeitanforderungen erfüllt.
Allgemeines

Das Besondere an diesem Protokoll ist, dass es zeitgesteuert arbeitet, d. h., es als Steuersignale die gemeinsame Uhrzeit verwendet. Die Uhren der einzelnen Teilnehmer werden ständig durch Mittelwertbildung der Differenzen zwischen realer Ankunft der Nachricht und erwarteter Ankunft der Nachricht synchronisiert. Dieser Uhrensynchronisationsalgorithmus arbeitet dezentral und ist fehlertolerant gegenüber beliebigen Einzelfehlern. Die erwarteten Ankunftszeiten werden a priori in der MEDL (Message Descriptor List) festgelegt. Durch die MEDL ist jedem Teilnehmer bekannt, wann es ihm erlaubt ist zu senden und wann er empfangen muss.

Diese Art der Kommunikationsaufteilung wird TDMA (Time Division Multiple Access) genannt. In einer TDMA-Runde hat jeder Teilnehmer die Möglichkeit für eine bestimmte Zeit seine Nachricht zu senden. Die TDMA-Runde wiederholt sich, sobald die vorherige abgeschlossen ist.

Um die Störung der gesamten Kommunikation durch einen defekten Teilnehmer zu verhindern, der sinnlos Daten auf die Kanäle sendet (der sogenannte „Babbling idiot“), hat jeder Teilnehmer einen lokalen Buswächter (Bus-Topologie), der unabhängig vom Teilnehmer das Senden auf die Kanäle nur während der in der MEDL festgelegten Sendezeit zulässt. Bei Stern-Topologie wird pro Kanal ein zentraler Buswächter für alle Teilnehmer verwendet (Kostenersparnis).

Die Nachricht eines Teilnehmers muss durch einen minimalen Header ergänzt werden und dieser entstandene Frame wird durch eine CRC-Checksumme geschützt.

Eine weitere Maßnahme, um auch für sicherheitskritische Anwendungen geeignet zu sein, ist der Membership-Service, bei dem jeder Knoten eine Liste der als fehlerfrei angenommenen Knoten führt. Sollte die Membership-Liste nicht mit denen der anderen Knoten übereinstimmen, dann nimmt dieser Knoten einen Fehler bei sich selbst an und schaltet sich ab (Passive-Mode). Bei jeder Übertragung wird die Membership-Liste aktualisiert. Sollte ein Knoten einen fehlerhaften Frame senden, wird dieser aus der Liste ausgeschlossen.

Ein (geringes) Risiko bei diesem Verfahren ist, dass sich sogenannte Cliquen bilden, das sind zwei oder mehrere Gruppen, die sich untereinander als fehlerfrei ansehen und nur miteinander kommunizieren. Um dies zu vermeiden, prüft jeder Knoten zusätzlich, ob er Mitglied der größten 'Clique' ist und schaltet bei negativem Ergebnis in den passiven Modus.

TTP wird in einer Reihe von industriellen Serienprojekten eingesetzt. Honeywell verwendet das Protokoll in den Triebwerkssteuerungssystemen (FADEC) für die Lockheed Martin F-16 und für das Trainingsflugzeug Aermacchi M 346 sowie in einem Fly-by-Wire-Cockpit. Im Airbus A380 Mega-Airliner wird TTP zur Steuerung des von Nord-Micro hergestellten Kabinendrucksystems eingesetzt. Hamilton Sundstrand hat sich für den Einsatz einer TTP-basierten Datenkommunikationsplattform in den Stromerzeugungs- und Kabinensystemen des Boeing 787 Dreamliner entschieden. Alcatel benutzt das Protokoll seit Juni 2002 als Feldbusprotokoll in der Bahnhofssignalsteueranlage ELEKTRA 2."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_Car_Airplane> .

<http://www.w3id.org/ecsel-dr-AT#W3C_Data_Knowledge_Stack> a rdfs:Class ;
  rdfs:comment """also often referred to as Semantic Web Stack. 
Visualized in 2D or 3D. 
Starting at bottom with basic concepts  of the Web as URI, IRI, HTTP and UNICODE, followed by Syntax of Data with concepts like Turtle, RFD/XML etc.. 
Then Knowledge Respresentation layer contains RDF, and in parallel the query block with SPARQL is shown. 
On top of this Semantics with RDFS and OWL and in parallel Rules with RIF. 
On top of this comes Logic.

The W3C layers sit  directly on top of the OSI layers. This can be verifies by the fact that HTTP is a protocol which belongs to OSI leyer 7 as well as to W3C layer 1."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#NetworkLayerModel> .

<http://www.w3id.org/ecsel-dr-RAMI40#Dimension> a rdfs:Class ;
  rdfs:label "Dimension" ;
  rdfs:comment "Abstract class to describe the three different dimensions of RAMI4.0" .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_2_4> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ISA-95_CrossLayerCommunication> .

<http://www.w3id.org/ecsel-dr-SO#Product_Level_2> a rdfs:Class ;
  rdfs:comment "The product levels 3 to 1 are aggregated levels that are based on information from product level 4. (hierarchal aggregation level)"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Product_Level> .

<http://www.w3id.org/ecsel-dr-SO#hasProductLevel2ID> a rdf:Property ;
  rdfs:comment "Product Level 2: PK; Name of the product in level 2"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Product_Level_2> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#Lot_Size> a rdfs:Class ;
  rdfs:comment "A measure or quantity increment acceptable to or specified by the party offering to buy or sell. Used also as an alternative term for lot quantity."@en .

<http://www.w3id.org/ecsel-dr-SO#hasLotSizeQuantity> a rdf:Property ;
  rdfs:comment "Lot Size: Standard (FE) or optimal (BE) lot size for respective PL3"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Lot_Size> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AT#LIMS> a rdfs:Class ;
  rdfs:label "Laboratory Information Management System"@de ;
  rdfs:comment """LIMS steht für Labor-Informations- und Management-System. Diese Kategorie von Softwaresystemen befasst sich mit der Datenverarbeitung im analytischen Labor.[1] Es handelt sich um Software-basierten Labor- und Informations- Managementsysteme, die Eigenschaften haben, die die Operation eines modernen Labors unterstützen. LIMS Systeme werden teilweise auch Labor-Informationssystem (LIS) oder Labor-Managementsystem (LMS) bezeichnet.

Haupteigenschaften der LIMS sind unter anderem die Unterstützung von Arbeitsabläufen und der Datenverfolgung, eine flexible Architektur, Schnittstellen zum Austausch von Daten mit anderen Systemen.

LIMS haben sich über die Jahre von einem einfachen Verfolgungstool (Tracking) für zu testende Proben zu Enterprise Resource Planning (ERP) tools entwickelt, mit denen viele Aspekte der Laborinformatik abgedeckt werden. [2]

Die Aufgaben von LIMS leiten sich im Wesentlichen aus der Chemometrik her. Es werden unterschiedliche Prinzipien gemäß der zu begleitenden Prozesskette umgesetzt. In der Regel werden zwei Systemstränge umgesetzt:

    Messstrang (Messgeräte, Aufnahme und Speicherung der Messwerte aus Sensoren und DFÜ...)
    Kontrollstrang (mathematische Verarbeitung und Auswertung der Messdaten, Probenmanagement, Abrechnung usw.)

LIMS bestehen damit aus mindestens den Grundmodulen Messwerterfassung und Messwertauswertung."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-SCP#CLM> a rdfs:Class ;
  rdfs:label "CLM"@iri-based .

<http://www.w3id.org/ecsel-dr-SCP#use> a rdf:Property ;
  rdfs:label "use"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#CLM> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#OrderLineItem> .

<http://www.w3id.org/ecsel-dr-SCP#provide> a rdf:Property ;
  rdfs:label "provide"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#CLM> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#Promise> .

<http://www.w3id.org/ecsel-dr-SCP#create> a rdf:Property ;
  rdfs:label "create"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#CLM> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#PrioritizedOrders> .

<http://www.w3id.org/ecsel-dr-AT#XML-Schema> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#DataLanguage_XML-based> .

<http://www.w3id.org/ecsel-dr-SO#Process_Flow> a rdfs:Class ;
  rdfs:comment """\"A wafer technology is defined as a manufacturing process flow on wafer level including wafer test and pre-assembly which creates one device (discrete technology) or a set of different devices (IC technology) to be used in a product.  
\""""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Process> .

<http://www.w3id.org/ecsel-dr-SO#hasProductNumber> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Process_Flow> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Product_Number> .

<http://www.w3id.org/ecsel-dr-AT#FactoryLayoutPlanning> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#PLM1_Module> .

<http://www.w3id.org/ecsel-dr-AT#Repeater> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#CommunicationDevice> .

<http://www.w3id.org/ecsel-dr-SO#Equipment_Group> a rdfs:Class ;
  rdfs:comment "Each machine is allocated to a group of machines doing similar processes. The equipment groups are described and allocated in the master entity “Equipment Group”. (master entity)"@en .

<http://www.w3id.org/ecsel-dr-SO#hasShiftID> a rdf:Property ;
  rdfs:comment "Shift: PK; Name of shift"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Shift> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasShift> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Equipment_Group> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Shift> .

<http://www.w3id.org/ecsel-dr-SO#hasNumberOfParallelTools> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Equipment_Group> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-SO#hasMaxThroughputPerWeek> a rdf:Property ;
  rdfs:comment "Maximum Throughput per week"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Equipment_Group> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-SO#hasEquipmentGroupType> a rdf:Property ;
  rdfs:comment "Equipment Group: Refers to the technology used for the process tool: Lithography, Plasma Etching, Diffusion, Tester, Prober, etc."@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Equipment_Group> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PWR#Depletion_Mode> a rdfs:Class ;
  rdfs:label "Depletion Mode" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Operation_Mode> .

<http://www.w3id.org/ecsel-dr-PWR#Is_Working_As> a rdf:Property ;
  rdfs:label "The Depletion Mode Is Working As" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Depletion_Mode> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Variable_Resistance> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-PWR#Acting_As> .

<http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_system_SySD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_core_system_SySD> .

<http://www.w3id.org/ecsel-dr-AT#RelationalDatabase-System> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Database-System> .

<http://www.w3.org/ns/ssn/systems/ActuationRange> a rdfs:Class ;
  rdfs:label "Actuation Range" ;
  rdfs:comment "The range of property values that can be the Result of an Actuation under the defined Conditions." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/systems/SystemProperty> .

<http://www.w3id.org/ecsel-dr-PMV#BPFlow> a rdfs:Class ;
  rdfs:label "Business Process Flow" ;
  rdfs:comment """An EPC describes a Business Process Flow, which is a sequence of required tasks to create specified outputs using defined inputs.
A Business Process Flow is a sequence of required tasks to create specified outputs using defined inputs.""" .

<http://www.w3id.org/ecsel-dr-PMV#hasSuperior> a rdf:Property ;
  rdfs:label "hasSuperior" ;
  rdfs:comment "EPCs have value-added chain diagrams as superior. The connector is used to represent the hierarchical order." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#BPFlow> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#VACD> .

<http://www.w3id.org/ecsel-dr-PMV#isSubFlowOf> a rdf:Property ;
  rdfs:label "isSubFlowOf" ;
  rdfs:comment "EPCs can have other EPCs as superiors. The connector is used to represent the hierarchical order." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#BPFlow> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Task> .

<http://www.w3id.org/ecsel-dr-PMV#hasPreviousModel> a rdf:Property ;
  rdfs:label "hasPreviousModel" ;
  rdfs:comment "An EPC can have another EPC previous to itself and is dependent on its results. The connector is used to represent the chronological order in a VACD." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#BPFlow> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#BPFlow> .

<http://www.w3id.org/ecsel-dr-PMV#hasNextModel> a rdf:Property ;
  rdfs:label "hasNextModel" ;
  rdfs:comment "An EPC can have another EPC following which is dependent on the result. The connector is used to represent the chronological order in a VACD." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#BPFlow> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#BPFlow> .

<http://www.w3id.org/ecsel-dr-AH#Tablet_computer> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Device> .

<http://www.w3id.org/ecsel-dr-AT#SupplyChainSimulationSystem> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Simulation-System> .

<http://www.w3id.org/ecsel-dr-PWR#Platform> a rdfs:Class ;
  rdfs:comment """An Entity to which other Entities can be attached - particularly semiconductor products and other platforms.

Example: A post might act as the platform, a body might act as a platform for an attached device.""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Physical_Object> .

<http://www.w3id.org/ecsel-dr-PWR#in_deployment> a rdf:Property ;
  rdfs:label "in deployment" ;
  rdfs:comment "Relation between a Platform and a Deployment, recording that the object was used as a platform for a system/ a device (sensor/power converter) for a particular deployment: as in this PhysicalObject is acting as a Platform inDeployment Deployment." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Platform> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Deployment> .

<http://www.w3id.org/ecsel-dr-AT#DataLanguage_XML-based> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L3_KnowledgeRepresentation> .

<http://www.w3id.org/ecsel-dr-PWR#Control_Method> a rdfs:Class ;
  rdfs:label "Control Method" ;
  rdfs:comment "It is the method used to turn on, turn off , increaseing, and decreasing output current/voltage." .

<http://www.w3id.org/ecsel-dr-PWR#Utilities> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#IndutrialSector> .

<http://www.w3id.org/ecsel-dr-AT#CPF8_CC-Link> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3id.org/ecsel-dr-AT#CPF3_6_Profinet_IO_ClassC> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#CPF3_Profibus_ProfiNet> .

<http://www.w3id.org/ecsel-dr-PWR#TheDeviceOutput> a rdfs:Class ;
  rdfs:label "SiC MOSFET Output" ;
  rdfs:comment "the device output is a piece of information (value), the value itself being represented by an The device function value." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Information_Object> .

<http://www.w3id.org/ecsel-dr-PWR#is_produced_by> a rdf:Property ;
  rdfs:label "is produced by" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#TheDeviceOutput> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Infineon_Device> .

<http://www.w3id.org/ecsel-dr-AT#WLAN_802_11> a rdfs:Class ;
  rdfs:comment """Collection of technologies defined in several sub-standards of IEEE 802.11: 
a, b, g, n, ac, 
They differ in the frequency band (2,4 GHz or 5 GHz), the data transmission rate and several specific methods."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> .

<http://www.w3id.org/ecsel-dr-AT#DNS-SD> a rdfs:Class ;
  rdfs:comment """Security issues
Because mDNS operates under a different trust model than unicast DNS—trusting the entire network rather than a designated DNS server, it is vulnerable to spoofing attacks by any system within the multicast IP range. Like SNMP and many other network management protocols, it can also be used by attackers to quickly gain detailed knowledge of the network and its machines.[28] Because of this, applications should still authenticate and encrypt traffic to remote hosts (e.g. via RSA, SSH, etc.) after discovering and resolving them through DNS-SD/mDNS.""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-PWR#Blocking_Voltage> a rdfs:Class ;
  rdfs:label "Break Down/Blocking Voltage" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Property> .

<http://www.w3id.org/ecsel-dr-AT#EDIFACT_DELFOR> a rdfs:Class ;
  rdfs:label "Delivery Forecast"@en ;
  rdfs:comment "EDIFACT message for delivery advises. May contain mandatory parts (delivery advises which are seen by the customer as mandatory, i.e. \"fixed\" orders) as well as non-mandatory parts (which are forecasts to deliveries)."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#EDIFACT-Specification> .

<http://www.w3id.org/ecsel-dr-PWR#On-State_Voltage> a rdfs:Class ;
  rdfs:label "On-State Voltage" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Property> .

<http://www.w3id.org/ecsel-dr-PWR#has_A_Voltage> a rdf:Property ;
  rdfs:label "has A Voltage" ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Negative_(-)> .

<http://www.w3id.org/ecsel-dr-PWR#has_a_Voltage_Equals_or_Greater_Than> a rdf:Property ;
  rdfs:label "has a Voltage Equals or Greater Than" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#On-State_Voltage> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Threshold_Voltage> .

<http://www.w3id.org/ecsel-dr-AT#TokenRing> a rdfs:Class ;
  rdfs:comment """Token Ring is a networking technology for computer networks, specified in the IEEE 802.5 specification. It defines cable types and signaling for the physical layer, packet formats, and media access control (MAC) / link layer protocols of the OSI model. It is one of the two implementations of the token passing method.
The token-ring technology was largely replaced by the various Ethernet variants and is hardly used today in LAN new installations.
Token Ring can be used for Layer 1 and 2 in a TCP/IP protocol stack or as part of the Network Layer in the AppleTalk-Protocol stack (TokenTalk)."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> .

<http://www.w3id.org/ecsel-dr-PRIMA#ProjectTeamMember> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PRIMA#Role> .

<http://www.w3id.org/ecsel-dr-PWR#ElectronicEquipment,Instruments&Components> a rdfs:Class ;
  rdfs:label "ElectronicEquipment,Instruments&Components" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#TechnologyHardware&Equipment> .

<http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> a rdfs:Class ;
  rdfs:label "Motor Control and Drive Solution" ;
  rdfs:comment "A motor control and drive solution is a semiconductor solution which function is to drive and control a motor." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> .

<http://www.w3.org/ns/org#OrganizationalUnit> a rdfs:Class ;
  rdfs:label "Organizational Unit" ;
  rdfs:comment "An Organization such as a department or support unit which is part of some larger Organization and only has full recognition within the context of that Organization. In particular the unit would not be regarded as a legal entity in its own right." .

<http://www.w3id.org/ecsel-dr-AT#ARCNET> a rdfs:Class ;
  rdfs:comment """ARCNET (Attached Resource Computer Network) is a networking technology for local area networks (LANs). It defines cable types and signaling for the physical layer, and packet formats and media access control (MAC) / link layer protocols of the OSI model.

On December 1, 1977 ARCNET was first presented to the public, after the computer manufacturer Datapoint, who had developed this technique, in the same year, the installation of the first customer, the Chase Manhattan Bank in New York City, had completed. ARCNET was developed at the same time as Ethernet, but was held as a proprietary unique selling point for a number of years until Standard Microsystems Corporation took over the production of the corresponding controllers, reaching a release in 1982, and winning Novell as another partner in 1985. [1] For example, ARCNET is one of the foundations of BACnet.

ARCNET is physically constructed either as a classic 10BASE2 Ethernet as a bus or alternatively as a star or tree. [2] In the case of the bus variant, the switching components are simple tees, or star active or passive hubs, whereby active and passive hubs can be mixed as desired. In its original form, ARCNET was built with coaxial cables. During development, UTP and fiber were also specified. The coaxial cables do not conform to the 10BASE2 (Thin Ethernet) known type RG-58 (with a characteristic impedance of 50 ohms), but RG-62 with a characteristic impedance of 93 ohms. As a result, Arcnet's Ethernet adoption accelerated, as RG-62 cables matched IBM's SNA cabling and many of them could now rely on existing infrastructure.

Connection to the hub and the computer can be made in star form directly via BNC connector without the TBASE2 known T-piece to the hub, where no terminator is required because the termination of the cable is done directly in the hub or on the card. The bus variant is as wired with T-pieces as 10BASE2 and also has terminating resistors (93 ohms) at the cable end. The possible distances between nodes are 2.5 to 4 times 10BASE2.The access method of ARCNET is token passing on a token bus. Here, similar to the access procedure token ring, a token is sent on the journey, which is passed on in a fixed order. For token ring, this is dictated by the ring wiring. With ARCNET, the token is always sent to the entire network, and the next station in a logical order receives the token. The order is to be given to the cards as node ID (consecutive numbering) on ​​an externally accessible DIP switch; For current products, the ARCNET ID is communicated to the card via the software.

The access method of ARCNET is token passing on a token bus. Here, similar to the access procedure token ring, a token is sent on the journey, which is passed on in a fixed order. For token ring, this is dictated by the ring wiring. With ARCNET, the token is always sent to the entire network, and the next station in a logical order receives the token. The order is to be given to the cards as node ID (consecutive numbering) on an externally accessible DIP switch; For current products, the ARCNET ID is communicated to the card via the software.

The transfer rate is lower than Ethernet and Token Ring at 2.5 Mbps (20 Mbps using ARCNET-Plus cards). However, as with Token Ring, no collision slows down the speed of transmission - even at maximum network load - even higher speeds can be achieved with 2.5 Mbit than with 4 times faster Ethernet networks. The US network specialist Thomas Conrad in 1990 under the name \"TCNS\" a (unspecified) 100-Mbit version of the ARCNET with RG-62 and fiber optic cabling was presented that had all the advantages of ARCNET via Ethernet and Token Ring. Compaq dropped this system but after the acquisition of Thomas Conrad in favor of the meanwhile much cheaper become Fast Ethernet. In the early years, however, ARCNET was much less expensive than Ethernet or Token Ring in terms of components, cabling and maintenance costs.

A special feature were the ARCNET cards. ARCNET was an open design and in particular had a standardized map API, so that even cards from different manufacturers could work with a single driver. This practical simplification was later also used by many manufacturers with the widespread NE2000-compatible Ethernet cards. Even there, this reduced the development costs and soon led to very inexpensive cards. Today's ARCNET cards, however, require vendor-specific drivers.

An ARCNET network with a hub in the middle gave a good example in explaining network topologies: the wiring was a star, electrically the network was a bus and logically a ring. ARCNET has become less important with the proliferation of Fast Ethernet in local area networks, but continues to be used in areas such as industrial manufacturing, printing, wind energy, but also medical and logistics."""@en , """ARCNET (Attached Resource Computer Network) ist eine Vernetzungstechnologie für lokale Netzwerke (LANs). Sie definiert Kabeltypen und Signalisierung für die Bitübertragungsschicht (physische Schicht) und Paketformate und Protokolle für die Medienzugriffskontrolle (Media Access Control, MAC)/Sicherungsschicht des OSI-Modells.

Am 1. Dezember 1977 wurde ARCNET erstmals der Öffentlichkeit vorgestellt, nachdem der Computerhersteller Datapoint, der diese Technik entwickelt hatte, im selben Jahr die Installation beim ersten Kunden, der Chase Manhattan Bank in New York City, abgeschlossen hatte.[1] ARCNET wurde zur gleichen Zeit wie Ethernet entwickelt, aber einige Jahre als proprietäres Alleinstellungsmerkmal gehalten, bis die Standard Microsystems Corporation die Produktion der entsprechenden Controller übernahm, im Jahr 1982 eine Freigabe erreichte, und im Jahr 1985 als weiteren Partner Novell gewann.[1] Inzwischen ist ARCNET beispielsweise eine der Grundlagen von BACnet.

ARCNET wird physisch entweder wie ein klassisches 10BASE2-Ethernet als Bus oder alternativ als Stern bzw. Baum aufgebaut.[2] Die Vermittlungskomponenten sind bei der Bus-Variante einfache T-Stücke, oder beim Stern aktive oder passive Hubs, wobei aktive und passive Hubs beliebig gemischt werden können. In der ursprünglichen Form wurde ARCNET mit Koaxialkabeln aufgebaut. Im Lauf der Entwicklung wurden auch UTP und Glasfaser spezifiziert. Die Koaxialkabel entsprechen nicht dem von 10BASE2 (Thin Ethernet) bekannten Typ RG-58 (mit einem Wellenwiderstand von 50 Ohm), sondern RG-62 mit einem Wellenwiderstand von 93 Ohm. Dieser Umstand sorgte zeitweilig für eine schnellere Verbreitung von Arcnet gegenüber Ethernet, da die RG-62-Kabel IBMs SNA-Verkabelung entsprachen und darum vielerorts bereits auf eine bestehende Infrastruktur zurückgegriffen werden konnte.

Der Anschluss an Hub und Computer erfolgt wahlweise in Sternform direkt per BNC-Steckverbinder ohne das durch 10BASE2 bekannte T-Stück an den Hub, wobei kein Abschlusswiderstand erforderlich ist, da die Terminierung der Kabel direkt im Hub bzw. auf der Karte erfolgt. Die Bus-Variante ist genauso mit T-Stücken verkabelt wie 10BASE2 und hat auch Abschlusswiderstände (93 Ohm) am Kabelende. Die möglichen Abstände zwischen Knotenpunkten liegen beim 2,5- bis 4-fachen von 10BASE2.

Das Zugriffsverfahren von ARCNET ist Token Passing auf einem Token Bus. Hier wird, ähnlich wie beim Zugriffsverfahren Token Ring, ein Token auf die Reise geschickt, das in einer festgelegten Reihenfolge weitergereicht wird. Bei Token Ring ist dies durch die Ring-Verkabelung vorgegeben. Bei ARCNET wird das Token immer in das gesamte Netzwerk gesendet, und die nächste Station in einer logischen Reihenfolge nimmt das Token auf. Die Reihenfolge ist den Karten als Knoten-ID (fortlaufende Nummerierung) auf einem außen zugänglichen DIP-Switch mitzugeben; bei aktuellen Produkten wird die ARCNET-ID über die Software der Karte mitgeteilt.

Die Übertragungsrate liegt mit 2,5 Mbit/s (20 Mbit/s durch Einsatz von ARCNET-Plus Karten) niedriger als Ethernet und Token Ring. Da aber, wie bei Token Ring, keine Kollision das Tempo der Übertragung bremst, ist - gerade bei höchster Netzlast - schon mit 2,5 Mbit eine höhere Geschwindigkeit zu erreichen als bei 4-mal schnelleren Ethernet-Netzwerken. Vom US-Netzwerkspezialisten Thomas Conrad wurde 1990 unter dem Namen „TCNS“ auch eine (nicht spezifizierte) 100-Mbit-Variante des ARCNET mit RG-62 und Glasfaserverkabelung vorgestellt, die über alle Vorteile von ARCNET über Ethernet und Token Ring verfügte. Compaq ließ dieses System aber nach der Übernahme von Thomas Conrad zu Gunsten des zwischenzeitlich deutlich billiger gewordenen Fast Ethernet fallen. In den Anfangsjahren war ARCNET hingegen sowohl bei den Komponenten, als auch bei der Verkabelung und den Wartungskosten wesentlich preisgünstiger als Ethernet oder Token Ring.

Eine Besonderheit waren auch die ARCNET-Karten. ARCNET war ein offenes Design und verfügte insbesondere auch über ein standardisiertes Karten-API, so dass auch Karten unterschiedlicher Hersteller mit einem einheitlichen Treiber arbeiten konnten. Diese praktische Vereinfachung nutzten später auch viele Hersteller mit den weit verbreiteten NE2000-kompatiblen Ethernet-Karten. Auch dort reduzierte dies die Entwicklungskosten und führte schon bald zu sehr preiswerten Karten. Heutige ARCNET-Karten benötigen jedoch herstellerspezifische Treiber.

Ein ARCNET-Netzwerk mit einem Hub in der Mitte gab ein gutes Beispiel bei der Erklärung von Netz-Topologien ab: die Verkabelung bildete einen Stern, elektrisch war das Netz ein Bus und logisch ein Ring. ARCNET hat mit der weiteren Verbreitung von Fast Ethernet in lokalen Netzwerken an Bedeutung verloren, wird aber weiterhin in Bereichen wie industrielle Fertigung, Drucktechnik, Windenergietechnik, aber auch Medizintechnik und Logistik eingesetzt."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> .

<http://www.w3id.org/ecsel-dr-SO#Process> a rdfs:Class ;
  rdfs:comment "Sequence of interdependent and linked procedures which, at every stage, consume one or more resources (employee time, energy, machines, money) to convert inputs (data, material, parts, etc.) into outputs. These outputs then serve as inputs for the next stage until a known goal or end result is reached."@en .

<http://www.w3id.org/ecsel-dr-SO#Time_Constraints> a rdfs:Class ;
  rdfs:comment "As single operations can set the lot to a time-critical state, time constraints can ensure that the operation setting it to an uncritical state is not delayed. Also the other case where certain time has to be spent between two operations can be covered with this master entity. (workflow deswcriptive master entities)"@en .

<http://www.w3id.org/ecsel-dr-SO#Dry_Etching> a rdfs:Class ;
  rdfs:comment "Dry etching is a process whereby etching is accomplished by a reactive gas as opposed to a liquid. Dry etching techniques include plasma etch, reactive ion etch, magnetically enhanced reactive ion etch, inductively coupled plasma, electron spin resonance, etc."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Workshop> .

<http://www.w3.org/ns/sosa/sampling/SampleRelationship> a rdfs:Class ;
  rdfs:comment "Members of this class represent a relationship between a sample and another." .

<http://www.w3.org/ns/sosa/sampling/natureOfRelationship> a rdf:Property ;
  rdfs:label "nature of relationship" ;
  rdfs:comment "Links a SampleRelationship to an indication of the nature of the relationship." ;
  rdfs:domain <http://www.w3.org/ns/sosa/sampling/SampleRelationship> ;
  rdfs:range <http://www.w3.org/ns/sosa/sampling/SampleRelationship> .

<http://www.w3.org/ns/sosa/sampling/relatedSample> a rdf:Property ;
  rdfs:label "related sample" ;
  rdfs:comment "Links a SampleRelationship to the related Sample." ;
  rdfs:domain <http://www.w3.org/ns/sosa/sampling/SampleRelationship> ;
  rdfs:range <http://www.w3.org/ns/sosa/Sample> .

<http://www.w3id.org/ecsel-dr-AT#SPARQL_Language> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#DataLanguage_SemanticWebStackBased> .

<http://www.w3id.org/ecsel-dr-PWR#On-State_Resistance> a rdfs:Class ;
  rdfs:label "On-State Resistance" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Property> .

<http://www.w3id.org/ecsel-dr-AT#MaterialFlowPlanning> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#PLM1_Module> .

<http://www.w3id.org/ecsel-dr-AH#AH_AuthorizationControlService_SD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_service_SD> .

<http://www.w3id.org/ecsel-dr-AT#DataTransmissionUnit> a rdfs:Class ;
  rdfs:comment "Units of technical data transfer. Shows the different data groupings at the  ISO/OSI communication layers, e.g. bits on the physical link layer and packets at the network layer."@en .

<http://www.w3id.org/ecsel-dr-PROD#FinishedProduct> a rdfs:Class ;
  rdfs:comment "end result of the manufacturing process" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PROD#Product> .

<http://www.w3id.org/ecsel-dr-PROD#finishedProductNumber> a rdf:Property ;
  rdfs:comment "finishedProductNumber is the unique identifier for a FinishedProduct" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#FinishedProduct> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PROD#alternateProduct> a rdf:Property ;
  rdfs:comment "all FinishedProducts that share the same SalesProductNumber" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#FinishedProduct> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PROD#FinishedProduct> .

<http://www.w3id.org/ecsel-dr-PROD#deliveryLeadTime> a rdf:Property ;
  rdfs:comment """The typical delay between the receipt of the order and the goods either leaving the warehouse or being prepared for pickup, in case the delivery method is on site pickup.
http://schema.org/deliveryLeadTime
""" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#FinishedProduct> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-PROD#hasSKU_SM> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#FinishedProduct> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PROD#SKU> .

<http://www.w3id.org/ecsel-dr-AH#AH_system_documentation> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#System_documentation> .

<http://www.w3id.org/ecsel-dr-AH#Programmable_Logic_Controller> a rdfs:Class ;
  rdfs:label "PLC"@en , "SPS"@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Device> .

<http://www.w3.org/ns/ssn/systems/Sensitivity> a rdfs:Class ;
  rdfs:label "Sensitivity" ;
  rdfs:comment "As a Sensor Property: Sensitivity is the quotient of the change in a Result of Observations and the corresponding change in a value of an ObservableProperty being observed, under the defined Conditions." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/systems/SystemProperty> .

<http://www.w3id.org/ecsel-dr-AT#W3C_L5_DataSemantics> a rdfs:Class .

<http://www.w3.org/ns/ssn/systems/DetectionLimit> a rdfs:Class ;
  rdfs:label "Detection Limit" ;
  rdfs:comment "An observed value for which the probability of falsely claiming the absence of a component in a material is beta, given a probability alpha of falsely claiming its presence." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/systems/SystemProperty> .

<http://www.w3id.org/ecsel-dr-SCP#Forecast> a rdfs:Class ;
  rdfs:label "Forecast"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#OperationalDemand> .

<http://www.w3id.org/ecsel-dr-PWR#Height> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#GeometricDimension> .

<http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitecture> a rdfs:Class ;
  rdfs:label "Service Oriented Architecture Protocols"@de .

<http://www.w3id.org/ecsel-dr-PMV#ComputerHardware> a rdfs:Class ;
  rdfs:label "Computer Hardware" ;
  rdfs:comment "Physical equipment that makes up a computer system, such as circuit boards, keyboard and mouse, monitor, printer, power supply, storage devices. Contrasts with software." ;
  rdfs:subClassOf <http://purl.org/dc/terms/PhysicalResource> .

<http://www.w3id.org/ecsel-dr-PMV#isUsedBy> a rdf:Property ;
  rdfs:label "isUsedBy" ;
  rdfs:comment "An external resource is used by a function in a process flow." ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Function> .

<http://www.w3id.org/ecsel-dr-PMV#SplitRule> a rdfs:Class ;
  rdfs:label "Split Rule" ;
  rdfs:comment "Rule element that splits the control flow into several branches. Has one incoming path and several (at least two) outgoing paths." .

<http://www.w3id.org/ecsel-dr-PMV#Subprocess> a rdfs:Class ;
  rdfs:label "Subprocess" ;
  rdfs:comment "A grouping of related tasks that create an output within the larger objective of the subprocess. E.g. Create and Maintain Purchase Orders" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#StructuralFunctionObject> .

<http://www.w3.org/2006/time#TemporalUnit> a rdfs:Class ;
  rdfs:label "Temporal unit"@en ;
  rdfs:comment "A standard duration, which provides a scale factor for a time extent, or the granularity or precision for a time position."@en ;
  rdfs:subClassOf <http://www.w3.org/2006/time#TemporalDuration> .

<http://www.w3id.org/ecsel-dr-AH#Illumination_device> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Constrained_device> .

<http://www.w3id.org/ecsel-dr-SCP#WIP> a rdfs:Class ;
  rdfs:label "WIP"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#Stocks> .

<http://www.w3id.org/ecsel-dr-PWR#Voltage-Controlled> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Control_Method> .

<http://www.w3id.org/ecsel-dr-AH#AH_application_service> a rdfs:Class ;
  rdfs:comment "Application services – they are application specific and are implemented by application systems along with functionalities (to match requirements of an application)"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_service> .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer2_DistributedControl_SCADA> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer> .

<http://www.w3id.org/ecsel-dr-AT#StationaryRobot> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ActuatorDevice> .

<http://www.w3id.org/ecsel-dr-AH#AH_SessionManagementService_SD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service_SD> .

<http://www.w3id.org/ecsel-dr-AT#CPF11_TCNet> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3id.org/ecsel-dr-AT#ToolingMachine> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ActuatorDevice> .

<http://www.w3id.org/ecsel-dr-AT#MIS> a rdfs:Class ;
  rdfs:label "Management Information System"@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3.org/2006/time#TRS> a rdfs:Class ;
  rdfs:label "Temporal Reference System"@en ;
  rdfs:comment """A temporal reference system, such as a temporal coordinate system (with an origin, direction, and scale), a calendar-clock combination, or a (possibly hierarchical) ordinal system. 

This is a stub class, representing the set of all temporal reference systems."""@en .

<http://www.w3id.org/ecsel-dr-AT#SoA_ServiceBroker> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitecture_FunctionPattern> .

<http://www.w3id.org/ecsel-dr-AT#MessageBroker-System> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-AT#ISA-Standard> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Standard> .

<http://www.w3.org/ns/ssn/systems/MaintenanceSchedule> a rdfs:Class ;
  rdfs:label "Maintenance Schdule" ;
  rdfs:comment "Schedule of maintenance for a System in the specified Conditions." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/systems/OperatingProperty> .

<http://www.w3.org/2006/time#GeneralDateTimeDescription> a rdfs:Class ;
  rdfs:label "Generalized date-time description"@en ;
  rdfs:comment "Description of date and time structured with separate values for the various elements of a calendar-clock system"@en ;
  rdfs:subClassOf <http://www.w3.org/2006/time#TemporalPosition> .

<http://www.w3id.org/ecsel-dr-AH#InformationModel> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AH#isInformationModelOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#InformationModel> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#Service> .

<http://www.w3id.org/ecsel-dr-PRIMA#WorkPackage> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PRIMA#isWorkPackageOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PRIMA#WorkPackage> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PWR#Enhancement> a rdfs:Class ;
  rdfs:label "Enhancement Mode" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Operation_Mode> .

<http://www.w3id.org/ecsel-dr-PWR#The_Enhansment_Mode_Is_Working_As> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Enhancement> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#Switcher> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-PWR#Acting_As> .

<http://www.w3id.org/ecsel-dr-SCP#TargetAllocation> a rdfs:Class ;
  rdfs:label "TargetAllocation"@iri-based .

<http://www.w3id.org/ecsel-dr-SCP#figureOutFrom> a rdf:Property ;
  rdfs:label "figureOutFrom"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#TargetAllocation> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#AATP> .

<http://www.w3id.org/ecsel-dr-AH#Constrained_device> a rdfs:Class ;
  rdfs:comment """A constrained device is a device in the sense of an service-oriented architecture that is restricted in terms of processing capabilities (speed, complexity of operations), memory and power supply. 
The concept constrained device was introduced in the context of the Internet of Things (IoT) and refers for example to sensor devices, location devices, switches etc. which are connected by low-power wireless communication technologies like BLE, ZigBee, Z-Wave etc., have a battery on board that should last for two to three years and which are (very) small in physical size."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Device> .

<http://www.w3id.org/ecsel-dr-PWR#Healthcare> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#IndutrialSector> .

<http://www.w3id.org/ecsel-dr-PWR#SwitchingValue> a rdfs:Class ;
  rdfs:label "SwitchingValue" ;
  rdfs:comment """The value of the result of the method (procedures) of the device function. The result is an information object that encodes some value for a feature. 
For example:
-If we consider the observation is the method used for sensing of the sensors, then the observation has a result which is the output of the sensor,
-If -If we consider the amplification is the method used for boosting of the power converter, then the amplification has a result which is the output of the  power converter,""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Abstract> .

<http://www.w3id.org/ecsel-dr-PROD#FPOS> a rdfs:Class ;
  rdfs:comment "Fabrication Position: product & manufacturing route; where it is produced - coarse" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PROD#PlanningElement> .

<http://www.w3id.org/ecsel-dr-PROD#hasDREP> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#FPOS> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PROD#DREP> .

<http://www.w3id.org/ecsel-dr-PROD#CPNSpec> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PROD#customerPartNumber> a rdf:Property ;
  rdfs:comment "product identifier used by the customer to identify one IFX product" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#CPNSpec> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PROD#customer> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PROD#CPNSpec> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PROD#Organization> .

<http://www.w3.org/ns/ssn/systems/SystemLifetime> a rdfs:Class ;
  rdfs:label "System Lifetime" ;
  rdfs:comment "The System continues to operate as defined using SystemCapability. If, however, the SurvivalRange is violated, the System is 'damaged' and SystemCapability specifications may no longer hold." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/systems/SurvivalProperty> .

<http://www.w3id.org/ecsel-dr-PWR#Documents> a rdfs:Class ;
  rdfs:comment "The document class presents those things which are, broadly conceived, \"documents''. It should contain the manuals and the data sheet of the devices." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Information_Object> .

<http://www.w3id.org/ecsel-dr-SCP#Orders> a rdfs:Class ;
  rdfs:label "Orders"@iri-based .

<http://www.w3id.org/ecsel-dr-PWR#Operation_Mode> a rdfs:Class ;
  rdfs:label "Operation Mode" .

<http://www.w3id.org/ecsel-dr-AT#Bridge> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#CommunicationDevice> .

<http://www.w3id.org/ecsel-dr-RAMI40#Sensor> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-SO#Shift> a rdfs:Class ;
  rdfs:comment "Each workshop has a certain technical and operational workforce organized in shifts described in the “Shift” entity."@en .

<http://www.w3id.org/ecsel-dr-SO#hasWorkforce> a rdf:Property ;
  rdfs:comment "Shift: Overall number of operational workers assigned to the shift"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Shift> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-AT#CPF13_EthernetPowerlink> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3id.org/ecsel-dr-PWR#Sensors> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Semiconductors> .

<http://www.w3id.org/ecsel-dr-PMV#IFXProcessFramework> a rdfs:Class ;
  rdfs:label "Infineon Process Framework" ;
  rdfs:comment "IPF is the structured overview of all IFX Core and Enabler Processes. It contains 4 Core Processes and 6 Enabler Processes." .

<http://www.w3id.org/ecsel-dr-AH#AH_InterCloudNegotiationsService_SD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service_SD> .

<http://www.w3id.org/ecsel-dr-SCP#PrioritizedOrders> a rdfs:Class ;
  rdfs:label "PrioritizedOrders"@iri-based .

<http://www.w3id.org/ecsel-dr-SCP#hasInputin> a rdf:Property ;
  rdfs:label "hasInputin"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#PrioritizedOrders> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#OperationalDemand> .

<http://www.w3id.org/ecsel-dr-AT#XMPP> a rdfs:Class ;
  rdfs:label "Extensible Messaging and Presence Protocol"@en ;
  rdfs:comment """XMPP (Extensible Messaging and Presence Protocol)
\"An open technology for real-time communication, which powers a wide range of applications including instant messaging, presence, multi-party chat, voice and video calls, collaboration, lightweight middleware, content syndication, and generalized routing of XML data.\"
(https://www.postscapes.com/internet-of-things-protocols/)"""@en , "Supported by the XMPP community. Used by large companies for Push notifications, instant messaging and chat. (Delsing)"@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-AH#AH_OrchestrationSystem_SysDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_system_SySDD> .

<http://www.w3id.org/ecsel-dr-AH#AH_OrchestrationService_SD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_service_SD> .

<http://www.w3id.org/ecsel-dr-OM#OrderChangeRequest> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-OM#hasPartialCancelQuantityQuantityBuyer> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderChangeRequest> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#hasPONumberOCR> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderChangeRequest> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#hasSupplierComments> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderChangeRequest> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-OM#hasLineIDOCR> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderChangeRequest> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#hasPartialCancelQuantitySupplier> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderChangeRequest> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#requiresUserAction> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderChangeRequest> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#UserAction> .

<http://www.w3id.org/ecsel-dr-OM#requiresAction> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderChangeRequest> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#Action> .

<http://www.w3id.org/ecsel-dr-OM#hasOpenQuantityOCR> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderChangeRequest> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#hasPromisedDockDate> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderChangeRequest> ;
  rdfs:range xsd:dateTime .

<http://www.w3id.org/ecsel-dr-OM#hasRequestedDockDate> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderChangeRequest> ;
  rdfs:range xsd:dateTime .

<http://www.w3id.org/ecsel-dr-OM#hasSupplierReasonCode> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderChangeRequest> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-OM#hasCurrentDockDate> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderChangeRequest> ;
  rdfs:range xsd:dateTime .

<http://www.w3id.org/ecsel-dr-OM#isReconciledOrderLineItem> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderChangeRequest> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#OrderLineItem> .

<http://www.w3id.org/ecsel-dr-AH#Gateway> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Device> .

<http://www.w3id.org/ecsel-dr-OOSMP#Product> a rdfs:Class ;
  rdfs:label "Product" ;
  rdfs:comment "A product is something that is produced with effort (e.g. by mechanical or industrial processes) and sold to a customer. A product is either tangible (physical product) or intangible (service)." .

<http://www.w3id.org/ecsel-dr-AT#HTML> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L2_DataSyntax> .

<http://www.w3id.org/ecsel-dr-AH#Smartphone> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Device> .

<http://www.w3id.org/ecsel-dr-PMV#BPLandscape> a rdfs:Class ;
  rdfs:label "Business Process Landscape" ;
  rdfs:comment "A Business Process Landscape is a detailed overview of a specific Core- or Enabler Process." .

<http://www.w3id.org/ecsel-dr-OOSMP#_3DMagneticSensor> a rdfs:Class ;
  rdfs:label "3D Magnetic Sensor" ;
  rdfs:comment """Capable of measuring 3D, linear and rotational movement. The sensor realizes an accurate three-dimensional sensing with extremely low power consumption. Capable of detecting the magnetic field in the x, y, and z-direction, the sensor is ideally suited for the measurement
of linear, rotation or 3 dimensional movements.""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#MagneticPositionSensor> .

<http://www.w3id.org/ecsel-dr-AH#AH_AuthorizationSystem_WADL> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#System_WebApplicationDescription_WADL> .

<http://www.w3id.org/ecsel-dr-PROD#NotReleasedProduct> a rdfs:Class ;
  rdfs:comment "NotReleasedProduct are those finishedProductNumbers that are not allowed to be shipped to any customer" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PROD#Product> .

<http://www.w3id.org/ecsel-dr-AT#STOMP> a rdfs:Class ;
  rdfs:label "Streaming Text Oriented Message Protocol"@en ;
  rdfs:comment """Simple (or Streaming) Text Oriented Message Protocol (STOMP), formerly known as TTMP, is a simple text-based protocol, designed for working with message-oriented middleware (MOM). It provides an interoperable wire format that allows STOMP clients to talk with any message broker supporting the protocol. It is thus language-agnostic, meaning a broker developed for one programming language or platform can receive communications from client software developed in another language.

Overview
The protocol is broadly similar to HTTP, and works over TCP using the following commands:
CONNECT
SEND
SUBSCRIBE
UNSUBSCRIBE
BEGIN
COMMIT
ABORT
ACK
NACK
DISCONNECT

Communication between client and server is through a \"frame\" consisting of a number of lines. The first line contains the command, followed by headers in the form <key>: <value> (one per line), followed by a blank line and then the body content, ending in a null character. Communication between server and client is through a MESSAGE, RECEIPT or ERROR frame with a similar format of headers and body content.

Implementations
These are some MOM products that support STOMP:
Apache ActiveMQ, also known as Fuse Message Broker
HornetQ
Net::STOMP::Client (an open source client implementation in Perl)
ocamlmq (A lightweight STOMP message broker, written in OCaml)
Open Message Queue (OpenMQ)
POE::Component::MessageQueue (a server implementation in Perl)
RabbitMQ (message broker, has support for STOMP)
Ruby server, also known as stompserver
stomp.erl (an open source client implementation in Erlang)
syslog-ng through its STOMP destination plugin
Stomp.py (an open source client implementation in Python)
tStomp (an open source client implementation in Tcl)
STOMP Implementation in Spring Framework
A list of implementations is also maintained on the STOMP web site."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-AT#EDIFACT_DESADV> a rdfs:Class ;
  rdfs:label "Despatch Advice"@de ;
  rdfs:comment "EDIFACT message for despatch advise (delivery announcement)"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#EDIFACT-Specification> .

<http://www.w3id.org/ecsel-dr-OOSMP#HallSwitch> a rdfs:Class ;
  rdfs:label "Hall Switch" ;
  rdfs:comment "The sensor provides an easy-to-use and cost effective solution for position sensing applications, requiring high temperature stability of the magnetic threshold. Today the market demands smaller and more energy efficient Hall switches. To satisfy the needs of more compact designs and environmental legislation  with a high quality product is very difficult. Infineon offers attractive pricing, reliable supply, benchmark quality and excellent design-in support to contribute to the customers success." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#MagneticPositionSensor> .

<http://www.w3id.org/ecsel-dr-AT#RosettaNet-Specification> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#EDI_Specification> .

<http://www.w3id.org/ecsel-dr-SCP#OpenOrderBook> a rdfs:Class ;
  rdfs:label "OpenOrderBook"@iri-based .

<http://www.w3id.org/ecsel-dr-SCP#ConfirmedDate> a rdf:Property ;
  rdfs:label "ConfirmedDate"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#OpenOrderBook> ;
  rdfs:range xsd:dateTime .

<http://www.w3id.org/ecsel-dr-SCP#resultIn> a rdf:Property ;
  rdfs:label "resultIn"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#OpenOrderBook> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#OrdersReschedule> .

<http://www.w3id.org/ecsel-dr-SCP#ConfirmedQuantity> a rdf:Property ;
  rdfs:label "ConfirmedQuantity"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#OpenOrderBook> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-PMV#ProcessDiagram> a rdfs:Class ;
  rdfs:label "Process Diagram" ;
  rdfs:comment "The first level of process decomposition that is comprised of subprocesses that depict a business objective." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#Model> .

<http://www.w3.org/ns/org#Organization> a rdfs:Class ;
  rdfs:label "Organization" ;
  rdfs:comment "Represents a collection of people organized together into a community or other social, commercial or political structure. The group has some common purpose or reason for existence which goes beyond the set of people belonging to it and can act as an Agent. Organizations are often decomposed into hierarchical structures." .

<http://www.w3.org/ns/org#hasUnit> a rdf:Property ;
  rdfs:domain <http://www.w3.org/ns/org#Organization> ;
  rdfs:range <http://www.w3.org/ns/org#OrganizationalUnit> .

<http://www.w3id.org/ecsel-dr-SCP#CapacityBottleneck> a rdfs:Class ;
  rdfs:label "CapacityBottleneck"@iri-based .

<http://www.w3id.org/ecsel-dr-SCP#match> a rdf:Property ;
  rdfs:label "match"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#CapacityBottleneck> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#SupplyDemandMatch> .

<http://www.w3id.org/ecsel-dr-SCP#DB> a rdfs:Class ;
  rdfs:label "DB"@iri-based ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SCP#Stocks> .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_CrossLayerCommunication> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-SO#Production_Requests> a rdfs:Class ;
  rdfs:comment "Production requests definte what the facilities need to produce when and in what quantity."@en .

<http://www.w3id.org/ecsel-dr-AT#DDS> a rdfs:Class ;
  rdfs:label "Data-Distribution Service for Real-Time Systems"@en ;
  rdfs:comment """The Data Distribution Service (DDS™) is a middleware protocol and API standard for data-centric connectivity from the Object Management Group® (OMG®). It integrates the components of a system together, providing low-latency data connectivity, extreme reliability, and a scalable architecture that business and mission-critical Internet of Things (IoT) applications need.
In a distributed system, middleware is the software layer that lies between the operating system and applications. It enables the various components of a system to more easily communicate and share data. It simplifies the development of distributed systems by letting software developers focus on the specific purpose of their applications rather than the mechanics of passing information between applications and systems.
The DDS Middleware is a software layer that abstracts the Application from the details of the operating system, network transport, and low-level data formats. The same concepts and APIs are provided in different programming languages allowing applications to exchange information across of operating systems, languages, and processor architectures. Low-level details like data wire format, discovery, connections, reliability, protocols, Qos management, etc. are managed by the middleware."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-AH#AH_SessionManagementService_IDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service_IDD> .

<http://www.w3id.org/ecsel-dr-AH#Sensor_device> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Constrained_device> .

<http://www.w3.org/ns/sosa/Actuation> a rdfs:Class ;
  rdfs:label "Actuation"@en ;
  rdfs:comment "An Actuation carries out an (Actuation) Procedure to change the state of the world using an Actuator."@en .

<http://www.w3.org/ns/sosa/madeByActuator> a rdf:Property ;
  rdfs:label "made by actuator"@en ;
  rdfs:comment "Relation linking an Actuation to the Actuator that made that Actuation."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Actuation> ;
  rdfs:range <http://www.w3.org/ns/sosa/Actuator> .

<http://www.w3.org/ns/sosa/actsOnProperty> a rdf:Property ;
  rdfs:label "acts on property"@en ;
  rdfs:comment "Relation between an Actuation and the property of a FeatureOfInterest it is acting upon."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Actuation> ;
  rdfs:range <http://www.w3.org/ns/sosa/ActuatableProperty> .

<http://www.w3id.org/ecsel-dr-PMV#EnvironmentalData> a rdfs:Class ;
  rdfs:label "Environmental Data" ;
  rdfs:comment "Additional information to a process like work schedule, production plans, etc." ;
  rdfs:subClassOf <http://www.ontologydesignpatterns.org/cp/owl/informationrealization.owl#InformationObject> .

<http://www.w3id.org/ecsel-dr-PMV#isTransformedBy> a rdf:Property ;
  rdfs:label "isTransformedBy" ;
  rdfs:comment "Environmental data is transformed by a function in a process flow." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#EnvironmentalData> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Function> .

<http://www.w3id.org/ecsel-dr-PWR#Semiconductors> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Semiconductors&SemiconductorEquipment> .

<http://www.w3.org/ns/ssn/systems/OperatingProperty> a rdfs:Class ;
  rdfs:label "Operating Property" ;
  rdfs:comment "An identifiable characteristic that represents how the System operates under the specified Conditions. May describe power ranges, power sources, standard configurations, attachments and the like." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/Property> .

<http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution_DCLinkVoltage155> a rdfs:Class ;
  rdfs:label "Motor Control and Drive Solution With DC Link Voltage 155.0" ;
  rdfs:comment "Motor control and drive solution with DC link voltage equal to 155.0." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> .

<http://www.w3id.org/ecsel-dr-AT#PL_Phase2_Maintenance_Improvement> a rdfs:Class ;
  rdfs:comment """This phase also treats product types or product classes. 
It addresses the activities of continuous or periodic improvement of the product (type). 
Examples for such improvements are software updates (new versions) for the products, model upgrades, face lifts, design corrections and improvements etc. 
Initiation and data for such improvements often come from products of the type which are already in use (products in the field). This means, that this phase starts typically AFTER the start of the production phase (phase 3) and after the start of the usage and maintenance phase (phase 4), otherwise there would be no products in the field ..."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ProductLifecyclePhase> .

<http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system_SySD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_core_system_SySD> .

<http://www.w3id.org/ecsel-dr-OOSMP#ApplicationLevel2> a rdfs:Class ;
  rdfs:label "Application Level 2" ;
  rdfs:comment "The medium application level which can have several sub application levels (application level 3) and can be assigned to super application levels (application level 1)" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea> .

<http://www.w3id.org/ecsel-dr-OOSMP#subApplicationAreaOfApplicationLevel1> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationLevel2> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationLevel1> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#subApplicationAreaOf> .

<http://www.w3id.org/ecsel-dr-OOSMP#hasApplicationLevel3> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationLevel2> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#ApplicationLevel3> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#hasSubApplicationArea> .

<http://www.w3id.org/ecsel-dr-SCP#Confirmation> a rdfs:Class ;
  rdfs:label "Confirmation"@iri-based .

<http://www.w3id.org/ecsel-dr-AT#OPC_UA> a rdfs:Class ;
  rdfs:label "Open Platform Communications Unified Architecture"@en ;
  rdfs:comment "UA Security includes authentication and authorization, encryption and data integrity through signing. It is based on the web service security specifications. Web Services uses WS Secure Conversation directly and is thus compatible with .Net and other SOAP implementations. For the binary variant, the algorithms were adopted by WS Secure Conversation and also converted into a binary equivalent. This is now called UA Secure Conversation."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitecture> .

<http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> a rdfs:Class ;
  rdfs:label "Semiconductor Product" ;
  rdfs:comment "A semiconductor product is a physical product that is produced and sold within the semiconductor industry." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#PhysicalProduct> .

<http://www.w3id.org/ecsel-dr-AT#OASIS-Standard> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Standard> .

<http://www.w3id.org/ecsel-dr-AH#System-of-Systems_Design_Description_SoSDD> a rdfs:Class ;
  rdfs:comment "Is an high level view, describing how system of systems main functionalities have been technologically implemented, i.e. which technologies have been used and how it is physically implemented. The SoSDD refers to a number of SySDDs (which are the building blocks in the SySD) and as such indirectly to how the included systems are implemented. (Source: Arrowhead Framework Definitions V2.4)"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_system_of_systems_documentation_document> .

<http://www.w3id.org/ecsel-dr-AH#refersToSoSD> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#System-of-Systems_Design_Description_SoSDD> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#System-of-Systems_Description_SoSD> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#refersTo> .

<http://www.w3id.org/ecsel-dr-AH#refersToSySDD> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AH#System-of-Systems_Design_Description_SoSDD> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AH#System_Design_Description_SySDD> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-AH#refersTo> .

<http://www.w3id.org/ecsel-dr-AT#OSI_L4_TransportLayer> a rdfs:Class ;
  rdfs:label "Transport Layer"@en , "Transportschicht"@de ;
  rdfs:comment """Ensures that messages are delivered error-free, in sequence, and with no losses or duplications. 
Host-to-host flow control: Host refers to a device on which an application system runs which sends or receives a message. I.e., this layer is the lowest layer which cares for end-to-end communication in terms of devices. 
Topics: Message segmentation, Message acknowledgement, Message traffic control, Session multiplexing
Example protocols: TCP, SPX, UDP"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_DetailedLayer> .

<http://www.w3id.org/ecsel-dr-AT#BigDataAnalytics-System> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-AT#SECS_GEM> a rdfs:Class ;
  rdfs:label "SEMI Equipment Communications Standard / Generic Equipment Model"@en ;
  rdfs:comment """The SECS/GEM is the semiconductor's equipment interface protocol for equipment-to-host data communications. In an automated fab, the interface can start and stop equipment processing, collect measurement data, change variables and select recipes for products. The SECS (SEMI Equipment Communications Standard)/GEM (Generic Equipment Model) standards do all this in a defined way.

Developed by the SEMI (Semiconductor Equipment and Materials International) organization,[1] the standards define a common set of equipment behaviour and communications capabilities.

The Generic Model for Communications and Control Of Manufacturing Equipment (GEM) standard is maintained and published by the non-profit organization Semiconductor Equipment and Materials International (SEMI). Generally speaking, the SECS/GEM standard defines messages, state machines and scenarios to enable factory software to control and monitor manufacturing equipment. The GEM standard is formally designated and referred to as SEMI standard E30, but frequently simply referred to as the GEM or SECS/GEM standard. GEM intends \"to produce economic benefits for both device manufacturers and equipment suppliers...\" by defining \"... a common set of equipment behavior and communications capabilities that provide the functionality and flexibility to support the manufacturing automation programs of semiconductor device manufacturers\" [SEMI E30, 1.3]. GEM is a standard implementation of the SECS-II standard, SEMI standard E5. Many equipment in semiconductor (front end and back end), surface mount technology, electronics assembly, photovoltaic, flat panel display and other manufacturing industries worldwide provide a GEM/SECS interface on the manufacturing equipment so that the factory host software can communicate with the machine for monitoring and/or controlling purposes. Because the GEM standard was written with very few semiconductor-specific features, it can be applied to virtually any automated manufacturing equipment in any industry.

All GEM compliant manufacturing equipment share a consistent interface and certain consistent behavior. GEM equipment can communicate with a GEM capable host using either TCP/IP (using the HSMS standard, SEMI E37) or RS-232 based protocol (using the SECS-I standard, SEMI E4). Often both protocols are supported. Each equipment can be monitored and controlled using a common set of SECS-II messages specified by GEM.

There are many additional SEMI standards and factory specifications that reference the GEM standard its features. These additional standards are either industry-specific or equipment-type specific. Following are a few examples.

Source: https://en.wikipedia.org/wiki/SECS/GEM"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitecture> .

<http://www.w3id.org/ecsel-dr-AT#SoA_ServiceRepository> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitecture_FunctionPattern> .

<http://www.w3id.org/ecsel-dr-AH#AH_ServiceDiscoveryService_SD> a rdfs:Class ;
  rdfs:comment "Service Description (SD) of the Arrowhead mandatory core service Service Discovery Service which is provided by the mandatory core system Service Registry."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_service_SD> .

<http://www.w3id.org/ecsel-dr-AT#CPF3_3_Profinet_CBA> a rdfs:Class ;
  rdfs:comment """Profinet verwendet die folgenden Protokolle:

Ethernet: Nur Full-Duplex mit 100 MBit/s elektrisch (100BASE-TX) oder optisch (100BASE-FX) nach IEEE 802.3 sind als Geräteanschluss erlaubt. Autocrossover ist für alle Anschlüsse obligatorisch damit auf den Einsatz von gekreuzten Kabeln verzichtet werden kann. Aus IEEE 802.1Q wird das VLAN mit Priority Tagging verwendet. Alle Echtzeitdaten erhalten damit die größtmögliche Priorität 6 und werden darum mit einer minimalen Verzögerung von einem Switch weitergeleitet.

Das Profinet-Protokoll kann mit jedem Ethernet-Analysewerkzeug aufgezeichnet und dargestellt werden. Wireshark decodiert in der aktuellen Version auch die Profinet-Telegramme.

Das Media Redundancy Protocol (MRP) erlaubt den Aufbau einer redundanten, protokollunabhängigen Ringtopologie mit einer Umschaltzeit unter 50 ms. Für redundante Ringschaltungen ohne Zeitverzögerung im Fehlerfall muss das Media Redundancy Real-Time Protocol (MRRT) verwendet werden.

Das Link Layer Discovery Protocol (LLDP) ist mit zusätzlichen Parametern erweitert worden, so dass neben der Erkennung der Nachbarn auch die Laufzeit der Signale auf den Verbindungsleitungen mitgeteilt werden kann.

Internet: Für den Verbindungsaufbau und die azyklischen Dienste wird das Internet Protocol (IP) verwendet. Das Address Resolution Protocol (ARP) wird dazu mit der Erkennung von doppelten IP-Adressen erweitert. Für die Vergabe der IP-Adressen wird obligatorisch das Discovery and basic Configuration Protocol (DCP) eingesetzt. Optional kann dazu auch DHCP eingesetzt werden.

Für den Aufbau und die Verwaltung von Verbindungen wird das bekannte „Remote Procedure Call (RPC)“-Protokoll eingesetzt. Bei CBA werden dabei die „Distributed Component Object Model (DCOM)“-Objekte verwendet.

Profinet-Protokolle und -Dienste: Um diese Funktionen zu erreichen sind verschiedene Protokollstufen definiert:

    Die TCP/IP Protokolle für Profinet CBA mit Reaktionszeiten im Bereich von 100 ms
    Das RT (Real-Time) Protokoll für Profinet CBA und Profinet IO der Klassen A & B, Anwendungen mit typisch 10 ms Zykluszeiten
    Das IRT (Isochronous Real-Time) Protokoll für Profinet IO der Klasse C, Anwendungen bei der Antriebstechnik mit Zykluszeiten unter 1 ms""" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#CPF3_Profibus_ProfiNet> .

<http://www.w3id.org/ecsel-dr-RAMI40#Standard_Organisation> a rdfs:Class ;
  rdfs:comment """Standards organisations that prepares and publishes International Standards for all electrical, electronic and related technologies

e.g. IEC (International Electrotechnical Commission)""" .

<http://www.w3id.org/ecsel-dr-RAMI40#Uses> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#Standard_Organisation> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-RAMI40#Standard> .

<http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> a rdfs:Class ;
  rdfs:label "Fieldbus Communication Profile Family" ;
  rdfs:comment "Ein Feldbus definiert einen kompletten Protokoll-Stack über die 7 SChichten des OSI-Schichtenmodells. Ggf. werden nicht alle Schichten belegt." .

<http://www.w3id.org/ecsel-dr-AH#AH_application_service_SD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Service_Description_SD> .

<http://www.w3id.org/ecsel-dr-AT#OPC> a rdfs:Class ;
  rdfs:label "Open Platform Communications"@en ;
  rdfs:comment """OPC (Open Platform Communication or OLE for Process Control) is a service-oriented communication protocol which was developed based on Microsoft standards like DCOM and Object Linking and Embedding (OLE). 
It is the basis for OPC-UA (which defines a Microsoft-independent architecture). 

For communication between the applications, OPC mainly uses Microsoft's Distributed Component Object Model (DCOM) technology. Thanks to DCOM, it is transparent for OPC applications whether the data exchanged via OPC comes from an application in its own address space, from a foreign, local process, or even from a computer remotely connected via TCP / IP. The transmission and access speeds are DCOM usual slowed down by unnecessary administrative effort.
DCOM makes other applications, (compiled) functions and objects accessible. The OPC standard now defines certain DCOM objects, i. H. The functions / interfaces that an OPC user must make available (via DCOM) in order to exchange data with other OPC applications. The exact specifications required for an implementation can be freely downloaded from the OPC Foundation website.

Disadvantages / criticisms
OPC is based (with a few specifications) on Microsoft's DCOM specification. Communication over the boundaries of firewalls or domains is possible in the best case using so-called OPC tunnels. These software products convert the OPC communication into \"normal\" TCP / IP communication, transport it over the network and convert the TCP / IP into OPC communication in the target computer again. This significantly facilitates the general configuration.
However, even without an OPC tunnel, OPC can communicate across routers and firewalls, even if the server and client are not in the same domain. Authentication takes place via the local user table. Disadvantage: For this an identical local user must exist on both terminals (server and client), under which the OPC or DCOM communication is handled (server and client must run under this user). Also the password must be identical. However, this proves to be extremely impractical in many scenarios.
Furthermore, it is useful or even necessary to restrict the DCOM communication ports; This is possible via a Windows registry entry. The number of required ports depends on the application itself."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-AH#AH_core_service_SD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Service_Description_SD> .

<http://www.w3.org/2006/time#DateTimeDescription> a rdfs:Class ;
  rdfs:label "Date-Time description"@en ;
  rdfs:comment "Description of date and time structured with separate values for the various elements of a calendar-clock system. The temporal reference system is fixed to Gregorian Calendar, and the range of year, month, day properties restricted to corresponding XML Schema types xsd:gYear, xsd:gMonth and xsd:gDay, respectively."@en ;
  rdfs:subClassOf <http://www.w3.org/2006/time#GeneralDateTimeDescription> .

<http://www.w3.org/ns/sosa/Result> a rdfs:Class ;
  rdfs:label "Result"@en ;
  rdfs:comment "The Result of an Observation, Actuation, or act of Sampling. To store an observation's simple result value one can use the hasSimpleResult property."@en .

<http://www.w3id.org/ecsel-dr-AT#CommunicationDevice> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Device> .

<http://www.w3id.org/ecsel-dr-AT#PLM2_System_Suite> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#PLM-System-SecondGeneration> .

<http://www.w3id.org/ecsel-dr-PWR#Region_of_Operation> a rdfs:Class ;
  rdfs:label "Region of Operation" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Operating_Property> .

<http://www.w3id.org/ecsel-dr-AH#Industrial_personal_computer> a rdfs:Class ;
  rdfs:label "IPC"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Device> .

<http://www.w3id.org/ecsel-dr-PMV#Screen> a rdfs:Class ;
  rdfs:label "Screen" ;
  rdfs:comment "A transaction in SAP is described as a screen. Here, they represent the actions undertaken in the application SAP to perform a function in a process flow." .

<http://www.w3id.org/ecsel-dr-PMV#hasTransactionCode> a rdf:Property ;
  rdfs:label "hasTransactionCode" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Screen> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AH#Data_format> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#CAN_Bus> a rdfs:Class ;
  rdfs:label "Controller Area Network Bus"@de ;
  rdfs:comment """Der CAN-Bus (Controller Area Network) ist ein serielles Bussystem und gehört zu den Feldbussen.

Er wurde 1983 vom Unternehmen Bosch entwickelt und 1986 zusammen mit Intel vorgestellt. Sein Zweck ist es, Kabelbäume zu reduzieren und hiermit Kosten und Gewicht zu sparen. Zur damaligen Zeit konnte die Gesamtlänge aller Kabel im Kraftfahrzeug ohne CAN bis zu 2 km betragen.

CAN ist als ISO 11898 international standardisiert und definiert die Layer 1 (physische Schicht) und 2 (Datensicherungsschicht) im ISO/OSI-Referenzmodell. Die beiden gängigsten Realisierungen der physischen Schichten sind nach ISO 11898-2 (Highspeed-CAN) und ISO 11898-3 (Lowspeed-CAN). Sie unterscheiden sich in zahlreichen Eigenschaften und sind nicht zueinander kompatibel."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_Car_Airplane> .

<http://www.w3id.org/ecsel-dr-AH#Data_link_and_media_access_technology> a rdfs:Class ;
  rdfs:comment "corresponds to OSI layer 1 and 2 technologies, like Ethernet, WLAN (802.11), WPAN (802.15.4), EtherCAT, ProfiNet, ..." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Communication_technology> .

<http://www.w3id.org/ecsel-dr-AT#WSDL> a rdfs:Class ;
  rdfs:comment "Die Web Services Description Language (WSDL) ist eine plattform-, programmiersprachen- und protokollunabhängige Beschreibungssprache für Netzwerkdienste (Webservices) zum Austausch von Nachrichten auf Basis von XML. WSDL ist ein industrieller Standard des World Wide Web Consortiums (W3C)." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#MarkupLanguage> .

<http://www.w3id.org/ecsel-dr-AT#CPF16_SERCOS> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3id.org/ecsel-dr-SCP#ordersScheduleLine> a rdfs:Class ;
  rdfs:label "ordersScheduleLine"@iri-based .

<http://www.w3id.org/ecsel-dr-RAMI40#I4.0Component> a rdfs:Class ;
  rdfs:comment """Globally uniquely identifiable participant with communication capability consisting of administration shell and asset within an I4.0 system. 
Source: Industrie 4.0 – Begriffe/Terms, VDI Statusreport Industrie 4.0 (April 2017)""" .

<http://www.w3id.org/ecsel-dr-RAMI40#contains_Admin_Shell> a rdf:Property ;
  rdfs:comment "Points the I4.0 Component to the Administration Shell" ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#I4.0Component> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-RAMI40#Admin_Shell> .

<http://www.w3.org/TR/vocab-ssn-ext/ObservationCollection> a rdfs:Class ;
  rdfs:comment "An Observation Collection has at least one member, and may have one of any of the other seven properties mentioned in restrictions." .

<http://www.w3.org/TR/vocab-ssn-ext/hasUltimateFeatureOfInterest> a rdf:Property ;
  rdfs:comment "Link to the ultimate feature of interest of an observation or act of sampling. This is useful when the proximate feature of interest is a sample of the ultimate feature of interest, directly or transitively." ;
  rdfs:range <http://www.w3.org/ns/sosa/FeatureOfInterest> .

<http://www.w3.org/TR/vocab-ssn-ext/hasMember> a rdf:Property ;
  rdfs:comment "Link to a member of a collection of observations that share the same value for one or more of the characteristic properties." ;
  rdfs:domain <http://www.w3.org/TR/vocab-ssn-ext/ObservationCollection> ;
  rdfs:range <http://www.w3.org/TR/vocab-ssn-ext/ObservationCollection> .

<http://www.w3id.org/ecsel-dr-AT#PL_Phase4_Usage_Maintenance> a rdfs:Class ;
  rdfs:comment """Phase in the product lifecycle in which a product is used by the customer and (maybe) is maintained. 
Product refers to an individual product, i.e. an instance of the product type or class. A property of an product instance is that it can be uniquely identified, e.g. by a serial number."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ProductLifecyclePhase> .

<http://www.w3id.org/ecsel-dr-PWR#Deployment> a rdfs:Class ;
  rdfs:comment "The ongoing Process of Entities (for the purposes of this ontology, mainly the Infineon device) deployed for a particular purpose. For example, a particular Sensor deployed on a Platform, or a whole network of Sensors deployed for an observation campaign. The deployment may have sub processes, such as installation, maintenance, addition, and decomissioning and removal." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Deployment-related_Process> .

<http://www.w3id.org/ecsel-dr-PMV#ModelElement> a rdfs:Class ;
  rdfs:label "Model Element" ;
  rdfs:comment "An EPC model element is part of the EPC meta model and can be represented by a Function, an Event, an Operator, a Process Interface." .

<http://www.w3id.org/ecsel-dr-AT#OSI_Layer_Model_detailed> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#NetworkLayerModel> .

<http://www.w3id.org/ecsel-dr-AH#Switch_device> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Constrained_device> .

<http://www.w3id.org/ecsel-dr-AT#SSN> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Ontology> .

<http://www.w3id.org/ecsel-dr-AT#RFID> a rdfs:Class ;
  rdfs:label "Radio Frequency Identification" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> .

<http://www.w3id.org/ecsel-dr-AT#Bit> a rdfs:Class ;
  rdfs:comment "Base element of technical (physical) data transfer. Binary information: 0 or 1. May be represented by electromagnetical principles like wave modulation."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#DataTransmissionUnit> .

<http://www.w3id.org/ecsel-dr-PWR#Blocking_Capability> a rdfs:Class ;
  rdfs:label "Blocking Capability" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Property> .

<http://www.w3id.org/ecsel-dr-SO#Mask> a rdfs:Class ;
  rdfs:comment "A transparent (glass or quartz) plate covered with an array of patterns used in making an IC. Each pattern consists of opaque and transparent areas that define the size and shape of all circuit and device elements. The mask is used to expose selected areas, and defines the areas to be processed. Masks may use emulsion, chrome, iron oxide, silicon or other material to produce the opaque areas."@en .

<http://www.w3id.org/ecsel-dr-SO#requires> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Mask> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Lithography> .

<http://www.w3id.org/ecsel-dr-PMV#MachineResource> a rdfs:Class ;
  rdfs:label "Machine Resource" ;
  rdfs:comment "Semi or fully automated device that magnifies human physical and/or mental capabilities in performing one or more operations." ;
  rdfs:subClassOf <http://purl.org/dc/terms/PhysicalResource> .

<http://www.w3id.org/ecsel-dr-PMV#FunctionObject> a rdfs:Class ;
  rdfs:label "Function Object" ;
  rdfs:comment "In IndustryPrint 5, function objects are used to model the decomposition of a process." .

<http://www.w3.org/2006/time#DateTimeInterval> a rdfs:Class ;
  rdfs:label "Date-time interval"@en ;
  rdfs:comment "DateTimeInterval is a subclass of ProperInterval, defined using the multi-element DateTimeDescription."@en ;
  rdfs:subClassOf <http://www.w3.org/2006/time#ProperInterval> .

<http://www.w3.org/2006/time#hasDateTimeDescription> a rdf:Property ;
  rdfs:label "has Date-Time description"@en ;
  rdfs:comment "Value of DateTimeInterval expressed as a structured value. The beginning and end of the interval coincide with the limits of the shortest element in the description."@en ;
  rdfs:domain <http://www.w3.org/2006/time#DateTimeInterval> ;
  rdfs:range <http://www.w3.org/2006/time#GeneralDateTimeDescription> .

<http://www.w3.org/2006/time#xsdDateTime> a rdf:Property ;
  rdfs:label "has XSD date-time"@en ;
  rdfs:comment "Value of DateTimeInterval expressed as a compact value."@en ;
  rdfs:domain <http://www.w3.org/2006/time#DateTimeInterval> ;
  rdfs:range xsd:dateTime .

<http://www.w3id.org/ecsel-dr-SO#WIP_Station> a rdfs:Class ;
  rdfs:comment "Work in Progress (WIP) processing occurs here. WIP refers to the units of production that have been released into the factory, but have not yet been scrapped, have not been sent our for external rework, and have not finished processing through all of the production steps."@en .

<http://www.w3id.org/ecsel-dr-AT#CharacterSet> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L1_WebPlatform> .

<http://www.w3id.org/ecsel-dr-PWR#Microcontroller> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Semiconductors> .

<http://www.w3id.org/ecsel-dr-AT#SensorDevice> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Device> .

<http://www.w3id.org/ecsel-dr-OOSMP#Radar> a rdfs:Class ;
  rdfs:label "Radar" ;
  rdfs:comment "Infineon’s range of radar offerings provide unique benefits not possible with traditional motion sensing technology. Whether you require increased range coverage for outdoor lighting or a small form factor solution to enable soft landing in your multicopter our radar provides you with the ability to make your motion sensing applications perform in a way previously not possible. The BGT24M/L family is the largest and highest integrated 24GHz ISM band radar transceiver family currently in the market, providing a range of different transmitter and receiver channel configurations, supporting different application requirements. the sensor allows a Long range distance detection of moving objects up to 30 m and a wide range speed detection up to more than ±100 km/h." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#Sensor> .

<http://www.w3id.org/ecsel-dr-SCP#OperationalDemand> a rdfs:Class ;
  rdfs:label "OperationalDemand"@iri-based .

<http://www.w3id.org/ecsel-dr-SCP#ATP> a rdfs:Class ;
  rdfs:label "ATP"@iri-based .

<http://www.w3id.org/ecsel-dr-PMV#AND> a rdfs:Class ;
  rdfs:label "AND" ;
  rdfs:comment "All outgoing process paths must be followed." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#Connector> .

<http://www.w3id.org/ecsel-dr-AH#Semantic_Profile_SP> a rdfs:Class ;
  rdfs:comment "Provides a description of the semantics for the data (e.g. SenML, SensML, …), the data format and what is the type of the encoding (e.g., JSON, XML, EXI compressed XML). (Source: Arrowhead Framework Definitions V2.4)"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_service_documentation_document> .

<http://www.w3id.org/ecsel-dr-AT#Router> a rdfs:Class ;
  rdfs:label "Router"@en ;
  rdfs:comment """A router is a networking device that forwards data packets between computer networks. Routers perform the traffic directing functions on the Internet. Data sent through the internet, such as a web page or email, is in the form of data packets. A packet is typically forwarded from one router to another router through the networks that constitute an internetwork until it reaches its destination node. 
A router is connected to two or more data lines from different networks. When a data packet comes in on one of the lines, the router reads the network address information in the packet to determine the ultimate destination. Then, using information in its routing table or routing policy, it directs the packet to the next network on its journey. 
The most familiar type of routers are home and small office routers that simply forward IP packets between the home computers and the Internet. An example of a router would be the owner's cable or DSL router, which connects to the Internet through an Internet service provider (ISP). More sophisticated routers, such as enterprise routers, connect large business or ISP networks up to the powerful core routers that forward data at high speed along the optical fiber lines of the Internet backbone. Though routers are typically dedicated hardware devices, software-based routers also exist."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#CommunicationDevice> .

<http://www.w3id.org/ecsel-dr-AT#TCP_IP> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_3_4_NetworkTechnology> .

<http://www.w3id.org/ecsel-dr-PWR#Device> a rdfs:Class ;
  rdfs:comment "A device is a physical piece of technology - a system in a box. Devices may of course be build of smaller devices and software components.\"" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#System> .

<http://www.w3id.org/ecsel-dr-AT#ANSI-Standard> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Standard> .

<http://www.w3id.org/ecsel-dr-PMV#Process> a rdfs:Class ;
  rdfs:label "Process" ;
  rdfs:comment "A collection of subprocesses that meet a specific business objective. E.g. Perform Sourcing or Purchase Materials and Services" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#StructuralFunctionObject> .

<http://www.w3id.org/ecsel-dr-AH#AH_ServiceRegistry_WADL> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#System_WebApplicationDescription_WADL> .

<http://www.w3id.org/ecsel-dr-SO#Tool> a rdfs:Class ;
  rdfs:comment "a tool is any pieve of semiconductor fabrication or inspection equipment designed to process wafers. Often used synonymously with equipment in the silicon wafer processing industry."@en .

<http://www.w3id.org/ecsel-dr-AT#4G_LTE> a rdfs:Class ;
  rdfs:label "Long Term Evolution"@en ;
  rdfs:comment """Fourth generation of wireless wide area data transmission networks. 
Minimal size of radio transport block: subframe with length of 1ms"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> .

<http://www.w3id.org/ecsel-dr-AH#AH_application_servcice_IDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Interface_Design_Description_IDD> .

<http://www.w3id.org/ecsel-dr-PWR#Drain> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#Device_Elements> .

<http://www.w3id.org/ecsel-dr-PWR#Switcher> a rdfs:Class ;
  rdfs:label "Switcher" .

<http://www.w3id.org/ecsel-dr-AH#AH_TokenGenerationService_IDD> a rdfs:Class ;
  rdfs:comment "Interface Design Description (IDD) of the Arrowhead mandatory core service Token Generation Service which is provided by the mandatory core system Authorization System."@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_service_IDD> .

<http://www.w3id.org/ecsel-dr-AT#EDIFACT-DataFormat> a rdfs:Class ;
  rdfs:comment """Data Format of EDIFACT messages. 
Describes e.g. block organization, data field separators etc. 
Holds for all EDIFACT messages (which are described in DataSemantics class hierarchy)."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L2_DataSyntax> .

<http://www.w3id.org/ecsel-dr-SO#Owner> a rdfs:Class ;
  rdfs:comment "an owner is the entity that has the highest level of access authority or legal right to a system or equipment."@en .

<http://www.w3id.org/ecsel-dr-AT#FactorySimulationSystem> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Simulation-System> .

<http://www.w3id.org/ecsel-dr-SO#Product_Level_3> a rdfs:Class ;
  rdfs:comment """The static bottlenecks are determined in the “Product Level 3” master entity
because the mid capacity planning is done on this first aggregated product level. There is no big difference in capacity from the aggregated level 3 product to its child level 4 products. (hierarchal aggregation level)"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Product_Level> .

<http://www.w3id.org/ecsel-dr-SO#hasChipsPerWafer> a rdf:Property ;
  rdfs:comment "Product Level 4: Number of chips on a wafer"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Product_Level_3> ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-AH#Personal_computer> a rdfs:Class ;
  rdfs:label "PC"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#Device> .

<https://w3id.org/linkml/Any> a rdfs:Class ;
  rdfs:comment "An unconstrained type or object" .

<http://www.w3id.org/ecsel-dr-AT#Bluetooth> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> .

<http://www.w3id.org/ecsel-dr-AT#Device> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#SoA_Client> a rdfs:Class ;
  rdfs:comment """\"Role\" or function of an software (application) system that consumes / uses one or several services to other systems in a client-server communication pattern / process. 
Other names: Service Consumer"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitecture_FunctionPattern> .

<http://www.w3id.org/ecsel-dr-PMV#HumanOutput> a rdfs:Class ;
  rdfs:label "Human Output" ;
  rdfs:comment "Human being that puts effort in the processing of a process step (function). It belongs to the organizational unit that is responsible for the specific process step." ;
  rdfs:subClassOf <http://xmlns.com/foaf/0.1/Person> .

<http://www.w3id.org/ecsel-dr-PMV#processes> a rdf:Property ;
  rdfs:label "processes" ;
  rdfs:comment "Some person, referred to as human output here, processes a function in a process flow. " ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#HumanOutput> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Function> .

<http://www.w3id.org/ecsel-dr-SO#Technology> a rdfs:Class ;
  rdfs:comment "A semiconductor technology is a set of equipment, processes, manufacturing techniques and the related methods and procedures to enable the design & production of components, sub-components and modules."@en .

<http://www.w3id.org/ecsel-dr-SO#hasSupplyChainID> a rdf:Property ;
  rdfs:comment "Technology: FK; Assignment of technology to supply chain"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Technology> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AH#AH_SessionEstablishService_IDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service_IDD> .

<http://www.w3id.org/ecsel-dr-SO#Hot> a rdfs:Class ;
  rdfs:comment "[Priority Class] these lots are processed after a certain maximum waiting time which is shorter than the maximum waiting time of standard lots. In general, for all classes, if there is more than one product type waiting."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Priority_Classes> .

<http://www.w3id.org/ecsel-dr-SO#hasHotTimeout> a rdf:Property ;
  rdfs:comment "length of, or element of the length of, a temporal extent expressed in hours"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Hot> ;
  rdfs:range xsd:decimal .

<http://www.w3id.org/ecsel-dr-PWR#IndutrialSector> a rdfs:Class ;
  rdfs:comment """The collection of all localized groups of enterprises that are producers of industrial commodities, in which each such group together forms the major industrial sector for the region. 'Industrial commodities' includes MechanicalDevices and basic industrial materials. Examples include 'the world industrial sector', the 'industrial sector of China'. The Chinese water pump industry would not be an exemplar of IndustrialEconomicSector but would rather be a sub-industry (see subIndustries) of it. On the other hand, chinese water pump manufacturers would be considered groupMembers of 'the industrial sector of China'.

This classification is done by The Global Industry Classification Standard (GICS) is an industry taxonomy developed in 1999 by MSCI and Standard & Poor's (S&P) for use by the global financial community. The GICS structure consists of 11 sectors, 24 industry groups, 68 industries and 157 sub-industries[1] into which S&P has categorized all major public companies""" .

<http://www.w3id.org/ecsel-dr-SO#Simulation_Route> a rdfs:Class ;
  rdfs:comment "A simulation route (AKA workroute) represents a sequence of process steps in manufacutring (mainly at wafer fab). This is a simulation entity and not a form of production/planning."@en .

<http://www.w3id.org/ecsel-dr-AT#Switch> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#CommunicationDevice> .

<http://www.w3id.org/ecsel-dr-AH#Local_network> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#CoAP> a rdfs:Class ;
  rdfs:label "Constrained Application Protocol"@en ;
  rdfs:comment """CoAP is an application layer protocol that is intended for use in resource-constrained internet devices, such as WSN nodes. CoAP is designed to easily translate to HTTP for simplified integration with the web, while also meeting specialized requirements such as multicast support, very low overhead, and simplicity. The CoRE group has proposed the following features for CoAP: RESTful protocol design minimizing the complexity of mapping with HTTP, Low header overhead and parsing complexity, URI and content-type support, Support for the discovery of resources provided by known CoAP services. Simple subscription for a resource, and resulting push notifications, Simple caching based on max-age.
(https://www.postscapes.com/internet-of-things-protocols/)"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_5_7_ApplicationProtocol> .

<http://www.w3id.org/ecsel-dr-PMV#Task> a rdfs:Class ;
  rdfs:label "Task" ;
  rdfs:comment "The lowest level of detail, a task are the activities required to execute a subprocess. A single task within a subprocess can be manual or system supported. E.g. Create Purchase Order" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#Function> , <http://www.w3id.org/ecsel-dr-PMV#ModelElement> , <http://www.w3id.org/ecsel-dr-PMV#ModellingFunctionObject> .

<http://www.w3id.org/ecsel-dr-PMV#isCarriedOutBy> a rdf:Property ;
  rdfs:label "isCarriedOutBy" ;
  rdfs:comment "A process step is carried out by role(s) or organizational unit(s) (equivalent to R in RACI notation)." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Task> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#isActivatedByTask> a rdf:Property ;
  rdfs:label "isActivatedByTask" ;
  rdfs:comment "Represents the inverse property of activatesTask." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Task> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Rule> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-PMV#isActivatedBy> .

<http://www.w3id.org/ecsel-dr-PMV#isWorkedOnByCollaborationOf> a rdf:Property ;
  rdfs:label "isWorkedOnByCollaborationOf" ;
  rdfs:comment "A process step is worked on by collaboration of role(s)." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Task> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Role> .

<http://www.w3id.org/ecsel-dr-PMV#hasSubFlow> a rdf:Property ;
  rdfs:label "hasSubFlow" ;
  rdfs:comment "EPCs can have other EPCs as subordinates. The connector is used to represent the hierarchical order." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Task> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#BPFlow> .

<http://www.w3id.org/ecsel-dr-PMV#hasHandling> a rdf:Property ;
  rdfs:label "has Handling" ;
  rdfs:comment "Describes the requirements for the specific handling of objects." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Task> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#resultIsForwardedTo> a rdf:Property ;
  rdfs:label "resultIsForwardedTo" ;
  rdfs:comment "A result of a process step is forwarded to role(s)." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Task> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#Role> .

<http://www.w3id.org/ecsel-dr-PMV#isSupportedBy> a rdf:Property ;
  rdfs:label "isSupportedBy" ;
  rdfs:comment "A process step is supported by an application system type." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Task> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#ApplicationSystemType> .

<http://www.w3id.org/ecsel-dr-PMV#hasAsInput> a rdf:Property ;
  rdfs:label "hasAsInput" ;
  rdfs:comment "A process step can have technical term(s) as input." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Task> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#TechnicalTerm> .

<http://www.w3id.org/ecsel-dr-PMV#hasAsOutput> a rdf:Property ;
  rdfs:label "hasAsOutput" ;
  rdfs:comment "A process step can have technical term(s) as output." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PMV#Task> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PMV#TechnicalTerm> .

<http://www.w3id.org/ecsel-dr-AT#ZigBee_IP> a rdfs:Class ;
  rdfs:comment """ZigBee IP
ZigBee IP ist eine im Jahr 2012 erschienene Spezifikation für drahtlose Netzwerke mit Anbindung an das Internet[8]. Die ZigBee Alliance orientiert sich bei der Entwicklung an bestehenden Protokollen von Standardisierungsgremien wie IETF, IEEE, W3C, ISO und IEC. Der Stack nutzt in der Netzwerk-Schicht (OSI-Modell Network Layer) unter anderem die von der IETF entwickelten Protokolle 6LoWPAN und RPL.[8] Das 6LoWPAN-Protokoll ermöglicht die direkte Anbindung von Geräten oder Sensornetzwerken an das Internet über IPv6 (Internet of Things)."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_3_4_NetworkTechnology> .

<http://www.w3id.org/ecsel-dr-SO#Process_Class> a rdfs:Class ;
  rdfs:comment "A Process Class is the second hierarchy level in the Technology Catalogue and is a subset of top hierarchy level \"Technology Class\". A Process Class is defined by the device category and its generation or wafer diameter."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Process> .

<http://www.w3id.org/ecsel-dr-AT#ProductionCellPlanning> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#PLM1_Module> .

<http://www.w3.org/ns/ssn/Property> a rdfs:Class ;
  rdfs:label "Property"@en ;
  rdfs:comment "A quality of an entity. An aspect of an entity that is intrinsic to and cannot exist without the entity."@en .

<http://www.w3id.org/ecsel-dr-AT#ISA-95_Communication> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AH#AH_InterCloudNegotiationsService_IDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service_IDD> .

<http://www.w3id.org/ecsel-dr-PROD#Organization> a rdfs:Class ;
  rdfs:comment "An organization is en entity comprising multiple people. In SSC, this class mainly refers to businesses." .

<http://www.w3id.org/ecsel-dr-AT#MESA-Standard> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Standard> .

<http://www.w3id.org/ecsel-dr-AH#AH_core_system_SySD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#System_Description_SySD> .

<http://www.w3id.org/ecsel-dr-PWR#Resistance> a rdfs:Class .

<http://www.w3.org/ns/sosa/FeatureOfInterest> a rdfs:Class ;
  rdfs:label "Feature Of Interest"@en ;
  rdfs:comment "The thing whose property is being estimated or calculated in the course of an Observation to arrive at a Result or whose property is being manipulated by an Actuator, or which is being sampled or transformed in an act of Sampling."@en .

<http://www.w3id.org/ecsel-dr-AT#CPF4_P-NET> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3id.org/ecsel-dr-SO#Capacity> a rdfs:Class ;
  rdfs:comment "As soon as a machine has free capacity: 1. all lots which belong to a priority class have to be dispatched imediately accordung to their priority rank."@en .

<http://www.w3id.org/ecsel-dr-SO#hasWIPStation> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Capacity> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#WIP_Station> .

<http://www.w3id.org/ecsel-dr-SO#Implantation> a rdfs:Class ;
  rdfs:comment "Implantation or Ion Implantation is a technique where ions are accelerated to a higher energy and speed an injected into a semiconductor. The dominant techniques for introducing dopants into a semiconductor."@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-SO#Workshop> .

<http://www.w3id.org/ecsel-dr-OM#OrderLineItem> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-OM#hasAllocated> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderLineItem> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#Supply> .

<http://www.w3id.org/ecsel-dr-OM#isReconciledOrderChangeRequest> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderLineItem> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OM#OrderChangeRequest> .

<http://www.w3id.org/ecsel-dr-OM#hasCustomerRequestedDate> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderLineItem> ;
  rdfs:range xsd:dateTime .

<http://www.w3id.org/ecsel-dr-OM#hasOpenQuantityOLI> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderLineItem> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#hasConfirmedQuantity> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderLineItem> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#hasLineIDOLI> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderLineItem> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#hasConfirmedDeliveryDate> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#OrderLineItem> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-AT#CPF1_FOUNDATION_Fieldbus> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family> .

<http://www.w3id.org/ecsel-dr-AT#IT-Vendor> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#isVendorOf> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-AT#IT-Vendor> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-AT#IT-System> .

<http://www.w3id.org/ecsel-dr-AT#CPF3_5_Profinet_IO_ClassB> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#CPF3_Profibus_ProfiNet> .

<http://www.w3.org/ns/ssn/systems/Frequency> a rdfs:Class ;
  rdfs:label "Frequency" ;
  rdfs:comment "The smallest possible time between one Observation, Actuation, or Sampling and the next, under the defined Conditions." ;
  rdfs:subClassOf <http://www.w3.org/ns/ssn/systems/SystemProperty> .

<http://www.w3id.org/ecsel-dr-RAMI40#EnergyEfficiency> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-RAMI40#Submodel> .

<http://www.w3id.org/ecsel-dr-RAMI40#energy_Efficiency_Value> a rdf:Property ;
  rdfs:comment "Points to the value of the Energy Efficiency comsuption." ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-RAMI40#EnergyEfficiency> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-RAMI40#Measure> .

<http://www.w3id.org/ecsel-dr-SO#Supply_Chain> a rdfs:Class ;
  rdfs:comment "The entity “Supply Chain” describes the supply chain from the topmost level with all possible material flow edges, referring on the FabIDs (master entity)"@en .

<http://www.w3id.org/ecsel-dr-SO#hasTravelTime> a rdf:Property ;
  rdfs:comment "length of, or element of the length of, a temporal extent expressed in seconds"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Supply_Chain> ;
  rdfs:range xsd:decimal .

<http://www.w3id.org/ecsel-dr-SO#hasPlant> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Supply_Chain> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Plant> .

<http://www.w3id.org/ecsel-dr-SO#toFabID> a rdf:Property ;
  rdfs:comment "Supply Chain: FK; Sink ID of supply chain edge"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Supply_Chain> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#fromFabID> a rdf:Property ;
  rdfs:comment "Supply Chain: FK; Source ID of supply chain edge"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Supply_Chain> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-SO#hasSupplyChainName> a rdf:Property ;
  rdfs:comment "Supply Chain: Name of the supply chain"@en ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SO#Supply_Chain> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-OOSMP#PressureSensor> a rdfs:Class ;
  rdfs:label "Pressure Sensor" ;
  rdfs:comment "A pressure sensor is a sensor which measures pressure." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#Sensor> .

<http://www.w3id.org/ecsel-dr-PWR#Products> a rdfs:Class ;
  rdfs:comment """The superclass of all classes describing products or services types, either by nature or purpose. Examples for such subclasses are \"TV set\", \"vacuum cleaner\", etc. An instance of this class can be either an actual product or service (gr:Individual), a placeholder instance for unknown instances of a mass-produced commodity (gr:SomeItems), or a model / prototype specification (gr:ProductOrServiceModel). When in doubt, use gr:SomeItems.

Examples: 
a) MyCellphone123, i.e. my personal, tangible cell phone (gr:Individual)
b) Siemens1234, i.e. the Siemens cell phone make and model 1234 (gr:ProductOrServiceModel)
c) dummyCellPhone123 as a placeholder for actual instances of a certain kind of cell phones (gr:SomeItems)""" .

<http://www.w3id.org/ecsel-dr-PWR#hasAnApplicationArea> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Products> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#ApplicationArea> .

<http://www.w3id.org/ecsel-dr-PWR#hasAdimension> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-PWR#Products> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PWR#GeometricDimension> .

<http://www.w3id.org/ecsel-dr-AT#SOAP> a rdfs:Class ;
  rdfs:comment """SOAP (ursprünglich für Simple Object Access Protocol) ist ein Netzwerkprotokoll, mit dessen Hilfe Daten zwischen Systemen ausgetauscht und Remote Procedure Calls durchgeführt werden können. SOAP ist ein industrieller Standard des World Wide Web Consortiums (W3C).
SOAP stützt sich auf XML zur Repräsentation der Daten und auf Internet-Protokolle der Transport- und Anwendungsschicht (vgl. TCP/IP-Referenzmodell) zur Übertragung der Nachrichten. Die gängigste Kombination ist SOAP über HTTP und TCP. SOAP kann beispielsweise auch über SMTP[1] oder JMS[2] verwendet werden. Die mit der Nachricht übermittelten Nutzdaten müssen nicht zwingend in XML gesendet werden, andere Formate wie Base64 oder CSV sind auch möglich.[3][4] Die Abkürzung SOAP wird offiziell ab Version 1.2 nicht mehr als Akronym gebraucht, da es erstens (subjektiv) keineswegs einfach (Simple) ist und zweitens nicht nur dem Zugriff auf Objekte (Object Access) dient. 
Arbeitsweise

SOAP ist ein Protokoll zum Austausch XML-Information-Set-basierter Nachrichten über ein Rechnernetz und hat den Status einer W3C-Empfehlung. Es stellt Regeln für das Nachrichtendesign auf. Es regelt, wie Daten in der Nachricht abzubilden und zu interpretieren sind, und gibt eine Konvention für entfernte Prozeduraufrufe mittels SOAP-Nachrichten vor. SOAP macht keine Vorschriften zur Semantik applikationsspezifischer Daten, die versendet werden sollen, sondern stellt ein Rahmenwerk (framework) zur Verfügung, welches erlaubt, dass beliebige applikationsspezifische Informationen übertragen werden können. SOAP wird für entfernte Prozeduraufrufe ebenso genutzt wie für einfache Nachrichtensysteme beziehungsweise zum Datenaustausch. Zum Senden von Nachrichten können beliebige Transportprotokolle verwendet werden, beispielsweise FTP, SMTP, HTTP oder auch JMS. In der Praxis wird aufgrund der Kompatibilität mit gängigen Netzwerk-Architekturen (wie Firewalls) meist auf HTTP zurückgegriffen. Auch ist mittels HTTPS die verschlüsselte Übertragung von SOAP-Nachrichten möglich. Das ermöglicht jedoch keine End-to-End-Verschlüsselung. Diese wird durch WS-Security ermöglicht, das auf der Ebene der Nachrichten und nicht auf der Ebene des unterliegenden Transportprotokolls ansetzt. Das XML Information Set der SOAP-Anfrage wird bei Nutzung von HTTP(S) im Body eines HTTP POST Requests als XML an eine gegebene URL geschickt.

SOAP wird regelmäßig dort eingesetzt, wo der direkte Zugang fremder Systeme zu einer Informationsquelle nicht sinnvoll erscheint. Dies kann an Kompatibilitätsproblemen zwischen verschiedenen Anwendungsarchitekturen liegen, aber auch an Sicherheitsaspekten. So kann der (partielle) Zugriff auf eine Datenbank ermöglicht werden, ohne dass dem Anwenderprogramm der direkte Zugang gestattet werden muss. Über die SOAP-Schnittstelle kann die Menge der ausführbaren Methoden reglementiert und definiert werden.

Die Kommunikation mit SOAP ermöglicht die Kopplung von Systemen, der offene Entwurf von SOAP ermöglicht jedoch lediglich den Aufbau schwach gekoppelter Systeme. Die Flexibilität des Konzeptes wird durch Nachteile in Übertragungsvolumen und Rechenaufwand erkauft. Das XML-Dokument muss beim Sender zunächst aufgebaut und anschließend validiert werden. Das Konzept verfolgt das Ziel eines leichtgewichtigen Protokolls, aufgrund des flexiblen Einsatzbereiches führt die zu übertragende Datei jedoch eine Reihe von Metadaten mit sich, die bei der Konstruktion des XML-Dokuments hinzugefügt werden. So führt beispielsweise das einfache Versenden von „Wahr“ oder „Falsch“ zu einem Datenvolumen von mehreren hundert Bytes, obwohl in einem stark gekoppelten System theoretisch ein Bit reichen würde. Durch die Möglichkeit des flexiblen Aufbaus des Dokuments können jedoch komplexe Transaktionen in einer Anfrage atomar zusammengefasst werden, während in stark gekoppelten Systemen hierzu oftmals mehrere Anfragen gestellt werden müssen. Dies verbessert das Nutzlastverhältnis (Nutzdaten zu Meta-Daten) und den Kommunikationsaufwand (für den Aufbau einer Verbindung, nur ein Senden/Empfangen).

SOAP unterscheidet zwischen dem endgültigen Empfänger und Zwischenempfängern. Dies ermöglicht es, eine Nachricht über verschiedene „Hops“ zu schicken, bei denen sogar verschiedene Transportprotokolle verwendet werden. Beispielsweise kann zum ersten Hop die Nachricht mittels JMS geschickt werden, danach über E-Mail und schließlich dem Empfänger mittels HTTP. Der Absender muss über die Zwischenhops keine Information haben, die Middleware jedoch schon."""@de ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitecture> .

<http://www.w3id.org/ecsel-dr-PWR#Energy_Storage> a rdfs:Class ;
  rdfs:label "Energy Storage" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#ApplicationArea> .

<http://www.w3id.org/ecsel-dr-AT#3G_UMTS> a rdfs:Class ;
  rdfs:label "Universal Mobile Telecommunications System"@en ;
  rdfs:comment """Third generation of wireless wide area data transmission networks. 
First generation with completely separated infrastructure, i.e. own modules and antennas at base stations and own antennas in Smartphones"""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology> .

<http://www.w3id.org/ecsel-dr-SCP#Promise> a rdfs:Class ;
  rdfs:label "Promise"@iri-based .

<http://www.w3id.org/ecsel-dr-SCP#transfer> a rdf:Property ;
  rdfs:label "transfer"@iri-based ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-SCP#Promise> ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SCP#Confirmation> .

<http://www.w3id.org/ecsel-dr-PWR#ConsumerStaples> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PWR#IndutrialSector> .

<http://www.w3id.org/ecsel-dr-AH#AH_core_system_SySDD> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#System_Design_Description_SySDD> .

<http://www.w3id.org/ecsel-dr-AT#PL_Phase3_Production> a rdfs:Class ;
  rdfs:comment """Phase in the product lifecycle in which a product is produced. 
Product refers in this phase to an individual product, i.e. an instance of the product type or class. A property of an product instance is that it can be uniquely identified, e.g. by a serial number."""@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#ProductLifecyclePhase> .

<http://www.w3id.org/ecsel-dr-RAMI40#Measure> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AH#System_Description_SySD> a rdfs:Class ;
  rdfs:comment "Is the “Black box” description of the system, i.e., the main services and interfaces of a system, without describing its internal implementation. The SySD refers to a number of IDDs. (Source: Arrowhead Framework Definitions V2.4)"@en ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AH#AH_system_documentation_document> .

<http://www.w3.org/ns/sosa/Sampling> a rdfs:Class ;
  rdfs:label "Sampling"@en ;
  rdfs:comment "An act of Sampling carries out a sampling Procedure to create or transform one or more samples."@en .

<http://www.w3.org/ns/sosa/madeBySampler> a rdf:Property ;
  rdfs:label "made by sampler"@en ;
  rdfs:comment "Relation linking an act of Sampling to the Sampler (sampling device or entity) that made it."@en ;
  rdfs:domain <http://www.w3.org/ns/sosa/Sampling> ;
  rdfs:range <http://www.w3.org/ns/sosa/Sampler> .

<http://xmlns.com/foaf/0.1/Document> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-AT#ANSI_X12-DataFormat> a rdfs:Class ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-AT#W3C_L2_DataSyntax> .

<http://www.w3id.org/ecsel-dr-PMV#ProcessTypeMap> a rdfs:Class ;
  rdfs:label "Process Type Map" ;
  rdfs:comment "A set of process types and related process groups that define the enterprise for a particular industry/sector." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-PMV#Model> .

<http://www.w3id.org/ecsel-dr-OM#ContactPersonData> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-OM#hasFax> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#ContactPersonData> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#hasTelephone> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#ContactPersonData> ;
  rdfs:range xsd:int .

<http://www.w3id.org/ecsel-dr-OM#hasEmail> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#ContactPersonData> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-OM#hasName> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#ContactPersonData> ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-OM#hasDepartment> a rdf:Property ;
  rdfs:domain <http://www.w3id.org/ecsel-dr-OM#ContactPersonData> ;
  rdfs:range xsd:string .

<http://www.w3.org/2006/time#hasDuration> a rdf:Property ;
  rdfs:label "has duration"@en ;
  rdfs:comment "Duration of a temporal entity, event or activity, or thing, expressed as a scaled value"@en ;
  rdfs:range <http://www.w3.org/2006/time#Duration> ;
  rdfs:subPropertyOf <http://www.w3.org/2006/time#hasTemporalDuration> .

<http://www.w3.org/2006/time#hasDurationDescription> a rdf:Property ;
  rdfs:label "has duration description"@en ;
  rdfs:comment "Duration of a temporal entity, expressed using a structured description"@en ;
  rdfs:range <http://www.w3.org/2006/time#GeneralDurationDescription> ;
  rdfs:subPropertyOf <http://www.w3.org/2006/time#hasTemporalDuration> .

<http://www.w3.org/2006/time#hasTime> a rdf:Property ;
  rdfs:label "has time"@en ;
  rdfs:comment "Supports the association of a temporal entity (instant or interval) to any thing"@en ;
  rdfs:range <http://www.w3.org/2006/time#TemporalEntity> .

<http://www.w3.org/ns/sosa/hasSimpleResult> a rdf:Property ;
  rdfs:label "has simple result"@en ;
  rdfs:comment "The simple value of an Observation or Actuation or act of Sampling."@en ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-AH#hasArchitecturalPart> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-AH#isArchitecturalPartOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-AT#hasCommunicationDevice> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-AT#hasImplementationTechnology> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-AT#isServiceDescriptionLanguageOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-AT#standardizedBy> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-AT#supportedByTechnologyOrProtocol> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-OM#consitsOfOpenOrder> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-OM#isDescribedByCustomerData> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-OM#isDescribedByCustomerPlantData> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-OM#isDescribedBySupplierData> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-OM#isOwnedByCustomer> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-OM#isPartOfOpenOrder> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-OM#isRequestedByCustomer> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-OOSMP#OPNStatusOf> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#semiconductorProductStatusOf> .

<http://www.w3id.org/ecsel-dr-OOSMP#RoHSCompliantStatusOf> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#semiconductorProductStatusOf> .

<http://www.w3id.org/ecsel-dr-OOSMP#abbreviation> a rdf:Property ;
  rdfs:label "Abbreviation" ;
  rdfs:comment "Any abbreviation of a concept" ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-OOSMP#completelyLeadFreeStatusOf> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#semiconductorProductStatusOf> .

<http://www.w3id.org/ecsel-dr-OOSMP#designTargetOf> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> .

<http://www.w3id.org/ecsel-dr-OOSMP#halogenFreeStatusOf> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#semiconductorProductStatusOf> .

<http://www.w3id.org/ecsel-dr-OOSMP#identifier> a rdf:Property ;
  rdfs:label "Identifier" ;
  rdfs:comment "Any identifier (ID) of a concept" ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-OOSMP#integrationLevelOf> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> .

<http://www.w3id.org/ecsel-dr-OOSMP#mainPowerDeviceTypeOf> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> .

<http://www.w3id.org/ecsel-dr-OOSMP#motorTypeOf> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> .

<http://www.w3id.org/ecsel-dr-OOSMP#mountingStyleOf> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#Sensor> .

<http://www.w3id.org/ecsel-dr-OOSMP#priceIndicationOf> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> .

<http://www.w3id.org/ecsel-dr-OOSMP#productQualificationOf> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#qualificationOf> .

<http://www.w3id.org/ecsel-dr-OOSMP#qualificationOf> a rdf:Property ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-OOSMP#sensingTypeOf> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> .

<http://www.w3id.org/ecsel-dr-OOSMP#solutionQualificationOf> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution> ;
  rdfs:subPropertyOf <http://www.w3id.org/ecsel-dr-OOSMP#qualificationOf> .

<http://www.w3id.org/ecsel-dr-OOSMP#topologyOf> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution> .

<http://www.w3id.org/ecsel-dr-OOSMP#uniformResourceLocator> a rdf:Property ;
  rdfs:label "Uniform Resource Locator" ;
  rdfs:comment "A Uniform Resource Locator (URL) is an address that shows where a particular page can be found on the World Wide Web." ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#hasCompletionStatus> a rdf:Property ;
  rdfs:label "hasCompletionStatus" ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#hasCreator> a rdf:Property ;
  rdfs:label "hasCreator" ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#hasIPCode> a rdf:Property ;
  rdfs:label "hasIPCode" ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#hasIdentifier> a rdf:Property ;
  rdfs:label "has Identifier" ;
  rdfs:comment "Represents the unique identifier of the element." ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#hasMission> a rdf:Property ;
  rdfs:label "has Mission" ;
  rdfs:comment "Describes the mission or goal of a business process (flow)." ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#hasOrphan> a rdf:Property ;
  rdfs:label "hasOrphan" ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#hasOwner> a rdf:Property ;
  rdfs:label "has Owner" ;
  rdfs:comment "Represents the owner of a business process (flow)." ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#hasProjectScope> a rdf:Property ;
  rdfs:label "hasProjectScope" ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#hasRequirements> a rdf:Property ;
  rdfs:label "has Requirements" ;
  rdfs:comment "Description of all requirements for the certain input or output." ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#hasScope> a rdf:Property ;
  rdfs:label "has Scope" ;
  rdfs:comment "Denotes the scope of a specific business process (flow)." ;
  rdfs:range xsd:string .

<http://www.w3id.org/ecsel-dr-PMV#leadsTo> a rdf:Property ;
  rdfs:label "leadsTo" ;
  rdfs:comment "The connector is used to represent the chronological order in an EPC." ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-PRIMA#hasCategoryFactor> a rdf:Property ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-PRIMA#isCategoryLevelOf> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> .

<http://www.w3id.org/ecsel-dr-PRIMA#isProjectStatus> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject> .

<http://www.w3id.org/ecsel-dr-PROD#minOrderQuantity> a rdf:Property ;
  rdfs:range xsd:integer .

<http://www.w3id.org/ecsel-dr-PROD#shippedTo> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-RAMI40#has_RAMI_Hierarchy_Level> a rdf:Property ;
  rdfs:comment "Connects the concepts with the correspondent layer in the RAMI Hierarchy Levels" ;
  rdfs:range <http://www.w3id.org/ecsel-dr-RAMI40#RAMI_Hierarchy_Level_Dimension> .

<http://www.w3id.org/ecsel-dr-RAMI40#has_RAMI_Life_Cycle_Layer> a rdf:Property ;
  rdfs:comment "Connects the concepts with the correspondent layer in the RAMI Hierarchy Levels" ;
  rdfs:range <http://www.w3id.org/ecsel-dr-RAMI40#RAMI_Life_Cycle_Dimension> .

<http://www.w3id.org/ecsel-dr-RAMI40#usesStandard> a rdf:Property ;
  rdfs:comment "Points to the standards describing the functions attached to the asset via the administration shell" ;
  rdfs:range <http://www.w3id.org/ecsel-dr-RAMI40#Standard> .

<http://www.w3id.org/ecsel-dr-SO#dedicates> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#hasBottlenecks> a rdf:Property ;
  rdfs:range <http://www.w3id.org/ecsel-dr-SO#Bottlenecks> .

<http://www.w3id.org/ecsel-dr-SO#isBottlenecksOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isCurrentWIP> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isDeliveryCommitmentOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isDemandOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isEquipmentGroupOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isEquipmentOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isEventCalendarOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isFabOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isLotEventOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isLotOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isLotSizeOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isManuallyLoadedBy> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isNeededBy> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isOperationOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isOwnedBy> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isPartOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isPlantOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isPriorityClassOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isProductLevelOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isReleasePlanOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isRequiredBy> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isRoboticallyLoadedBy> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isRouteOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isShiftOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isTargetCostsOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isTargetRevenueOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isTechnologyOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isTimeConstraintsOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isUnloadedBy> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isWIPStationOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#isWorkshopOf> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#preceeds> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3id.org/ecsel-dr-SO#processes> a rdf:Property ;
  rdfs:range <https://w3id.org/linkml/Any> .

<http://www.w3.org/2006/time#generalDay> a rdfs:Datatype ;
  rdfs:label "Generalized day"@en ;
  rdfs:comment """Day of month - formulated as a text string with a pattern constraint to reproduce the same lexical form as gDay, except that values up to 99 are permitted, in order to support calendars with more than 31 days in a month. 
Note that the value-space is not defined, so a generic OWL2 processor cannot compute ordering relationships of values of this type."""@en .

<http://www.w3.org/2006/time#generalMonth> a rdfs:Datatype ;
  rdfs:label "Generalized month"@en ;
  rdfs:comment """Month of year - formulated as a text string with a pattern constraint to reproduce the same lexical form as gMonth, except that values up to 20 are permitted, in order to support calendars with more than 12 months in the year. 
Note that the value-space is not defined, so a generic OWL2 processor cannot compute ordering relationships of values of this type."""@en .

<http://www.w3.org/2006/time#generalYear> a rdfs:Datatype ;
  rdfs:label "Generalized year"@en ;
  rdfs:comment """Year number - formulated as a text string with a pattern constraint to reproduce the same lexical form as gYear, but not restricted to values from the Gregorian calendar. 
Note that the value-space is not defined, so a generic OWL2 processor cannot compute ordering relationships of values of this type."""@en .

<http://www.w3id.org/ecsel-dr-OOSMP#Topology> a rdfs:Class ;
  rdfs:label "Topology" ;
  rdfs:comment "Topology describes the arrangement and the amount of chips in a semiconductor solution. A toplogy can be \"3 phase\", \"half bridge\", \"h-bridge\", \"high side\", \"low side\" and \"relay\"." .

<http://www.w3id.org/ecsel-dr-OOSMP#HBridge_Topology> a <http://www.w3id.org/ecsel-dr-OOSMP#Topology> .

<http://www.w3id.org/ecsel-dr-OOSMP#HalfBridge_Topology> a <http://www.w3id.org/ecsel-dr-OOSMP#Topology> .

<http://www.w3id.org/ecsel-dr-OOSMP#HighSide_Topology> a <http://www.w3id.org/ecsel-dr-OOSMP#Topology> .

<http://www.w3id.org/ecsel-dr-OOSMP#LowSide_Topology> a <http://www.w3id.org/ecsel-dr-OOSMP#Topology> .

<http://www.w3id.org/ecsel-dr-OOSMP#Relay_Topology> a <http://www.w3id.org/ecsel-dr-OOSMP#Topology> .

<http://www.w3id.org/ecsel-dr-OOSMP#_3Phase_Topology> a <http://www.w3id.org/ecsel-dr-OOSMP#Topology> .

<http://www.w3id.org/ecsel-dr-PRIMA#Category> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PRIMA#Autobahn> a <http://www.w3id.org/ecsel-dr-PRIMA#Category> .

<http://www.w3id.org/ecsel-dr-PRIMA#Expedition> a <http://www.w3id.org/ecsel-dr-PRIMA#Category> .

<http://www.w3id.org/ecsel-dr-PRIMA#Mission> a <http://www.w3id.org/ecsel-dr-PRIMA#Category> .

<http://www.w3id.org/ecsel-dr-OOSMP#RoHSCompliantStatus> a rdfs:Class ;
  rdfs:label "RoHS Compliant Status" ;
  rdfs:comment "This status determines whether a product is RoHS compliant or not." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProductStatus> .

<http://www.w3id.org/ecsel-dr-OOSMP#NotRoHSCompliant_Status> a <http://www.w3id.org/ecsel-dr-OOSMP#RoHSCompliantStatus> .

<http://www.w3id.org/ecsel-dr-OOSMP#RoHSCompliant_Status> a <http://www.w3id.org/ecsel-dr-OOSMP#RoHSCompliantStatus> .

<http://www.w3id.org/ecsel-dr-OOSMP#IntegrationLevel> a rdfs:Class ;
  rdfs:label "Integration Level" ;
  rdfs:comment "Each motor control and drive solution has an integration level which states if the different stage are built in an integrated or discrete way. The stages of a motor control and drive solution are \"Controller\", \"Driver\", \"Power Stage\". Following this, the different integration levels are \"discrete\" (not integrated), \"fully integrated\", \"integrated controller driver\", \"integrated driver power stage\", \"integrated power stage\"." .

<http://www.w3id.org/ecsel-dr-OOSMP#Discrete_SolutionIntegrationLevel> a <http://www.w3id.org/ecsel-dr-OOSMP#IntegrationLevel> .

<http://www.w3id.org/ecsel-dr-OOSMP#FullyIntegrated_SolutionIntegrationLevel> a <http://www.w3id.org/ecsel-dr-OOSMP#IntegrationLevel> .

<http://www.w3id.org/ecsel-dr-OOSMP#IntegratedControllerDriver_SolutionIntegrationLevel> a <http://www.w3id.org/ecsel-dr-OOSMP#IntegrationLevel> .

<http://www.w3id.org/ecsel-dr-OOSMP#IntegratedDriverPowerStage_SolutionIntegrationLevel> a <http://www.w3id.org/ecsel-dr-OOSMP#IntegrationLevel> .

<http://www.w3id.org/ecsel-dr-OOSMP#IntegratedPowerStage_SolutionIntegrationLevel> a <http://www.w3id.org/ecsel-dr-OOSMP#IntegrationLevel> .

<http://www.w3id.org/ecsel-dr-OOSMP#MountingStyle> a rdfs:Class ;
  rdfs:label "Mounting Style" ;
  rdfs:comment "Each sensor has a specific mounting style. A mounting style can either be a \"SMDSMT\" or \"Through Hole\"." .

<http://www.w3id.org/ecsel-dr-OOSMP#SMDSMT_MountingStyle> a <http://www.w3id.org/ecsel-dr-OOSMP#MountingStyle> .

<http://www.w3id.org/ecsel-dr-OOSMP#ThroughHole_MountingStyle> a <http://www.w3id.org/ecsel-dr-OOSMP#MountingStyle> .

<http://www.w3id.org/ecsel-dr-RAMI40#RAMI_IT_Layer_Dimension> a rdfs:Class ;
  rdfs:label "RAMI IT Layer Dimension" ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-RAMI40#Dimension> .

<http://www.w3id.org/ecsel-dr-RAMI40#Asset> a <http://www.w3id.org/ecsel-dr-RAMI40#RAMI_IT_Layer_Dimension> ;
  rdfs:comment "Clearly identifiable asset for the Administration Shell" .

<http://www.w3id.org/ecsel-dr-RAMI40#Business> a <http://www.w3id.org/ecsel-dr-RAMI40#RAMI_IT_Layer_Dimension> , <http://www.w3id.org/ecsel-dr-RAMI40#View> .

<http://www.w3id.org/ecsel-dr-RAMI40#Communication> a <http://www.w3id.org/ecsel-dr-RAMI40#RAMI_IT_Layer_Dimension> .

<http://www.w3id.org/ecsel-dr-RAMI40#Functional> a <http://www.w3id.org/ecsel-dr-RAMI40#RAMI_IT_Layer_Dimension> .

<http://www.w3id.org/ecsel-dr-RAMI40#Information> a <http://www.w3id.org/ecsel-dr-RAMI40#RAMI_IT_Layer_Dimension> .

<http://www.w3id.org/ecsel-dr-RAMI40#Integration> a <http://www.w3id.org/ecsel-dr-RAMI40#RAMI_IT_Layer_Dimension> .

<http://www.w3id.org/ecsel-dr-OOSMP#CompletelyLeadFreeStatus> a rdfs:Class ;
  rdfs:label "Completely Lead Free Status" ;
  rdfs:comment "This status determines whether a semiconductor product is lead free or not." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProductStatus> .

<http://www.w3id.org/ecsel-dr-OOSMP#CompletelyLeadFree_Status> a <http://www.w3id.org/ecsel-dr-OOSMP#CompletelyLeadFreeStatus> .

<http://www.w3id.org/ecsel-dr-OOSMP#NotCompletelyLeadFree_Status> a <http://www.w3id.org/ecsel-dr-OOSMP#CompletelyLeadFreeStatus> .

<http://www.w3id.org/ecsel-dr-RAMI40#RAMI_Life_Cycle_Dimension> a rdfs:Class ;
  rdfs:label "RAMI Life Cycle Dimension" ;
  rdfs:comment "It describes the different Life Cycle and Value Stream layers for the RAMI model according to the IEC 62890 Standard." ;
  rdfs:seeAlso <http://www.zvei.org/en/subjects/Industry-40/Pages/The-Reference-Architectural-Model-RAMI-40-and-the-Industrie-40-Component.aspx> ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-RAMI40#Dimension> .

<http://www.w3id.org/ecsel-dr-RAMI40#Instance> a <http://www.w3id.org/ecsel-dr-RAMI40#RAMI_Life_Cycle_Dimension> .

<http://www.w3id.org/ecsel-dr-RAMI40#Type> a <http://www.w3id.org/ecsel-dr-RAMI40#RAMI_Life_Cycle_Dimension> .

<http://www.w3id.org/ecsel-dr-OOSMP#HalogenFreeStatus> a rdfs:Class ;
  rdfs:label "Halogen Free Status" ;
  rdfs:comment "This status determines whether a semiconductor product is halogen free or not." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProductStatus> .

<http://www.w3id.org/ecsel-dr-OOSMP#HalogenFree_Status> a <http://www.w3id.org/ecsel-dr-OOSMP#HalogenFreeStatus> .

<http://www.w3id.org/ecsel-dr-OOSMP#NotHalogenFree_Status> a <http://www.w3id.org/ecsel-dr-OOSMP#HalogenFreeStatus> .

<http://www.w3id.org/ecsel-dr-OOSMP#DesignTarget> a rdfs:Class ;
  rdfs:label "Design Target" ;
  rdfs:comment "Semiconductor solutions are design for different purposes, with different design goals respectively. Design targets comprise \"flexible to design\", \"easy to design\" and \"allrounder\"." .

<http://www.w3id.org/ecsel-dr-OOSMP#Allrounder_DesignTarget> a <http://www.w3id.org/ecsel-dr-OOSMP#DesignTarget> .

<http://www.w3id.org/ecsel-dr-OOSMP#EasyToDesign_DesignTarget> a <http://www.w3id.org/ecsel-dr-OOSMP#DesignTarget> .

<http://www.w3id.org/ecsel-dr-OOSMP#FlexibleToDesign_DesignTarget> a <http://www.w3id.org/ecsel-dr-OOSMP#DesignTarget> .

<http://www.w3id.org/ecsel-dr-RAMI40#RAMI_Hierarchy_Level_Dimension> a rdfs:Class ;
  rdfs:comment "It describes the functional classification of various circumstances within Industrie 4.0. For classification within a factory, this axis of the reference architecture(layers) follows the IEC 62264 Standard." ;
  rdfs:seeAlso <http://www.zvei.org/en/subjects/Industry-40/Pages/The-Reference-Architectural-Model-RAMI-40-and-the-Industrie-40-Component.aspx> ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-RAMI40#Dimension> .

<http://www.w3id.org/ecsel-dr-RAMI40#Connected_World> a <http://www.w3id.org/ecsel-dr-RAMI40#RAMI_Hierarchy_Level_Dimension> .

<http://www.w3id.org/ecsel-dr-RAMI40#Control_Device> a <http://www.w3id.org/ecsel-dr-RAMI40#RAMI_Hierarchy_Level_Dimension> .

<http://www.w3id.org/ecsel-dr-RAMI40#Enterprise> a <http://www.w3id.org/ecsel-dr-RAMI40#RAMI_Hierarchy_Level_Dimension> .

<http://www.w3id.org/ecsel-dr-RAMI40#Field_Device> a <http://www.w3id.org/ecsel-dr-RAMI40#RAMI_Hierarchy_Level_Dimension> .

<http://www.w3id.org/ecsel-dr-RAMI40#Product> a <http://www.w3id.org/ecsel-dr-RAMI40#RAMI_Hierarchy_Level_Dimension> .

<http://www.w3id.org/ecsel-dr-RAMI40#Station> a <http://www.w3id.org/ecsel-dr-RAMI40#RAMI_Hierarchy_Level_Dimension> .

<http://www.w3id.org/ecsel-dr-RAMI40#Work_Center> a <http://www.w3id.org/ecsel-dr-RAMI40#RAMI_Hierarchy_Level_Dimension> .

<http://www.w3id.org/ecsel-dr-PRIMA#ProjectStatus> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-PRIMA#Idea> a <http://www.w3id.org/ecsel-dr-PRIMA#ProjectStatus> .

<http://www.w3id.org/ecsel-dr-PRIMA#Implemented> a <http://www.w3id.org/ecsel-dr-PRIMA#ProjectStatus> .

<http://www.w3id.org/ecsel-dr-PRIMA#InPreperation> a <http://www.w3id.org/ecsel-dr-PRIMA#ProjectStatus> .

<http://www.w3id.org/ecsel-dr-PRIMA#OnHold> a <http://www.w3id.org/ecsel-dr-PRIMA#ProjectStatus> .

<http://www.w3id.org/ecsel-dr-PRIMA#Running> a <http://www.w3id.org/ecsel-dr-PRIMA#ProjectStatus> .

<http://www.w3id.org/ecsel-dr-PRIMA#Withdrawn> a <http://www.w3id.org/ecsel-dr-PRIMA#ProjectStatus> .

<http://www.w3id.org/ecsel-dr-RAMI40#Expression_Semantic> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-RAMI40#Confirmation> a <http://www.w3id.org/ecsel-dr-RAMI40#Expression_Semantic> .

<http://www.w3id.org/ecsel-dr-RAMI40#Measurement> a <http://www.w3id.org/ecsel-dr-RAMI40#Expression_Semantic> .

<http://www.w3id.org/ecsel-dr-RAMI40#Requirement> a <http://www.w3id.org/ecsel-dr-RAMI40#Expression_Semantic> .

<http://www.w3id.org/ecsel-dr-OM#Action> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-OM#Pull> a <http://www.w3id.org/ecsel-dr-OM#Action> .

<http://www.w3id.org/ecsel-dr-OM#Push> a <http://www.w3id.org/ecsel-dr-OM#Action> .

<http://www.w3id.org/ecsel-dr-OM#Reconfirm> a <http://www.w3id.org/ecsel-dr-OM#Action> .

<http://www.w3id.org/ecsel-dr-OOSMP#MainPowerDeviceType> a rdfs:Class ;
  rdfs:label "Main Power Device Type" ;
  rdfs:comment "Each motor control and drive solution has a main power device type. Main power device type can be an \"IGBT\", \"MOSFET\" or \"Relay\"." .

<http://www.w3id.org/ecsel-dr-OOSMP#IGBT_MainPowerDeviceType> a <http://www.w3id.org/ecsel-dr-OOSMP#MainPowerDeviceType> .

<http://www.w3id.org/ecsel-dr-OOSMP#MOSFET_MainPowerDeviceType> a <http://www.w3id.org/ecsel-dr-OOSMP#MainPowerDeviceType> .

<http://www.w3id.org/ecsel-dr-OOSMP#Relay_MainPowerDeviceType> a <http://www.w3id.org/ecsel-dr-OOSMP#MainPowerDeviceType> .

<http://www.w3id.org/ecsel-dr-RAMI40#View> a rdfs:Class ;
  rdfs:comment "Different views associated to the Administration Shell via the Submodels" .

<http://www.w3id.org/ecsel-dr-RAMI40#Construction> a <http://www.w3id.org/ecsel-dr-RAMI40#View> .

<http://www.w3id.org/ecsel-dr-RAMI40#Function> a <http://www.w3id.org/ecsel-dr-RAMI40#View> .

<http://www.w3id.org/ecsel-dr-RAMI40#Location> a <http://www.w3id.org/ecsel-dr-RAMI40#View> .

<http://www.w3id.org/ecsel-dr-RAMI40#Performance> a <http://www.w3id.org/ecsel-dr-RAMI40#View> .

<http://www.w3id.org/ecsel-dr-OOSMP#SensingType> a rdfs:Class ;
  rdfs:label "Sensing Type" ;
  rdfs:comment "The sensing type of a semiconductor solution determines whether a semiconductor solution contains a sensor (\"WithSensor\") or not (\"WithoutSensor)." .

<http://www.w3id.org/ecsel-dr-OOSMP#WithSensor_SensingType> a <http://www.w3id.org/ecsel-dr-OOSMP#SensingType> .

<http://www.w3id.org/ecsel-dr-OOSMP#WithoutSensor_SensingType> a <http://www.w3id.org/ecsel-dr-OOSMP#SensingType> .

<http://www.w3id.org/ecsel-dr-OOSMP#PriceIndication> a rdfs:Class ;
  rdfs:label "Price Indication" ;
  rdfs:comment "A price indication helps the customer to evaluate the price of an item. A price indication can be \"high\", \"low\", or \"medium\"." .

<http://www.w3id.org/ecsel-dr-OOSMP#HighPrice_PriceIndication> a <http://www.w3id.org/ecsel-dr-OOSMP#PriceIndication> .

<http://www.w3id.org/ecsel-dr-OOSMP#LowPrice_PriceIndication> a <http://www.w3id.org/ecsel-dr-OOSMP#PriceIndication> .

<http://www.w3id.org/ecsel-dr-OOSMP#MediumPrice_PriceIndication> a <http://www.w3id.org/ecsel-dr-OOSMP#PriceIndication> .

<http://www.w3id.org/ecsel-dr-OOSMP#Qualification> a rdfs:Class ;
  rdfs:label "Qualification" ;
  rdfs:comment "If a product/solution has a certain qualification, the product/solution fulfills the standards of this certain industry." .

<http://www.w3id.org/ecsel-dr-OOSMP#Automotive_Qualification> a <http://www.w3id.org/ecsel-dr-OOSMP#Qualification> .

<http://www.w3id.org/ecsel-dr-OOSMP#Industrial_Qualification> a <http://www.w3id.org/ecsel-dr-OOSMP#Qualification> .

<http://www.w3id.org/ecsel-dr-OOSMP#OPNStatus> a rdfs:Class ;
  rdfs:label "OPN Status" ;
  rdfs:comment "This status determines the OPN status of a product. The OPN status of a product can either be \"active\", \"active and preferred\", \"discontinued\" and \"not for new design\"." ;
  rdfs:subClassOf <http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProductStatus> .

<http://www.w3id.org/ecsel-dr-OOSMP#ActiveAndPreferred_OPNStatus> a <http://www.w3id.org/ecsel-dr-OOSMP#OPNStatus> .

<http://www.w3id.org/ecsel-dr-OOSMP#Active_OPNStatus> a <http://www.w3id.org/ecsel-dr-OOSMP#OPNStatus> .

<http://www.w3id.org/ecsel-dr-OOSMP#Discontinued_OPNStatus> a <http://www.w3id.org/ecsel-dr-OOSMP#OPNStatus> .

<http://www.w3id.org/ecsel-dr-OOSMP#NotForNewDesign_OPNStatus> a <http://www.w3id.org/ecsel-dr-OOSMP#OPNStatus> .

<http://www.w3id.org/ecsel-dr-OM#UserAction> a rdfs:Class .

<http://www.w3id.org/ecsel-dr-OM#Accepted> a <http://www.w3id.org/ecsel-dr-OM#UserAction> .

<http://www.w3id.org/ecsel-dr-OM#AcceptedWithChange> a <http://www.w3id.org/ecsel-dr-OM#UserAction> .

<http://www.w3id.org/ecsel-dr-OM#Rejected> a <http://www.w3id.org/ecsel-dr-OM#UserAction> .

<http://www.w3id.org/ecsel-dr-OOSMP#MotorType> a rdfs:Class ;
  rdfs:label "Motor Type" ;
  rdfs:comment "Each motor control and drive solution has a motor type. The different motor types that exist are \"brushed DC\", \"induction\", \"permanent magnet stepper\", \"PMSM BLDC\" and \"switched reluctance\"." .

<http://www.w3id.org/ecsel-dr-OOSMP#BrushedDC_MotorType> a <http://www.w3id.org/ecsel-dr-OOSMP#MotorType> .

<http://www.w3id.org/ecsel-dr-OOSMP#Induction_MotorType> a <http://www.w3id.org/ecsel-dr-OOSMP#MotorType> .

<http://www.w3id.org/ecsel-dr-OOSMP#PMSM_BLDC_MotorType> a <http://www.w3id.org/ecsel-dr-OOSMP#MotorType> .

<http://www.w3id.org/ecsel-dr-OOSMP#PermanentMagnetStepper_MotorType> a <http://www.w3id.org/ecsel-dr-OOSMP#MotorType> .

<http://www.w3id.org/ecsel-dr-OOSMP#SwitchedReluctance_MotorType> a <http://www.w3id.org/ecsel-dr-OOSMP#MotorType> .