@prefix : . @prefix dc: . @prefix org: . @prefix owl: . @prefix rdf: . @prefix xml: . @prefix xsd: . @prefix foaf: . @prefix rdfs: . @prefix skos: . @prefix swrl: . @prefix time: . @prefix vann: . @prefix swrlb: . @prefix terms: . @prefix schema: . @prefix ecsel-dr-AH: . @prefix ecsel-dr-AT: . @prefix ecsel-dr-PROD: . @prefix ecsel-dr-OOSMP: . @prefix ecsel-dr-RAMI40: . @base . rdf:type owl:Ontology ; dc:description "Holistic ontology that represents supply chains that manufacture semiconductors or use semiconductors as part of what they produce."@en ; dc:title "Digital Reference"@en ; terms:created "2019-11-07"@en ; terms:isVersionOf ; terms:modified "2019-11-29"@en ; terms:title "Digital Reference"@en ; vann:preferredNamespaceUri "http://www.w3id.org/ecsel-dr/" ; rdfs:label "Digital Reference"@en ; owl:versionInfo "Version 1.0"@en . ################################################################# # Annotation properties ################################################################# ### http://purl.org/dc/elements/1.1/description dc:description rdf:type owl:AnnotationProperty . ### http://purl.org/dc/elements/1.1/source dc:source rdf:type owl:AnnotationProperty . ### http://purl.org/dc/elements/1.1/title dc:title rdf:type owl:AnnotationProperty . ### http://purl.org/dc/terms/contributor terms:contributor rdf:type owl:AnnotationProperty . ### http://purl.org/dc/terms/created terms:created rdf:type owl:AnnotationProperty . ### http://purl.org/dc/terms/creator terms:creator rdf:type owl:AnnotationProperty . ### http://purl.org/dc/terms/description terms:description rdf:type owl:AnnotationProperty . ### http://purl.org/dc/terms/isVersionOf terms:isVersionOf rdf:type owl:AnnotationProperty . ### http://purl.org/dc/terms/license terms:license rdf:type owl:AnnotationProperty . ### http://purl.org/dc/terms/modified terms:modified rdf:type owl:AnnotationProperty . ### http://purl.org/dc/terms/rights terms:rights rdf:type owl:AnnotationProperty . ### http://purl.org/dc/terms/title terms:title rdf:type owl:AnnotationProperty . ### http://purl.org/vocab/vann/preferredNamespacePrefix vann:preferredNamespacePrefix rdf:type owl:AnnotationProperty . ### http://purl.org/vocab/vann/preferredNamespaceUri vann:preferredNamespaceUri rdf:type owl:AnnotationProperty . ### http://schema.org/domainIncludes schema:domainIncludes rdf:type owl:AnnotationProperty . ### http://schema.org/rangeIncludes schema:rangeIncludes rdf:type owl:AnnotationProperty . ### http://www.w3.org/2000/01/rdf-schema#comment rdfs:comment rdf:type owl:AnnotationProperty ; rdfs:comment "The definition or description of a concept" ; skos:prefLabel "Comment" ; rdfs:range xsd:string . ### http://www.w3.org/2000/01/rdf-schema#isDefinedBy rdfs:isDefinedBy rdf:type owl:AnnotationProperty ; rdfs:comment "Indicates that an instance is defined by an organization" , "Links an instance with an organization" ; skos:prefLabel "Is Defined By" ; rdfs:range org:Organization . ### http://www.w3.org/2000/01/rdf-schema#label rdfs:label rdfs:comment "Any name of a concept" ; skos:prefLabel "Label" ; rdfs:range xsd:string . ### http://www.w3.org/2001/XMLSchema#pattern xsd:pattern rdf:type owl:AnnotationProperty . ### http://www.w3.org/2004/02/skos/core#altLabel skos:altLabel rdf:type owl:AnnotationProperty ; rdfs:comment "The alternative name of a conept, e.g. a misspelled name, a concept can have one or more alternative names." ; skos:prefLabel "Alternative Label" ; ecsel-dr-OOSMP:abbreviation "altLabel" ; rdfs:subPropertyOf rdfs:label ; rdfs:range xsd:string . ### http://www.w3.org/2004/02/skos/core#changeNote skos:changeNote rdf:type owl:AnnotationProperty . ### http://www.w3.org/2004/02/skos/core#definition skos:definition rdf:type owl:AnnotationProperty . ### http://www.w3.org/2004/02/skos/core#editorialNote skos:editorialNote rdf:type owl:AnnotationProperty . ### http://www.w3.org/2004/02/skos/core#example skos:example rdf:type owl:AnnotationProperty . ### http://www.w3.org/2004/02/skos/core#hiddenLabel skos:hiddenLabel rdf:type owl:AnnotationProperty ; skos:prefLabel "Hidden Label" ; ecsel-dr-OOSMP:abbreviation "The hidden name of a conept, e.g. a misspelled name, a concept can have one or more hidden names." , "hiddenLabel" ; rdfs:subPropertyOf rdfs:label ; rdfs:range xsd:string . ### http://www.w3.org/2004/02/skos/core#historyNote skos:historyNote rdf:type owl:AnnotationProperty . ### http://www.w3.org/2004/02/skos/core#note skos:note rdf:type owl:AnnotationProperty . ### http://www.w3.org/2004/02/skos/core#preLabel skos:preLabel rdf:type owl:AnnotationProperty . ### http://www.w3.org/2004/02/skos/core#prefLabel skos:prefLabel rdf:type owl:AnnotationProperty ; rdfs:comment "The preferred and commonly used name of a conept, a concept can only have onepreferred name." ; skos:prefLabel "Preferred Label" ; ecsel-dr-OOSMP:abbreviation "prefLabel" ; rdfs:subPropertyOf rdfs:label ; rdfs:range xsd:string . ### http://www.w3.org/2004/02/skos/core#scopeNote skos:scopeNote rdf:type owl:AnnotationProperty . ### http://www.w3.org/2004/02/skos/core#semanticRelation skos:semanticRelation rdf:type owl:AnnotationProperty . ### http://www.w3id.org/ecsel-dr-OOSMP#abbreviation ecsel-dr-OOSMP:abbreviation rdf:type owl:AnnotationProperty ; rdfs:comment "Any abbreviation of a concept" ; skos:prefLabel "Abbreviation" ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OOSMP#identifier ecsel-dr-OOSMP:identifier rdf:type owl:AnnotationProperty ; rdfs:comment "Any identifier (ID) of a concept" ; skos:prefLabel "Identifier" ; ecsel-dr-OOSMP:abbreviation "ID" ; rdfs:range xsd:int , xsd:integer , xsd:string . ### http://www.w3id.org/ecsel-dr-OOSMP#identifier_organizationalUnit ecsel-dr-OOSMP:identifier_organizationalUnit rdf:type owl:AnnotationProperty ; rdfs:comment "Any identifier (ID) of an organizational unit" ; skos:prefLabel "Unit ID" ; ecsel-dr-OOSMP:abbreviation "ID" ; rdfs:subPropertyOf ecsel-dr-OOSMP:identifier ; rdfs:range xsd:int ; rdfs:domain org:OrganizationalUnit . ### http://www.w3id.org/ecsel-dr-OOSMP#identifier_product ecsel-dr-OOSMP:identifier_product rdf:type owl:AnnotationProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:identifier ; rdfs:range xsd:string ; rdfs:domain ecsel-dr-OOSMP:Product . ### http://www.w3id.org/ecsel-dr-OOSMP#identifier_product_internetSalesProductNumber ecsel-dr-OOSMP:identifier_product_internetSalesProductNumber rdf:type owl:AnnotationProperty ; rdfs:comment "The internet sales product number (ISPN) of a product" ; skos:prefLabel "Internet Sales Product Number" ; ecsel-dr-OOSMP:abbreviation "ISPN" ; rdfs:subPropertyOf ecsel-dr-OOSMP:identifier_product ; rdfs:range xsd:string ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct . ### http://www.w3id.org/ecsel-dr-OOSMP#identifier_product_orderablePartNumber ecsel-dr-OOSMP:identifier_product_orderablePartNumber rdf:type owl:AnnotationProperty ; rdfs:comment "The orderable part number (OPN) of a product" ; skos:prefLabel "Orderable Part Number" ; ecsel-dr-OOSMP:abbreviation "OPN" ; rdfs:subPropertyOf ecsel-dr-OOSMP:identifier_product ; rdfs:range xsd:string ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct . ### http://www.w3id.org/ecsel-dr-OOSMP#identifier_solution ecsel-dr-OOSMP:identifier_solution rdf:type owl:AnnotationProperty ; rdfs:comment "Any identifier (ID) of a solution" ; skos:prefLabel "Solution ID" ; ecsel-dr-OOSMP:abbreviation "ID" ; rdfs:subPropertyOf ecsel-dr-OOSMP:identifier ; rdfs:range xsd:string ; rdfs:domain ecsel-dr-OOSMP:Solution . ### http://www.w3id.org/ecsel-dr-OOSMP#uniformResourceLocator ecsel-dr-OOSMP:uniformResourceLocator rdf:type owl:AnnotationProperty ; rdfs:comment "A Uniform Resource Locator (URL) is an address that shows where a particular page can be found on the World Wide Web." ; skos:prefLabel "Uniform Resource Locator" ; ecsel-dr-OOSMP:abbreviation "URL" ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OOSMP#uniformResourceLocator_productDatasheet ecsel-dr-OOSMP:uniformResourceLocator_productDatasheet rdf:type owl:AnnotationProperty ; rdfs:comment "The uniform resource locator (URL) of the datasheet of a product" ; skos:prefLabel "Product Datasheet URL" ; ecsel-dr-OOSMP:abbreviation "URL" ; rdfs:subPropertyOf ecsel-dr-OOSMP:uniformResourceLocator ; rdfs:range xsd:string ; rdfs:domain ecsel-dr-OOSMP:Product . ### http://www.w3id.org/ecsel-dr-OOSMP#uniformResourceLocator_productPage ecsel-dr-OOSMP:uniformResourceLocator_productPage rdf:type owl:AnnotationProperty ; rdfs:comment "The uniform resource locator (URL) of the page of a product" ; skos:prefLabel "Product Page URL" ; ecsel-dr-OOSMP:abbreviation "URL" ; rdfs:subPropertyOf ecsel-dr-OOSMP:uniformResourceLocator ; rdfs:range xsd:string ; rdfs:domain ecsel-dr-OOSMP:Product . ### http://www.w3id.org/ecsel-dr-OOSMP#uniformResourceLocator_productPicture ecsel-dr-OOSMP:uniformResourceLocator_productPicture rdf:type owl:AnnotationProperty ; rdfs:comment "The uniform resource locator (URL) of the picture of a product" ; skos:prefLabel "Product Picture URL" ; ecsel-dr-OOSMP:abbreviation "URL" ; rdfs:subPropertyOf ecsel-dr-OOSMP:uniformResourceLocator ; rdfs:range xsd:string ; rdfs:domain ecsel-dr-OOSMP:Product . ### http://www.w3id.org/ecsel-dr-RAMI40#latestStardardVersion ecsel-dr-RAMI40:latestStardardVersion rdf:type owl:AnnotationProperty . ### http://xmlns.com/foaf/0.1/name foaf:name rdf:type owl:AnnotationProperty . ################################################################# # Datatypes ################################################################# ### http://www.w3.org/2001/XMLSchema#date xsd:date rdf:type rdfs:Datatype . ### http://www.w3.org/2001/XMLSchema#duration xsd:duration rdf:type rdfs:Datatype . ### http://www.w3.org/2001/XMLSchema#gDay xsd:gDay rdf:type rdfs:Datatype . ### http://www.w3.org/2001/XMLSchema#gMonth xsd:gMonth rdf:type rdfs:Datatype . ### http://www.w3.org/2001/XMLSchema#gYear xsd:gYear rdf:type rdfs:Datatype . ### http://www.w3.org/2001/XMLSchema#gYearMonth xsd:gYearMonth rdf:type rdfs:Datatype . ### http://www.w3.org/2006/time#generalDay time:generalDay rdf:type rdfs:Datatype ; 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 ; rdfs:label "Generalized day"@en ; skos:definition """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 time:generalMonth rdf:type rdfs:Datatype ; 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 ; rdfs:label "Generalized month"@en ; skos:definition """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 time:generalYear rdf:type rdfs:Datatype ; 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 ; rdfs:label "Generalized year"@en ; skos:definition """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 . ################################################################# # Object Properties ################################################################# ### http://www.w3.org/2006/time#after time:after rdf:type owl:ObjectProperty ; owl:inverseOf time:before ; rdfs:domain time:TemporalEntity ; rdfs:range time:TemporalEntity ; 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:label "after"@en ; skos:definition "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 . ### http://www.w3.org/2006/time#before time:before rdf:type owl:ObjectProperty , owl:TransitiveProperty ; rdfs:domain time:TemporalEntity ; rdfs:range time:TemporalEntity ; 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:label "before"@en ; skos:definition "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 . ### http://www.w3.org/2006/time#dayOfWeek time:dayOfWeek rdf:type owl:ObjectProperty ; rdfs:domain time:GeneralDateTimeDescription ; rdfs:range time:DayOfWeek ; rdfs:comment "The day of week, whose value is a member of the class time:DayOfWeek"@en ; rdfs:label "day of week"@en ; skos:definition "The day of week, whose value is a member of the class time:DayOfWeek"@en . ### http://www.w3.org/2006/time#hasBeginning time:hasBeginning rdf:type owl:ObjectProperty ; rdfs:subPropertyOf time:hasTime ; rdfs:domain time:TemporalEntity ; rdfs:range time:Instant ; rdfs:comment "Beginning of a temporal entity"@en ; rdfs:label "has beginning"@en ; skos:definition "Beginning of a temporal entity."@en . ### http://www.w3.org/2006/time#hasDateTimeDescription time:hasDateTimeDescription rdf:type owl:ObjectProperty ; rdfs:domain time:DateTimeInterval ; rdfs:range time:GeneralDateTimeDescription ; 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:label "has Date-Time description"@en ; skos:definition "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 . ### http://www.w3.org/2006/time#hasDuration time:hasDuration rdf:type owl:ObjectProperty ; rdfs:subPropertyOf time:hasTemporalDuration ; rdfs:range time:Duration ; rdfs:comment "Duration of a temporal entity, expressed as a scaled value or nominal value"@en ; rdfs:label "has duration"@en ; skos:definition "Duration of a temporal entity, event or activity, or thing, expressed as a scaled value"@en . ### http://www.w3.org/2006/time#hasDurationDescription time:hasDurationDescription rdf:type owl:ObjectProperty ; rdfs:subPropertyOf time:hasTemporalDuration ; rdfs:range time:GeneralDurationDescription ; rdfs:comment "Duration of a temporal entity, expressed using a structured description"@en ; rdfs:label "has duration description"@en ; skos:definition "Duration of a temporal entity, expressed using a structured description"@en . ### http://www.w3.org/2006/time#hasEnd time:hasEnd rdf:type owl:ObjectProperty ; rdfs:subPropertyOf time:hasTime ; rdfs:domain time:TemporalEntity ; rdfs:range time:Instant ; rdfs:comment "End of a temporal entity."@en ; rdfs:label "has end"@en ; skos:definition "End of a temporal entity."@en . ### http://www.w3.org/2006/time#hasTRS time:hasTRS rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( time:GeneralDurationDescription time:TemporalPosition ) ] ; rdfs:range time:TRS ; rdfs:comment "The temporal reference system used by a temporal position or extent description. "@en ; rdfs:label "Temporal reference system used"@en ; skos:definition "The temporal reference system used by a temporal position or extent description. "@en . ### http://www.w3.org/2006/time#hasTemporalDuration time:hasTemporalDuration rdf:type owl:ObjectProperty ; rdfs:domain time:TemporalEntity ; rdfs:range time:TemporalDuration ; rdfs:comment "Duration of a temporal entity."@en ; rdfs:label "has temporal duration"@en ; skos:definition "Duration of a temporal entity."@en . ### http://www.w3.org/2006/time#hasTime time:hasTime rdf:type owl:ObjectProperty ; rdfs:range time:TemporalEntity ; rdfs:comment "Supports the association of a temporal entity (instant or interval) to any thing"@en ; rdfs:label "has time"@en ; skos:definition "Supports the association of a temporal entity (instant or interval) to any thing"@en ; skos:editorialNote "Feature at risk - added in 2017 revision, and not yet widely used. "@en . ### http://www.w3.org/2006/time#inDateTime time:inDateTime rdf:type owl:ObjectProperty ; rdfs:subPropertyOf time:inTemporalPosition ; rdfs:domain time:Instant ; rdfs:range time:GeneralDateTimeDescription ; rdfs:comment "Position of an instant, expressed using a structured description"@en ; rdfs:label "in date-time description"@en ; skos:definition "Position of an instant, expressed using a structured description"@en . ### http://www.w3.org/2006/time#inTemporalPosition time:inTemporalPosition rdf:type owl:ObjectProperty ; rdfs:domain time:Instant ; rdfs:range time:TemporalPosition ; rdfs:comment "Position of a time instant"@en ; rdfs:label "Temporal position"@en ; skos:definition "Position of a time instant"@en . ### http://www.w3.org/2006/time#inTimePosition time:inTimePosition rdf:type owl:ObjectProperty ; rdfs:subPropertyOf time:inTemporalPosition ; rdfs:domain time:Instant ; rdfs:range time:TimePosition ; rdfs:comment "Position of an instant, expressed as a temporal coordinate or nominal value"@en ; rdfs:label "Time position"@en ; skos:definition "Position of a time instant expressed as a TimePosition"@en . ### http://www.w3.org/2006/time#inside time:inside rdf:type owl:ObjectProperty ; rdfs:domain time:Interval ; rdfs:range time:Instant ; rdfs:comment "An instant that falls inside the interval. It is not intended to include beginnings and ends of intervals."@en ; rdfs:label "has time instant inside"@en ; skos:definition "An instant that falls inside the interval. It is not intended to include beginnings and ends of intervals."@en . ### http://www.w3.org/2006/time#intervalAfter time:intervalAfter rdf:type owl:ObjectProperty ; rdfs:subPropertyOf time:after , time:intervalDisjoint ; owl:inverseOf time:intervalBefore ; rdfs:domain time:ProperInterval ; rdfs:range time:ProperInterval ; 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:label "interval after"@en ; skos:definition "If a proper interval T1 is intervalAfter another proper interval T2, then the beginning of T1 is after the end of T2."@en . ### http://www.w3.org/2006/time#intervalBefore time:intervalBefore rdf:type owl:ObjectProperty ; rdfs:subPropertyOf time:before , time:intervalDisjoint ; rdfs:domain time:ProperInterval ; rdfs:range time:ProperInterval ; 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:label "interval before"@en ; skos:definition "If a proper interval T1 is intervalBefore another proper interval T2, then the end of T1 is before the beginning of T2."@en . ### http://www.w3.org/2006/time#intervalContains time:intervalContains rdf:type owl:ObjectProperty ; owl:inverseOf time:intervalDuring ; rdfs:domain time:ProperInterval ; rdfs:range time:ProperInterval ; 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:label "interval contains"@en ; skos:definition "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 . ### http://www.w3.org/2006/time#intervalDisjoint time:intervalDisjoint rdf:type owl:ObjectProperty ; rdfs:domain time:ProperInterval ; rdfs:range time:ProperInterval ; 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:label "interval disjoint"@en ; skos:definition "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 ; skos:note "This interval relation is not included in the 13 basic relationships defined in Allen (1984), but is defined in (T.3) as the union of :intervalBefore v :intervalAfter . However, that is outside OWL2 expressivity, so is implemented as an explicit property, with :intervalBefore , :intervalAfter as sub-properties"@en . ### http://www.w3.org/2006/time#intervalDuring time:intervalDuring rdf:type owl:ObjectProperty ; rdfs:subPropertyOf time:intervalIn ; rdfs:domain time:ProperInterval ; rdfs:range time:ProperInterval ; 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:label "interval during"@en ; skos:definition "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 . ### http://www.w3.org/2006/time#intervalEquals time:intervalEquals rdf:type owl:ObjectProperty ; rdfs:domain time:ProperInterval ; rdfs:range time:ProperInterval ; owl:propertyDisjointWith time:intervalIn ; 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:label "interval equals"@en ; skos:definition "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 . ### http://www.w3.org/2006/time#intervalFinishedBy time:intervalFinishedBy rdf:type owl:ObjectProperty ; owl:inverseOf time:intervalFinishes ; rdfs:domain time:ProperInterval ; rdfs:range time:ProperInterval ; 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:label "interval finished by"@en ; skos:definition "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 . ### http://www.w3.org/2006/time#intervalFinishes time:intervalFinishes rdf:type owl:ObjectProperty ; rdfs:subPropertyOf time:intervalIn ; rdfs:domain time:ProperInterval ; rdfs:range time:ProperInterval ; 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:label "interval finishes"@en ; skos:definition "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 . ### http://www.w3.org/2006/time#intervalIn time:intervalIn rdf:type owl:ObjectProperty ; rdfs:domain time:ProperInterval ; rdfs:range time:ProperInterval ; 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:label "interval in"@en ; skos:definition "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 ; skos:note "This interval relation is not included in the 13 basic relationships defined in Allen (1984), but is referred to as 'an important relationship' in Allen and Ferguson (1997). It is the disjoint union of :intervalStarts v :intervalDuring v :intervalFinishes . However, that is outside OWL2 expressivity, so is implemented as an explicit property, with :intervalStarts , :intervalDuring , :intervalFinishes as sub-properties"@en . ### http://www.w3.org/2006/time#intervalMeets time:intervalMeets rdf:type owl:ObjectProperty ; owl:inverseOf time:intervalMetBy ; rdfs:domain time:ProperInterval ; rdfs:range time:ProperInterval ; 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:label "interval meets"@en ; skos:definition "If a proper interval T1 is intervalMeets another proper interval T2, then the end of T1 is coincident with the beginning of T2."@en . ### http://www.w3.org/2006/time#intervalMetBy time:intervalMetBy rdf:type owl:ObjectProperty ; rdfs:domain time:ProperInterval ; rdfs:range time:ProperInterval ; 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:label "interval met by"@en ; skos:definition "If a proper interval T1 is intervalMetBy another proper interval T2, then the beginning of T1 is coincident with the end of T2."@en . ### http://www.w3.org/2006/time#intervalOverlappedBy time:intervalOverlappedBy rdf:type owl:ObjectProperty ; owl:inverseOf time:intervalOverlaps ; rdfs:domain time:ProperInterval ; rdfs:range time:ProperInterval ; 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:label "interval overlapped by"@en ; skos:definition "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 . ### http://www.w3.org/2006/time#intervalOverlaps time:intervalOverlaps rdf:type owl:ObjectProperty ; rdfs:domain time:ProperInterval ; rdfs:range time:ProperInterval ; 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:label "interval overlaps"@en ; skos:definition "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 . ### http://www.w3.org/2006/time#intervalStartedBy time:intervalStartedBy rdf:type owl:ObjectProperty ; owl:inverseOf time:intervalStarts ; rdfs:domain time:ProperInterval ; rdfs:range time:ProperInterval ; 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:label "interval started by"@en ; skos:definition "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 . ### http://www.w3.org/2006/time#intervalStarts time:intervalStarts rdf:type owl:ObjectProperty ; rdfs:subPropertyOf time:intervalIn ; rdfs:domain time:ProperInterval ; rdfs:range time:ProperInterval ; 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:label "interval starts"@en ; skos:definition "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 . ### http://www.w3.org/2006/time#monthOfYear time:monthOfYear rdf:type owl:ObjectProperty ; rdfs:domain time:GeneralDateTimeDescription ; rdfs:range time:MonthOfYear ; rdfs:comment "The month of the year, whose value is a member of the class time:MonthOfYear"@en ; rdfs:label "month of year"@en ; skos:definition "The month of the year, whose value is a member of the class time:MonthOfYear"@en ; skos:editorialNote "Feature at risk - added in 2017 revision, and not yet widely used. "@en . ### http://www.w3.org/2006/time#timeZone time:timeZone rdf:type owl:ObjectProperty ; rdfs:domain time:GeneralDateTimeDescription ; rdfs:range time:TimeZone ; rdfs:comment "The time zone for clock elements in the temporal position"@en ; rdfs:label "in time zone"@en ; skos:historyNote """In the original 2006 version of OWL-Time, the range of time:timeZone was a TimeZone class in a separate namespace \"http://www.w3.org/2006/timezone#\". An alignment axiom tzont:TimeZone rdfs:subClassOf time:TimeZone . allows data encoded according to the previous version to be consistent with the updated ontology. """ ; skos:note """IANA maintains a database of timezones. These are well maintained and generally considered authoritative, but individual items are not available at individual URIs, so cannot be used directly in data expressed using OWL-Time. DBPedia provides a set of resources corresponding to the IANA timezones, with a URI for each (e.g. http://dbpedia.org/resource/Australia/Eucla). The World Clock service also provides a list of time zones with the description of each available as an individual webpage with a convenient individual URI (e.g. https://www.timeanddate.com/time/zones/acwst). These or other, similar, resources might be used as a value of the time:timeZone property.""" . ### http://www.w3.org/2006/time#unitType time:unitType rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( time:Duration time:GeneralDateTimeDescription ) ] ; rdfs:range time:TemporalUnit ; rdfs:comment "The temporal unit which provides the precision of a date-time value or scale of a temporal extent"@en ; rdfs:label "temporal unit type"@en . ### http://www.w3.org/TR/vocab-ssn-ext/hasMember rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range , ; rdfs:comment "Link to a member of a collection of observations that share the same value for one or more of the characteristic properties." . ### http://www.w3.org/TR/vocab-ssn-ext/hasUltimateFeatureOfInterest rdf:type owl:ObjectProperty ; rdfs:range ; 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." . ### http://www.w3.org/ns/org#hasUnit org:hasUnit rdf:type owl:ObjectProperty ; owl:inverseOf org:unitOf ; rdf:type owl:InverseFunctionalProperty ; rdfs:domain org:Organization ; rdfs:range org:OrganizationalUnit . ### http://www.w3.org/ns/org#unitOf org:unitOf rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain org:OrganizationalUnit ; rdfs:range org:Organization . ### http://www.w3.org/ns/sosa/actsOnProperty rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; schema:domainIncludes ; schema:rangeIncludes ; rdfs:comment "Relation between an Actuation and the property of a FeatureOfInterest it is acting upon."@en ; rdfs:isDefinedBy ; rdfs:label "acts on property"@en ; skos:definition "Relation between an Actuation and the property of a FeatureOfInterest it is acting upon."@en ; skos:example "In the activity (Actuation) of automatically closing a window if the temperature in a room drops below 20 degrees Celsius, the property on which the Actuator acts upon is the state of the window as it changes from being open to being closed. "@en . ### http://www.w3.org/ns/sosa/hasFeatureOfInterest rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain , , ; rdfs:range , ; schema:domainIncludes , , ; schema:rangeIncludes , ; 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:isDefinedBy ; rdfs:label "has feature of interest"@en ; skos:definition "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 ; skos:example "For example, in an Observation of the weight of a person, the FeatureOfInterest is the person and the property is its weight."@en . ### http://www.w3.org/ns/sosa/hasResult rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain , , ; rdfs:range , ; schema:domainIncludes , , ; schema:rangeIncludes , ; rdfs:comment "Relation linking an Observation or Actuation or act of Sampling and a Result or Sample."@en ; rdfs:isDefinedBy ; rdfs:label "has result"@en ; skos:definition "Relation linking an Observation or Actuation or act of Sampling and a Result or Sample."@en . ### http://www.w3.org/ns/sosa/hasSample rdf:type owl:ObjectProperty ; owl:inverseOf ; rdf:type owl:InverseFunctionalProperty ; rdfs:domain ; rdfs:range ; schema:domainIncludes ; schema:rangeIncludes ; rdfs:comment "Relation between a FeatureOfInterest and the Sample used to represent it."@en ; rdfs:isDefinedBy ; rdfs:label "has sample"@en ; skos:definition "Relation between a FeatureOfInterest and the Sample used to represent it."@en . ### http://www.w3.org/ns/sosa/hosts rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range , , , ; owl:propertyChainAxiom ( ) ; schema:domainIncludes ; schema:rangeIncludes , , , ; rdfs:comment "Relation between a Platform and a Sensor, Actuator, Sampler, or Platform, hosted or mounted on it."@en ; rdfs:isDefinedBy ; rdfs:label "hosts"@en ; skos:definition "Relation between a Platform and a Sensor, Actuator, Sampler, or Platform, hosted or mounted on it."@en . ### http://www.w3.org/ns/sosa/isActedOnBy rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; schema:domainIncludes ; schema:rangeIncludes ; rdfs:comment "Relation between an ActuatableProperty of a FeatureOfInterest and an Actuation changing its state."@en ; rdfs:isDefinedBy ; rdfs:label "is acted on by"@en ; skos:definition "Relation between an ActuatableProperty of a FeatureOfInterest and an Actuation changing its state."@en ; skos:example "In the activity (Actuation) of automatically closing a window if the temperature in a room drops below 20 degrees Celsius, the property on which the Actuator acts upon is the state of the window as it changes from being open to being closed. "@en . ### http://www.w3.org/ns/sosa/isFeatureOfInterestOf rdf:type owl:ObjectProperty ; rdfs:domain , ; rdfs:range , , ; schema:domainIncludes , ; schema:rangeIncludes , , ; 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:isDefinedBy ; rdfs:label "is feature of interest of"@en ; skos:definition "A relation between a FeatureOfInterest and an Observation about it, an Actuation acting on it, or an act of Sampling that sampled it."@en . ### http://www.w3.org/ns/sosa/isHostedBy rdf:type owl:ObjectProperty ; rdfs:domain , , , ; rdfs:range ; schema:domainIncludes , , , ; schema:rangeIncludes ; rdfs:comment "Relation between a Sensor, Actuator, Sampler, or Platform, and the Platform that it is mounted on or hosted by."@en ; rdfs:isDefinedBy ; rdfs:label "is hosted by"@en ; skos:definition "Relation between a Sensor, Actuator, Sampler, or Platform, and the Platform that it is mounted on or hosted by."@en . ### http://www.w3.org/ns/sosa/isObservedBy rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; schema:domainIncludes ; schema:rangeIncludes ; rdfs:comment "Relation between an ObservableProperty and the Sensor able to observe it."@en ; rdfs:isDefinedBy ; rdfs:label "is observed by"@en ; skos:definition "Relation between an ObservableProperty and the Sensor able to observe it."@en . ### http://www.w3.org/ns/sosa/isResultOf rdf:type owl:ObjectProperty ; rdfs:domain , ; rdfs:range , , ; schema:domainIncludes , ; schema:rangeIncludes , , ; rdfs:comment "Relation linking a Result to the Observation or Actuation or act of Sampling that created or caused it."@en ; rdfs:isDefinedBy ; rdfs:label "is result of"@en ; skos:definition "Relation linking a Result to the Observation or Actuation or act of Sampling that created or caused it."@en . ### http://www.w3.org/ns/sosa/isSampleOf rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; schema:domainIncludes ; schema:rangeIncludes ; rdfs:comment "Relation from a Sample to the FeatureOfInterest that it is intended to be representative of."@en ; rdfs:isDefinedBy ; rdfs:label "is sample of"@en ; skos:definition "Relation from a Sample to the FeatureOfInterest that it is intended to be representative of."@en . ### http://www.w3.org/ns/sosa/madeActuation rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; schema:domainIncludes ; schema:rangeIncludes ; rdfs:comment "Relation between an Actuator and the Actuation it has made."@en ; rdfs:isDefinedBy ; rdfs:label "made actuation"@en ; skos:definition "Relation between an Actuator and the Actuation it has made."@en . ### http://www.w3.org/ns/sosa/madeByActuator rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; schema:domainIncludes ; schema:rangeIncludes ; rdfs:comment "Relation linking an Actuation to the Actuator that made that Actuation."@en ; rdfs:isDefinedBy ; rdfs:label "made by actuator"@en ; skos:definition "Relation linking an Actuation to the Actuator that made that Actuation."@en . ### http://www.w3.org/ns/sosa/madeBySampler rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; schema:domainIncludes ; schema:rangeIncludes ; rdfs:comment "Relation linking an act of Sampling to the Sampler (sampling device or entity) that made it."@en ; rdfs:isDefinedBy ; rdfs:label "made by sampler"@en ; skos:definition "Relation linking an act of Sampling to the Sampler (sampling device or entity) that made it."@en . ### http://www.w3.org/ns/sosa/madeBySensor rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; schema:domainIncludes ; schema:rangeIncludes ; rdfs:comment "Relation between an Observation and the Sensor which made the Observation."@en ; rdfs:isDefinedBy ; rdfs:label "made by sensor"@en ; skos:definition "Relation between an Observation and the Sensor which made the Observation."@en . ### http://www.w3.org/ns/sosa/madeObservation rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; schema:domainIncludes ; schema:rangeIncludes ; rdfs:comment "Relation between a Sensor and an Observation made by the Sensor."@en ; rdfs:isDefinedBy ; rdfs:label "made observation"@en ; skos:definition "Relation between a Sensor and an Observation made by the Sensor."@en . ### http://www.w3.org/ns/sosa/madeSampling rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; schema:domainIncludes ; schema:rangeIncludes ; rdfs:comment "Relation between a Sampler (sampling device or entity) and the Sampling act it performed."@en ; rdfs:isDefinedBy ; rdfs:label "made sampling"@en ; skos:definition "Relation between a Sampler (sampling device or entity) and the Sampling act it performed."@en . ### http://www.w3.org/ns/sosa/observedProperty rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; schema:domainIncludes ; schema:rangeIncludes ; 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:isDefinedBy ; rdfs:label "observed property"@en ; skos:definition "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 . ### http://www.w3.org/ns/sosa/observes rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; schema:domainIncludes ; schema:rangeIncludes ; rdfs:comment "Relation between a Sensor and an ObservableProperty that it is capable of sensing."@en ; rdfs:isDefinedBy ; rdfs:label "observes"@en ; skos:definition "Relation between a Sensor and an ObservableProperty that it is capable of sensing."@en . ### http://www.w3.org/ns/sosa/phenomenonTime rdf:type owl:ObjectProperty ; rdfs:domain , , ; rdfs:range time:TemporalEntity ; schema:domainIncludes , , ; schema:rangeIncludes time:TemporalEntity ; 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:isDefinedBy ; rdfs:label "phenomenon time"@en ; skos:definition "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 . ### http://www.w3.org/ns/sosa/usedProcedure rdf:type owl:ObjectProperty ; rdfs:domain , , ; rdfs:range ; owl:propertyChainAxiom ( ) , ( ) , ( ) ; schema:domainIncludes , , ; schema:rangeIncludes ; 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:isDefinedBy ; rdfs:label "used procedure"@en ; skos:definition "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 . ### http://www.w3.org/ns/sosa/sampling/hasSampleRelationship rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "Links a sample to a Sample Relationship (which links to a related Sample)." ; rdfs:isDefinedBy "http://www.w3.org/ns/sosa/sampling/" ; rdfs:label "has sample relationship" . ### http://www.w3.org/ns/sosa/sampling/natureOfRelationship rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "Links a SampleRelationship to an indication of the nature of the relationship." ; rdfs:label "nature of relationship" . ### http://www.w3.org/ns/sosa/sampling/relatedSample rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "Links a SampleRelationship to the related Sample." ; rdfs:isDefinedBy "http://www.w3.org/ns/sosa/sampling/" ; rdfs:label "related sample" . ### http://www.w3.org/ns/ssn/deployedOnPlatform rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment "Relation between a Deployment and the Platform on which the Systems are deployed."@en ; rdfs:isDefinedBy ; rdfs:label "deployed on platform"@en ; skos:definition "Relation between a Deployment and the Platform on which the Systems are deployed."@en . ### http://www.w3.org/ns/ssn/deployedSystem rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment "Relation between a Deployment and a deployed System."@en ; rdfs:isDefinedBy ; rdfs:label "deployed system"@en ; skos:definition "Relation between a Deployment and a deployed System."@en . ### http://www.w3.org/ns/ssn/detects rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; 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:isDefinedBy ; rdfs:label "detects"@en ; skos:definition "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 . ### http://www.w3.org/ns/ssn/forProperty rdf:type owl:ObjectProperty ; rdfs:range ; rdfs:comment "A relation between some aspect of an entity and a Property."@en ; rdfs:isDefinedBy ; rdfs:label "for property"@en ; skos:definition "A relation between some aspect of an entity and a Property."@en ; skos:example "For example, from a Sensor to the properties it can observe; from an Actuator to the properties it can act on; from a Deployment to the properties it was installed to observe or act on; from a SystemCapability to the Property the capability is described for."@en . ### http://www.w3.org/ns/ssn/hasDeployment rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "Relation between a System and a Deployment, recording that the System is deployed in that Deployment."@en ; rdfs:isDefinedBy ; rdfs:label "has deployment"@en ; skos:definition "Relation between a System and a Deployment, recording that the System is deployed in that Deployment."@en . ### http://www.w3.org/ns/ssn/hasInput rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "Relation between a Procedure and an Input to it."@en ; rdfs:isDefinedBy ; rdfs:label "has input"@en ; skos:definition "Relation between a Procedure and an Input to it."@en . ### http://www.w3.org/ns/ssn/hasOutput rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "Relation between a Procedure and an Output of it."@en ; rdfs:isDefinedBy ; rdfs:label "has output"@en ; skos:definition "Relation between a Procedure and an Output of it."@en . ### http://www.w3.org/ns/ssn/hasProperty rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:range ; rdfs:comment "Relation between an entity and a Property of that entity."@en ; rdfs:isDefinedBy ; rdfs:label "has property"@en ; skos:definition "Relation between an entity and a Property of that entity."@en . ### http://www.w3.org/ns/ssn/hasSubSystem rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "Relation between a System and its component parts."@en ; rdfs:isDefinedBy ; rdfs:label "has subsystem"@en ; skos:definition "Relation between a System and its component parts."@en . ### http://www.w3.org/ns/ssn/implementedBy rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:comment "Relation between a Procedure (an algorithm, procedure or method) and an entity that implements that Procedure in some executable way."@en ; rdfs:isDefinedBy ; rdfs:label "implemented by"@en ; skos:definition "Relation between a Procedure (an algorithm, procedure or method) and an entity that implements that Procedure in some executable way."@en ; skos:example "For example, the relationship between a scientific measuring Procedure and a sensor that senses via that Procedure."@en . ### http://www.w3.org/ns/ssn/implements rdf:type owl:ObjectProperty ; rdfs:range ; rdfs:comment "Relation between an entity that implements a Procedure in some executable way and the Procedure (an algorithm, procedure or method)."@en ; rdfs:isDefinedBy ; rdfs:label "implements"@en ; skos:definition "Relation between an entity that implements a Procedure in some executable way and the Procedure (an algorithm, procedure or method)."@en ; skos:example "For example, the relationship between a sensor and the scientific measuring Procedure via which it senses."@en . ### http://www.w3.org/ns/ssn/inDeployment rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "Relation between a Platform and a Deployment, meaning that the deployedSystems of the Deployment are hosted on the Platform."@en ; rdfs:isDefinedBy ; rdfs:label "in deployment"@en ; skos:definition "Relation between a Platform and a Deployment, meaning that the deployedSystems of the Deployment are hosted on the Platform."@en ; skos:example "For example, a relation between a buoy and a deployment of several Sensors."@en . ### http://www.w3.org/ns/ssn/isPropertyOf rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:comment "Relation between a Property and the entity it belongs to."@en ; rdfs:isDefinedBy ; rdfs:label "is property of"@en ; skos:definition "Relation between a Property and the entity it belongs to."@en . ### http://www.w3.org/ns/ssn/isProxyFor rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "A relation from a Stimulus to the Property that the Stimulus is serving as a proxy for."@en ; rdfs:isDefinedBy ; rdfs:label "is proxy for"@en ; skos:definition "A relation from a Stimulus to the Property that the Stimulus is serving as a proxy for."@en ; skos:example "For example, the expansion of quicksilver is a stimulus that serves as a proxy for some temperature property. An increase or decrease in the velocity of spinning cups on a wind sensor is serving as a proxy for the wind speed."@en . ### http://www.w3.org/ns/ssn/oversamplingUsed rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "Link to the oversampling rate." ; rdfs:label "oversampling used" . ### http://www.w3.org/ns/ssn/wasOriginatedBy rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "Relation between an Observation and the Stimulus that originated it."@en ; rdfs:isDefinedBy ; rdfs:label "was originated by"@en ; skos:definition "Relation between an Observation and the Stimulus that originated it."@en . ### http://www.w3.org/ns/ssn/systems/hasOperatingProperty rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "Relation from an OperatingRange of a System to an OperatingProperty describing the operating range of the System." ; rdfs:isDefinedBy ; rdfs:label "has operating property" . ### http://www.w3.org/ns/ssn/systems/hasOperatingRange rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "Relation from a System to an OperatingRange describing the normal operating environment of the System." ; rdfs:isDefinedBy ; rdfs:label "has operating range" . ### http://www.w3.org/ns/ssn/systems/hasSurvivalProperty rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "Relation from a SurvivalRange of a System to a SurvivalProperty describing the survival range of the System." ; rdfs:isDefinedBy ; rdfs:label "has survival property" . ### http://www.w3.org/ns/ssn/systems/hasSurvivalRange rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "Relation from a System to SurvivalRange." ; rdfs:isDefinedBy ; rdfs:label "has survival range" . ### http://www.w3.org/ns/ssn/systems/hasSystemCapability rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "Relation from a System to a SystemCapability describing the capabilities of the System under certain Conditions." ; rdfs:isDefinedBy ; rdfs:label "has system capability" . ### http://www.w3.org/ns/ssn/systems/hasSystemProperty rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "Relation from a SystemCapability of a System to a SystemProperty describing the capabilities of the System." ; rdfs:isDefinedBy ; rdfs:label "has system property" . ### http://www.w3.org/ns/ssn/systems/inCondition rdf:type owl:ObjectProperty ; rdfs:domain , , ; rdfs:range ; rdfs:comment "Describes the prevailing environmental Conditions for SystemCapabilities, OperatingRanges and SurvivalRanges." ; rdfs:isDefinedBy ; rdfs:label "in condition" ; skos:example "Used for example to say that a Sensor has a particular accuracy in particular Conditions." . ### http://www.w3.org/ns/ssn/systems/qualityOfObservation rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; 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:isDefinedBy ; rdfs:label "quality of observation" . ### http://www.w3id.org/ecsel-dr-AH#containsDevice ecsel-dr-AH:containsDevice rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:hasArchitecturalPart ; owl:inverseOf ecsel-dr-AH:isDeviceIn ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AH:AH_local_cloud ecsel-dr-AH:Local_network ) ] ; rdfs:range ecsel-dr-AH:Device . ### http://www.w3id.org/ecsel-dr-AH#definesCompliantDocumentation ecsel-dr-AH:definesCompliantDocumentation rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-AH:Service-oriented_Architecture ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AH:Service_documentation ecsel-dr-AH:System_documentation ) ] . ### http://www.w3id.org/ecsel-dr-AH#definesCompliantService ecsel-dr-AH:definesCompliantService rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-AH:Service-oriented_Architecture ; rdfs:range ecsel-dr-AH:Service . ### http://www.w3id.org/ecsel-dr-AH#definesCompliantSystem ecsel-dr-AH:definesCompliantSystem rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-AH:Service-oriented_Architecture ; rdfs:range ecsel-dr-AH:Software_system . ### http://www.w3id.org/ecsel-dr-AH#definesCompliantSystemArchitecture ecsel-dr-AH:definesCompliantSystemArchitecture rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-AH:Service-oriented_Architecture ; rdfs:range ecsel-dr-AH:System-of-Systems . ### http://www.w3id.org/ecsel-dr-AH#documents ecsel-dr-AH:documents rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-AH:isDocumentedBy ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AH:Service_documentation ecsel-dr-AH:System_documentation ) ] ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AH:Service ecsel-dr-AH:Software_system ecsel-dr-AH:System-of-Systems ) ] . ### http://www.w3id.org/ecsel-dr-AH#documentsAHServiceCommSecurityMechanism ecsel-dr-AH:documentsAHServiceCommSecurityMechanism rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:documentsAHServiceCommTech ; rdf:type owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AH:Communication_Profile_CP ecsel-dr-AH:Interface_Design_Description_IDD ) ] ; rdfs:range ecsel-dr-AH:Communication_security_mechanism . ### http://www.w3id.org/ecsel-dr-AH#documentsAHServiceCommTech ecsel-dr-AH:documentsAHServiceCommTech rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:documentsServicePart ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AH:Communication_Profile_CP ecsel-dr-AH:Interface_Design_Description_IDD ) ] ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AH:Communication_security_mechanism ecsel-dr-AH:Data_format ecsel-dr-AH:Transfer_protocol ) ] . ### http://www.w3id.org/ecsel-dr-AH#documentsAHServiceDataFormat ecsel-dr-AH:documentsAHServiceDataFormat rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:documentsAHServiceCommTech ; rdf:type owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AH:Communication_Profile_CP ecsel-dr-AH:Interface_Design_Description_IDD ) ] ; rdfs:range ecsel-dr-AH:Data_format . ### http://www.w3id.org/ecsel-dr-AH#documentsAHServiceInformationModel ecsel-dr-AH:documentsAHServiceInformationModel rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:documentsServicePart ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AH:Interface_Design_Description_IDD ecsel-dr-AH:Semantic_Profile_SP ) ] ; rdfs:range ecsel-dr-AH:InformationModel . ### http://www.w3id.org/ecsel-dr-AH#documentsAHServiceMethod ecsel-dr-AH:documentsAHServiceMethod rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:documentsServicePart ; rdfs:domain ecsel-dr-AH:Interface_Design_Description_IDD ; rdfs:range ecsel-dr-AH:Method ; 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 . ### http://www.w3id.org/ecsel-dr-AH#documentsAHServiceTransferProtocol ecsel-dr-AH:documentsAHServiceTransferProtocol rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:documentsAHServiceCommTech ; rdf:type owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AH:Communication_Profile_CP ecsel-dr-AH:Interface_Design_Description_IDD ) ] ; rdfs:range ecsel-dr-AH:Transfer_protocol . ### http://www.w3id.org/ecsel-dr-AH#documentsServicePart ecsel-dr-AH:documentsServicePart rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-AH:Documentation_document . ### http://www.w3id.org/ecsel-dr-AH#hasArchitecturalPart ecsel-dr-AH:hasArchitecturalPart rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-AH:isArchitecturalPartOf . ### http://www.w3id.org/ecsel-dr-AH#hasInformationModel ecsel-dr-AH:hasInformationModel rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-AH:isInformationModelOf ; rdfs:domain ecsel-dr-AH:Service ; rdfs:range ecsel-dr-AH:InformationModel . ### http://www.w3id.org/ecsel-dr-AH#hasMethod ecsel-dr-AH:hasMethod rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:hasArchitecturalPart ; owl:inverseOf ecsel-dr-AH:isMethodOf ; rdfs:domain ecsel-dr-AH:Service ; rdfs:range ecsel-dr-AH:Method . ### http://www.w3id.org/ecsel-dr-AH#hasPart ecsel-dr-AH:hasPart rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-AH:isPartOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AH:Service_documentation ecsel-dr-AH:System_documentation ) ] ; rdfs:range ecsel-dr-AH:Documentation_document . ### http://www.w3id.org/ecsel-dr-AH#hasProperty ecsel-dr-AH:hasProperty rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-AH:isPropertyOf ; rdfs:domain ecsel-dr-AH:Service-oriented_Architecture ; rdfs:range ecsel-dr-AH:SoA_property . ### http://www.w3id.org/ecsel-dr-AH#hosts ecsel-dr-AH:hosts rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:hasArchitecturalPart ; owl:inverseOf ecsel-dr-AH:isHostedBy , ecsel-dr-AH:runsOn ; rdfs:domain ecsel-dr-AH:Device ; rdfs:range ecsel-dr-AH:Software_system . ### http://www.w3id.org/ecsel-dr-AH#isAHServiceDocumentedBy ecsel-dr-AH:isAHServiceDocumentedBy rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:isServiceDocumentedBy ; rdfs:domain ecsel-dr-AH:AH_service ; rdfs:range ecsel-dr-AH:AH_service_documentation . ### http://www.w3id.org/ecsel-dr-AH#isAHSystemDocumentedBy ecsel-dr-AH:isAHSystemDocumentedBy rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:isSystemDocumentedBy ; rdfs:domain ecsel-dr-AH:AH_system ; rdfs:range ecsel-dr-AH:AH_system_documentation . ### http://www.w3id.org/ecsel-dr-AH#isArchitecturalPartOf ecsel-dr-AH:isArchitecturalPartOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-AH#isDeviceIn ecsel-dr-AH:isDeviceIn rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:isArchitecturalPartOf ; rdfs:domain ecsel-dr-AH:Device ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AH:AH_local_cloud ecsel-dr-AH:Local_network ) ] . ### http://www.w3id.org/ecsel-dr-AH#isDocumentedBy ecsel-dr-AH:isDocumentedBy rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AH:Service ecsel-dr-AH:Software_system ecsel-dr-AH:System-of-Systems ) ] ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AH:Service_documentation ecsel-dr-AH:System_documentation ) ] . ### http://www.w3id.org/ecsel-dr-AH#isHostedBy ecsel-dr-AH:isHostedBy rdf:type owl:ObjectProperty ; owl:equivalentProperty ecsel-dr-AH:runsOn ; rdfs:subPropertyOf ecsel-dr-AH:isArchitecturalPartOf ; rdfs:domain ecsel-dr-AH:Software_system ; rdfs:range ecsel-dr-AH:Device . ### http://www.w3id.org/ecsel-dr-AH#isInformationModelOf ecsel-dr-AH:isInformationModelOf rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-AH:InformationModel ; rdfs:range ecsel-dr-AH:Service . ### http://www.w3id.org/ecsel-dr-AH#isMethodOf ecsel-dr-AH:isMethodOf rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:isArchitecturalPartOf ; rdfs:domain ecsel-dr-AH:Method ; rdfs:range ecsel-dr-AH:Service . ### http://www.w3id.org/ecsel-dr-AH#isPartOf ecsel-dr-AH:isPartOf rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-AH:Documentation_document ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AH:Service_documentation ecsel-dr-AH:System_documentation ) ] . ### http://www.w3id.org/ecsel-dr-AH#isPartOfServiceDoc ecsel-dr-AH:isPartOfServiceDoc rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:isPartOf ; rdfs:domain ecsel-dr-AH:AH_service_documentation_document ; rdfs:range ecsel-dr-AH:AH_service_documentation . ### http://www.w3id.org/ecsel-dr-AH#isPartOfSoSDoc ecsel-dr-AH:isPartOfSoSDoc rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:isPartOf ; rdfs:domain ecsel-dr-AH:AH_system_of_systems_documentation_document ; rdfs:range ecsel-dr-AH:AH_system_of_systems_documentation . ### http://www.w3id.org/ecsel-dr-AH#isPartOfSystemDoc ecsel-dr-AH:isPartOfSystemDoc rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:isPartOf ; rdfs:domain ecsel-dr-AH:AH_system_documentation_document ; rdfs:range ecsel-dr-AH:AH_system_documentation . ### http://www.w3id.org/ecsel-dr-AH#isPropertyOf ecsel-dr-AH:isPropertyOf rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-AH:SoA_property ; rdfs:range ecsel-dr-AH:Service-oriented_Architecture . ### http://www.w3id.org/ecsel-dr-AH#isReferredToBy ecsel-dr-AH:isReferredToBy rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-AH:refersTo ; rdfs:domain ecsel-dr-AH:Documentation_document ; rdfs:range ecsel-dr-AH:Documentation_document . ### http://www.w3id.org/ecsel-dr-AH#isServiceDocumentedBy ecsel-dr-AH:isServiceDocumentedBy rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:isDocumentedBy ; rdfs:domain ecsel-dr-AH:Service ; rdfs:range ecsel-dr-AH:Service_documentation . ### http://www.w3id.org/ecsel-dr-AH#isServiceProducerOf ecsel-dr-AH:isServiceProducerOf rdf:type owl:ObjectProperty ; owl:equivalentProperty ecsel-dr-AH:produces ; owl:inverseOf ecsel-dr-AH:producedBy ; rdfs:domain ecsel-dr-AH:Software_system ; rdfs:range ecsel-dr-AH:Service . ### http://www.w3id.org/ecsel-dr-AH#isSystemDocumentedBy ecsel-dr-AH:isSystemDocumentedBy rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:isDocumentedBy ; rdfs:domain ecsel-dr-AH:Software_system ; rdfs:range ecsel-dr-AH:System_documentation . ### http://www.w3id.org/ecsel-dr-AH#producedBy ecsel-dr-AH:producedBy rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:isArchitecturalPartOf ; owl:inverseOf ecsel-dr-AH:produces ; rdfs:domain ecsel-dr-AH:Service ; rdfs:range ecsel-dr-AH:Software_system . ### http://www.w3id.org/ecsel-dr-AH#produces ecsel-dr-AH:produces rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:hasArchitecturalPart ; rdfs:domain ecsel-dr-AH:Software_system ; rdfs:range ecsel-dr-AH:Service ; 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 . ### http://www.w3id.org/ecsel-dr-AH#refersTo ecsel-dr-AH:refersTo rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-AH:Documentation_document ; rdfs:range ecsel-dr-AH:Documentation_document ; 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 . ### http://www.w3id.org/ecsel-dr-AH#refersToCP ecsel-dr-AH:refersToCP rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:refersTo ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-AH:Interface_Design_Description_IDD ; rdfs:range ecsel-dr-AH:Communication_Profile_CP ; 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 . ### http://www.w3id.org/ecsel-dr-AH#refersToIDD ecsel-dr-AH:refersToIDD rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:refersTo ; rdfs:domain ecsel-dr-AH:System_Description_SySD ; rdfs:range ecsel-dr-AH:Interface_Design_Description_IDD . ### http://www.w3id.org/ecsel-dr-AH#refersToSD ecsel-dr-AH:refersToSD rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:refersTo ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-AH:Interface_Design_Description_IDD ; rdfs:range ecsel-dr-AH:Service_Description_SD . ### http://www.w3id.org/ecsel-dr-AH#refersToSP ecsel-dr-AH:refersToSP rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:refersTo ; rdfs:domain ecsel-dr-AH:Interface_Design_Description_IDD ; rdfs:range ecsel-dr-AH:Semantic_Profile_SP ; 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 . ### http://www.w3id.org/ecsel-dr-AH#refersToSoSD ecsel-dr-AH:refersToSoSD rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:refersTo ; rdfs:domain ecsel-dr-AH:System-of-Systems_Design_Description_SoSDD ; rdfs:range ecsel-dr-AH:System-of-Systems_Description_SoSD . ### http://www.w3id.org/ecsel-dr-AH#refersToSySD ecsel-dr-AH:refersToSySD rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:refersTo ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AH:System-of-Systems_Description_SoSD ecsel-dr-AH:System-of-Systems_Design_Description_SoSDD ecsel-dr-AH:System_Design_Description_SySDD ) ] ; rdfs:range ecsel-dr-AH:System_Description_SySD . ### http://www.w3id.org/ecsel-dr-AH#refersToSySDD ecsel-dr-AH:refersToSySDD rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:refersTo ; rdfs:domain ecsel-dr-AH:System-of-Systems_Design_Description_SoSDD ; rdfs:range ecsel-dr-AH:System_Design_Description_SySDD . ### http://www.w3id.org/ecsel-dr-AH#runsOn ecsel-dr-AH:runsOn rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-AH:Software_system ; rdfs:range ecsel-dr-AH:Device . ### http://www.w3id.org/ecsel-dr-AH#usesCommTech ecsel-dr-AH:usesCommTech rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-AH:Service ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AH:Communication_technology ecsel-dr-AH:Data_format ) ] . ### http://www.w3id.org/ecsel-dr-AH#usesDataFormat ecsel-dr-AH:usesDataFormat rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:usesCommTech ; rdfs:domain ecsel-dr-AH:Service ; rdfs:range ecsel-dr-AH:Data_format . ### http://www.w3id.org/ecsel-dr-AH#usesSecurityMechanism ecsel-dr-AH:usesSecurityMechanism rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:usesCommTech ; rdfs:domain ecsel-dr-AH:Service ; rdfs:range ecsel-dr-AH:Communication_security_mechanism . ### http://www.w3id.org/ecsel-dr-AH#usesTransferProtocol ecsel-dr-AH:usesTransferProtocol rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-AH:usesCommTech ; rdfs:domain ecsel-dr-AH:Service ; rdfs:range ecsel-dr-AH:Transfer_protocol . ### http://www.w3id.org/ecsel-dr-AT#belongsToISA-95-Layer ecsel-dr-AT:belongsToISA-95-Layer rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-AT:IT-System ; rdfs:range ecsel-dr-AT:ISA-95_Layer . ### http://www.w3id.org/ecsel-dr-AT#containsOSILayer ecsel-dr-AT:containsOSILayer rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-AT:OSI_AggregatedLayer ; rdfs:range ecsel-dr-AT:OSI_DetailedLayer . ### http://www.w3id.org/ecsel-dr-AT#dataTransmissionUnitOf ecsel-dr-AT:dataTransmissionUnitOf rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-AT:hasDataTransmissionUnit ; rdfs:domain ecsel-dr-AT:DataTransmissionUnit ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AT:OSI_AggregatedLayer ecsel-dr-AT:OSI_DetailedLayer ) ] . ### http://www.w3id.org/ecsel-dr-AT#has-IT-ModuleOrPart ecsel-dr-AT:has-IT-ModuleOrPart rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-AT:isPartOf-IT-Suite ; rdfs:domain ecsel-dr-AT:IT-System ; rdfs:range ecsel-dr-AT:IT-System . ### http://www.w3id.org/ecsel-dr-AT#hasCommunicationDevice ecsel-dr-AT:hasCommunicationDevice rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-AT:isDeviceOfOSILayer . ### http://www.w3id.org/ecsel-dr-AT#hasDataTransmissionUnit ecsel-dr-AT:hasDataTransmissionUnit rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AT:OSI_AggregatedLayer ecsel-dr-AT:OSI_DetailedLayer ) ] ; rdfs:range ecsel-dr-AT:DataTransmissionUnit . ### http://www.w3id.org/ecsel-dr-AT#hasImplementationTechnology ecsel-dr-AT:hasImplementationTechnology rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-AT:implementsOSILayer . ### http://www.w3id.org/ecsel-dr-AT#hasServiceDescriptionLanguage ecsel-dr-AT:hasServiceDescriptionLanguage rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-AT:isServiceDescriptionLanguageOf ; rdfs:domain ecsel-dr-AT:ServiceOrientedArchitecture ; rdfs:range ecsel-dr-AT:W3C_L5_DataSemantics . ### http://www.w3id.org/ecsel-dr-AT#hasVendor ecsel-dr-AT:hasVendor rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-AT:isVendorOf ; rdfs:domain ecsel-dr-AT:IT-System ; rdfs:range ecsel-dr-AT:IT-Vendor . ### http://www.w3id.org/ecsel-dr-AT#implementsOSILayer ecsel-dr-AT:implementsOSILayer rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AT:OSI_1_2_NetAccessTechnology ecsel-dr-AT:OSI_3_4_NetworkTechnology ecsel-dr-AT:OSI_5_7_ApplicationProtocol ) ] ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AT:OSI_AggregatedLayer ecsel-dr-AT:OSI_DetailedLayer ) ] . ### http://www.w3id.org/ecsel-dr-AT#isDeviceOfOSILayer ecsel-dr-AT:isDeviceOfOSILayer rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AT:CommunicationDevice ecsel-dr-AT:Computer ) ] ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AT:OSI_AggregatedLayer ecsel-dr-AT:OSI_DetailedLayer ) ] . ### http://www.w3id.org/ecsel-dr-AT#isPartOf-IT-Suite ecsel-dr-AT:isPartOf-IT-Suite rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-AT:IT-System ; rdfs:range ecsel-dr-AT:IT-System . ### http://www.w3id.org/ecsel-dr-AT#isServiceDescriptionLanguageOf ecsel-dr-AT:isServiceDescriptionLanguageOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-AT#isVendorOf ecsel-dr-AT:isVendorOf rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-AT:IT-Vendor ; rdfs:range ecsel-dr-AT:IT-System . ### http://www.w3id.org/ecsel-dr-AT#standardOf ecsel-dr-AT:standardOf rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-AT:standardizedBy ; rdfs:domain ecsel-dr-AT:Standard ; rdfs:range owl:Thing . ### http://www.w3id.org/ecsel-dr-AT#standardizedBy ecsel-dr-AT:standardizedBy rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-AT#supportedByTechnologyOrProtocol ecsel-dr-AT:supportedByTechnologyOrProtocol rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-AT:usedInISA-95_Communication . ### http://www.w3id.org/ecsel-dr-AT#usedInISA-95_Communication ecsel-dr-AT:usedInISA-95_Communication rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AT:OSI_1_2_NetAccessTechnology ecsel-dr-AT:OSI_3_4_NetworkTechnology ecsel-dr-AT:OSI_5_7_ApplicationProtocol ecsel-dr-AT:ServiceOrientedArchitecture ) ] ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-AT:ISA-95_Communication ecsel-dr-AT:ISA-95_CrossLayerCommunication ) ] . ### http://www.w3id.org/ecsel-dr-AT#usedInISA-95_Layer ecsel-dr-AT:usedInISA-95_Layer rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-AT:Device ; rdfs:range ecsel-dr-AT:ISA-95_Layer . ### http://www.w3id.org/ecsel-dr-OM#Allocates rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#belongsToOpenOrder rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#consistsOfOrderLineItem rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#consitsOfOpenOrder rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; owl:inverseOf . ### http://www.w3id.org/ecsel-dr-OM#containsContactPersonData rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#containsCustomerData rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#containsCustomerPlantData rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#containsOrderLineItem rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#containsSupplierData rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#describesCustomer rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; owl:inverseOf ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#describesCustomerPlant rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; owl:inverseOf ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#describesSupplier rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; owl:inverseOf ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#hasAllocated rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#isAllocatedBy rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#isAllocatedTo rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#isDeliveredToCustomerPlant rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#isDescribedByCustomerData rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty . ### http://www.w3id.org/ecsel-dr-OM#isDescribedByCustomerPlantData rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty . ### http://www.w3id.org/ecsel-dr-OM#isDescribedBySupplierData rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty . ### http://www.w3id.org/ecsel-dr-OM#isOwnedByCustomer rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; owl:inverseOf . ### http://www.w3id.org/ecsel-dr-OM#isPartOfOpenOrder rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty . ### http://www.w3id.org/ecsel-dr-OM#isPartOfOpenOrderBook rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#isReconciledOrderChangeRequest rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdf:type owl:FunctionalProperty , owl:InverseFunctionalProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#isReconciledOrderLineItem rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdf:type owl:FunctionalProperty , owl:InverseFunctionalProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#isRequestedByCustomer rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; owl:inverseOf ; rdf:type owl:FunctionalProperty . ### http://www.w3id.org/ecsel-dr-OM#ownsCustomerPlant rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#requestsOrderChangeRequest rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#requiresAction rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OM#requiresUserAction rdf:type owl:ObjectProperty ; rdfs:subPropertyOf owl:topObjectProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-OOSMP#OPNStatusOf ecsel-dr-OOSMP:OPNStatusOf rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:semiconductorProductStatusOf ; owl:inverseOf ecsel-dr-OOSMP:hasOPNStatus ; rdf:type owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:OPNStatus ; rdfs:range ecsel-dr-OOSMP:SemiconductorProduct . ### http://www.w3id.org/ecsel-dr-OOSMP#RoHSCompliantStatusOf ecsel-dr-OOSMP:RoHSCompliantStatusOf rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:semiconductorProductStatusOf ; owl:inverseOf ecsel-dr-OOSMP:hasRoHSCompliantStatus ; rdf:type owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:RoHSCompliantStatus ; rdfs:range ecsel-dr-OOSMP:SemiconductorProduct . ### http://www.w3id.org/ecsel-dr-OOSMP#belongsToDivision ecsel-dr-OOSMP:belongsToDivision rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:belongsToOrganizationalUnit ; owl:inverseOf ecsel-dr-OOSMP:responsibleForApplicationLevel3_Division ; rdfs:domain ecsel-dr-OOSMP:ApplicationLevel3 ; rdfs:range ecsel-dr-OOSMP:Division . ### http://www.w3id.org/ecsel-dr-OOSMP#belongsToOrganizationalUnit ecsel-dr-OOSMP:belongsToOrganizationalUnit rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-OOSMP:responsibleForApplicationArea ; rdfs:domain ecsel-dr-OOSMP:ApplicationArea ; rdfs:range org:OrganizationalUnit . ### http://www.w3id.org/ecsel-dr-OOSMP#belongsToProductLine ecsel-dr-OOSMP:belongsToProductLine rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:belongsToOrganizationalUnit ; owl:inverseOf ecsel-dr-OOSMP:responsibleForApplicationArea_ProductLine ; rdfs:domain ecsel-dr-OOSMP:ApplicationArea ; rdfs:range ecsel-dr-OOSMP:ProductLine . ### http://www.w3id.org/ecsel-dr-OOSMP#canBeAppliedIn ecsel-dr-OOSMP:canBeAppliedIn rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-OOSMP:findsApplicationThrough ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-OOSMP:Product ecsel-dr-OOSMP:Solution ) ] ; rdfs:range ecsel-dr-OOSMP:ApplicationArea . ### http://www.w3id.org/ecsel-dr-OOSMP#completelyLeadFreeStatusOf ecsel-dr-OOSMP:completelyLeadFreeStatusOf rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:semiconductorProductStatusOf ; owl:inverseOf ecsel-dr-OOSMP:hasCompletelyLeadFreeStatus ; rdf:type owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:CompletelyLeadFreeStatus ; rdfs:range ecsel-dr-OOSMP:SemiconductorProduct . ### http://www.w3id.org/ecsel-dr-OOSMP#containsAdditionalPowerManagement ecsel-dr-OOSMP:containsAdditionalPowerManagement rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:containsProduct ; owl:inverseOf ecsel-dr-OOSMP:partOfAsAdditionalPowerManagement ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range ecsel-dr-OOSMP:AdditionalPowerManagement . ### http://www.w3id.org/ecsel-dr-OOSMP#containsDiscretePowerStage ecsel-dr-OOSMP:containsDiscretePowerStage rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:containsProduct ; owl:inverseOf ecsel-dr-OOSMP:partOfAsDiscretePowerStage ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range ecsel-dr-OOSMP:DiscretePowerStage . ### http://www.w3id.org/ecsel-dr-OOSMP#containsGateDriver ecsel-dr-OOSMP:containsGateDriver rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:containsProduct ; owl:inverseOf ecsel-dr-OOSMP:partOfAsGateDriver ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range ecsel-dr-OOSMP:GateDriver . ### http://www.w3id.org/ecsel-dr-OOSMP#containsIntelligentPowerModule ecsel-dr-OOSMP:containsIntelligentPowerModule rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:containsProduct ; owl:inverseOf ecsel-dr-OOSMP:partOfAsIntelligentPowerModule ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range ecsel-dr-OOSMP:IntelligentPowerModule . ### http://www.w3id.org/ecsel-dr-OOSMP#containsMicrocontroller ecsel-dr-OOSMP:containsMicrocontroller rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:containsProduct ; owl:inverseOf ecsel-dr-OOSMP:partOfAsMicrocontroller ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range ecsel-dr-OOSMP:Microcontroller . ### http://www.w3id.org/ecsel-dr-OOSMP#containsProduct ecsel-dr-OOSMP:containsProduct rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-OOSMP:partOf ; rdfs:domain ecsel-dr-OOSMP:Solution ; rdfs:range ecsel-dr-OOSMP:Product . ### http://www.w3id.org/ecsel-dr-OOSMP#containsSmartDriver ecsel-dr-OOSMP:containsSmartDriver rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:containsProduct ; owl:inverseOf ecsel-dr-OOSMP:partOfAsSmartDriver ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range ecsel-dr-OOSMP:SmartDriver . ### http://www.w3id.org/ecsel-dr-OOSMP#couldContainSensor ecsel-dr-OOSMP:couldContainSensor rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:containsProduct ; owl:inverseOf ecsel-dr-OOSMP:partOfAsPotentialSensor ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range ecsel-dr-OOSMP:Sensor . ### http://www.w3id.org/ecsel-dr-OOSMP#designTargetOf ecsel-dr-OOSMP:designTargetOf rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-OOSMP:hasDesignTarget ; rdf:type owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:DesignTarget ; rdfs:range ecsel-dr-OOSMP:MotorControlAndDriveSolution . ### http://www.w3id.org/ecsel-dr-OOSMP#findsApplicationThrough ecsel-dr-OOSMP:findsApplicationThrough rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-OOSMP:ApplicationArea ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-OOSMP:Product ecsel-dr-OOSMP:Solution ) ] . ### http://www.w3id.org/ecsel-dr-OOSMP#halogenFreeStatusOf ecsel-dr-OOSMP:halogenFreeStatusOf rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:semiconductorProductStatusOf ; owl:inverseOf ecsel-dr-OOSMP:hasHalogenFreeStatus ; rdf:type owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:HalogenFreeStatus ; rdfs:range ecsel-dr-OOSMP:SemiconductorProduct . ### http://www.w3id.org/ecsel-dr-OOSMP#hasApplicationLevel2 ecsel-dr-OOSMP:hasApplicationLevel2 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasSubApplicationArea ; owl:inverseOf ecsel-dr-OOSMP:subApplicationAreaOfApplicationLevel1 ; rdfs:domain ecsel-dr-OOSMP:ApplicationLevel1 ; rdfs:range ecsel-dr-OOSMP:ApplicationLevel2 . ### http://www.w3id.org/ecsel-dr-OOSMP#hasApplicationLevel3 ecsel-dr-OOSMP:hasApplicationLevel3 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasSubApplicationArea ; owl:inverseOf ecsel-dr-OOSMP:subApplicationAreaOfApplicationLevel2 ; rdfs:domain ecsel-dr-OOSMP:ApplicationLevel2 ; rdfs:range ecsel-dr-OOSMP:ApplicationLevel3 . ### http://www.w3id.org/ecsel-dr-OOSMP#hasBusinessLine ecsel-dr-OOSMP:hasBusinessLine rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasSubUnit ; owl:inverseOf ecsel-dr-OOSMP:subUnitOfDivision ; rdf:type owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:Division ; rdfs:range ecsel-dr-OOSMP:BusinessLine . ### http://www.w3id.org/ecsel-dr-OOSMP#hasCompletelyLeadFreeStatus ecsel-dr-OOSMP:hasCompletelyLeadFreeStatus rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasSemiconductorProductStatus ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range ecsel-dr-OOSMP:CompletelyLeadFreeStatus . ### http://www.w3id.org/ecsel-dr-OOSMP#hasDesignTarget ecsel-dr-OOSMP:hasDesignTarget rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorSolution ; rdfs:range ecsel-dr-OOSMP:DesignTarget . ### http://www.w3id.org/ecsel-dr-OOSMP#hasHalogenFreeStatus ecsel-dr-OOSMP:hasHalogenFreeStatus rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasSemiconductorProductStatus ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range ecsel-dr-OOSMP:HalogenFreeStatus . ### http://www.w3id.org/ecsel-dr-OOSMP#hasIntegrationLevel ecsel-dr-OOSMP:hasIntegrationLevel rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-OOSMP:integrationLevelOf ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range ecsel-dr-OOSMP:IntegrationLevel . ### http://www.w3id.org/ecsel-dr-OOSMP#hasMainApplication ecsel-dr-OOSMP:hasMainApplication rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasSubApplicationArea ; owl:inverseOf ecsel-dr-OOSMP:subApplicationAreaOfIndustry ; rdfs:domain ecsel-dr-OOSMP:Industry ; rdfs:range ecsel-dr-OOSMP:MainApplication . ### http://www.w3id.org/ecsel-dr-OOSMP#hasMainPowerDeviceType ecsel-dr-OOSMP:hasMainPowerDeviceType rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-OOSMP:mainPowerDeviceTypeOf ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range ecsel-dr-OOSMP:MainPowerDeviceType . ### http://www.w3id.org/ecsel-dr-OOSMP#hasMotorType ecsel-dr-OOSMP:hasMotorType rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-OOSMP:motorTypeOf ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range ecsel-dr-OOSMP:MotorType . ### http://www.w3id.org/ecsel-dr-OOSMP#hasMountingStyle ecsel-dr-OOSMP:hasMountingStyle rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-OOSMP:mountingStyleOf ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:Sensor ; rdfs:range ecsel-dr-OOSMP:MountingStyle . ### http://www.w3id.org/ecsel-dr-OOSMP#hasOPNStatus ecsel-dr-OOSMP:hasOPNStatus rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasSemiconductorProductStatus ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range ecsel-dr-OOSMP:OPNStatus . ### http://www.w3id.org/ecsel-dr-OOSMP#hasPackingType ecsel-dr-OOSMP:hasPackingType rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-OOSMP:packingTypeOf ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range ecsel-dr-OOSMP:PackingType . ### http://www.w3id.org/ecsel-dr-OOSMP#hasPriceIndication ecsel-dr-OOSMP:hasPriceIndication rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-OOSMP:priceIndicationOf ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorSolution ; rdfs:range ecsel-dr-OOSMP:PriceIndication ; rdfs:comment "BOM" . ### http://www.w3id.org/ecsel-dr-OOSMP#hasProductLine ecsel-dr-OOSMP:hasProductLine rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasSubUnit ; owl:inverseOf ecsel-dr-OOSMP:subUnitOfBusinessLine ; rdf:type owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:BusinessLine ; rdfs:range ecsel-dr-OOSMP:ProductLine . ### http://www.w3id.org/ecsel-dr-OOSMP#hasProductQualification ecsel-dr-OOSMP:hasProductQualification rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasQualification ; owl:inverseOf ecsel-dr-OOSMP:productQualificationOf ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range ecsel-dr-OOSMP:Qualification . ### http://www.w3id.org/ecsel-dr-OOSMP#hasQualification ecsel-dr-OOSMP:hasQualification rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-OOSMP:qualificationOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-OOSMP:SemiconductorProduct ecsel-dr-OOSMP:SemiconductorSolution ) ] ; rdfs:range ecsel-dr-OOSMP:Qualification . ### http://www.w3id.org/ecsel-dr-OOSMP#hasRoHSCompliantStatus ecsel-dr-OOSMP:hasRoHSCompliantStatus rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasSemiconductorProductStatus ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range ecsel-dr-OOSMP:RoHSCompliantStatus . ### http://www.w3id.org/ecsel-dr-OOSMP#hasSemiconductorProductStatus ecsel-dr-OOSMP:hasSemiconductorProductStatus rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-OOSMP:semiconductorProductStatusOf ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range ecsel-dr-OOSMP:SemiconductorProductStatus . ### http://www.w3id.org/ecsel-dr-OOSMP#hasSensingType ecsel-dr-OOSMP:hasSensingType rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-OOSMP:sensingTypeOf ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range ecsel-dr-OOSMP:SensingType . ### http://www.w3id.org/ecsel-dr-OOSMP#hasSensorSubApplication ecsel-dr-OOSMP:hasSensorSubApplication rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasSubApplicationArea ; owl:inverseOf ecsel-dr-OOSMP:subApplicationAreaOfSensorMainApplication ; rdfs:domain ecsel-dr-OOSMP:SensorMainApplication ; rdfs:range ecsel-dr-OOSMP:SensorSubApplication . ### http://www.w3id.org/ecsel-dr-OOSMP#hasSolutionQualification ecsel-dr-OOSMP:hasSolutionQualification rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasQualification ; owl:inverseOf ecsel-dr-OOSMP:solutionQualificationOf ; rdfs:domain ecsel-dr-OOSMP:SemiconductorSolution ; rdfs:range ecsel-dr-OOSMP:Qualification . ### http://www.w3id.org/ecsel-dr-OOSMP#hasSubApplication ecsel-dr-OOSMP:hasSubApplication rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasSubApplicationArea ; owl:inverseOf ecsel-dr-OOSMP:subApplicationAreaOfMainApplication ; rdfs:domain ecsel-dr-OOSMP:MainApplication ; rdfs:range ecsel-dr-OOSMP:SubApplication . ### http://www.w3id.org/ecsel-dr-OOSMP#hasSubApplicationArea ecsel-dr-OOSMP:hasSubApplicationArea rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-OOSMP:subApplicationAreaOf ; rdf:type owl:IrreflexiveProperty ; rdfs:domain ecsel-dr-OOSMP:ApplicationArea ; rdfs:range ecsel-dr-OOSMP:ApplicationArea . ### http://www.w3id.org/ecsel-dr-OOSMP#hasSubUnit ecsel-dr-OOSMP:hasSubUnit rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-OOSMP:subUnitOf ; rdf:type owl:IrreflexiveProperty ; rdfs:domain org:OrganizationalUnit ; rdfs:range org:OrganizationalUnit . ### http://www.w3id.org/ecsel-dr-OOSMP#hasTopology ecsel-dr-OOSMP:hasTopology rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-OOSMP:topologyOf ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range ecsel-dr-OOSMP:Topology . ### http://www.w3id.org/ecsel-dr-OOSMP#integrationLevelOf ecsel-dr-OOSMP:integrationLevelOf rdf:type owl:ObjectProperty , owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:IntegrationLevel ; rdfs:range ecsel-dr-OOSMP:MotorControlAndDriveSolution . ### http://www.w3id.org/ecsel-dr-OOSMP#mainPowerDeviceTypeOf ecsel-dr-OOSMP:mainPowerDeviceTypeOf rdf:type owl:ObjectProperty , owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:MainPowerDeviceType ; rdfs:range ecsel-dr-OOSMP:MotorControlAndDriveSolution . ### http://www.w3id.org/ecsel-dr-OOSMP#motorTypeOf ecsel-dr-OOSMP:motorTypeOf rdf:type owl:ObjectProperty , owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:MotorType ; rdfs:range ecsel-dr-OOSMP:MotorControlAndDriveSolution . ### http://www.w3id.org/ecsel-dr-OOSMP#mountingStyleOf ecsel-dr-OOSMP:mountingStyleOf rdf:type owl:ObjectProperty , owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:MountingStyle ; rdfs:range ecsel-dr-OOSMP:Sensor . ### http://www.w3id.org/ecsel-dr-OOSMP#ownedBy ecsel-dr-OOSMP:ownedBy rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-OOSMP:owns ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:Product ; rdfs:range org:OrganizationalUnit . ### http://www.w3id.org/ecsel-dr-OOSMP#owns ecsel-dr-OOSMP:owns rdf:type owl:ObjectProperty , owl:InverseFunctionalProperty ; rdfs:domain org:OrganizationalUnit ; rdfs:range ecsel-dr-OOSMP:Product . ### http://www.w3id.org/ecsel-dr-OOSMP#packingTypeOf ecsel-dr-OOSMP:packingTypeOf rdf:type owl:ObjectProperty , owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:PackingType ; rdfs:range ecsel-dr-OOSMP:SemiconductorProduct . ### http://www.w3id.org/ecsel-dr-OOSMP#partOf ecsel-dr-OOSMP:partOf rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-OOSMP:Product ; rdfs:range ecsel-dr-OOSMP:Solution . ### http://www.w3id.org/ecsel-dr-OOSMP#partOfAsAdditionalPowerManagement ecsel-dr-OOSMP:partOfAsAdditionalPowerManagement rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:partOf ; rdfs:domain ecsel-dr-OOSMP:AdditionalPowerManagement ; rdfs:range ecsel-dr-OOSMP:MotorControlAndDriveSolution . ### http://www.w3id.org/ecsel-dr-OOSMP#partOfAsDiscretePowerStage ecsel-dr-OOSMP:partOfAsDiscretePowerStage rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:partOf ; rdfs:domain ecsel-dr-OOSMP:DiscretePowerStage ; rdfs:range ecsel-dr-OOSMP:MotorControlAndDriveSolution . ### http://www.w3id.org/ecsel-dr-OOSMP#partOfAsGateDriver ecsel-dr-OOSMP:partOfAsGateDriver rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:partOf ; rdfs:domain ecsel-dr-OOSMP:GateDriver ; rdfs:range ecsel-dr-OOSMP:MotorControlAndDriveSolution . ### http://www.w3id.org/ecsel-dr-OOSMP#partOfAsIntelligentPowerModule ecsel-dr-OOSMP:partOfAsIntelligentPowerModule rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:partOf ; rdfs:domain ecsel-dr-OOSMP:IntelligentPowerModule ; rdfs:range ecsel-dr-OOSMP:MotorControlAndDriveSolution . ### http://www.w3id.org/ecsel-dr-OOSMP#partOfAsMicrocontroller ecsel-dr-OOSMP:partOfAsMicrocontroller rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:partOf ; rdfs:domain ecsel-dr-OOSMP:Microcontroller ; rdfs:range ecsel-dr-OOSMP:MotorControlAndDriveSolution . ### http://www.w3id.org/ecsel-dr-OOSMP#partOfAsPotentialSensor ecsel-dr-OOSMP:partOfAsPotentialSensor rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:partOf ; rdfs:domain ecsel-dr-OOSMP:Sensor ; rdfs:range ecsel-dr-OOSMP:MotorControlAndDriveSolution . ### http://www.w3id.org/ecsel-dr-OOSMP#partOfAsSmartDriver ecsel-dr-OOSMP:partOfAsSmartDriver rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:partOf ; rdfs:domain ecsel-dr-OOSMP:SmartDriver ; rdfs:range ecsel-dr-OOSMP:MotorControlAndDriveSolution . ### http://www.w3id.org/ecsel-dr-OOSMP#priceIndicationOf ecsel-dr-OOSMP:priceIndicationOf rdf:type owl:ObjectProperty , owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:PriceIndication ; rdfs:range ecsel-dr-OOSMP:SemiconductorSolution . ### http://www.w3id.org/ecsel-dr-OOSMP#productQualificationOf ecsel-dr-OOSMP:productQualificationOf rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:qualificationOf ; rdfs:domain ecsel-dr-OOSMP:Qualification ; rdfs:range ecsel-dr-OOSMP:SemiconductorProduct . ### http://www.w3id.org/ecsel-dr-OOSMP#qualificationOf ecsel-dr-OOSMP:qualificationOf rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-OOSMP:Qualification ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-OOSMP:SemiconductorProduct ecsel-dr-OOSMP:SemiconductorSolution ) ] . ### http://www.w3id.org/ecsel-dr-OOSMP#responsibleForApplicationArea ecsel-dr-OOSMP:responsibleForApplicationArea rdf:type owl:ObjectProperty ; rdfs:domain org:OrganizationalUnit ; rdfs:range ecsel-dr-OOSMP:ApplicationArea . ### http://www.w3id.org/ecsel-dr-OOSMP#responsibleForApplicationArea_ProductLine ecsel-dr-OOSMP:responsibleForApplicationArea_ProductLine rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:responsibleForApplicationArea ; rdfs:domain ecsel-dr-OOSMP:ProductLine ; rdfs:range ecsel-dr-OOSMP:ApplicationArea . ### http://www.w3id.org/ecsel-dr-OOSMP#responsibleForApplicationLevel3_Division ecsel-dr-OOSMP:responsibleForApplicationLevel3_Division rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:responsibleForApplicationArea ; rdfs:domain ecsel-dr-OOSMP:Division ; rdfs:range ecsel-dr-OOSMP:ApplicationLevel3 . ### http://www.w3id.org/ecsel-dr-OOSMP#semiconductorProductStatusOf ecsel-dr-OOSMP:semiconductorProductStatusOf rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProductStatus ; rdfs:range ecsel-dr-OOSMP:SemiconductorProduct . ### http://www.w3id.org/ecsel-dr-OOSMP#sensingTypeOf ecsel-dr-OOSMP:sensingTypeOf rdf:type owl:ObjectProperty , owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SensingType ; rdfs:range ecsel-dr-OOSMP:MotorControlAndDriveSolution . ### http://www.w3id.org/ecsel-dr-OOSMP#solutionQualificationOf ecsel-dr-OOSMP:solutionQualificationOf rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:qualificationOf ; rdfs:domain ecsel-dr-OOSMP:Qualification ; rdfs:range ecsel-dr-OOSMP:SemiconductorSolution . ### http://www.w3id.org/ecsel-dr-OOSMP#subApplicationAreaOf ecsel-dr-OOSMP:subApplicationAreaOf rdf:type owl:ObjectProperty , owl:IrreflexiveProperty ; rdfs:domain ecsel-dr-OOSMP:ApplicationArea ; rdfs:range ecsel-dr-OOSMP:ApplicationArea . ### http://www.w3id.org/ecsel-dr-OOSMP#subApplicationAreaOfApplicationLevel1 ecsel-dr-OOSMP:subApplicationAreaOfApplicationLevel1 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:subApplicationAreaOf ; rdfs:domain ecsel-dr-OOSMP:ApplicationLevel2 ; rdfs:range ecsel-dr-OOSMP:ApplicationLevel1 . ### http://www.w3id.org/ecsel-dr-OOSMP#subApplicationAreaOfApplicationLevel2 ecsel-dr-OOSMP:subApplicationAreaOfApplicationLevel2 rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:subApplicationAreaOf ; rdfs:domain ecsel-dr-OOSMP:ApplicationLevel3 ; rdfs:range ecsel-dr-OOSMP:ApplicationLevel2 . ### http://www.w3id.org/ecsel-dr-OOSMP#subApplicationAreaOfIndustry ecsel-dr-OOSMP:subApplicationAreaOfIndustry rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:subApplicationAreaOf ; rdfs:domain ecsel-dr-OOSMP:MainApplication ; rdfs:range ecsel-dr-OOSMP:Industry . ### http://www.w3id.org/ecsel-dr-OOSMP#subApplicationAreaOfMainApplication ecsel-dr-OOSMP:subApplicationAreaOfMainApplication rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:subApplicationAreaOf ; rdfs:domain ecsel-dr-OOSMP:SubApplication ; rdfs:range ecsel-dr-OOSMP:MainApplication . ### http://www.w3id.org/ecsel-dr-OOSMP#subApplicationAreaOfSensorMainApplication ecsel-dr-OOSMP:subApplicationAreaOfSensorMainApplication rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:subApplicationAreaOf ; rdfs:domain ecsel-dr-OOSMP:SensorSubApplication ; rdfs:range ecsel-dr-OOSMP:SensorMainApplication . ### http://www.w3id.org/ecsel-dr-OOSMP#subUnitOf ecsel-dr-OOSMP:subUnitOf rdf:type owl:ObjectProperty , owl:IrreflexiveProperty ; rdfs:domain org:OrganizationalUnit ; rdfs:range org:OrganizationalUnit . ### http://www.w3id.org/ecsel-dr-OOSMP#subUnitOfBusinessLine ecsel-dr-OOSMP:subUnitOfBusinessLine rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:subUnitOf ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:ProductLine ; rdfs:range ecsel-dr-OOSMP:BusinessLine . ### http://www.w3id.org/ecsel-dr-OOSMP#subUnitOfDivision ecsel-dr-OOSMP:subUnitOfDivision rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:subUnitOf ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:BusinessLine ; rdfs:range ecsel-dr-OOSMP:Division . ### http://www.w3id.org/ecsel-dr-OOSMP#topologyOf ecsel-dr-OOSMP:topologyOf rdf:type owl:ObjectProperty , owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:Topology ; rdfs:range ecsel-dr-OOSMP:MotorControlAndDriveSolution . ### http://www.w3id.org/ecsel-dr-PMV#activates rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; 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:label "activates" ; skos:altLabel "activ" . ### http://www.w3id.org/ecsel-dr-PMV#activatesFunction rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ) ] ; 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:label "activatesFunction" ; skos:altLabel "activ function" . ### http://www.w3id.org/ecsel-dr-PMV#activatesTask rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment "Specialization of the activates property that links the class Rule with Task in the course of the process flow." ; rdfs:label "activatesTask" ; skos:altLabel "activ task" . ### http://www.w3id.org/ecsel-dr-PMV#belongsTo rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "Denotes the connection between a \"Function\" and another \"Process\" as this process may deliver an output used in this function." ; rdfs:label "belongsTo" ; skos:altLabel "belong" . ### http://www.w3id.org/ecsel-dr-PMV#carriesOut rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain , [ rdf:type owl:Class ; owl:unionOf ( org:OrganizationalUnit ) ] ; rdfs:range ; rdfs:comment "Role(s) or Organizational unit(s) that carrries (carry) out the process step (equivalent to R in RACI notation)" ; rdfs:label "carriesOut" ; skos:altLabel "carri" . ### http://www.w3id.org/ecsel-dr-PMV#connectedTo rdf:type owl:ObjectProperty , owl:SymmetricProperty , owl:TransitiveProperty ; rdfs:domain ; rdfs:range ; rdfs:label "connectedTo" ; skos:altLabel "connect" . ### http://www.w3id.org/ecsel-dr-PMV#contains rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:label "contains" ; skos:altLabel "contain" . ### http://www.w3id.org/ecsel-dr-PMV#contributesTo rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment "Role(s) that contribute(s) to a process step during it is carried out." ; rdfs:label "contributesTo" ; skos:altLabel "contribut" . ### http://www.w3id.org/ecsel-dr-PMV#controls rdf:type owl:ObjectProperty ; owl:inverseOf ; rdf:type owl:InverseFunctionalProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "A goal controls the outcome of a function in a process flow." ; rdfs:label "controls" ; skos:altLabel "control" . ### http://www.w3id.org/ecsel-dr-PMV#creates rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain , [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; rdfs:comment "A process step creates an event. The connector is used to represent the chronological order in an EPC." ; rdfs:label "creates" ; skos:altLabel "creat" . ### http://www.w3id.org/ecsel-dr-PMV#diagramedOn rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; rdfs:label "diagramedOn" ; skos:altLabel "diagram" . ### http://www.w3id.org/ecsel-dr-PMV#evaluates rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment "A rule evaluates an event. The connector is used to represent the chronological order in an EPC." ; rdfs:label "evaluates" ; skos:altLabel "evalu" . ### http://www.w3id.org/ecsel-dr-PMV#executes rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment "A function in a process flow excutes software." ; rdfs:label "executes" ; skos:altLabel "execut" . ### http://www.w3id.org/ecsel-dr-PMV#flow rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; 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:label "flow" ; skos:altLabel "flow" . ### http://www.w3id.org/ecsel-dr-PMV#follows rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain , ; rdfs:range , ; rdfs:comment "A process step follows a process step. The connector is used to represent the chronological order in an EPC." ; rdfs:label "follows" ; skos:altLabel "follow" . ### http://www.w3id.org/ecsel-dr-PMV#hasAsInput rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment "A process step can have technical term(s) as input." ; rdfs:label "hasAsInput" ; skos:altLabel "input" . ### http://www.w3id.org/ecsel-dr-PMV#hasAsOutput rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment "A process step can have technical term(s) as output." ; rdfs:label "hasAsOutput" ; skos:altLabel "output" . ### http://www.w3id.org/ecsel-dr-PMV#hasNextModel rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; 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:label "hasNextModel" ; skos:altLabel "model" . ### http://www.w3id.org/ecsel-dr-PMV#hasObject rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:comment "EPCs and Value-added chain diagrams consist of objects." ; rdfs:label "hasObject" ; skos:altLabel "object" . ### http://www.w3id.org/ecsel-dr-PMV#hasOutput rdf:type owl:ObjectProperty ; owl:inverseOf ; rdf:type owl:InverseFunctionalProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "A function in a process flow produces a physical or non-physical output." ; rdfs:label "hasOutput" ; skos:altLabel "output" . ### http://www.w3id.org/ecsel-dr-PMV#hasPreviousModel rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; 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:label "hasPreviousModel" ; skos:altLabel "previou model" . ### http://www.w3id.org/ecsel-dr-PMV#hasSubFlow rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment "EPCs can have other EPCs as subordinates. The connector is used to represent the hierarchical order." ; rdfs:label "hasSubFlow" ; skos:altLabel "sub flow" . ### http://www.w3id.org/ecsel-dr-PMV#hasSubModel rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "Denotes to which instance of \"Process\" an instance of a \"Process Element\" belongs." ; rdfs:label "hasSubModel" ; skos:altLabel "sub model" . ### http://www.w3id.org/ecsel-dr-PMV#hasSubordinate rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment "Value-added chain diagrams have EPCs as subordinates. The connector is used to represent the hierarchical order." ; rdfs:label "hasSubordinate" ; skos:altLabel "subordin" . ### http://www.w3id.org/ecsel-dr-PMV#hasSubordinateVACD rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment "Value-added chain diagrams have value-added chain diagrams as subordinates. The connector is used to represent the hierarchical order." ; rdfs:label "hasSubordinateVACD" ; skos:altLabel "subordin vacd" . ### http://www.w3id.org/ecsel-dr-PMV#hasSuperior rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "EPCs have value-added chain diagrams as superior. The connector is used to represent the hierarchical order." ; rdfs:label "hasSuperior" ; skos:altLabel "superior" . ### http://www.w3id.org/ecsel-dr-PMV#hasSuperiorVACD rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "Value-added chain diagrams have another value-added chain diagram as superior. The connector is used to represent the hierarchical order." ; rdfs:label "hasSuperiorVACD" ; skos:altLabel "superior vacd" . ### http://www.w3id.org/ecsel-dr-PMV#isActivatedBy rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ) ] ; 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:label "isActivatedBy" ; skos:altLabel "activ" . ### http://www.w3id.org/ecsel-dr-PMV#isActivatedByFunction rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; rdfs:comment "Represents the inverse property of activatesFunction." ; rdfs:label "isActivatedByFunction" ; skos:altLabel "activ function" . ### http://www.w3id.org/ecsel-dr-PMV#isActivatedByTask rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "Represents the inverse property of activatesTask." ; rdfs:label "isActivatedByTask" ; skos:altLabel "activ task" . ### http://www.w3id.org/ecsel-dr-PMV#isAssignedTo rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range , ; rdfs:comment "A rule is assigned to a process step. The connector is used to represent the chronological order in an EPC." ; rdfs:label "isAssignedTo" ; skos:altLabel "assign" . ### http://www.w3id.org/ecsel-dr-PMV#isCarriedOutBy rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range , [ rdf:type owl:Class ; owl:unionOf ( org:OrganizationalUnit ) ] ; rdfs:comment "A process step is carried out by role(s) or organizational unit(s) (equivalent to R in RACI notation)." ; rdfs:label "isCarriedOutBy" ; skos:altLabel "carri" . ### http://www.w3id.org/ecsel-dr-PMV#isControlledBy rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "The result of a function in a process flow is controlled by a goal." ; rdfs:label "isControlledBy" ; skos:altLabel "control" . ### http://www.w3id.org/ecsel-dr-PMV#isCreatedBy rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range , [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:comment "An event is created by a process step. The connector is used to represent the chronological order in an EPC." ; rdfs:label "isCreatedBy" ; skos:altLabel "creat" . ### http://www.w3id.org/ecsel-dr-PMV#isDependentOn rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment "An event is dependent on a rule. The connector is used to represent the chronological order in an EPC." ; rdfs:label "isDependentOn" ; skos:altLabel "depend" . ### http://www.w3id.org/ecsel-dr-PMV#isEvaluatedBy rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "An event is evaluated by a rule. The connector is used to represent the chronological order in an EPC." ; rdfs:label "isEvaluatedBy" ; skos:altLabel "evalu" . ### http://www.w3id.org/ecsel-dr-PMV#isExecutedBy rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "Software is executed by a function in a process flow." ; rdfs:label "isExectuedBy" ; skos:altLabel "exectu" . ### http://www.w3id.org/ecsel-dr-PMV#isInputFor rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "A software independent business object or product/services may be input for a process step." ; rdfs:label "isInputFor" ; skos:altLabel "input" . ### http://www.w3id.org/ecsel-dr-PMV#isInputOf rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range ; 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:label "isInputFor" ; skos:altLabel "isinput" . ### http://www.w3id.org/ecsel-dr-PMV#isLinkedBy rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:label "isLinkedBy" ; skos:altLabel "link" . ### http://www.w3id.org/ecsel-dr-PMV#isOutputOf rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain , ; rdfs:range , ; rdfs:comment "A software independent business object may be output of a process step." , "Physical or non-physical output is produced by a function in a process flow." ; rdfs:label "isOutputOf" ; skos:altLabel "output" . ### http://www.w3id.org/ecsel-dr-PMV#isPredecessorOf rdf:type owl:ObjectProperty ; rdfs:domain , ; rdfs:range , ; rdfs:comment "The connector is used to represent the chronological order of value chain elements." ; rdfs:label "isPredecessorOf" ; skos:altLabel "predecessor" . ### http://www.w3id.org/ecsel-dr-PMV#isProcessedBy rdf:type owl:ObjectProperty ; owl:inverseOf ; rdf:type owl:FunctionalProperty , owl:InverseFunctionalProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "The execution of a function in a process flow is processed by a person (human output)." ; rdfs:label "isProcessedBy" ; skos:altLabel "process" . ### http://www.w3id.org/ecsel-dr-PMV#isRepresentedBy rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain , [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range , ; rdfs:comment "Represents the inverse property of represents." ; rdfs:label "isRepresentedBy" ; skos:altLabel "repres" . ### http://www.w3id.org/ecsel-dr-PMV#isResponsibleFor rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain org:OrganizationalUnit ; rdfs:range ; rdfs:comment "An organizational unit is responible for a function in a process flow." ; rdfs:label "isResponsibleFor" ; skos:altLabel "respons" . ### http://www.w3id.org/ecsel-dr-PMV#isSubFlowOf rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "EPCs can have other EPCs as superiors. The connector is used to represent the hierarchical order." ; rdfs:label "isSubFlowOf" ; skos:altLabel "sub flow" . ### http://www.w3id.org/ecsel-dr-PMV#isSupportedBy rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment "A process step is supported by an application system type." ; rdfs:label "isSupportedBy" ; skos:altLabel "support" . ### http://www.w3id.org/ecsel-dr-PMV#isTransformedBy rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; rdfs:comment "Environmental data is transformed by a function in a process flow." ; rdfs:label "isTransformedBy" ; skos:altLabel "transform" . ### http://www.w3id.org/ecsel-dr-PMV#isUnderResponsibilityOf rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range org:OrganizationalUnit ; rdfs:comment "The execution of a function in a process flow is under the responsibility of an organizational unit." ; rdfs:label "isUnderResponsibilityOf" ; skos:altLabel "respons" . ### http://www.w3id.org/ecsel-dr-PMV#isUsedBy rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range ; rdfs:comment "An external resource is used by a function in a process flow." ; rdfs:label "isUsedBy" ; skos:altLabel "use" . ### http://www.w3id.org/ecsel-dr-PMV#isWorkedOnByCollaborationOf rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "A process step is worked on by collaboration of role(s)." ; rdfs:label "isWorkedOnByCollaborationOf" ; skos:altLabel "work collabor" . ### http://www.w3id.org/ecsel-dr-PMV#leadsTo rdf:type owl:ObjectProperty ; rdfs:comment "The connector is used to represent the chronological order in an EPC." ; rdfs:label "leadsTo" ; skos:altLabel "lead" . ### http://www.w3id.org/ecsel-dr-PMV#leadsToEvent rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:comment "A rule leads to an event. The connector is used to represent the chronological order in an EPC." ; rdfs:label "leadsToEvent" ; skos:altLabel "lead event" . ### http://www.w3id.org/ecsel-dr-PMV#leadsToRule rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain , ; rdfs:range ; rdfs:comment "A process step leads to a rule. The connector is used to represent the chronological order in an EPC." ; rdfs:label "leadsToRule" ; skos:altLabel "lead rule" . ### http://www.w3id.org/ecsel-dr-PMV#links rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "links" ; skos:altLabel "link" . ### http://www.w3id.org/ecsel-dr-PMV#mustBeInformedAbout rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range ; 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:label "mustBeInformedAbout" ; skos:altLabel "inform" . ### http://www.w3id.org/ecsel-dr-PMV#processes rdf:type owl:ObjectProperty , owl:FunctionalProperty , owl:InverseFunctionalProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "Some person, referred to as human output here, processes a function in a process flow. " ; rdfs:label "processes" ; skos:altLabel "process" . ### http://www.w3id.org/ecsel-dr-PMV#relevantFor rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:comment "An object is relevant for EPCs and value-added chain diagrams." ; rdfs:label "relevantFor" ; skos:altLabel "relev" . ### http://www.w3id.org/ecsel-dr-PMV#represents rdf:type owl:ObjectProperty ; rdfs:domain , ; rdfs:range , [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:comment "A aris:BPActivity is the graphical representation of a aris:VACD or aris:BPFlow in a aris:VACD." ; rdfs:label "represents" ; skos:altLabel "repres" . ### http://www.w3id.org/ecsel-dr-PMV#resultIsForwardedTo rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "A result of a process step is forwarded to role(s)." ; rdfs:label "resultIsForwardedTo" ; skos:altLabel "result forward" . ### http://www.w3id.org/ecsel-dr-PMV#supports rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "A process step is supported by an Application system." ; rdfs:label "supports" ; skos:altLabel "support" . ### http://www.w3id.org/ecsel-dr-PMV#transforms rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "A function in a process flow transforms environmental data like work schedules." ; rdfs:label "transforms" ; skos:altLabel "transform" . ### http://www.w3id.org/ecsel-dr-PMV#uses rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:comment "A function in a process flow uses external resources like machines or computer hardware during its execution." ; rdfs:label "uses" ; skos:altLabel "use" . ### http://www.w3id.org/ecsel-dr-PRIMA#hasCategoryLevel rdf:type owl:ObjectProperty ; owl:inverseOf ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PRIMA#hasCertificationLevel rdf:type owl:ObjectProperty ; owl:inverseOf ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PRIMA#hasContributor rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ) ] . ### http://www.w3id.org/ecsel-dr-PRIMA#hasProjectStatus rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PRIMA#hasRole rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PRIMA#hasSubProject rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PRIMA#hasTask rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PRIMA#hasTrainingLevel rdf:type owl:ObjectProperty ; owl:inverseOf ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PRIMA#hasWorkPackage rdf:type owl:ObjectProperty ; owl:inverseOf ; rdf:type owl:FunctionalProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PRIMA#isCategoryLevelOf rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PRIMA#isCertificationLevelOf rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PRIMA#isContributorOf rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PRIMA#isProjectStatus rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PRIMA#isRoleOf rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PRIMA#isSubProjectOf rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PRIMA#isTaskOf rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ) ] . ### http://www.w3id.org/ecsel-dr-PRIMA#isTrainingLevelOf rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PRIMA#isWorkPackageOf rdf:type owl:ObjectProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range [ rdf:type owl:Class ; owl:unionOf ( ) ] . ### http://www.w3id.org/ecsel-dr-PROD#alternateProduct ecsel-dr-PROD:alternateProduct rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-PROD:FinishedProduct ; rdfs:range ecsel-dr-PROD:FinishedProduct ; rdfs:comment "all FinishedProducts that share the same SalesProductNumber" . ### http://www.w3id.org/ecsel-dr-PROD#customer ecsel-dr-PROD:customer rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-PROD:CPNSpec ; rdfs:range ecsel-dr-PROD:Organization . ### http://www.w3id.org/ecsel-dr-PROD#customerPartNumberSpecification ecsel-dr-PROD:customerPartNumberSpecification rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-PROD:SalesProduct ; rdfs:range ecsel-dr-PROD:CPNSpec ; rdfs:comment """contain relevant information including customer and CPN Several CPNs can be linked to the same SP number 'sold-to'""" . ### http://www.w3id.org/ecsel-dr-PROD#hasDREP ecsel-dr-PROD:hasDREP rdf:type owl:ObjectProperty , owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-PROD:FPOS ; rdfs:range ecsel-dr-PROD:DREP . ### http://www.w3id.org/ecsel-dr-PROD#hasFPOS ecsel-dr-PROD:hasFPOS rdf:type owl:ObjectProperty , owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-PROD:PPOS ; rdfs:range ecsel-dr-PROD:FPOS . ### http://www.w3id.org/ecsel-dr-PROD#hasFinishedProduct ecsel-dr-PROD:hasFinishedProduct rdf:type owl:ObjectProperty , owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-PROD:SalesProduct ; rdfs:range ecsel-dr-PROD:FinishedProduct ; rdfs:comment "SalesProduct hasFinishedProduct FinishedProduct" . ### http://www.w3id.org/ecsel-dr-PROD#hasRfP ecsel-dr-PROD:hasRfP rdf:type owl:ObjectProperty , owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-PROD:PPOS ; rdfs:range ecsel-dr-PROD:RfP . ### http://www.w3id.org/ecsel-dr-PROD#hasSKU_PD ecsel-dr-PROD:hasSKU_PD rdf:type owl:ObjectProperty , owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-PROD:DREP ; rdfs:range ecsel-dr-PROD:SKU . ### http://www.w3id.org/ecsel-dr-PROD#hasSKU_SM ecsel-dr-PROD:hasSKU_SM rdf:type owl:ObjectProperty , owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-PROD:FinishedProduct ; rdfs:range ecsel-dr-PROD:SKU . ### http://www.w3id.org/ecsel-dr-PROD#hasSalesProduct ecsel-dr-PROD:hasSalesProduct rdf:type owl:ObjectProperty , owl:InverseFunctionalProperty ; rdfs:domain ecsel-dr-PROD:RfP ; rdfs:range ecsel-dr-PROD:SalesProduct ; rdfs:comment "FinishedProduct hasSalesProduct SalesProduct" . ### http://www.w3id.org/ecsel-dr-PROD#isSimilarTo ecsel-dr-PROD:isSimilarTo rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-PROD:Product ; rdfs:range ecsel-dr-PROD:Product ; 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""" . ### http://www.w3id.org/ecsel-dr-PROD#shippedTo ecsel-dr-PROD:shippedTo rdf:type owl:ObjectProperty ; rdfs:domain [ rdf:type owl:Restriction ; owl:onProperty ecsel-dr-PROD:salesProductNumber ; owl:someValuesFrom xsd:string ] . ### http://www.w3id.org/ecsel-dr-PROD#substituteProduct ecsel-dr-PROD:substituteProduct rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-PROD:SalesProduct ; rdfs:range ecsel-dr-PROD:SalesProduct ; 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 """ . ### http://www.w3id.org/ecsel-dr-PWR#Acting_As rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-PWR#Has_Voltage rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "is a Volatge of" . ### http://www.w3id.org/ecsel-dr-PWR#Is_Working_As rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range ; rdfs:label "The Depletion Mode Is Working As" . ### http://www.w3id.org/ecsel-dr-PWR#Power_loss_Calculated_by rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range , ; rdfs:label "has a Power Loss Calculated by Multiplicatoin of" . ### http://www.w3id.org/ecsel-dr-PWR#The_Enhansment_Mode_Is_Working_As rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PWR#The_Temperature_Must_Not_Exceed rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "The Temperature Must Not Exceed" . ### http://www.w3id.org/ecsel-dr-PWR#amplified_by rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "The Act of The Switching" . ### http://www.w3id.org/ecsel-dr-PWR#are rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PWR#hasAdimension rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PWR#hasAnApplicationArea rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PWR#hasControlMethod rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PWR#hasIndustrySector rdf:type owl:ObjectProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PWR#has_A_Configuration rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "has A Configuration" . ### http://www.w3id.org/ecsel-dr-PWR#has_A_Voltage rdf:type owl:ObjectProperty ; rdfs:label "has A Voltage" . ### http://www.w3id.org/ecsel-dr-PWR#has_Properties rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "has Properties" . ### http://www.w3id.org/ecsel-dr-PWR#has_The_Elements rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "has The Elements" . ### http://www.w3id.org/ecsel-dr-PWR#has_The_Propeties_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "has The Propeties of" . ### http://www.w3id.org/ecsel-dr-PWR#has_a_Configuration rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "has a Configuration" . ### http://www.w3id.org/ecsel-dr-PWR#has_a_Voltage_Equals_or_Greater_Than rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "has a Voltage Equals or Greater Than" . ### http://www.w3id.org/ecsel-dr-PWR#has_an_Operation_Modes rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "has an Operation Modes" . ### http://www.w3id.org/ecsel-dr-PWR#has_an_Operation_Region rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "has an Operation Region" . ### http://www.w3id.org/ecsel-dr-PWR#has_an_Output_Current rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "has an Output Current" . ### http://www.w3id.org/ecsel-dr-PWR#has_deployment rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-PWR#has_information_object rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:comment "States that the devices have ona or more information objects, which can be a sensor data sheet for the sensors." ; rdfs:isDefinedBy "IFX" ; rdfs:label "has information object" . ### http://www.w3id.org/ecsel-dr-PWR#has_input rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "has input" . ### http://www.w3id.org/ecsel-dr-PWR#has_output rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "has output" . ### http://www.w3id.org/ecsel-dr-PWR#in_deployment rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; 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:isDefinedBy """World Wide Web Consortium SSN http://www.w3.org/2005/Incubator/ssn/ssnx/ssn#inDeployment""" ; rdfs:label "in deployment" . ### http://www.w3id.org/ecsel-dr-PWR#is_a_Product_of rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "is a Product of" . ### http://www.w3id.org/ecsel-dr-PWR#is_produced_by rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "is produced by" . ### http://www.w3id.org/ecsel-dr-PWR#made_(the_method_name,_e.g.:_observation,_and_amlification) rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "Makes Switching" . ### http://www.w3id.org/ecsel-dr-RAMI40#IsUsedBy ecsel-dr-RAMI40:IsUsedBy rdf:type owl:ObjectProperty ; owl:inverseOf ecsel-dr-RAMI40:Uses ; rdfs:domain ecsel-dr-RAMI40:Standard ; rdfs:range ecsel-dr-RAMI40:Standard_Organisation . ### http://www.w3id.org/ecsel-dr-RAMI40#Uses ecsel-dr-RAMI40:Uses rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-RAMI40:Standard_Organisation ; rdfs:range ecsel-dr-RAMI40:Standard . ### http://www.w3id.org/ecsel-dr-RAMI40#contains_Admin_Shell ecsel-dr-RAMI40:contains_Admin_Shell rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-RAMI40:I4.0Component ; rdfs:range ecsel-dr-RAMI40:Admin_Shell ; rdfs:comment "Points the I4.0 Component to the Administration Shell" . ### http://www.w3id.org/ecsel-dr-RAMI40#describes ecsel-dr-RAMI40:describes rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-RAMI40:Admin_Shell ; rdfs:range ecsel-dr-RAMI40:Asset ; rdfs:comment "Connect the Asset with the Administration Shell" . ### http://www.w3id.org/ecsel-dr-RAMI40#energy_Efficiency_Value ecsel-dr-RAMI40:energy_Efficiency_Value rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-RAMI40:EnergyEfficiency ; rdfs:range ecsel-dr-RAMI40:Measure ; rdfs:comment "Points to the value of the Energy Efficiency comsuption." . ### http://www.w3id.org/ecsel-dr-RAMI40#hasData ecsel-dr-RAMI40:hasData rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-RAMI40:Admin_Shell ; rdfs:range ecsel-dr-RAMI40:Submodel ; skos:definition "Connects the AdminShell with the different types of Data for the Object/Entity" . ### http://www.w3id.org/ecsel-dr-RAMI40#hasDataType ecsel-dr-RAMI40:hasDataType rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-RAMI40:Submodel ; rdfs:comment "Points to the datatypes of the Submodels" . ### http://www.w3id.org/ecsel-dr-RAMI40#hasReference ecsel-dr-RAMI40:hasReference rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-RAMI40:Submodel . ### http://www.w3id.org/ecsel-dr-RAMI40#hasSemanticExpression ecsel-dr-RAMI40:hasSemanticExpression rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-RAMI40:Submodel ; rdfs:range ecsel-dr-RAMI40:Expression_Semantic . ### http://www.w3id.org/ecsel-dr-RAMI40#hasSubmodel ecsel-dr-RAMI40:hasSubmodel rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-RAMI40:Admin_Shell ; rdfs:range ecsel-dr-RAMI40:Submodel . ### http://www.w3id.org/ecsel-dr-RAMI40#hasUsedDate ecsel-dr-RAMI40:hasUsedDate rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-RAMI40:Standard ; rdfs:range ecsel-dr-RAMI40:UsedDate ; rdfs:comment "The date that standard has been used" . ### http://www.w3id.org/ecsel-dr-RAMI40#hasVersion ecsel-dr-RAMI40:hasVersion rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-RAMI40:Standard ; rdfs:range ecsel-dr-RAMI40:StandardVersion ; rdfs:comment "The current version of Standard." . ### http://www.w3id.org/ecsel-dr-RAMI40#has_RAMI_Hierarchy_Level ecsel-dr-RAMI40:has_RAMI_Hierarchy_Level rdf:type owl:ObjectProperty ; rdfs:range ecsel-dr-RAMI40:RAMI_Hierarchy_Level_Dimension ; skos:definition "Connects the concepts with the correspondent layer in the RAMI Hierarchy Levels" . ### http://www.w3id.org/ecsel-dr-RAMI40#has_RAMI_Life_Cycle_Layer ecsel-dr-RAMI40:has_RAMI_Life_Cycle_Layer rdf:type owl:ObjectProperty ; rdfs:range ecsel-dr-RAMI40:RAMI_Life_Cycle_Dimension ; skos:definition "Connects the concepts with the correspondent layer in the RAMI Hierarchy Levels" . ### http://www.w3id.org/ecsel-dr-RAMI40#inAccordanceWith ecsel-dr-RAMI40:inAccordanceWith rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-RAMI40:Submodel ; rdfs:range ecsel-dr-RAMI40:Standard ; rdfs:comment "The Submodel is in accordance with a given standard specified in the STO ontology" . ### http://www.w3id.org/ecsel-dr-RAMI40#isConnectedTo ecsel-dr-RAMI40:isConnectedTo rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-RAMI40:Admin_Shell ; rdfs:range ecsel-dr-RAMI40:Dimension ; rdfs:comment "Connects the Admin Shell with the different RAMI4.0 Dimensions" . ### http://www.w3id.org/ecsel-dr-RAMI40#isDescribedWith ecsel-dr-RAMI40:isDescribedWith rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-RAMI40:Admin_Shell ; rdfs:range ecsel-dr-RAMI40:Standard . ### http://www.w3id.org/ecsel-dr-RAMI40#isPartOf ecsel-dr-RAMI40:isPartOf rdf:type owl:ObjectProperty ; rdfs:domain ecsel-dr-RAMI40:Asset ; rdfs:range ecsel-dr-RAMI40:Asset ; rdfs:comment "A relation between any entities, in this case, the Asset can be part of other Asset(s)." ; rdfs:isDefinedBy . ### http://www.w3id.org/ecsel-dr-RAMI40#usesStandard ecsel-dr-RAMI40:usesStandard rdf:type owl:ObjectProperty ; rdfs:range ecsel-dr-RAMI40:Standard ; rdfs:comment "Points to the standards describing the functions attached to the asset via the administration shell" . ### http://www.w3id.org/ecsel-dr-SCP#calculate rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "calculate"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#calculateBased rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "calculateBased"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#calculateBasedOn rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "calculateBasedOn"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#consistOf rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "consistOf"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#constitute rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "constitute"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#consume rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "consume"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#contribute rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "contribute"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#create rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "create"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#enterTo rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "enterTo"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#figureOutFrom rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "figureOutFrom"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#generate rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "generate"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#goesTo rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "goesTo"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#hasInput rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "hasInput"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#hasInputin rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "hasInputin"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#hasResult rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "hasResult"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#isPartOf rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "isPartOf"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#isPlaceOrders rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "isPlaceOrders"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#isResultOf rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "isResultOf"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#isTransferTo rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "isTransferTo"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#match rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "match"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#matchIn rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "matchIn"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#matchTO rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "matchTO"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#obtainFrom rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "obtainFrom"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#provide rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "provide"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#resultIn rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "resultIn"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#resultTo rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "resultTo"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#sendTo rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "sendTo"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#sortTo rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "sortTo"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#transfer rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "transfer"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#transferTo rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "transferTo"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#use rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "use"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#useIn rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "useIn"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#useUp rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; rdfs:label "useUp"@iri-based . ### http://www.w3id.org/ecsel-dr-SO#belongsTo rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#consistsOf rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#dedicates rdf:type owl:ObjectProperty ; owl:inverseOf . ### http://www.w3id.org/ecsel-dr-SO#hasBottlenecks rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasCurrentWIP rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasDeliveryCommitment rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasDemand rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain , [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range , . ### http://www.w3id.org/ecsel-dr-SO#hasEquipment rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain , ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasEquipmentGroup rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasEventCalendar rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasFab rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasLot rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasLotEvent rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasLotSize rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasOperation rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain , [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasOwner rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasPart rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasPlant rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasPriorityClass rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasProductLevel rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasProductNumber rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasReleasePlan rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasRoute rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain , [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range , . ### http://www.w3id.org/ecsel-dr-SO#hasShift rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasTargetCosts rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasTargetRevenue rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasTechnology rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain , [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasTimeConstraints rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasWIPStation rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#hasWorkshop rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#isBottlenecksOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isCurrentWIP rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isDedicatedTo rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#isDeliveryCommitmentOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isDemandOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isEquipmentGroupOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isEquipmentOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isEventCalendarOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isFabOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isLotEventOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isLotOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isLotSizeOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isManuallyLoadedBy rdf:type owl:ObjectProperty ; owl:inverseOf . ### http://www.w3id.org/ecsel-dr-SO#isNeededBy rdf:type owl:ObjectProperty ; owl:inverseOf . ### http://www.w3id.org/ecsel-dr-SO#isOperationOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isOwnedBy rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isPartOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isPlantOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isPreceededBy rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#isPriorityClassOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isProcessedBy rdf:type owl:ObjectProperty ; owl:inverseOf ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#isProductLevelOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isReleasePlanOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isRequiredBy rdf:type owl:ObjectProperty ; owl:inverseOf . ### http://www.w3id.org/ecsel-dr-SO#isResponsibleFor rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#isRoboticallyLoadedBy rdf:type owl:ObjectProperty ; owl:inverseOf . ### http://www.w3id.org/ecsel-dr-SO#isRouteOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isShiftOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isTargetCostsOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isTargetRevenueOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isTechnologyOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isTimeConstraintsOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isUnloadedBy rdf:type owl:ObjectProperty ; owl:inverseOf . ### http://www.w3id.org/ecsel-dr-SO#isWIPStationOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#isWorkshopOf rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#manuallyLoads rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; 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" . ### http://www.w3id.org/ecsel-dr-SO#needsPurge rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#preceeds rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#processes rdf:type owl:ObjectProperty . ### http://www.w3id.org/ecsel-dr-SO#requires rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#roboticallyLoads rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range ; 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" . ### http://www.w3id.org/ecsel-dr-SO#unloads rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ### http://www.w3id.org/ecsel-dr-SO#usesOneOrMoreTechnology rdf:type owl:ObjectProperty ; rdfs:domain ; rdfs:range . ################################################################# # Data properties ################################################################# ### http://www.w3.org/2006/time#day time:day rdf:type owl:DatatypeProperty ; rdfs:domain time:GeneralDateTimeDescription ; 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:label "day"@en ; skos:definition """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 . ### http://www.w3.org/2006/time#dayOfYear time:dayOfYear rdf:type owl:DatatypeProperty ; rdfs:domain time:GeneralDateTimeDescription ; rdfs:range xsd:nonNegativeInteger ; rdfs:comment "The number of the day within the year"@en ; rdfs:label "day of year"@en ; skos:definition "The number of the day within the year"@en . ### http://www.w3.org/2006/time#days time:days rdf:type owl:DatatypeProperty ; rdfs:domain time:GeneralDurationDescription ; rdfs:range xsd:decimal ; rdfs:comment "length of, or element of the length of, a temporal extent expressed in days"@en ; rdfs:label "days duration"@en ; skos:definition "length of, or element of the length of, a temporal extent expressed in days"@en . ### http://www.w3.org/2006/time#hasXSDDuration time:hasXSDDuration rdf:type owl:DatatypeProperty ; rdfs:domain time:TemporalEntity ; rdfs:range xsd:duration ; rdfs:comment "Extent of a temporal entity, expressed using xsd:duration"@en ; rdfs:label "has XSD duration"@en ; skos:definition "Extent of a temporal entity, expressed using xsd:duration"@en ; skos:editorialNote "Feature at risk - added in 2017 revision, and not yet widely used. "@en . ### http://www.w3.org/2006/time#hour time:hour rdf:type owl:DatatypeProperty ; rdfs:domain time:GeneralDateTimeDescription ; rdfs:range xsd:nonNegativeInteger ; rdfs:comment "Hour position in a calendar-clock system."@en ; rdfs:label "hour"@en ; skos:definition "Hour position in a calendar-clock system."@en . ### http://www.w3.org/2006/time#hours time:hours rdf:type owl:DatatypeProperty ; rdfs:domain time:GeneralDurationDescription ; rdfs:range xsd:decimal ; rdfs:comment "length of, or element of the length of, a temporal extent expressed in hours"@en ; rdfs:label "hours duration"@en ; skos:definition "length of, or element of the length of, a temporal extent expressed in hours"@en . ### http://www.w3.org/2006/time#inXSDDate time:inXSDDate rdf:type owl:DatatypeProperty ; rdfs:domain time:Instant ; rdfs:range xsd:date ; rdfs:comment "Position of an instant, expressed using xsd:date"@en ; rdfs:label "in XSD date"@en ; skos:definition "Position of an instant, expressed using xsd:date"@en . ### http://www.w3.org/2006/time#inXSDDateTime time:inXSDDateTime rdf:type owl:DatatypeProperty ; rdfs:domain time:Instant ; rdfs:range xsd:dateTime ; rdfs:comment "Position of an instant, expressed using xsd:dateTime"@en ; rdfs:label "in XSD Date-Time"@en ; owl:deprecated "true"^^xsd:boolean ; skos:definition "Position of an instant, expressed using xsd:dateTime"@en ; skos:note "The property :inXSDDateTime is replaced by :inXSDDateTimeStamp which makes the time-zone field mandatory."@en . ### http://www.w3.org/2006/time#inXSDDateTimeStamp time:inXSDDateTimeStamp rdf:type owl:DatatypeProperty ; rdfs:domain time:Instant ; rdfs:range xsd:dateTimeStamp ; rdfs:comment "Position of an instant, expressed using xsd:dateTimeStamp"@en ; rdfs:label "in XSD Date-Time-Stamp"@en ; skos:definition "Position of an instant, expressed using xsd:dateTimeStamp"@en . ### http://www.w3.org/2006/time#inXSDgYear time:inXSDgYear rdf:type owl:DatatypeProperty ; rdfs:domain time:Instant ; rdfs:range xsd:gYear ; rdfs:comment "Position of an instant, expressed using xsd:gYear"@en ; rdfs:label "in XSD g-Year"@en ; skos:definition "Position of an instant, expressed using xsd:gYear"@en . ### http://www.w3.org/2006/time#inXSDgYearMonth time:inXSDgYearMonth rdf:type owl:DatatypeProperty ; rdfs:domain time:Instant ; rdfs:range xsd:gYearMonth ; rdfs:comment "Position of an instant, expressed using xsd:gYearMonth"@en ; rdfs:label "in XSD g-YearMonth"@en ; skos:definition "Position of an instant, expressed using xsd:gYearMonth"@en . ### http://www.w3.org/2006/time#minute time:minute rdf:type owl:DatatypeProperty ; rdfs:domain time:GeneralDateTimeDescription ; rdfs:range xsd:nonNegativeInteger ; rdfs:comment "Minute position in a calendar-clock system."@en ; rdfs:label "minute"@en ; skos:definition "Minute position in a calendar-clock system."@en . ### http://www.w3.org/2006/time#minutes time:minutes rdf:type owl:DatatypeProperty ; rdfs:domain time:GeneralDurationDescription ; rdfs:range xsd:decimal ; rdfs:comment "length, or element of, a temporal extent expressed in minutes"@en ; rdfs:label "minutes"@en ; skos:definition "length, or element of, a temporal extent expressed in minutes"@en . ### http://www.w3.org/2006/time#month time:month rdf:type owl:DatatypeProperty ; rdfs:domain time:GeneralDateTimeDescription ; 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:label "month"@en ; skos:definition """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 . ### http://www.w3.org/2006/time#months time:months rdf:type owl:DatatypeProperty ; rdfs:domain time:GeneralDurationDescription ; rdfs:range xsd:decimal ; rdfs:comment "length of, or element of the length of, a temporal extent expressed in months"@en ; rdfs:label "months duration"@en ; skos:definition "length of, or element of the length of, a temporal extent expressed in months"@en . ### http://www.w3.org/2006/time#nominalPosition time:nominalPosition rdf:type owl:DatatypeProperty ; rdfs:domain time:TimePosition ; rdfs:range xsd:string ; rdfs:comment "The (nominal) value indicating temporal position in an ordinal reference system "@en ; rdfs:label "Name of temporal position"@en ; skos:definition "The (nominal) value indicating temporal position in an ordinal reference system "@en . ### http://www.w3.org/2006/time#numericDuration time:numericDuration rdf:type owl:DatatypeProperty ; rdfs:domain time:Duration ; rdfs:range xsd:decimal ; rdfs:comment "Value of a temporal extent expressed as a decimal number scaled by a temporal unit"@en ; rdfs:label "Numeric value of temporal duration"@en ; skos:definition "Value of a temporal extent expressed as a decimal number scaled by a temporal unit"@en . ### http://www.w3.org/2006/time#numericPosition time:numericPosition rdf:type owl:DatatypeProperty ; rdfs:domain time:TimePosition ; rdfs:range xsd:decimal ; rdfs:comment "The (numeric) value indicating position within a temporal coordinate system "@en ; rdfs:label "Numeric value of temporal position"@en ; skos:definition "The (numeric) value indicating position within a temporal coordinate system "@en . ### http://www.w3.org/2006/time#second time:second rdf:type owl:DatatypeProperty ; rdfs:domain time:GeneralDateTimeDescription ; rdfs:range xsd:decimal ; rdfs:comment "Second position in a calendar-clock system."@en ; rdfs:label "second"@en . ### http://www.w3.org/2006/time#seconds time:seconds rdf:type owl:DatatypeProperty ; rdfs:domain time:GeneralDurationDescription ; rdfs:range xsd:decimal ; rdfs:comment "length of, or element of the length of, a temporal extent expressed in seconds"@en ; rdfs:label "seconds duration"@en ; rdfs:seeAlso . ### http://www.w3.org/2006/time#week time:week rdf:type owl:DatatypeProperty ; rdfs:domain time:GeneralDateTimeDescription ; rdfs:range xsd:nonNegativeInteger ; rdfs:comment "Week number within the year."@en ; rdfs:label "week"@en ; skos:note "Weeks are numbered differently depending on the calendar in use and the local language or cultural conventions (locale). ISO-8601 specifies that the first week of the year includes at least four days, and that Monday is the first day of the week. In that system, week 1 is the week that contains the first Thursday in the year."@en . ### http://www.w3.org/2006/time#weeks time:weeks rdf:type owl:DatatypeProperty ; rdfs:domain time:GeneralDurationDescription ; rdfs:range xsd:decimal ; rdfs:comment "length of, or element of the length of, a temporal extent expressed in weeks"@en ; rdfs:label "weeks duration"@en . ### http://www.w3.org/2006/time#xsdDateTime time:xsdDateTime rdf:type owl:DatatypeProperty ; rdfs:domain time:DateTimeInterval ; rdfs:range xsd:dateTime ; rdfs:comment "Value of DateTimeInterval expressed as a compact value."@en ; rdfs:label "has XSD date-time"@en ; owl:deprecated "true"^^xsd:boolean ; skos:note "Using xsd:dateTime in this place means that the duration of the interval is implicit: it corresponds to the length of the smallest non-zero element of the date-time literal. However, this rule cannot be used for intervals whose duration is more than one rank smaller than the starting time - e.g. the first minute or second of a day, the first hour of a month, or the first day of a year. In these cases the desired interval cannot be distinguished from the interval corresponding to the next rank up. Because of this essential ambiguity, use of this property is not recommended and it is deprecated."@en . ### http://www.w3.org/2006/time#year time:year rdf:type owl:DatatypeProperty ; rdfs:domain time:GeneralDateTimeDescription ; 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:label "year"@en . ### http://www.w3.org/2006/time#years time:years rdf:type owl:DatatypeProperty ; rdfs:domain time:GeneralDurationDescription ; rdfs:range xsd:decimal ; rdfs:comment "length of, or element of the length of, a temporal extent expressed in years"@en ; rdfs:label "years duration"@en . ### http://www.w3.org/ns/sosa/hasSimpleResult rdf:type owl:DatatypeProperty ; schema:domainIncludes , , ; rdfs:comment "The simple value of an Observation or Actuation or act of Sampling."@en ; rdfs:isDefinedBy ; rdfs:label "has simple result"@en ; skos:definition "The simple value of an Observation or Actuation or act of Sampling."@en ; skos:example "For instance, the values 23 or true."@en . ### http://www.w3.org/ns/sosa/resultTime rdf:type owl:DatatypeProperty ; rdfs:range xsd:dateTime ; schema:domainIncludes , , ; rdfs:comment "The result time is the instant of time when the Observation, Actuation or Sampling activity was completed."@en ; rdfs:isDefinedBy ; rdfs:label "result time"@en ; skos:definition "The result time is the instant of time when the Observation, Actuation or Sampling activity was completed."@en . ### http://www.w3id.org/ecsel-dr-AH#DeviceID ecsel-dr-AH:DeviceID rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ecsel-dr-AH:Device ; rdfs:range xsd:string ; rdfs:comment """Data property of each device in Arrowhead context. Needed by Device Discovery service. Purpose: provides an unique identifier for a device."""@en . ### http://www.w3id.org/ecsel-dr-AH#DeviceName ecsel-dr-AH:DeviceName rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-AH:Device ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-AH#IP_address ecsel-dr-AH:IP_address rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-AH:Device ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-AH#MAC_address ecsel-dr-AH:MAC_address rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-AH:Device ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OM#hasConfirmedDeliveryDate rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OM#hasConfirmedQuantity rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasCurrentDockDate rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:dateTime . ### http://www.w3id.org/ecsel-dr-OM#hasCustomerAddress rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdfs:domain ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OM#hasCustomerNo rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasCustomerPartNumber rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasCustomerReferenceNo rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasCustomerRequestedDate rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:dateTime . ### http://www.w3id.org/ecsel-dr-OM#hasDepartment rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OM#hasEmail rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OM#hasFax rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasIcoterms rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OM#hasItemNo rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasItemPrice rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-OM#hasLineIDOCR rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasLineIDOLI rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasModeOfTransport rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OM#hasName rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OM#hasOpenQuantityOCR rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasOpenQuantityOLI rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasPONumberOCR rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasPONumberOO rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasPartialCancelQuantityQuantityBuyer rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasPartialCancelQuantitySupplier rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasPlantAddress rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdfs:domain ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OM#hasPromisedDockDate rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:dateTime . ### http://www.w3id.org/ecsel-dr-OM#hasRequestedDockDate rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:dateTime . ### http://www.w3id.org/ecsel-dr-OM#hasRequestedQuantity rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasResponseDate rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:dateTime . ### http://www.w3id.org/ecsel-dr-OM#hasSupplierAddress rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdfs:domain ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OM#hasSupplierComments rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OM#hasSupplierReasonCode rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OM#hasSupplierReferenceNo rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasTelephone rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasTotalConfirmedOpenQuantity rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasTotalConfirmedQuantity rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasTotalDeliveredQuantity rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasTotalOpenQuantity rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasTotalRequestedQuantity rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasTotalUnconfirmedOpenQuantity rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OM#hasUnitPrice rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf owl:topDataProperty ; rdf:type owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-OOSMP#hasApplicationCharacteristic ecsel-dr-OOSMP:hasApplicationCharacteristic rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OOSMP#hasBenefit ecsel-dr-OOSMP:hasBenefit rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasApplicationCharacteristic ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OOSMP#hasBudgetaryPrice ecsel-dr-OOSMP:hasBudgetaryPrice rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasChannelStructure ecsel-dr-OOSMP:hasChannelStructure rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasHierarchyInformation ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OOSMP#hasChipCount ecsel-dr-OOSMP:hasChipCount rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorSolution ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-OOSMP#hasChipCountDiscretePowerStage ecsel-dr-OOSMP:hasChipCountDiscretePowerStage rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasChipCount ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorSolution ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-OOSMP#hasChipCountGateDriver ecsel-dr-OOSMP:hasChipCountGateDriver rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasChipCount ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorSolution ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-OOSMP#hasChipCountIntelligentPowerModule ecsel-dr-OOSMP:hasChipCountIntelligentPowerModule rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasChipCount ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorSolution ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-OOSMP#hasChipCountMicrocontroller ecsel-dr-OOSMP:hasChipCountMicrocontroller rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasChipCount ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorSolution ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-OOSMP#hasChipCountSmartDriver ecsel-dr-OOSMP:hasChipCountSmartDriver rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasChipCount ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorSolution ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-OOSMP#hasDCLinkVoltage ecsel-dr-OOSMP:hasDCLinkVoltage rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasDCLinkVoltageCharacteristic ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasDCLinkVoltageCharacteristic ecsel-dr-OOSMP:hasDCLinkVoltageCharacteristic rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasDCLinkVoltageMax ecsel-dr-OOSMP:hasDCLinkVoltageMax rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasDCLinkVoltageCharacteristic ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasDCLinkVoltageMin ecsel-dr-OOSMP:hasDCLinkVoltageMin rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasDCLinkVoltageCharacteristic ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasElectricPower ecsel-dr-OOSMP:hasElectricPower rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasElectricPowerMax ecsel-dr-OOSMP:hasElectricPowerMax rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasElectricPower ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasElectricPowerMin ecsel-dr-OOSMP:hasElectricPowerMin rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasElectricPower ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasFeature ecsel-dr-OOSMP:hasFeature rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasApplicationCharacteristic ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintArea ecsel-dr-OOSMP:hasFootprintArea rdf:type owl:DatatypeProperty ; rdfs:domain [ rdf:type owl:Class ; owl:unionOf ( ecsel-dr-OOSMP:SemiconductorProduct ecsel-dr-OOSMP:SemiconductorSolution ) ] ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaDiscretePowerStage ecsel-dr-OOSMP:hasFootprintAreaDiscretePowerStage rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasFootprintAreaProductFamily ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorSolution ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaGateDriver ecsel-dr-OOSMP:hasFootprintAreaGateDriver rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasFootprintAreaProductFamily ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorSolution ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaIntelligentPowerModule ecsel-dr-OOSMP:hasFootprintAreaIntelligentPowerModule rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasFootprintAreaProductFamily ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorSolution ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaMicrocontroller ecsel-dr-OOSMP:hasFootprintAreaMicrocontroller rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasFootprintAreaProductFamily ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorSolution ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaProduct ecsel-dr-OOSMP:hasFootprintAreaProduct rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasFootprintArea ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaProductFamily ecsel-dr-OOSMP:hasFootprintAreaProductFamily rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasFootprintArea ; rdfs:domain ecsel-dr-OOSMP:SemiconductorSolution ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasFootprintAreaSmartDriver ecsel-dr-OOSMP:hasFootprintAreaSmartDriver rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasFootprintAreaProductFamily ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorSolution ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasHierarchyInformation ecsel-dr-OOSMP:hasHierarchyInformation rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OOSMP#hasPackageName ecsel-dr-OOSMP:hasPackageName rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasHierarchyInformation ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OOSMP#hasPackingSize ecsel-dr-OOSMP:hasPackingSize rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range xsd:int . ### http://www.w3id.org/ecsel-dr-OOSMP#hasProductFamilyName ecsel-dr-OOSMP:hasProductFamilyName rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasHierarchyInformation ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OOSMP#hasSupplyVoltage ecsel-dr-OOSMP:hasSupplyVoltage rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-OOSMP:Sensor ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasSupplyVoltageMax ecsel-dr-OOSMP:hasSupplyVoltageMax rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasSupplyVoltage ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:Sensor ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasSupplyVoltageMin ecsel-dr-OOSMP:hasSupplyVoltageMin rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasSupplyVoltage ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:Sensor ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasTargetApplication ecsel-dr-OOSMP:hasTargetApplication rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasApplicationCharacteristic ; rdfs:domain ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-OOSMP#hasTemperatueMax ecsel-dr-OOSMP:hasTemperatueMax rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasTemperature ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:Sensor ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasTemperature ecsel-dr-OOSMP:hasTemperature rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-OOSMP:Sensor ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-OOSMP#hasTemperatureMin ecsel-dr-OOSMP:hasTemperatureMin rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-OOSMP:hasTemperature ; rdf:type owl:FunctionalProperty ; rdfs:domain ecsel-dr-OOSMP:Sensor ; rdfs:range xsd:double . ### http://www.w3id.org/ecsel-dr-PMV#hasCompletionStatus rdf:type owl:DatatypeProperty ; rdfs:range xsd:string ; rdfs:label "hasCompletionStatus" ; skos:altLabel "complet statu" . ### http://www.w3id.org/ecsel-dr-PMV#hasCreator rdf:type owl:DatatypeProperty ; rdfs:range xsd:string ; rdfs:label "hasCreator" ; skos:altLabel "creator" . ### http://www.w3id.org/ecsel-dr-PMV#hasExperience rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Describes the experience that is required." ; rdfs:label "has Experience" ; skos:altLabel "experi" . ### http://www.w3id.org/ecsel-dr-PMV#hasHandling rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Describes the requirements for the specific handling of objects." ; rdfs:label "has Handling" ; skos:altLabel "handl" . ### http://www.w3id.org/ecsel-dr-PMV#hasIPCode rdf:type owl:DatatypeProperty ; rdfs:range xsd:string ; rdfs:label "hasIPCode" ; skos:altLabel "ip code" . ### http://www.w3id.org/ecsel-dr-PMV#hasIdentifier rdf:type owl:DatatypeProperty ; rdfs:range xsd:string ; rdfs:comment "Represents the unique identifier of the element." ; rdfs:label "has Identifier" , "hasIdentifier" ; skos:altLabel "identifi" . ### http://www.w3id.org/ecsel-dr-PMV#hasKnowledge rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Describes the knowledge that is required." ; rdfs:label "has Knwoledge" ; skos:altLabel "knwoledg" . ### http://www.w3id.org/ecsel-dr-PMV#hasMission rdf:type owl:DatatypeProperty ; rdfs:range xsd:string ; rdfs:comment "Describes the mission or goal of a business process (flow)." ; rdfs:label "has Mission" ; skos:altLabel "mission" . ### http://www.w3id.org/ecsel-dr-PMV#hasOrphan rdf:type owl:DatatypeProperty ; rdfs:range xsd:string ; rdfs:label "hasOrphan" ; skos:altLabel "orphan" . ### http://www.w3id.org/ecsel-dr-PMV#hasOwner rdf:type owl:DatatypeProperty ; rdfs:range xsd:string ; rdfs:comment "Represents the owner of a business process (flow)." ; rdfs:label "has Owner" ; skos:altLabel "owner" . ### http://www.w3id.org/ecsel-dr-PMV#hasPersonResponsible rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:label "hasPersonResponsible" ; skos:altLabel "person respons" . ### http://www.w3id.org/ecsel-dr-PMV#hasProjectScope rdf:type owl:DatatypeProperty ; rdfs:range xsd:string ; rdfs:label "hasProjectScope" ; skos:altLabel "project scope" . ### http://www.w3id.org/ecsel-dr-PMV#hasRemarkOrExample rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Denotes a remark or an example that is given specific to an element." ; rdfs:label "has remark or example" , "hasRemarkOrExample" ; skos:altLabel "remark exampl" . ### http://www.w3id.org/ecsel-dr-PMV#hasRequirements rdf:type owl:DatatypeProperty ; rdfs:range xsd:string ; rdfs:comment "Description of all requirements for the certain input or output." ; rdfs:label "has Requirements" ; skos:altLabel "requir" . ### http://www.w3id.org/ecsel-dr-PMV#hasScope rdf:type owl:DatatypeProperty ; rdfs:range xsd:string ; rdfs:comment "Denotes the scope of a specific business process (flow)." ; rdfs:label "has Scope" ; skos:altLabel "scope" . ### http://www.w3id.org/ecsel-dr-PMV#hasTransactionCode rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:label "hasTransactionCode" ; skos:altLabel "transact code" . ### http://www.w3id.org/ecsel-dr-PRIMA#hasBudgetFactor rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-PRIMA#hasBudgetValue rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-PRIMA#hasCategoryFactor rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-PRIMA#hasExperience rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-PRIMA#hasGoal rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-PRIMA#hasImpactFactor rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-PRIMA#hasInterfaceComplexityFactor rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-PRIMA#hasMinimumJobExperience rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-PRIMA#hasMinimumProjectManagerExperience rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ; rdfs:domain ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-PRIMA#hasName rdf:type owl:DatatypeProperty , owl:FunctionalProperty ; rdfs:domain ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-PRIMA#hasResultingFactorAverage rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-PROD#additionalProperty ecsel-dr-PROD:additionalProperty rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-PROD:Product ; rdfs:range xsd:string ; 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." . ### http://www.w3id.org/ecsel-dr-PROD#customerPartNumber ecsel-dr-PROD:customerPartNumber rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-PROD:CPNSpec ; rdfs:range xsd:string ; rdfs:comment "product identifier used by the customer to identify one IFX product" . ### http://www.w3id.org/ecsel-dr-PROD#deliveryLeadTime ecsel-dr-PROD:deliveryLeadTime rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-PROD:FinishedProduct ; rdfs:range xsd:integer ; 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 """ . ### http://www.w3id.org/ecsel-dr-PROD#finishedProductNumber ecsel-dr-PROD:finishedProductNumber rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-PROD:FinishedProduct ; rdfs:range xsd:string ; rdfs:comment "finishedProductNumber is the unique identifier for a FinishedProduct" . ### http://www.w3id.org/ecsel-dr-PROD#halogeenFree ecsel-dr-PROD:halogeenFree rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-PROD:SalesProduct ; rdfs:range xsd:boolean . ### http://www.w3id.org/ecsel-dr-PROD#hasProductFamily ecsel-dr-PROD:hasProductFamily rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-PROD:SalesProduct ; rdfs:range rdfs:Literal . ### http://www.w3id.org/ecsel-dr-PROD#location ecsel-dr-PROD:location rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-PROD:PlanningElement , ecsel-dr-PROD:Product ; rdfs:range xsd:string ; rdfs:comment "A Location within Infineon’s internal supply chain is a local area where products are manufactured or stored." . ### http://www.w3id.org/ecsel-dr-PROD#minOrderQuantity ecsel-dr-PROD:minOrderQuantity rdf:type owl:DatatypeProperty ; rdfs:domain [ rdf:type owl:Restriction ; owl:onProperty ecsel-dr-PROD:minOrderQuantity ; owl:minQualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onDataRange xsd:integer ] ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-PROD#orderablePartNumber ecsel-dr-PROD:orderablePartNumber rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-PROD:SalesProduct ; rdfs:range xsd:string ; rdfs:comment """Customers may use the OPN as their customer part number for ordering at Infineon based on product attributes""" . ### http://www.w3id.org/ecsel-dr-PROD#salesProductName ecsel-dr-PROD:salesProductName rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-PROD:SalesProduct ; rdfs:range xsd:string ; 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 ). """ . ### http://www.w3id.org/ecsel-dr-PROD#salesProductNumber ecsel-dr-PROD:salesProductNumber rdf:type owl:DatatypeProperty ; rdfs:subPropertyOf ecsel-dr-PROD:salesProductName ; rdfs:domain ecsel-dr-PROD:SalesProduct ; rdfs:range xsd:string ; rdfs:comment "A salesProductNumber is a unique identifier of a Sales Product" . ### http://www.w3id.org/ecsel-dr-RAMI40#hasDate ecsel-dr-RAMI40:hasDate rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-RAMI40:Date ; rdfs:range xsd:dateTime . ### http://www.w3id.org/ecsel-dr-RAMI40#hasDescription ecsel-dr-RAMI40:hasDescription rdf:type owl:DatatypeProperty ; rdfs:domain ecsel-dr-RAMI40:Asset ; rdfs:range xsd:string ; skos:definition "Description of the Object/Entity" . ### http://www.w3id.org/ecsel-dr-SCP#ConfirmedDate rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:dateTime ; rdfs:label "ConfirmedDate"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#ConfirmedQuantity rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:label "ConfirmedQuantity"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#CustomerLocation rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:label "CustomerLocation"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#CustomersID rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:label "CustomersID"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#Granularity rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range rdfs:Literal ; rdfs:label "Granularity"@iri-based . ### http://www.w3id.org/ecsel-dr-SO#fromEquipmentGroupID rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Material Transfer: FK; start Equipment Group of material transfer"@en . ### http://www.w3id.org/ecsel-dr-SO#fromFabID rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Supply Chain: FK; Source ID of supply chain edge"@en . ### http://www.w3id.org/ecsel-dr-SO#hasCapacityLoss rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:double ; rdfs:comment "Calendar: Facility capacity loss in percent"@en . ### http://www.w3id.org/ecsel-dr-SO#hasChipsPerWafer rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "Product Level 4: Number of chips on a wafer"@en . ### http://www.w3id.org/ecsel-dr-SO#hasCustomerWishTime rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:date ; rdfs:comment "PK; customer wish time of the demand entry" . ### http://www.w3id.org/ecsel-dr-SO#hasCycleTimeCommitmentID rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Cycle Time Commitment: FK; Name of the product level 3"@en . ### http://www.w3id.org/ecsel-dr-SO#hasCycleTimeCommittment rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:dateTime ; rdfs:comment "Cycle Time Commitment: Committed overall supply chain cycle time"@en , "length of, or element of the length of, a temporal extent expressed in seconds"@en . ### http://www.w3id.org/ecsel-dr-SO#hasDeliveryCommitmentID rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Delivery Commitment: FK; Name of the product level 3"@en . ### http://www.w3id.org/ecsel-dr-SO#hasDemandDueDate rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:date ; rdfs:comment "Demand: PK; Due Date of the demand entry"@en . ### http://www.w3id.org/ecsel-dr-SO#hasDemandQuantity rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "Demand: Demand amount"@en . ### http://www.w3id.org/ecsel-dr-SO#hasDemandType rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Demand: PK; Demand forecast or real demand"@en . ### http://www.w3id.org/ecsel-dr-SO#hasDevelopmentTimeout rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "length of, or element of the length of, a temporal extent expressed in hours"@en . ### http://www.w3id.org/ecsel-dr-SO#hasEnterMainQuantity rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "Lot Event: Number of units in the lot (wafers / chips) when entered the event"@en . ### http://www.w3id.org/ecsel-dr-SO#hasEnterState rdf:type owl:DatatypeProperty ; rdfs:domain , ; rdfs:range xsd:dateTime ; rdfs:comment "Lot Event: Time state is entered"@en , "Lot State: Time state is entered"@en . ### http://www.w3id.org/ecsel-dr-SO#hasEquipmentGroupID rdf:type owl:DatatypeProperty ; rdfs:domain , , , , ; rdfs:range xsd:string ; rdfs:comment "Current WIP: PK; FK; Name of Equipment Group"@en , "Equipment Group: PK; Name of the Workshop"@en , "Equipment: FK; technical equipment group affiliation; FK to FabID"@en , "Setup: FK; Name of equipment"@en . ### http://www.w3id.org/ecsel-dr-SO#hasEquipmentGroupType rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Equipment Group: Refers to the technology used for the process tool: Lithography, Plasma Etching, Diffusion, Tester, Prober, etc."@en . ### http://www.w3id.org/ecsel-dr-SO#hasEventCalendarType rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Event Calendar: Type of event"@en . ### http://www.w3id.org/ecsel-dr-SO#hasEventDate rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:dateTime ; rdfs:comment "Lot Event: Date event occurred (DD.MM.YYYY hh:mm:ss)"@en . ### http://www.w3id.org/ecsel-dr-SO#hasEventName rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Lot Event: Name of event that occurred to lot (Hold, Split, Merge, Scrap, etc.)"@en . ### http://www.w3id.org/ecsel-dr-SO#hasFabInternal rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:boolean ; rdfs:comment "Fab: Does the fab belong to the company or to an external partner"@en . ### http://www.w3id.org/ecsel-dr-SO#hasFabPseudonym rdf:type owl:DatatypeProperty ; rdfs:domain , , , , , ; rdfs:range xsd:string ; rdfs:comment "Calendar: FK; Name of the facility"@en , "Demand: PK; Fab where the demand appears"@en , "Equipment Group: FK"@en , "FK; Name of the facility"@en , "Fab: PK; Name of the production unit"@en , "Release Plan: FK; Name of fab quantity of product level 4 is released"@en , "Workshop: FK; Name of the production unit"@en . ### http://www.w3id.org/ecsel-dr-SO#hasFabType rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Fab: Front End, Wafer Testing, Back End Assembly, Back End Final Test, …"@en . ### http://www.w3id.org/ecsel-dr-SO#hasFillRate rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:double ; rdfs:comment "Target Service Level: Rate of demand that can be fulfilled"@en . ### http://www.w3id.org/ecsel-dr-SO#hasFinishedProductCosts rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "Target Costs: Costs of a finished unit of a certain technology"@en . ### http://www.w3id.org/ecsel-dr-SO#hasFrequency rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-SO#hasHotTimeout rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "length of, or element of the length of, a temporal extent expressed in hours"@en . ### http://www.w3id.org/ecsel-dr-SO#hasLeaveMainQuantity rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "Lot Event: Number of units in the lot (wafers / chips) when left the event (Important for splits, merges and scraps)"@en . ### http://www.w3id.org/ecsel-dr-SO#hasLeaveState rdf:type owl:DatatypeProperty ; rdfs:domain , ; rdfs:range xsd:dateTime ; rdfs:comment "Lot Event: Time state is finished"@en , "Lot State: Time state is finished"@en . ### http://www.w3id.org/ecsel-dr-SO#hasLoadTimeWait rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "length of, or element of the length of, a temporal extent expressed in hours"@en . ### http://www.w3id.org/ecsel-dr-SO#hasLotDueDate rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:dateTime ; rdfs:comment "Lot Event: Date customer needs the lot delivered (DD.MM.YYYY hh:mm:ss)"@en , "Lot: Date customer needs the lot delivered (DD.MM.YYYY hh:mm:ss)"@en . ### http://www.w3id.org/ecsel-dr-SO#hasLotID rdf:type owl:DatatypeProperty ; rdfs:domain , , ; rdfs:range xsd:string ; rdfs:comment "Current WIP: PK; FK; Name of Lot"@en , "Lot Event: Name of the lot"@en , "Lot ID: PK; Name of the lot"@en . ### http://www.w3id.org/ecsel-dr-SO#hasLotOwner rdf:type owl:DatatypeProperty ; rdfs:domain , ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-SO#hasLotSizeAmount rdf:type owl:DatatypeProperty ; rdfs:domain , ; rdfs:range xsd:integer ; rdfs:comment "Lot Event: Amount of units in the lot"@en , "Lot: Amount of units in the lot"@en . ### http://www.w3id.org/ecsel-dr-SO#hasLotSizeQuantity rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Lot Size: Standard (FE) or optimal (BE) lot size for respective PL3"@en . ### http://www.w3id.org/ecsel-dr-SO#hasMaxThroughputPerWeek rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "Maximum Throughput per week"@en . ### http://www.w3id.org/ecsel-dr-SO#hasMaxWIP rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "Fab: Hard capacity restriction of process units (NULL if no restriction)"@en . ### http://www.w3id.org/ecsel-dr-SO#hasMeanTimeOffLine rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "length of, or element of the length of, a temporal extent expressed in hours"@en . ### http://www.w3id.org/ecsel-dr-SO#hasMeanTimeToFailure rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "length of, or element of the length of, a temporal extent expressed in seconds"@en , "mean time to failure - MTTF"@en . ### http://www.w3id.org/ecsel-dr-SO#hasMeanTimeToFailureDistribution rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-SO#hasMeanTimeToRepair rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "length of, or element of the length of, a temporal extent expressed in seconds"@en , "mean time to repair - MTTR"@en . ### http://www.w3id.org/ecsel-dr-SO#hasMeanTimeToRepairDistribution rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-SO#hasNumberOfParallelTools rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-SO#hasNumberOfProducts rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer . ### http://www.w3id.org/ecsel-dr-SO#hasOperationCritical rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:boolean ; rdfs:comment "Operation: Is the Operation critical in terms of SC planning (a Bottleneck) or not?"@en . ### http://www.w3id.org/ecsel-dr-SO#hasOperationID rdf:type owl:DatatypeProperty ; rdfs:domain , ; rdfs:range xsd:string ; rdfs:comment "FK; Name of operation"@en . ### http://www.w3id.org/ecsel-dr-SO#hasOperationName rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-SO#hasPTimePerUnit rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "Operation: Capacity consuming / relevant equipment processing time"@en , "length of, or element of the length of, a temporal extent expressed in seconds"@en . ### http://www.w3id.org/ecsel-dr-SO#hasParentLotEvent rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Lot Event: FK; Name of ancestor lot event (important to rebuild the lot history)"@en . ### http://www.w3id.org/ecsel-dr-SO#hasPlantID rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Fab: FK; Geographical location"@en , "Plant: PK; Will generally refer to the geographical location of the plant"@en . ### http://www.w3id.org/ecsel-dr-SO#hasPlantInternal rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:boolean ; rdfs:comment "Plant: Does the plant belong to the company or to an external partner"@en . ### http://www.w3id.org/ecsel-dr-SO#hasPlantName rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Plant: Will generally refer to the geographical location of the plant"@en . ### http://www.w3id.org/ecsel-dr-SO#hasPriority rdf:type owl:DatatypeProperty ; rdfs:domain , ; rdfs:range xsd:integer ; rdfs:comment "Current WIP: Priority of the lot"@en . ### http://www.w3id.org/ecsel-dr-SO#hasProcessingTimeDistribution rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string . ### http://www.w3id.org/ecsel-dr-SO#hasProductLevel2ID rdf:type owl:DatatypeProperty ; rdfs:domain , ; rdfs:range xsd:string ; rdfs:comment "Product Level 2: PK; Name of the product in level 2"@en , "Product Level 3: FK; Assignment of product to second product aggregation level"@en . ### http://www.w3id.org/ecsel-dr-SO#hasProductLevel3 rdf:type owl:DatatypeProperty ; rdfs:domain , ; rdfs:range xsd:string ; rdfs:comment "Lot Event: FK; Name of product level 3 lot belongs to"@en , "Lot: FK; Name of product level 3 lot belongs to"@en . ### http://www.w3id.org/ecsel-dr-SO#hasProductLevel3Pseudonym rdf:type owl:DatatypeProperty ; rdfs:domain , , , , , , , , , , ; rdfs:range xsd:string ; rdfs:comment "Demand: PK; Associated PL3"@en , "Product Level 3: PK; Name of the product in level 3"@en , "Product Level 4: FK; Assignment of product to first product aggregation level"@en . ### http://www.w3id.org/ecsel-dr-SO#hasPurgeDuration rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "length of, or element of the length of, a temporal extent expressed in hours"@en . ### http://www.w3id.org/ecsel-dr-SO#hasReleasePlanID rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Release Plan: FK; Name of the product level 3"@en . ### http://www.w3id.org/ecsel-dr-SO#hasResidualTimeInFab rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "Current WIP: Expected residual time lot spends in current Fab (FE/BE)"@en , "length of, or element of the length of, a temporal extent expressed in seconds"@en . ### http://www.w3id.org/ecsel-dr-SO#hasRevenuePerUnit rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "Target Revenue: Revenue per unit of a certain technology"@en . ### http://www.w3id.org/ecsel-dr-SO#hasReworkOperation rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Operation: [FK] Rework Operation, if needed"@en . ### http://www.w3id.org/ecsel-dr-SO#hasReworkProbabilityLots rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:double ; rdfs:comment "Operation: Probability of rework-tested full lots to be reworked"@en . ### http://www.w3id.org/ecsel-dr-SO#hasReworkProbabilityWafers rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:double ; rdfs:comment "Operation: Probability of rework-tested wafers to be reworked"@en . ### http://www.w3id.org/ecsel-dr-SO#hasReworkTest rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:boolean ; rdfs:comment "Operation: Are the processed lots tested for rework?"@en . ### http://www.w3id.org/ecsel-dr-SO#hasRobotLoadingTime rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "length of, or element of the length of, a temporal extent expressed in hours"@en . ### http://www.w3id.org/ecsel-dr-SO#hasRobotUnloadingTime rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "length of, or element of the length of, a temporal extent expressed in hours"@en . ### http://www.w3id.org/ecsel-dr-SO#hasRouteName rdf:type owl:DatatypeProperty ; rdfs:domain , ; rdfs:range xsd:string ; rdfs:comment "Name of route (usually equals product names requiring the route)"@en . ### http://www.w3id.org/ecsel-dr-SO#hasRoutePosition rdf:type owl:DatatypeProperty ; rdfs:domain , ; rdfs:range xsd:integer ; rdfs:comment "Lot Event: FK; Sequential number of the operation lot has entered"@en , "Lot: FK; Sequential number of the operation lot has entered"@en . ### http://www.w3id.org/ecsel-dr-SO#hasSamplingRate rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:double ; 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 . ### http://www.w3id.org/ecsel-dr-SO#hasScrappingProbabilityLots rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:double ; rdfs:comment "Operation: Probability of scrapping-tested full lots to be scrapped"@en . ### http://www.w3id.org/ecsel-dr-SO#hasScrappingProbabilityWafers rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:double ; rdfs:comment "Operation: Probability of scrapping-tested wafers to be scrapped"@en . ### http://www.w3id.org/ecsel-dr-SO#hasScrappingTest rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:boolean ; rdfs:comment "Operation: Are the processed lots tested for scrapping?"@en . ### http://www.w3id.org/ecsel-dr-SO#hasSequenceNumber rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "Lot Event: FK; Sequential number of the operation lot has entered"@en , "Lot State: FK; Sequential number of the operation lot has entered"@en , "Route: PK; Sequential number of operations along the route"@en . ### http://www.w3id.org/ecsel-dr-SO#hasShiftID rdf:type owl:DatatypeProperty ; rdfs:domain , ; rdfs:range xsd:string ; rdfs:comment "Shift: PK; Name of shift"@en . ### http://www.w3id.org/ecsel-dr-SO#hasSplitLotChips rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "split into lots with # chips, added due to data import" . ### http://www.w3id.org/ecsel-dr-SO#hasSplitLots rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "Split into # lots, added due to data import" . ### http://www.w3id.org/ecsel-dr-SO#hasStockOutProbability rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:double ; rdfs:comment "Target service level: Probability that customer demand cannot be fulfilled"@en . ### http://www.w3id.org/ecsel-dr-SO#hasSupplyChainID rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Technology: FK; Assignment of technology to supply chain"@en . ### http://www.w3id.org/ecsel-dr-SO#hasSupplyChainName rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Supply Chain: Name of the supply chain"@en . ### http://www.w3id.org/ecsel-dr-SO#hasTargetServiceLevelBeta rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:double ; rdfs:comment "Target Service Level: Target beta service level (Rate of demand to be fulfilled without delay)"@en . ### http://www.w3id.org/ecsel-dr-SO#hasTechnologyID rdf:type owl:DatatypeProperty ; rdfs:domain , , , , ; rdfs:range xsd:string ; rdfs:comment "Target Costs: FK; Name of the technology"@en , "Target Revenue: FK; Name of the technology"@en , "Target Service Level: FK; Name of the technology"@en , "Technology ID: FK; Assignment of product to highest product aggregation level (technology)"@en , "Technology ID: FK; Name of the technology"@en , "Technology: PK; Name of the technology"@en . ### http://www.w3id.org/ecsel-dr-SO#hasToolAvailability rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:boolean ; rdfs:comment "is tool available? boolean YES/NO"@en . ### http://www.w3id.org/ecsel-dr-SO#hasTransferMode rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Transfer Mode: Automation, AGV, milkrun or manual"@en . ### http://www.w3id.org/ecsel-dr-SO#hasTransferTime rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "Material Transfer: Duration of transfer from on to the other equipment"@en , "length of, or element of the length of, a temporal extent expressed in seconds"@en . ### http://www.w3id.org/ecsel-dr-SO#hasTravelTime rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "length of, or element of the length of, a temporal extent expressed in seconds"@en . ### http://www.w3id.org/ecsel-dr-SO#hasUnit rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "unit, added due to data import" . ### http://www.w3id.org/ecsel-dr-SO#hasUnitsPerTimePeriod rdf:type owl:DatatypeProperty ; rdfs:domain , ; rdfs:range xsd:integer ; rdfs:comment "Delivery Commitment: Quantity of committed delivery per time period (time period depends on company planning process)"@en , "Release Plan: Quantity of release per time period (time period depends on company)"@en . ### http://www.w3id.org/ecsel-dr-SO#hasVariancePTime rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:decimal ; rdfs:comment "Variance of capacity relevant operation processing time"@en , "length of, or element of the length of, a temporal extent expressed in seconds"@en . ### http://www.w3id.org/ecsel-dr-SO#hasWIPCostsPerUnitAndTimeUnit rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "Target Costs: Capital bounding costs + Storage costs + Mean production costs of a unit of a certain technology and time unit"@en . ### http://www.w3id.org/ecsel-dr-SO#hasWorkforce rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:integer ; rdfs:comment "Shift: Overall number of operational workers assigned to the shift"@en . ### http://www.w3id.org/ecsel-dr-SO#toEquipmentGroupID rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Material Transfer: FK; target EquipmentGroup of transfer"@en . ### http://www.w3id.org/ecsel-dr-SO#toFabID rdf:type owl:DatatypeProperty ; rdfs:domain ; rdfs:range xsd:string ; rdfs:comment "Supply Chain: FK; Sink ID of supply chain edge"@en . ################################################################# # Classes ################################################################# ### http://purl.org/dc/dcmitype/Service rdf:type owl:Class ; rdfs:subClassOf , . ### http://purl.org/dc/dcmitype/Software rdf:type owl:Class ; owl:equivalentClass ecsel-dr-AH:Software_system . ### http://purl.org/dc/terms/PhysicalResource terms:PhysicalResource rdf:type owl:Class . ### http://purl.org/ontology/is/core#InfoService rdf:type owl:Class ; rdfs:subClassOf . ### http://purl.org/vocommons/voaf#Vocabulary rdf:type owl:Class . ### http://www.ontologydesignpatterns.org/cp/owl/informationrealization.owl#InformationObject rdf:type owl:Class . ### http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Goal rdf:type owl:Class . ### http://www.w3.org/2006/time#DateTimeDescription time:DateTimeDescription rdf:type owl:Class ; rdfs:subClassOf time:GeneralDateTimeDescription , [ rdf:type owl:Restriction ; owl:onProperty time:hasTRS ; owl:hasValue ] , [ rdf:type owl:Restriction ; owl:onProperty time:day ; owl:allValuesFrom xsd:gDay ] , [ rdf:type owl:Restriction ; owl:onProperty time:month ; owl:allValuesFrom xsd:gMonth ] , [ rdf:type owl:Restriction ; owl:onProperty time:year ; owl:allValuesFrom xsd:gYear ] ; 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:label "Date-Time description"@en ; skos:definition "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 . ### http://www.w3.org/2006/time#DateTimeInterval time:DateTimeInterval rdf:type owl:Class ; rdfs:subClassOf time:ProperInterval ; rdfs:comment "DateTimeInterval is a subclass of ProperInterval, defined using the multi-element DateTimeDescription."@en ; rdfs:label "Date-time interval"@en ; skos:definition "DateTimeInterval is a subclass of ProperInterval, defined using the multi-element DateTimeDescription."@en ; skos:note ":DateTimeInterval can only be used for an interval whose limits coincide with a date-time element aligned to the calendar and timezone indicated. For example, while both have a duration of one day, the 24-hour interval beginning at midnight at the beginning of 8 May in Central Europe can be expressed as a :DateTimeInterval, but the 24-hour interval starting at 1:30pm cannot."@en . ### http://www.w3.org/2006/time#DayOfWeek time:DayOfWeek rdf:type owl:Class ; rdfs:subClassOf owl:Thing ; rdfs:comment "The day of week"@en ; rdfs:label "Day of week"@en ; skos:changeNote """Remove enumeration from definition, in order to allow other days to be used when required in other calendars. NOTE: existing days are still present as members of the class, but the class membership is now open. In the original OWL-Time the following constraint appeared: owl:oneOf ( time:Monday time:Tuesday time:Wednesday time:Thursday time:Friday time:Saturday time:Sunday ) ;"""@en ; skos:definition "The day of week"@en ; skos:note "Membership of the class :DayOfWeek is open, to allow for alternative week lengths and different day names."@en . ### http://www.w3.org/2006/time#Duration time:Duration rdf:type owl:Class ; rdfs:subClassOf time:TemporalDuration , [ rdf:type owl:Restriction ; owl:onProperty time:unitType ; owl:cardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:numericDuration ; owl:cardinality "1"^^xsd:nonNegativeInteger ] ; rdfs:comment "Duration of a temporal extent expressed as a number scaled by a temporal unit"@en ; rdfs:label "Time duration"@en ; skos:definition "Duration of a temporal extent expressed as a number scaled by a temporal unit"@en ; skos:note "Alternative to time:DurationDescription to support description of a temporal duration other than using a calendar/clock system."@en . ### http://www.w3.org/2006/time#DurationDescription time:DurationDescription rdf:type owl:Class ; rdfs:subClassOf time:GeneralDurationDescription , [ rdf:type owl:Restriction ; owl:onProperty time:hasTRS ; owl:hasValue ] , [ rdf:type owl:Restriction ; owl:onProperty time:days ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty time:hours ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty time:minutes ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty time:months ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty time:seconds ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty time:weeks ; owl:allValuesFrom xsd:decimal ] , [ rdf:type owl:Restriction ; owl:onProperty time:years ; owl:allValuesFrom xsd:decimal ] ; 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:label "Duration description"@en ; skos:definition "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 ; skos:note "In the Gregorian calendar the length of the month is not fixed. Therefore, a value like \"2.5 months\" cannot be exactly compared with a similar duration expressed in terms of weeks or days."@en . ### http://www.w3.org/2006/time#GeneralDateTimeDescription time:GeneralDateTimeDescription rdf:type owl:Class ; rdfs:subClassOf time:TemporalPosition , [ rdf:type owl:Restriction ; owl:onProperty time:unitType ; owl:cardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:dayOfWeek ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:monthOfYear ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:timeZone ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:day ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:dayOfYear ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:hour ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:minute ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:month ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:second ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:week ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:year ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] ; rdfs:comment "Description of date and time structured with separate values for the various elements of a calendar-clock system"@en ; rdfs:label "Generalized date-time description"@en ; skos:definition "Description of date and time structured with separate values for the various elements of a calendar-clock system"@en ; skos:note "Some combinations of properties are redundant - for example, within a specified :year if :dayOfYear is provided then :day and :month can be computed, and vice versa. Individual values should be consistent with each other and the calendar, indicated through the value of the :hasTRS property." . ### http://www.w3.org/2006/time#GeneralDurationDescription time:GeneralDurationDescription rdf:type owl:Class ; rdfs:subClassOf time:TemporalDuration , [ rdf:type owl:Restriction ; owl:onProperty time:hasTRS ; owl:cardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:days ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:hours ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:minutes ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:months ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:seconds ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:weeks ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:years ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] ; rdfs:comment "Description of temporal extent structured with separate values for the various elements of a calendar-clock system."@en ; rdfs:label "Generalized duration description"@en ; skos:definition "Description of temporal extent structured with separate values for the various elements of a calendar-clock system."@en ; skos:note "The extent of a time duration expressed as a GeneralDurationDescription depends on the Temporal Reference System. In some calendars the length of the week or month is not constant within the year. Therefore, a value like \"2.5 months\" may not necessarily be exactly compared with a similar duration expressed in terms of weeks or days. When non-earth-based calendars are considered even more care must be taken in comparing durations."@en . ### http://www.w3.org/2006/time#Instant time:Instant rdf:type owl:Class ; rdfs:subClassOf time:TemporalEntity ; owl:disjointWith time:ProperInterval ; rdfs:comment "A temporal entity with zero extent or duration"@en ; rdfs:label "Time instant"@en ; skos:definition "A temporal entity with zero extent or duration"@en . ### http://www.w3.org/2006/time#Interval time:Interval rdf:type owl:Class ; rdfs:subClassOf time:TemporalEntity ; rdfs:comment "A temporal entity with an extent or duration"@en ; rdfs:label "Time interval"@en ; skos:definition "A temporal entity with an extent or duration"@en . ### http://www.w3.org/2006/time#January time:January rdf:type owl:Class ; rdfs:subClassOf time:DateTimeDescription , [ rdf:type owl:Restriction ; owl:onProperty time:unitType ; owl:hasValue time:unitMonth ] , [ rdf:type owl:Restriction ; owl:onProperty time:month ; owl:hasValue "--01" ] ; rdfs:label "January" ; owl:deprecated "true"^^xsd:boolean ; skos:historyNote "This class was present in the 2006 version of OWL-Time. It was presented as an example of how DateTimeDescription could be specialized, but does not belong in the revised ontology. " . ### http://www.w3.org/2006/time#MonthOfYear time:MonthOfYear rdf:type owl:Class ; rdfs:subClassOf time:DateTimeDescription , [ rdf:type owl:Restriction ; owl:onProperty time:unitType ; owl:hasValue time:unitMonth ] , [ rdf:type owl:Restriction ; owl:onProperty time:day ; owl:cardinality "0"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:hour ; owl:cardinality "0"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:minute ; owl:cardinality "0"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:month ; owl:cardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:second ; owl:cardinality "0"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:week ; owl:cardinality "0"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:year ; owl:cardinality "0"^^xsd:nonNegativeInteger ] ; rdfs:comment "The month of the year"@en ; rdfs:label "Month of year"@en ; skos:definition "The month of the year"@en ; skos:editorialNote "Feature at risk - added in 2017 revision, and not yet widely used. "@en ; skos:note "Membership of the class :MonthOfYear is open, to allow for alternative annual calendars and different month names."@en . ### http://www.w3.org/2006/time#ProperInterval time:ProperInterval rdf:type owl:Class ; rdfs:subClassOf time:Interval ; 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:label "Proper interval"@en ; skos:definition "A temporal entity with non-zero extent or duration, i.e. for which the value of the beginning and end are different"@en . ### http://www.w3.org/2006/time#TRS time:TRS rdf:type owl:Class ; 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 ; rdfs:label "Temporal Reference System"@en ; skos:definition """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 ; skos:note "A taxonomy of temporal reference systems is provided in ISO 19108:2002 [ISO19108], including (a) calendar + clock systems; (b) temporal coordinate systems (i.e. numeric offset from an epoch); (c) temporal ordinal reference systems (i.e. ordered sequence of named intervals, not necessarily of equal duration)."@en . ### http://www.w3.org/2006/time#TemporalDuration time:TemporalDuration rdf:type owl:Class ; rdfs:comment "Time extent; duration of a time interval separate from its particular start position"@en ; rdfs:label "Temporal duration"@en ; skos:definition "Time extent; duration of a time interval separate from its particular start position"@en . ### http://www.w3.org/2006/time#TemporalEntity time:TemporalEntity rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:unionOf ( time:Instant time:Interval ) ] ; rdfs:subClassOf owl:Thing ; rdfs:comment "A temporal interval or instant." , "A temporal interval or instant."@en ; rdfs:isDefinedBy "http://www.w3.org/TR/owl-time/#time:TemporalEntity" ; rdfs:label "Temporal entity" , "Temporal entity"@en ; skos:definition "A temporal interval or instant."@en . ### http://www.w3.org/2006/time#TemporalPosition time:TemporalPosition rdf:type owl:Class ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty time:hasTRS ; owl:cardinality "1"^^xsd:nonNegativeInteger ] ; rdfs:comment "A position on a time-line"@en ; rdfs:label "Temporal position"@en ; skos:definition "A position on a time-line"@en . ### http://www.w3.org/2006/time#TemporalUnit time:TemporalUnit rdf:type owl:Class ; rdfs:subClassOf time:TemporalDuration ; 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:label "Temporal unit"@en ; skos:changeNote """Remove enumeration from definition, in order to allow other units to be used when required in other coordinate systems. NOTE: existing units are still present as members of the class, but the class membership is now open. In the original OWL-Time the following constraint appeared: owl:oneOf ( time:unitSecond time:unitMinute time:unitHour time:unitDay time:unitWeek time:unitMonth time:unitYear ) ;"""@en ; skos:definition "A standard duration, which provides a scale factor for a time extent, or the granularity or precision for a time position."@en ; skos:note "Membership of the class TemporalUnit is open, to allow for other temporal units used in some technical applications (e.g. millions of years, Baha'i month)."@en . ### http://www.w3.org/2006/time#TimePosition time:TimePosition rdf:type owl:Class ; rdfs:subClassOf time:TemporalPosition , [ rdf:type owl:Class ; owl:unionOf ( [ rdf:type owl:Restriction ; owl:onProperty time:nominalPosition ; owl:cardinality "1"^^xsd:nonNegativeInteger ] [ rdf:type owl:Restriction ; owl:onProperty time:numericPosition ; owl:cardinality "1"^^xsd:nonNegativeInteger ] ) ] ; 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:label "Time position"@en ; skos:definition "A temporal position described using either a (nominal) value from an ordinal reference system, or a (numeric) value in a temporal coordinate system. "@en . ### http://www.w3.org/2006/time#TimeZone time:TimeZone rdf:type owl:Class ; rdfs:comment """A Time Zone specifies the amount by which the local time is offset from UTC. A 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 ; rdfs:label "Time Zone"@en ; skos:definition """A Time Zone specifies the amount by which the local time is offset from UTC. A 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 ; skos:historyNote """In the original 2006 version of OWL-Time, the TimeZone class, with several properties corresponding to a specific model of time-zones, was defined in a separate namespace \"http://www.w3.org/2006/timezone#\". In the current version a class with same local name is put into the main OWL-Time namespace, removing the dependency on the external namespace. An alignment axiom tzont:TimeZone rdfs:subClassOf time:TimeZone . allows data encoded according to the previous version to be consistent with the updated ontology. """ ; skos:note """A designated timezone is associated with a geographic region. However, for a particular region the offset from UTC often varies seasonally, and the dates of the changes may vary from year to year. The timezone designation usually changes for the different seasons (e.g. Australian Eastern Standard Time vs. Australian Eastern Daylight Time). Furthermore, the offset for a timezone may change over longer timescales, though its designation might not. Detailed guidance about working with time zones is given in http://www.w3.org/TR/timezone/ ."""@en , "An ontology for time zone descriptions was described in [owl-time-20060927] and provided as RDF in a separate namespace tzont:. However, that ontology was incomplete in scope, and the example datasets were selective. Furthermore, since the use of a class from an external ontology as the range of an ObjectProperty in OWL-Time creates a dependency, reference to the time zone class has been replaced with the 'stub' class in the normative part of this version of OWL-Time."@en ; skos:scopeNote "In this implementation TimeZone has no properties defined. It should be thought of as an 'abstract' superclass of all specific timezone implementations." . ### http://www.w3.org/2006/time#Year time:Year rdf:type owl:Class ; rdfs:subClassOf time:DurationDescription , [ rdf:type owl:Restriction ; owl:onProperty time:days ; owl:cardinality "0"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:hours ; owl:cardinality "0"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:minutes ; owl:cardinality "0"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:months ; owl:cardinality "0"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:seconds ; owl:cardinality "0"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:weeks ; owl:cardinality "0"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty time:years ; owl:cardinality "1"^^xsd:nonNegativeInteger ] ; rdfs:comment "Year duration" ; rdfs:label "Year"@en ; owl:deprecated "true"^^xsd:boolean ; skos:definition "Year duration" ; skos:historyNote """Year was proposed in the 2006 version of OWL-Time as an example of how DurationDescription could be specialized to allow for a duration to be restricted to a number of years. It is deprecated in this edition of OWL-Time. """ ; skos:prefLabel "Anno"@it , "Année (calendrier)"@fr , "Ano"@pt , "Año"@es , "Jaar"@nl , "Jahr"@de , "Rok"@pl , "Year"@en , "Год"@ru , "سنة"@ar , "年"@ja , "年"@zh . ### http://www.w3.org/TR/vocab-ssn-ext/ObservationCollection rdf:type owl:Class ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty ; owl:minCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:maxQualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onDataRange owl:rational ] ; rdfs:comment "An Observation Collection has at least one member, and may have one of any of the other seven properties mentioned in restrictions." ; rdfs:isDefinedBy "http://www.w3.org/ns/ssn/ext/ObservationCollection" . ### http://www.w3.org/ns/org#Organization org:Organization rdf:type owl:Class ; owl:equivalentClass ecsel-dr-PROD: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." ; skos:prefLabel "Organization" . ### http://www.w3.org/ns/org#OrganizationalUnit org:OrganizationalUnit rdf:type owl:Class ; 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." ; skos:altLabel "Unit" ; skos:prefLabel "Organizational Unit" . ### http://www.w3.org/ns/sosa/ActuatableProperty rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] ; rdfs:comment "An actuatable quality (property, characteristic) of a FeatureOfInterest."@en ; rdfs:isDefinedBy ; rdfs:label "Actuatable Property"@en ; skos:definition "An actuatable quality (property, characteristic) of a FeatureOfInterest."@en ; skos:example "A window actuator acts by changing the state between a frame and a window. The ability of the window to be opened and closed is its ActuatableProperty."@en . ### http://www.w3.org/ns/sosa/Actuation rdf:type owl:Class ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:minCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:minCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:cardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:cardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:cardinality "1"^^xsd:nonNegativeInteger ] ; rdfs:comment "An Actuation carries out an (Actuation) Procedure to change the state of the world using an Actuator."@en ; rdfs:isDefinedBy ; rdfs:label "Actuation"@en ; skos:definition "An Actuation carries out an (Actuation) Procedure to change the state of the world using an Actuator."@en ; skos:example "The activity of automatically closing a window if the temperature in a room drops below 20 degree Celsius. The activity is the Actuation and the device that closes the window is the Actuator. The Procedure is the rule, plan, or specification that defines the conditions that triggers the Actuation, here a drop in temperature. "@en . ### http://www.w3.org/ns/sosa/Actuator rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:minCardinality "1"^^xsd:nonNegativeInteger ] ; rdfs:comment "A device that is used by, or implements, an (Actuation) Procedure that changes the state of the world."@en ; rdfs:isDefinedBy ; rdfs:label "Actuator"@en ; skos:definition "A device that is used by, or implements, an (Actuation) Procedure that changes the state of the world."@en ; skos:example "A window actuator for automatic window control, i.e., opening or closing the window."@en . ### http://www.w3.org/ns/sosa/FeatureOfInterest rdf:type owl:Class ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:minCardinality "1"^^xsd:nonNegativeInteger ] ; 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 ; rdfs:isDefinedBy ; rdfs:label "Feature Of Interest"@en ; skos:definition "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 ; skos:example "When measuring the height of a tree, the height is the observed ObservableProperty, 20m may be the Result of the Observation, and the tree is the FeatureOfInterest. A window is a FeatureOfInterest for an automatic window control Actuator."@en . ### http://www.w3.org/ns/sosa/ObservableProperty rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:allValuesFrom ] ; rdfs:comment "An observable quality (property, characteristic) of a FeatureOfInterest."@en ; rdfs:isDefinedBy ; rdfs:label "Observable Property"@en ; skos:definition "An observable quality (property, characteristic) of a FeatureOfInterest."@en ; skos:example "The height of a tree, the depth of a water body, or the temperature of a surface are examples of observable properties, while the value of a classic car is not (directly) observable but asserted."@en . ### http://www.w3.org/ns/sosa/Observation rdf:type owl:Class ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:minCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:cardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:cardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:cardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:cardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:cardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:cardinality "1"^^xsd:nonNegativeInteger ] ; 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 ; rdfs:isDefinedBy ; rdfs:label "Observation"@en ; skos:definition "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 ; skos: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."@en . ### http://www.w3.org/ns/sosa/Platform rdf:type owl:Class ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] ; rdfs:comment "A Platform is an entity that hosts other entities, particularly Sensors, Actuators, Samplers, and other Platforms."@en ; rdfs:isDefinedBy ; rdfs:label "Platform"@en ; skos:definition "A Platform is an entity that hosts other entities, particularly Sensors, Actuators, Samplers, and other Platforms."@en ; skos:example "A post, buoy, vehicle, ship, aircraft, satellite, cell-phone, human or animal may act as platforms for (technical or biological) sensors or actuators."@en . ### http://www.w3.org/ns/sosa/Procedure rdf:type owl:Class ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] ; 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 ; rdfs:isDefinedBy ; rdfs:label "Procedure"@en ; skos:definition "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 ; skos:example "The measured wind speed differs depending on the height of the sensor above the surface, e.g., due to friction. Consequently, procedures for measuring wind speed define a standard height for anemometers above ground, typically 10m for meteorological measures and 2m in Agrometeorology. This definition of height, sensor placement, and so forth are defined by the Procedure."@en ; skos:note "Many observations may be created via the same Procedure, the same way as many tables are assembled using the same instructions (as information objects, not their concrete realization)."@en . ### http://www.w3.org/ns/sosa/Result rdf:type owl:Class ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty ; owl:minCardinality "1"^^xsd:nonNegativeInteger ] ; 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 ; rdfs:isDefinedBy ; rdfs:label "Result"@en ; skos:definition "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 ; skos:example "The value 20 as the height of a certain tree together with the unit, e.g., Meter."@en . ### http://www.w3.org/ns/sosa/Sample rdf:type owl:Class ; rdfs:subClassOf , , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:minCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:minCardinality "1"^^xsd:nonNegativeInteger ] ; rdfs:comment "A Sample is the result from an act of Sampling."@en , "Feature which is intended to be representative of a FeatureOfInterest on which Observations may be made."@en , "Physical samples are sometimes known as 'specimens'."@en , """Samples are artifacts of an observational strategy, and have no significant function outside of their role in the observation process. The characteristics of the samples themselves are of little interest, except perhaps to the manager of a sampling campaign. A Sample is intended to sample some FatureOfInterest, so there is an expectation of at least one isSampleOf property. However, in some cases the identity, and even the exact type, of the sampled feature may not be known when observations are made using the sampling features."""@en ; rdfs:isDefinedBy ; rdfs:label "Sample"@en ; skos:definition "Feature which is intended to be representative of a FeatureOfInterest on which Observations may be made."@en ; skos:example "A 'station' is essentially an identifiable locality where a sensor system or Procedure may be deployed and an observation made. In the context of the observation model, it connotes the 'world in the vicinity of the station', so the observed properties relate to the physical medium at the station, and not to any physical artifact such as a mooring, buoy, benchmark, monument, well, etc."@en , "A statistical sample is often designed to be characteristic of an entire population, so that observations can be made regarding the sample that provide a good estimate of the properties of the population."@en ; skos:note "A transient sample, such as a ships-track or flight-line, might be identified and described, but is unlikely to be revisited exactly."@en . ### http://www.w3.org/ns/sosa/Sampler rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:minCardinality "1"^^xsd:nonNegativeInteger ] ; rdfs:comment "A device that is used by, or implements, a Sampling Procedure to create or transform one or more samples."@en ; rdfs:isDefinedBy ; rdfs:label "Sampler"@en ; skos:definition "A device that is used by, or implements, a Sampling Procedure to create or transform one or more samples."@en ; skos:example "A ball mill, diamond drill, hammer, hypodermic syringe and needle, image Sensor or a soil auger can all act as sampling devices (i.e., be Samplers). However, sometimes the distinction between the Sampler and the Sensor is not evident, as they are packaged as a unit. A Sampler need not be a physical device."@en . ### http://www.w3.org/ns/sosa/Sampling rdf:type owl:Class ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:minCardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:cardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:cardinality "1"^^xsd:nonNegativeInteger ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:cardinality "1"^^xsd:nonNegativeInteger ] ; rdfs:comment "An act of Sampling carries out a sampling Procedure to create or transform one or more samples."@en ; rdfs:isDefinedBy ; rdfs:label "Sampling"@en ; skos:definition "An act of Sampling carries out a sampling Procedure to create or transform one or more samples."@en ; skos:example "Crushing a rock sample in a ball mill."@en , "Digging a pit through a soil sequence."@en , "Dividing a field site into quadrants."@en , "Drawing blood from a patient."@en , "Drilling an observation well."@en , "Establishing a station for environmental monitoring."@en , "Registering an image of the landscape."@en , "Selecting a subset of a population."@en , "Sieving a powder to separate the subset finer than 100-mesh."@en , "Splitting a piece of drill-core to create two new samples."@en , "Taking a diamond-drill core from a rock outcrop."@en . ### http://www.w3.org/ns/sosa/Sensor rdf:type owl:Class ; owl:equivalentClass ecsel-dr-OOSMP:Sensor , ecsel-dr-RAMI40:Sensor ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:minCardinality "1"^^xsd:nonNegativeInteger ] ; 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:isDefinedBy ; rdfs:label "Sensor"@en ; skos:definition "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 ; skos:example "Accelerometers, gyroscopes, barometers, magnetometers, and so forth are Sensors that are typically mounted on a modern smart phone (which acts as Platform). Other examples of sensors include the human eyes."@en . ### http://www.w3.org/ns/sosa/sampling/RelationshipNature rdf:type owl:Class ; rdfs:comment "Nature of a relationship (between samples) - Members of this class indicate the nature of a relationship between two samples." ; rdfs:isDefinedBy "http://www.w3.org/ns/sosa/sampling/" . ### http://www.w3.org/ns/sosa/sampling/SampleRelationship rdf:type owl:Class ; rdfs:comment "Members of this class represent a relationship between a sample and another." ; rdfs:isDefinedBy "http://www.w3.org/ns/sosa/sampling/" . ### http://www.w3.org/ns/ssn/Condition rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "Used to specify ranges for qualities that act as Condition on a Systems' operation." ; rdfs:isDefinedBy ; rdfs:label "Condition" ; skos:example "For example, wind speed of 10-60m/s may be used as the Condition on a SystemProperty, for example, to state that a sensor has a particular Accuracy under that Condition." . ### http://www.w3.org/ns/ssn/Deployment rdf:type owl:Class ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] ; rdfs:comment "Describes the Deployment of one or more Systems for a particular purpose. Deployment may be done on a Platform."@en ; rdfs:isDefinedBy ; rdfs:label "Deployment"@en ; skos:definition "Describes the Deployment of one or more Systems for a particular purpose. Deployment may be done on a Platform."@en ; skos:example "For example, a temperature Sensor deployed on a wall, or a whole network of Sensors deployed for an Observation campaign."@en . ### http://www.w3.org/ns/ssn/Input rdf:type owl:Class ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:minCardinality "1"^^xsd:nonNegativeInteger ] ; rdfs:comment "Any information that is provided to a Procedure for its use."@en ; rdfs:isDefinedBy ; rdfs:label "Input"@en ; skos:definition "Any information that is provided to a Procedure for its use."@en . ### http://www.w3.org/ns/ssn/Output rdf:type owl:Class ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:minCardinality "1"^^xsd:nonNegativeInteger ] ; rdfs:comment "Any information that is reported from a Procedure."@en ; rdfs:isDefinedBy ; rdfs:label "Output"@en ; skos:definition "Any information that is reported from a Procedure."@en . ### http://www.w3.org/ns/ssn/OversamplingRate rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "Specifies the number of sensor measurements used internally to generate one sensor output result. (Oversampling rate = OSR)" ; rdfs:label "Oversampling Rate" . ### http://www.w3.org/ns/ssn/Property rdf:type owl:Class ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] ; rdfs:comment "A quality of an entity. An aspect of an entity that is intrinsic to and cannot exist without the entity."@en ; rdfs:isDefinedBy ; rdfs:label "Property"@en ; skos:definition "A quality of an entity. An aspect of an entity that is intrinsic to and cannot exist without the entity."@en . ### http://www.w3.org/ns/ssn/Stimulus rdf:type owl:Class ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:allValuesFrom ] ; 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 ; rdfs:isDefinedBy ; rdfs:label "Stimulus"@en ; skos:definition "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/System rdf:type owl:Class ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] , [ rdf:type owl:Restriction ; owl:onProperty [ owl:inverseOf ] ; owl:allValuesFrom ] ; 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 ; rdfs:isDefinedBy ; rdfs:label "System"@en ; skos:definition "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.w3.org/ns/ssn/systems/Accuracy rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy ; rdfs:label "Accuracy" . ### http://www.w3.org/ns/ssn/systems/ActuationRange rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "The range of property values that can be the Result of an Actuation under the defined Conditions." ; rdfs:isDefinedBy ; rdfs:label "Actuation Range" . ### http://www.w3.org/ns/ssn/systems/BatteryLifetime rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "Total useful life of a System's battery in the specified Conditions." ; rdfs:isDefinedBy ; rdfs:label "Battery Lifetime" . ### http://www.w3.org/ns/ssn/systems/DetectionLimit rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy ; rdfs:label "Detection Limit" . ### http://www.w3.org/ns/ssn/systems/Drift rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy ; rdfs:label "Drift" . ### http://www.w3.org/ns/ssn/systems/Frequency rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "The smallest possible time between one Observation, Actuation, or Sampling and the next, under the defined Conditions." ; rdfs:isDefinedBy ; rdfs:label "Frequency" . ### http://www.w3.org/ns/ssn/systems/Latency rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "The time between a command for an Observation and the Sensor providing a Result, under the defined Conditions." ; rdfs:isDefinedBy ; rdfs:label "Latency" . ### http://www.w3.org/ns/ssn/systems/MaintenanceSchedule rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "Schedule of maintenance for a System in the specified Conditions." ; rdfs:isDefinedBy ; rdfs:label "Maintenance Schdule" . ### http://www.w3.org/ns/ssn/systems/MeasurementRange rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy ; rdfs:label "Measurement Range" . ### http://www.w3.org/ns/ssn/systems/OperatingPowerRange rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "Power range in which System is expected to operate in the specified." ; rdfs:isDefinedBy ; rdfs:label "Operating Power Range" . ### http://www.w3.org/ns/ssn/systems/OperatingProperty rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy ; rdfs:label "Operating Property" . ### http://www.w3.org/ns/ssn/systems/OperatingRange rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy ; rdfs:label "Operating Range" . ### http://www.w3.org/ns/ssn/systems/Precision rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy ; rdfs:label "Precision" . ### http://www.w3.org/ns/ssn/systems/Resolution rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy ; rdfs:label "Resolution" . ### http://www.w3.org/ns/ssn/systems/ResponseTime rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy ; rdfs:label "Response Time" . ### http://www.w3.org/ns/ssn/systems/Selectivity rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy ; rdfs:label "Selectivity" . ### http://www.w3.org/ns/ssn/systems/Sensitivity rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy ; rdfs:label "Sensitivity" . ### http://www.w3.org/ns/ssn/systems/SurvivalProperty rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy ; rdfs:label "Survival Property" . ### http://www.w3.org/ns/ssn/systems/SurvivalRange rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy ; rdfs:label "Survival Range" . ### http://www.w3.org/ns/ssn/systems/SystemCapability rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] ; 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:isDefinedBy ; rdfs:label "System Capability" . ### http://www.w3.org/ns/ssn/systems/SystemLifetime rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy ; rdfs:label "System Lifetime" . ### http://www.w3.org/ns/ssn/systems/SystemProperty rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy ; rdfs:label "System Property" . ### http://www.w3id.org/ecsel-dr-AH#AH_AuthorizationControlService_IDD ecsel-dr-AH:AH_AuthorizationControlService_IDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_mandatory_core_service_IDD ; 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 . ### http://www.w3id.org/ecsel-dr-AH#AH_AuthorizationControlService_SD ecsel-dr-AH:AH_AuthorizationControlService_SD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_mandatory_core_service_SD . ### http://www.w3id.org/ecsel-dr-AH#AH_AuthorizationSystem_SySD ecsel-dr-AH:AH_AuthorizationSystem_SySD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_mandatory_core_system_SySD . ### http://www.w3id.org/ecsel-dr-AH#AH_AuthorizationSystem_SysDD ecsel-dr-AH:AH_AuthorizationSystem_SysDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_mandatory_core_system_SySDD . ### http://www.w3id.org/ecsel-dr-AH#AH_AuthorizationSystem_WADL ecsel-dr-AH:AH_AuthorizationSystem_WADL rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:System_WebApplicationDescription_WADL . ### http://www.w3id.org/ecsel-dr-AH#AH_DeviceDiscoveryService_IDD ecsel-dr-AH:AH_DeviceDiscoveryService_IDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_service_IDD ; rdfs:comment "Interface Design Description of the Arrowhead non-mandatory core service (automation supporting service) DeviceDiscovery, provided by the AH system DeviceRegistry."@en . ### http://www.w3id.org/ecsel-dr-AH#AH_DeviceDiscoveryService_SD ecsel-dr-AH:AH_DeviceDiscoveryService_SD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_service_SD ; rdfs:comment "Service Description of the Arrowhead non-mandatory core service (automation supporting service) DeviceDiscovery, provided by the AH system DeviceRegistry."@en . ### http://www.w3id.org/ecsel-dr-AH#AH_DeviceRegistrySystem_SySD ecsel-dr-AH:AH_DeviceRegistrySystem_SySD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_system_SySD . ### http://www.w3id.org/ecsel-dr-AH#AH_DeviceRegistrySystem_SySDD ecsel-dr-AH:AH_DeviceRegistrySystem_SySDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_system_SySDD . ### http://www.w3id.org/ecsel-dr-AH#AH_GatekeeperSystem_SySD ecsel-dr-AH:AH_GatekeeperSystem_SySD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_system_SySD . ### http://www.w3id.org/ecsel-dr-AH#AH_GatekeeperSystem_SySDD ecsel-dr-AH:AH_GatekeeperSystem_SySDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_system_SySDD . ### http://www.w3id.org/ecsel-dr-AH#AH_GatewaySystem_SySD ecsel-dr-AH:AH_GatewaySystem_SySD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_system_SySD . ### http://www.w3id.org/ecsel-dr-AH#AH_GatewaySystem_SySDD ecsel-dr-AH:AH_GatewaySystem_SySDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_system_SySDD . ### http://www.w3id.org/ecsel-dr-AH#AH_GlobalServiceDiscoveryService_IDD ecsel-dr-AH:AH_GlobalServiceDiscoveryService_IDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_service_IDD . ### http://www.w3id.org/ecsel-dr-AH#AH_GlobalServiceDiscoveryService_SD ecsel-dr-AH:AH_GlobalServiceDiscoveryService_SD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_service_SD . ### http://www.w3id.org/ecsel-dr-AH#AH_Historian_SySD ecsel-dr-AH:AH_Historian_SySD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_system_SySD . ### http://www.w3id.org/ecsel-dr-AH#AH_Historian_SysDD ecsel-dr-AH:AH_Historian_SysDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_system_SySDD . ### http://www.w3id.org/ecsel-dr-AH#AH_InterCloudNegotiationsService_IDD ecsel-dr-AH:AH_InterCloudNegotiationsService_IDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_service_IDD . ### http://www.w3id.org/ecsel-dr-AH#AH_InterCloudNegotiationsService_SD ecsel-dr-AH:AH_InterCloudNegotiationsService_SD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_service_SD . ### http://www.w3id.org/ecsel-dr-AH#AH_OrchestrationService_IDD ecsel-dr-AH:AH_OrchestrationService_IDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_mandatory_core_service_IDD ; 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 . ### http://www.w3id.org/ecsel-dr-AH#AH_OrchestrationService_SD ecsel-dr-AH:AH_OrchestrationService_SD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_mandatory_core_service_SD . ### http://www.w3id.org/ecsel-dr-AH#AH_OrchestrationSystem_SySD ecsel-dr-AH:AH_OrchestrationSystem_SySD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_mandatory_core_system_SySD . ### http://www.w3id.org/ecsel-dr-AH#AH_OrchestrationSystem_SysDD ecsel-dr-AH:AH_OrchestrationSystem_SysDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_mandatory_core_system_SySDD . ### http://www.w3id.org/ecsel-dr-AH#AH_Orchestrator_WADL ecsel-dr-AH:AH_Orchestrator_WADL rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:System_WebApplicationDescription_WADL . ### http://www.w3id.org/ecsel-dr-AH#AH_QoS-Manager_SySD ecsel-dr-AH:AH_QoS-Manager_SySD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_system_SySD . ### http://www.w3id.org/ecsel-dr-AH#AH_QoS-Manager_SySDD ecsel-dr-AH:AH_QoS-Manager_SySDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_system_SySDD . ### http://www.w3id.org/ecsel-dr-AH#AH_ServiceDiscoveryService_IDD ecsel-dr-AH:AH_ServiceDiscoveryService_IDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_mandatory_core_service_IDD ; 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 . ### http://www.w3id.org/ecsel-dr-AH#AH_ServiceDiscoveryService_SD ecsel-dr-AH:AH_ServiceDiscoveryService_SD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_mandatory_core_service_SD ; 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 . ### http://www.w3id.org/ecsel-dr-AH#AH_ServiceRegistrySystem_SySD ecsel-dr-AH:AH_ServiceRegistrySystem_SySD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_mandatory_core_system_SySD . ### http://www.w3id.org/ecsel-dr-AH#AH_ServiceRegistrySystem_SysDD ecsel-dr-AH:AH_ServiceRegistrySystem_SysDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_mandatory_core_system_SySDD . ### http://www.w3id.org/ecsel-dr-AH#AH_ServiceRegistry_WADL ecsel-dr-AH:AH_ServiceRegistry_WADL rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:System_WebApplicationDescription_WADL . ### http://www.w3id.org/ecsel-dr-AH#AH_SessionEstablishService_IDD ecsel-dr-AH:AH_SessionEstablishService_IDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_service_IDD . ### http://www.w3id.org/ecsel-dr-AH#AH_SessionEstablishService_SD ecsel-dr-AH:AH_SessionEstablishService_SD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_service_SD . ### http://www.w3id.org/ecsel-dr-AH#AH_SessionManagementService_IDD ecsel-dr-AH:AH_SessionManagementService_IDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_service_IDD . ### http://www.w3id.org/ecsel-dr-AH#AH_SessionManagementService_SD ecsel-dr-AH:AH_SessionManagementService_SD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_service_SD . ### http://www.w3id.org/ecsel-dr-AH#AH_StoreManagementService_IDD ecsel-dr-AH:AH_StoreManagementService_IDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_mandatory_core_service_IDD ; 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 . ### http://www.w3id.org/ecsel-dr-AH#AH_StoreManagementService_SD ecsel-dr-AH:AH_StoreManagementService_SD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_mandatory_core_service_SD ; rdfs:comment "Service Description (SD) of the Arrowhead mandatory core service Store Management Service which is provided by the mandatory core system Orchestrator."@en . ### http://www.w3id.org/ecsel-dr-AH#AH_SystemDiscoveryService_IDD ecsel-dr-AH:AH_SystemDiscoveryService_IDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_service_IDD . ### http://www.w3id.org/ecsel-dr-AH#AH_SystemDiscoveryService_SD ecsel-dr-AH:AH_SystemDiscoveryService_SD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_service_SD . ### http://www.w3id.org/ecsel-dr-AH#AH_SystemRegistrySystem_SySD ecsel-dr-AH:AH_SystemRegistrySystem_SySD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_system_SySD . ### http://www.w3id.org/ecsel-dr-AH#AH_SystemRegistrySystem_SySDD ecsel-dr-AH:AH_SystemRegistrySystem_SySDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_automation_supporting_system_SySDD . ### http://www.w3id.org/ecsel-dr-AH#AH_TokenGenerationServcie_SD ecsel-dr-AH:AH_TokenGenerationServcie_SD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_mandatory_core_service_SD . ### http://www.w3id.org/ecsel-dr-AH#AH_TokenGenerationService_IDD ecsel-dr-AH:AH_TokenGenerationService_IDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_mandatory_core_service_IDD ; 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 . ### http://www.w3id.org/ecsel-dr-AH#AH_application_servcice_IDD ecsel-dr-AH:AH_application_servcice_IDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Interface_Design_Description_IDD . ### http://www.w3id.org/ecsel-dr-AH#AH_application_service ecsel-dr-AH:AH_application_service rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_service ; rdfs:comment "Application services – they are application specific and are implemented by application systems along with functionalities (to match requirements of an application)"@en . ### http://www.w3id.org/ecsel-dr-AH#AH_application_service_SD ecsel-dr-AH:AH_application_service_SD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Service_Description_SD . ### http://www.w3id.org/ecsel-dr-AH#AH_application_system ecsel-dr-AH:AH_application_system rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_system ; owl:disjointWith ecsel-dr-AH:AH_core_system ; rdfs:label "Arrowhead Application Component"@en , "Arrowhead Application System"@en . ### http://www.w3id.org/ecsel-dr-AH#AH_application_system_SySD ecsel-dr-AH:AH_application_system_SySD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:System_Description_SySD . ### http://www.w3id.org/ecsel-dr-AH#AH_application_system_SySDD ecsel-dr-AH:AH_application_system_SySDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:System_Design_Description_SySDD . ### http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service ecsel-dr-AH:AH_automation_supporting_service rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_core_service . ### http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service_IDD ecsel-dr-AH:AH_automation_supporting_service_IDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_core_service_IDD . ### http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_service_SD ecsel-dr-AH:AH_automation_supporting_service_SD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_core_service_SD . ### http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system ecsel-dr-AH:AH_automation_supporting_system rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_core_system ; owl:disjointWith ecsel-dr-AH:AH_mandatory_core_system . ### http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system_SySD ecsel-dr-AH:AH_automation_supporting_system_SySD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_core_system_SySD . ### http://www.w3id.org/ecsel-dr-AH#AH_automation_supporting_system_SySDD ecsel-dr-AH:AH_automation_supporting_system_SySDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_core_system_SySDD . ### http://www.w3id.org/ecsel-dr-AH#AH_core_service ecsel-dr-AH:AH_core_service rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_service . ### http://www.w3id.org/ecsel-dr-AH#AH_core_service_IDD ecsel-dr-AH:AH_core_service_IDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Interface_Design_Description_IDD . ### http://www.w3id.org/ecsel-dr-AH#AH_core_service_SD ecsel-dr-AH:AH_core_service_SD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Service_Description_SD . ### http://www.w3id.org/ecsel-dr-AH#AH_core_system ecsel-dr-AH:AH_core_system rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_system ; 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:label "Arrowhead Core Component"@en , "Arrowhead Core System"@en . ### http://www.w3id.org/ecsel-dr-AH#AH_core_system_SySD ecsel-dr-AH:AH_core_system_SySD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:System_Description_SySD . ### http://www.w3id.org/ecsel-dr-AH#AH_core_system_SySDD ecsel-dr-AH:AH_core_system_SySDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:System_Design_Description_SySDD . ### http://www.w3id.org/ecsel-dr-AH#AH_local_cloud ecsel-dr-AH:AH_local_cloud rdf:type owl:Class ; rdfs:comment """An Arrowhead Local Cloud consists of one or several devices which are connected by an appropriate communication technology (typically a TCP/IP based local network on arbitrary wired or wireless data link and media access layer). One instance of each of the three mandatory AH core systems is running on one of the devices. On each device at least one AH system is running offering and/or consuming AH services."""@en , """An Arrowhead Local Cloud is a self-contained network with the three mandatory core systems deployed and at least one application system deployed. (Source: Arrowhead Device Registry Presentation 09/2017)"""@de , """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#AH_mandatory_core_service ecsel-dr-AH:AH_mandatory_core_service rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_core_service . ### http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_service_IDD ecsel-dr-AH:AH_mandatory_core_service_IDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_core_service_IDD ; 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 . ### http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_service_SD ecsel-dr-AH:AH_mandatory_core_service_SD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_core_service_SD . ### http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_system ecsel-dr-AH:AH_mandatory_core_system rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_core_system . ### http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_system_SySD ecsel-dr-AH:AH_mandatory_core_system_SySD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_core_system_SySD . ### http://www.w3id.org/ecsel-dr-AH#AH_mandatory_core_system_SySDD ecsel-dr-AH:AH_mandatory_core_system_SySDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_core_system_SySDD . ### http://www.w3id.org/ecsel-dr-AH#AH_service ecsel-dr-AH:AH_service rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Service ; 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 . ### http://www.w3id.org/ecsel-dr-AH#AH_service_documentation ecsel-dr-AH:AH_service_documentation rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Service_documentation . ### http://www.w3id.org/ecsel-dr-AH#AH_service_documentation_document ecsel-dr-AH:AH_service_documentation_document rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Documentation_document ; 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 . ### http://www.w3id.org/ecsel-dr-AH#AH_system ecsel-dr-AH:AH_system rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Software_system ; 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:label "Arrowhead component"@en , "Arrowhead system"@en . ### http://www.w3id.org/ecsel-dr-AH#AH_system_documentation ecsel-dr-AH:AH_system_documentation rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:System_documentation . ### http://www.w3id.org/ecsel-dr-AH#AH_system_documentation_document ecsel-dr-AH:AH_system_documentation_document rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Documentation_document . ### http://www.w3id.org/ecsel-dr-AH#AH_system_of_systems_documentation ecsel-dr-AH:AH_system_of_systems_documentation rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:System_documentation . ### http://www.w3id.org/ecsel-dr-AH#AH_system_of_systems_documentation_document ecsel-dr-AH:AH_system_of_systems_documentation_document rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Documentation_document . ### http://www.w3id.org/ecsel-dr-AH#Arrowhead ecsel-dr-AH:Arrowhead rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Service-oriented_Architecture ; rdfs:comment """The Arrowhead Framework is addressing IoT based automation. The approach take is that IoT's are abstracted to services. This to enable IoT interoperability in-between almost any IoT's. The creation of automation is based on the idea of local automation clouds."""@en , """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:label "AH"@en . ### http://www.w3id.org/ecsel-dr-AH#Communication_Profile_CP ecsel-dr-AH:Communication_Profile_CP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_service_documentation_document ; rdfs:comment """- It is associated a unique CP identifier that reports: + Transfer protocol (e.g., CoAP, REST_WS, DDS, JMS) + Security mechanism (e.g., DTLS, TLS, none) + Data format (e.g., XML, EXI, XTREE, JSON, IDL) It contains: - Message exchange patterns: request-response, publish-subscribe, one-to-many, etc - How security is handled - Endpoints, format depending on transfer protocol (IP address/port? XMPP chat room? AMQP queues and exchanges?) - Name of functions used for encoding / decoding - Meta-data used for transmission - Encoding: XML, JASON, etc. It must report examples of encoded messages - Pointers for external documents: + Standards used in the CP: EXI, XML, TLS, DDS, etc + Formal schema for encoding / decoding: xsd files, etc (Source: Arrowhead Wiki, last access 2019-03-25)"""@en , "Provides a description of technologies and specifications that build the Communication Profile of Arrowhead compliant services. It is identified by the following three characteristics: transfer protocol (e.g., CoAP, OPC-UA) and chosen lower level technology (e.g.802.15.4, ethernet, mod-bus), and security mechanism (e.g., DTLS). (Source: Arrowhead Framework Definitions V2.4)"@en , """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 . ### http://www.w3id.org/ecsel-dr-AH#Communication_security_mechanism ecsel-dr-AH:Communication_security_mechanism rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Communication_technology ; rdfs:comment "corresponds to a part of OSI layer 5" . ### http://www.w3id.org/ecsel-dr-AH#Communication_technology ecsel-dr-AH:Communication_technology rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AH#Constrained_device ecsel-dr-AH:Constrained_device rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Device ; 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 . ### http://www.w3id.org/ecsel-dr-AH#Data_format ecsel-dr-AH:Data_format rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AH#Data_link_and_media_access_technology ecsel-dr-AH:Data_link_and_media_access_technology rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Communication_technology ; rdfs:comment "corresponds to OSI layer 1 and 2 technologies, like Ethernet, WLAN (802.11), WPAN (802.15.4), EtherCAT, ProfiNet, ..." . ### http://www.w3id.org/ecsel-dr-AH#Data_model ecsel-dr-AH:Data_model rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AH#Device ecsel-dr-AH:Device rdf:type owl:Class ; owl:equivalentClass ecsel-dr-AT:Device , ; rdfs:comment """A device in the context of Arrowhead framework is a piece of equipment, machine, hardware, etc. with computational, memory, and communication capabilities which hosts one or several Arrowhead Framework systems. (Source: Arrowhead)"""@en , "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#Documentation_document ecsel-dr-AH:Documentation_document rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AH#End-to-End_communication_technology ecsel-dr-AH:End-to-End_communication_technology rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Communication_technology . ### http://www.w3id.org/ecsel-dr-AH#Gateway ecsel-dr-AH:Gateway rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Device . ### http://www.w3id.org/ecsel-dr-AH#Illumination_device ecsel-dr-AH:Illumination_device rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Constrained_device . ### http://www.w3id.org/ecsel-dr-AH#Industrial_personal_computer ecsel-dr-AH:Industrial_personal_computer rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Device ; rdfs:label "IPC"@en . ### http://www.w3id.org/ecsel-dr-AH#InformationModel ecsel-dr-AH:InformationModel rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AH#Interface_Design_Description_IDD ecsel-dr-AH:Interface_Design_Description_IDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_service_documentation_document ; 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 . ### http://www.w3id.org/ecsel-dr-AH#Local_network ecsel-dr-AH:Local_network rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AH#Method ecsel-dr-AH:Method rdf:type owl: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#Personal_computer ecsel-dr-AH:Personal_computer rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Device ; rdfs:label "PC"@en . ### http://www.w3id.org/ecsel-dr-AH#Point-to-Point_communication_technology ecsel-dr-AH:Point-to-Point_communication_technology rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Communication_technology ; rdfs:comment "corresponds to OSI layer 3, e.g. IPv4 or IPv6" . ### http://www.w3id.org/ecsel-dr-AH#Programmable_Logic_Controller ecsel-dr-AH:Programmable_Logic_Controller rdf:type owl:Class ; owl:equivalentClass ecsel-dr-AT:PLC ; rdfs:subClassOf ecsel-dr-AH:Device ; rdfs:label "PLC"@en , "SPS"@de . ### http://www.w3id.org/ecsel-dr-AH#Raspberry_Pi ecsel-dr-AH:Raspberry_Pi rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Device . ### http://www.w3id.org/ecsel-dr-AH#Semantic_Profile_SP ecsel-dr-AH:Semantic_Profile_SP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_service_documentation_document ; rdfs:comment """Framework Design Template: Semantic Profile Implementation related: what data means - It specifies the information model It contains: - How a specific piece of data (e.g., a temperature value or a pressure value) is encoded + Meaning of each field of each message type + Examples of the data structures used (opt.) - UML diagram for the data structure (opt.) - XSD describing how data is formatted for transmission (opt.) - Pointer to standards (XML, EXI, etc) Source: Arrowhead Wiki, last access 2019-03-25"""@en , "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 , """Remark HB: the description in the Arrowhead Framework Definitions V2.4 document and in Arrowhead Wiki are inconsistent! We assume the Wiki to be more actual."""@en . ### http://www.w3id.org/ecsel-dr-AH#Sensor_device ecsel-dr-AH:Sensor_device rdf:type owl:Class ; owl:equivalentClass ecsel-dr-AT:SensorDevice ; rdfs:subClassOf ecsel-dr-AH:Constrained_device . ### http://www.w3id.org/ecsel-dr-AH#Service ecsel-dr-AH:Service rdf:type owl:Class ; owl:disjointWith ecsel-dr-AH:Software_system ; 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 ; rdfs:label "Service"@en . ### http://www.w3id.org/ecsel-dr-AH#Service-oriented_Architecture ecsel-dr-AH:Service-oriented_Architecture rdf:type owl:Class ; rdfs:label "SoA"@en . ### http://www.w3id.org/ecsel-dr-AH#Service_Description_SD ecsel-dr-AH:Service_Description_SD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_service_documentation_document ; 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 . ### http://www.w3id.org/ecsel-dr-AH#Service_documentation ecsel-dr-AH:Service_documentation rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AH#Smartphone ecsel-dr-AH:Smartphone rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Device . ### http://www.w3id.org/ecsel-dr-AH#SoA_property ecsel-dr-AH:SoA_property rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AH#Software_system ecsel-dr-AH:Software_system rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AH#Switch_device ecsel-dr-AH:Switch_device rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Constrained_device . ### http://www.w3id.org/ecsel-dr-AH#System-of-Systems ecsel-dr-AH:System-of-Systems rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AH#System-of-Systems_Description_SoSD ecsel-dr-AH:System-of-Systems_Description_SoSD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_system_of_systems_documentation_document ; 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 . ### http://www.w3id.org/ecsel-dr-AH#System-of-Systems_Design_Description_SoSDD ecsel-dr-AH:System-of-Systems_Design_Description_SoSDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_system_of_systems_documentation_document ; 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 . ### http://www.w3id.org/ecsel-dr-AH#System_Description_SySD ecsel-dr-AH:System_Description_SySD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_system_documentation_document ; 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 . ### http://www.w3id.org/ecsel-dr-AH#System_Design_Description_SySDD ecsel-dr-AH:System_Design_Description_SySDD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_system_documentation_document ; 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 . ### http://www.w3id.org/ecsel-dr-AH#System_WebApplicationDescription_WADL ecsel-dr-AH:System_WebApplicationDescription_WADL rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:AH_system_documentation_document ; 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 . ### http://www.w3id.org/ecsel-dr-AH#System_documentation ecsel-dr-AH:System_documentation rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AH#Tablet_computer ecsel-dr-AH:Tablet_computer rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Device . ### http://www.w3id.org/ecsel-dr-AH#Transfer_protocol ecsel-dr-AH:Transfer_protocol rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AH:Communication_technology ; rdfs:comment "corresponds to OSI layers 6 and 7" . ### http://www.w3id.org/ecsel-dr-AT#AGV ecsel-dr-AT:AGV rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ActuatorDevice ; rdfs:label "AGV"@en , "Autonomously Guided Vehicle"@en , "FTF"@de , "Fahrerloses Transportfahrzeug"@de . ### http://www.w3id.org/ecsel-dr-AT#AMQP ecsel-dr-AT:AMQP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; rdfs:comment """AMQP (Advanced Message Queuing Protocol) \"An open standard application layer protocol for message-oriented middleware. The defining features of AMQP are message orientation, queuing, routing (including point-to-point and publish-and-subscribe), reliability and security.\" (https://www.postscapes.com/internet-of-things-protocols/ )"""@en , """AMQP mandates the behavior of the messaging provider and client to the extent that implementations from different vendors are interoperable, in the same way as SMTP, HTTP, FTP, etc. have created interoperable systems. Previous standardizations of middleware have happened at the API level (e.g. JMS) and were focused on standardizing programmer interaction with different middleware implementations, rather than on providing interoperability between multiple implementations.[2] Unlike JMS, which defines an API and a set of behaviors that a messaging implementation must provide, AMQP is a wire-level protocol. A wire-level protocol is a description of the format of the data that is sent across the network as a stream of bytes. Consequently, any tool that can create and interpret messages that conform to this data format can interoperate with any other compliant tool irrespective of implementation language. (https://en.wikipedia.org/wiki/Advanced_Message_Queuing_Protocol)"""@en , """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:label "Advanced Message Queuing Protocol"@en . ### http://www.w3id.org/ecsel-dr-AT#ANSI ecsel-dr-AT:ANSI rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:StandardisationOrganization . ### http://www.w3id.org/ecsel-dr-AT#ANSI-Standard ecsel-dr-AT:ANSI-Standard rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Standard . ### http://www.w3id.org/ecsel-dr-AT#ANSI_X12-DataFormat ecsel-dr-AT:ANSI_X12-DataFormat rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L2_DataSyntax . ### http://www.w3id.org/ecsel-dr-AT#ANSI_X12-Specification ecsel-dr-AT:ANSI_X12-Specification rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:EDI_Specification . ### http://www.w3id.org/ecsel-dr-AT#APS ecsel-dr-AT:APS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:IT-System ; rdfs:label "Advanced Planning System"@de . ### http://www.w3id.org/ecsel-dr-AT#ARCNET ecsel-dr-AT:ARCNET rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_1_2_NetAccessTechnology ; 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 . ### http://www.w3id.org/ecsel-dr-AT#AS2 ecsel-dr-AT:AS2 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; 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:label "Applicability Statement 2"@de . ### http://www.w3id.org/ecsel-dr-AT#ActuatorDevice ecsel-dr-AT:ActuatorDevice rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Device . ### http://www.w3id.org/ecsel-dr-AT#AppleTalk ecsel-dr-AT:AppleTalk rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_3_4_NetworkTechnology ; rdfs:comment "Outdated, replaced by IP-based service system by Apple, cf. Bonjour."@de . ### http://www.w3id.org/ecsel-dr-AT#AssemblyLinePlanning ecsel-dr-AT:AssemblyLinePlanning rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:PLM1_Module . ### http://www.w3id.org/ecsel-dr-AT#AutomationML ecsel-dr-AT:AutomationML rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:MarkupLanguage . ### http://www.w3id.org/ecsel-dr-AT#B2MML ecsel-dr-AT:B2MML rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:MarkupLanguage ; 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 , "Reference from article by Dennis Brandl"@en , """Software applications using B2MML import and export information using a standard “data exchange model.” This model does not represent the internal data structure of an application, but provides a vendor- and application-independent way to represent commonly exchanged information objects. This results in loose data coupling, because a change in one application does not require changes in other applications. The downside is that B2MML imports and exports are slower and are usually performed using a queued message exchange system, such as an enterprise service bus or manufacturing service bus. Queued message exchange systems provide guaranteed message delivery at the expense of reading and writing messages to permanent storage to handle service disruptions and equipment failures."""@en ; rdfs:label "Business to Manufacturing Markup Language"@en . ### http://www.w3id.org/ecsel-dr-AT#B2MML-based-Service ecsel-dr-AT:B2MML-based-Service rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ServiceOrientedArchitecture . ### http://www.w3id.org/ecsel-dr-AT#BI-System ecsel-dr-AT:BI-System rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:IT-System ; rdfs:label "Business Intelligence System"@de . ### http://www.w3id.org/ecsel-dr-AT#BigDataAnalytics-System ecsel-dr-AT:BigDataAnalytics-System rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:IT-System . ### http://www.w3id.org/ecsel-dr-AT#Bit ecsel-dr-AT:Bit rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:DataTransmissionUnit ; rdfs:comment "Base element of technical (physical) data transfer. Binary information: 0 or 1. May be represented by electromagnetical principles like wave modulation."@en . ### http://www.w3id.org/ecsel-dr-AT#Bluetooth ecsel-dr-AT:Bluetooth rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_1_2_NetAccessTechnology . ### http://www.w3id.org/ecsel-dr-AT#Bridge ecsel-dr-AT:Bridge rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:CommunicationDevice . ### http://www.w3id.org/ecsel-dr-AT#CAD-System ecsel-dr-AT:CAD-System rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:IT-System ; rdfs:label "Computer Aided Design System"@en . ### http://www.w3id.org/ecsel-dr-AT#CAN_Bus ecsel-dr-AT:CAN_Bus rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_Car_Airplane ; 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:label "Controller Area Network Bus"@de . ### http://www.w3id.org/ecsel-dr-AT#CPF10_VNET_IP ecsel-dr-AT:CPF10_VNET_IP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family . ### http://www.w3id.org/ecsel-dr-AT#CPF11_TCNet ecsel-dr-AT:CPF11_TCNet rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family . ### http://www.w3id.org/ecsel-dr-AT#CPF12_EtherCAT ecsel-dr-AT:CPF12_EtherCAT rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family ; rdfs:comment """EtherCAT (Ethernet for Control Automation Technology) ist ein von der Firma Beckhoff Automation initiiertes Echtzeit-Ethernet. Das in IEC-Standard 61158 offengelegte Protokoll eignet sich für harte wie weiche Echtzeitanforderungen in der Automatisierungstechnik. Die Schwerpunkte der Entwicklung von EtherCAT lagen auf kurzen Zykluszeiten (≤ 100 µs), niedrigem Jitter für exakte Synchronisierung (≤ 1 µs) und niedrigen Hardwarekosten. EtherCAT unterscheidet sich wesentlich von anderen Industrial Ethernet Lösungen. Während bei diesen der vom Master versendete Standard Ethernet Frame (gemäß IEEE 802.3) in jeder Anschaltung zunächst empfangen, dann interpretiert und die Prozessdaten weiterkopiert werden, entnehmen beim EtherCAT die EtherCAT Slave-Geräte die für sie bestimmten Daten, während das Telegramm das Gerät durchläuft. Ebenso werden Eingangsdaten im Durchlauf in das Telegramm eingefügt. Dabei wird ein Rahmen nicht vollständig empfangen, bevor er verarbeitet wird, sondern die Bearbeitung wird so früh wie möglich begonnen. Das Versenden erfolgt ebenso mit einem minimalen Versatz von wenigen Bitzeiten. ISO/OSI Referenzmodell Das ISO/OSI Modell für EtherCAT (Ethernet for Control Automation Technology) zeigt, dass EtherCAT die OSI-Schichten 1, 2 und 7 umfasst. Die Ebenen 3 bis 6 (\"TCP/IP-Stack\") werden nicht benötigt. (\"Der hier dargestellte TCP/IP-Stack wird für typische Feldgeräte nicht benötigt. Die EtherCAT-Master können ohne komplexe Tools über Standard-Mechanismen alle Daten eines EtherCAT-Slaves mit Namen und Datentypen darstellen.\"). EtherCAT nutzt den Ethernet Standard (IEEE 802.3 – Ethernet MAC und PHY) ohne Modifikationen."""@de , "s. auch Beckhoff-Vortrag im Folder der Automatisierungstechnik-VL der TU München von 2008" . ### http://www.w3id.org/ecsel-dr-AT#CPF13_EthernetPowerlink ecsel-dr-AT:CPF13_EthernetPowerlink rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family . ### http://www.w3id.org/ecsel-dr-AT#CPF14_EPA ecsel-dr-AT:CPF14_EPA rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family . ### http://www.w3id.org/ecsel-dr-AT#CPF15_ModBus ecsel-dr-AT:CPF15_ModBus rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family ; 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 . ### http://www.w3id.org/ecsel-dr-AT#CPF16_SERCOS ecsel-dr-AT:CPF16_SERCOS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family . ### http://www.w3id.org/ecsel-dr-AT#CPF17_RAPINet ecsel-dr-AT:CPF17_RAPINet rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family . ### http://www.w3id.org/ecsel-dr-AT#CPF18_SafetyNet_p ecsel-dr-AT:CPF18_SafetyNet_p rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family . ### http://www.w3id.org/ecsel-dr-AT#CPF1_FOUNDATION_Fieldbus ecsel-dr-AT:CPF1_FOUNDATION_Fieldbus rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family . ### http://www.w3id.org/ecsel-dr-AT#CPF2_ControlNet ecsel-dr-AT:CPF2_ControlNet rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family . ### http://www.w3id.org/ecsel-dr-AT#CPF3_1_Profibus_DP ecsel-dr-AT:CPF3_1_Profibus_DP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:CPF3_Profibus_ProfiNet ; 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.""" . ### http://www.w3id.org/ecsel-dr-AT#CPF3_2_Profibus_PA ecsel-dr-AT:CPF3_2_Profibus_PA rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:CPF3_Profibus_ProfiNet ; 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.""" . ### http://www.w3id.org/ecsel-dr-AT#CPF3_3_Profinet_CBA ecsel-dr-AT:CPF3_3_Profinet_CBA rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:CPF3_Profibus_ProfiNet ; rdfs:comment """PROFINET (Process Field Network) ist der offene Industrial-Ethernet-Standard der PROFIBUS-Nutzerorganisation e. V. (PNO) für die Automatisierung. Profinet nutzt TCP/IP und IT-Standards, ist Echtzeit-Ethernet-fähig und ermöglicht die Integration von Feldbus-Systemen. Das Konzept von Profinet ist modular aufgebaut, so dass der Anwender die Funktionalität selbst wählen kann. Diese unterscheidet sich im Wesentlichen durch die Art des Datenaustauschs, um den Anforderungen an Geschwindigkeit gerecht zu werden. Bei Profinet gibt es die beiden Sichtweisen Profinet IO und Profinet CBA: 1. Profinet IO (Input - Output) ist für die Anbindung von dezentraler Peripherie an eine Steuerung (Controller) geschaffen worden. Für die unterschiedlichen Einsatzgebiete sind die verfügbaren Funktionen und Echtzeit-Eigenschaften in die drei Konformitätsklassen CC-A, CC-B und CC-C aufgeteilt. 2. Profinet CBA (Component Based Automation) ist für die komponentenbasierte Kommunikation über TCP/IP und die Real-Time-Kommunikation für Echtzeitanforderungen im modularen Anlagenbau gedacht. Beide Kommunikationswege können parallel genutzt werden. Profinet IO und Profinet CBA können zur gleichen Zeit am selben Bussystem kommunizieren. Sie können sowohl separat betrieben als auch kombiniert werden, so dass eine Teilanlage mit Profinet IO in der Anlagensicht als eine Profinet-CBA-Anlage erscheint. Profinet IO erlaubt die Anbindung von dezentraler Peripherie an einen Controller und kann somit als direkter Nachfolger von Profibus DP gesehen werden. Profinet IO beschreibt den gesamten Datenaustausch zwischen Geräten mit Steuerungs- oder Regelungs-Funktionalität als IO-Controller und den Feldgeräten als IO-Devices für den zyklischen Datenaustausch sowie die Parametrierung und Diagnose. Dazu verwendet Profinet IO Ethernet-basierte Protokolle, folgt dem Producer-/Consumer-Modell und eignet sich je nach Konformitätsklasse für Buszykluszeiten von mehreren ms bis zu 31,25 μs. Feldgeräte in einem unterlagerten Feldbus-Strang können über einen IO-Proxy (Stellvertreter für ein unterlagertes Bussystem) in das Profinet-IO-System eingebunden werden. Damit können bestehende Profibus- oder Interbus-Systeme einfach in ein Profinet-IO-System eingebunden und weiterverwendet werden."""@de , """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""" , """https://de.wikipedia.org/wiki/Profinet Schöne Grafik mit dem OSI-Schichtenmodell und vier verschiedenen Grundkonfigurationen für Profinet (je zwei für Profinet IO und CBA, davon je eine ohne Zwischenstufen zwischen Ebene 2 und 7 und eine mit Zwischenstufen).""" . ### http://www.w3id.org/ecsel-dr-AT#CPF3_4_Profinet_IO_ClassA ecsel-dr-AT:CPF3_4_Profinet_IO_ClassA rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:CPF3_Profibus_ProfiNet . ### http://www.w3id.org/ecsel-dr-AT#CPF3_5_Profinet_IO_ClassB ecsel-dr-AT:CPF3_5_Profinet_IO_ClassB rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:CPF3_Profibus_ProfiNet . ### http://www.w3id.org/ecsel-dr-AT#CPF3_6_Profinet_IO_ClassC ecsel-dr-AT:CPF3_6_Profinet_IO_ClassC rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:CPF3_Profibus_ProfiNet . ### http://www.w3id.org/ecsel-dr-AT#CPF3_Profibus_ProfiNet ecsel-dr-AT:CPF3_Profibus_ProfiNet rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family ; rdfs:comment "Die Communication Protocol Family Profibus und Profinet ist eine Familie von Feldbus-Systemen."@de , """Profibus definiert drei Ebenen des OSI-Modells: Ebene 1, 2 und 7 (Datenübertragung, Sicherung und Anwendung). Die anderen Schichten werden nicht benötigt, (HB: da es sich um ein lokal begrenztes System mit bekannten Teilnehmern handelt). Anwendungsschicht: Die DP-Anwendungsschicht wurde in drei Schritten definiert. Das ursprünglich 1993 festgeschriebene DP-Protokoll wird heute umgangssprachlich als „DP-V0“ bezeichnet, die beiden Erweiterungen entsprechend „DP-V1“ und „DP-V2“. In den einzelnen Stufen wurden folgende Funktionen definiert: In DP-V0 der zyklische Austausch der Daten und Diagnosen. Geräte, die diesen Funktionsumfang unterstützen, finden vor allem in der allgemeinen Automatisierungstechnik und Maschinensteuerung Einsatz. In DP-V1 der azyklische Datenaustausch und die Alarmbehandlung. Geräte, die diese Erweiterungen unterstützen, finden sich vor allem in der Verfahrenstechnik. In DP-V2 der isochrone Datenaustausch, der Slave-Querverkehr und die Uhrzeitsynchronisation. Mit dieser Erweiterung wurde vor allem Anforderungen aus der Fertigungstechnik und Robotersteuerung Rechnung getragen. Das PA-Protokoll wurde im Rahmen der Entwicklungsstufe DP-V1 definiert. Die Anwendungsschicht (Schicht 7 des ISO/OSI-Referenzmodells) wird bei PROFIBUS-DP nicht verwendet. [2] Sicherungsschicht Beispielhafte Topologie zur Verdeutlichung der Kombination von Token-Passing mit einem Master-Slave-Verfahren Die Sicherungsschicht FDL (Fieldbus Data Link) arbeitet mit einem hybriden Zugriffsverfahren, das Token-Passing mit einem Master-Slave-Verfahren kombiniert. In einem PROFIBUS-Netzwerk sind die Steuerungen oder Prozessleitsysteme die Master und die Sensoren und Aktoren die Slaves. Bitübertragungsschicht Bei der Bitübertragungsschicht sind drei verschiedene Verfahren festgelegt: 1. Bei der elektrischen Übertragung nach EIA-485 werden verdrillte Zweidrahtleitungen mit einer Wellenimpedanz von 150 Ohm in einer Bustopologie eingesetzt. Es können Bitraten von 9600 bit/s bis 12 Mbit/s projektiert werden. Je nach verwendeter Bitrate ist die Kabellänge zwischen zwei Repeatern auf 100 bis 1200 Meter beschränkt. Dieses Übertragungsverfahren wird vor allem beim PROFIBUS DP und FMS eingesetzt. Für die elektrische Übertragung sind zwei verschiedene Kabeltypen spezifiziert (Typ A und Typ B). Das bekannteste Kabel ist das lilafarbene vom Typ A. 2. Bei der optischen Übertragung über Lichtwellenleiter kommen Stern-, Bus-, und Ring-Topologien zum Einsatz. Die Distanzen zwischen den Repeatern können bis zu 15 km betragen. Die Ring-Topologie kann auch redundant ausgeführt werden. 3. Bei der MBP (Manchester Bus Powered) Übertragungstechnik werden über dasselbe Kabel Daten und die Speisung der Feldgeräte übertragen. Die Leistung kann so begrenzt werden, dass auch ein Einsatz in explosionsgefährlicher Umgebung möglich ist. Dann spricht man von einem sogenannten eigensicheren Bereich. Dabei wird die Anwendung des FISCO Konzeptes empfohlen. Für diesen Bereich besitzen die Buskabel, die eine andere Spezifikation haben als der Kabeltyp A (EIA-485), einen blauen Mantel. Die Bustopologie kann bis zu 1900 Meter lang sein und lässt Abzweigungen zu den Feldgeräten mit maximal 120 Meter Länge zu. Die Bitrate beträgt hier fest 31,25 kbit/s. Diese Technologie ist speziell für den Einsatz in der Prozessautomation für PROFIBUS PA festgelegt worden. Für die Datenübertragung über Schleifkontakte, für mobile Teilnehmer oder für optische oder funktechnische Datenübertragung im freien Raum sind Produkte mehrerer Hersteller verfügbar, die aber in keiner Norm festgelegt sind (Wireless Profibus)."""@de . ### http://www.w3id.org/ecsel-dr-AT#CPF4_P-NET ecsel-dr-AT:CPF4_P-NET rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family . ### http://www.w3id.org/ecsel-dr-AT#CPF5_WorldFIP ecsel-dr-AT:CPF5_WorldFIP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family . ### http://www.w3id.org/ecsel-dr-AT#CPF6_INTERBUS ecsel-dr-AT:CPF6_INTERBUS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family . ### http://www.w3id.org/ecsel-dr-AT#CPF7_SwiftNet ecsel-dr-AT:CPF7_SwiftNet rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family . ### http://www.w3id.org/ecsel-dr-AT#CPF8_CC-Link ecsel-dr-AT:CPF8_CC-Link rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family . ### http://www.w3id.org/ecsel-dr-AT#CPF9_HART ecsel-dr-AT:CPF9_HART rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_CP_Family . ### http://www.w3id.org/ecsel-dr-AT#CSV ecsel-dr-AT:CSV rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L2_DataSyntax ; rdfs:label "Comma Separated Values" . ### http://www.w3id.org/ecsel-dr-AT#CharacterSet ecsel-dr-AT:CharacterSet rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L1_WebPlatform . ### http://www.w3id.org/ecsel-dr-AT#CoAP ecsel-dr-AT:CoAP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; 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:label "Constrained Application Protocol"@en . ### http://www.w3id.org/ecsel-dr-AT#CommunicationDevice ecsel-dr-AT:CommunicationDevice rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Device . ### http://www.w3id.org/ecsel-dr-AT#Computer ecsel-dr-AT:Computer rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Device . ### http://www.w3id.org/ecsel-dr-AT#ControlDevice ecsel-dr-AT:ControlDevice rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Device . ### http://www.w3id.org/ecsel-dr-AT#DDS ecsel-dr-AT:DDS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; rdfs:comment """DDS (Data-Distribution Service for Real-Time Systems) \"The first open international middleware standard directly addressing publish-subscribe communications for real-time and embedded systems.\" DDS portal: http://portals.omg.org/dds/"""@en , """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:label "Data-Distribution Service for Real-Time Systems"@en . ### http://www.w3id.org/ecsel-dr-AT#DHCP ecsel-dr-AT:DHCP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; 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:label "Dynamic Host Configuration Protocol"@de . ### http://www.w3id.org/ecsel-dr-AT#DNS ecsel-dr-AT:DNS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; 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:label "Domain Name Service"@de . ### http://www.w3id.org/ecsel-dr-AT#DNS-SD ecsel-dr-AT:DNS-SD rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; rdfs:comment """DNS-based service discovery DNS-SD allows clients to discover a named list of service instances, given a service type, and to resolve those services to hostnames using standard DNS queries. The specification is compatible with existing unicast DNS server and client software, but works equally well with Multicast DNS in a zero-configuration environment. Each service instance is described using a DNS SRV (RFC 2782) and DNS TXT (RFC 1035) record. A client discovers the list of available instances for a given service type by querying the DNS PTR (RFC 1035) record of that service type's name; the server returns zero or more names of the form \".\", each corresponding to a SRV/TXT record pair. The SRV record resolves to the domain name providing the instance, while the TXT can contain service-specific configuration parameter. A client can then resolve the A/AAAA record for the domain name and connect to the service. History In 1997 Stuart Cheshire proposed[16][self-published source?] adapting Apple's mature Name Binding Protocol to IP networks to address the lack of service discovery capability. Cheshire subsequently joined Apple and authored IETF draft proposals for Multicast DNS and DNS-based Service Discovery, supporting the transition from AppleTalk to IP networking. In 2002,[17] Apple announced an implementation of both protocols under the name Rendezvous (later renamed Bonjour), included in Mac OS X 10.2 and replacing the Service Location Protocol used in 10.1.[citation needed] In 2013, the proposals were ratified as RFC 6762[18] and RFC 6763.[19] DNS-SD with multicast Multicast DNS (mDNS) is a protocol that uses packets similar to unicast DNS except sent over a multicast link to resolve hostnames. Each host listens on the mDNS port, 5353, and resolves requests for the DNS record of its .local hostname (e.g. the A, AAAA, CNAME) to its IP address. When an mDNS client needs to resolve a local hostname to an IP address, it sends a DNS request for that name to a well-known multicast address; the computer with the corresponding A/AAAA record replies with its IP address. The mDNS multicast address is 224.0.0.251 for IPv4 and ff02::fb for IPv6 link-local addressing. DNS service discovery (DNS-SD) requests can also be sent over a multicast link,[20] and it can be combined with mDNS to yield zero-configuration DNS-SD. It still uses DNS PTR, SRV, TXT records to advertise instances of service types, domain names for those instances, and optional configuration parameters for connecting to those instances. But SRV records can now resolve to multicastable .local domain names, which mDNS can resolve to local IP addresses. Support DNS-SD is used by Apple products, most network printers, many Linux distributions including Debian and Ubuntu,[21] and a number of third party products for various operating systems. For example, many OS X network applications written by Apple, including Safari, iChat, and Messages, can use DNS-SD to locate nearby servers and peer-to-peer clients. On Windows, the operating system includes support for DNS-SD at least on Windows 10 for applications written using JavaScript[22] and other languages may be supported shortly. Individual applications may include their own support in older versions of the operating system, such that most instant messaging and VoIP clients on Windows support DNS-SD. Some Unix, BSD, and Linux distributions also include DNS-SD. For example, Ubuntu ships Avahi, an mDNS/DNS-SD implementation, in its base distribution. Service types are given on a first-serve basis. A service type registry was originally maintained by DNS-SD.org,[23] but has since been merged into IANA's registry for DNS SRV records.""" , """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.""" , "https://en.wikipedia.org/wiki/Zero-configuration_networking#DNS-SD" . ### http://www.w3id.org/ecsel-dr-AT#DPWS ecsel-dr-AT:DPWS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ServiceOrientedArchitecture ; rdfs:comment "DPWS is standardized by OASIS. DPWS was introduced by Microsoft as part of their .NET suite of tools and protocols."@de , """Das Devices Profile for Web Services (kurz DPWS) spezifiziert einen Standard mit dem es ermöglicht werden soll, Web Services auf eingebetteten Systemen, also auf Hardware mit (möglicherweise stark) eingeschränkten Ressourcen, einzusetzen. DPWS kombiniert hierfür eine Auswahl bestehender WS-*-Spezifikationen zusammen mit einigen Erweiterungen bzw. einigen neuen Spezifikationen zu einem Profil, auf dessen Basis netzwerkfähige eingebettete Systeme sicher miteinander kommunizieren können, dynamisch entfernte Geräte bzw. Dienste entdecken können, selbständig Dienste beschreiben können und Ereignisse auslösen bzw. Ereignisse anderer Dienste abonnieren können. Um diese Ziele zu erreichen werden im Devices Profile for Web Services die bestehenden Spezifikationen WS-Addressing, WS-Policy, WS-Security und WS-Metadata Exchange bzw. WS-Transfer miteinander kombiniert, und insbesondere für das dynamische Entdecken von Diensten und für die ereignisbasierte Kommunikation die neuen Spezifikationen WS-Discovery und WS-Eventing definiert. Ursprünglich wurde die Devices Profile for Web Services Spezifikation von der Firma Microsoft entwickelt, und eine Implementierung von DPWS ist ebenfalls integriert in Windows Vista. Open-Source-Implementierungen der DPWS-Spezifikation entstanden z. B. im Rahmen der Web Services for Devices Initiative"""@de , """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:label "Device Profile for Web Services" . ### http://www.w3id.org/ecsel-dr-AT#DSL ecsel-dr-AT:DSL rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_1_2_NetAccessTechnology . ### http://www.w3id.org/ecsel-dr-AT#DataLanguage_SemanticWebStackBased ecsel-dr-AT:DataLanguage_SemanticWebStackBased rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L3_KnowledgeRepresentation . ### http://www.w3id.org/ecsel-dr-AT#DataLanguage_XML-based ecsel-dr-AT:DataLanguage_XML-based rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L3_KnowledgeRepresentation . ### http://www.w3id.org/ecsel-dr-AT#DataTransmissionUnit ecsel-dr-AT:DataTransmissionUnit rdf:type owl: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-AT#Database-System ecsel-dr-AT:Database-System rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:IT-System . ### http://www.w3id.org/ecsel-dr-AT#Device ecsel-dr-AT:Device rdf:type owl:Class ; owl:equivalentClass . ### http://www.w3id.org/ecsel-dr-AT#DeviceControlApp ecsel-dr-AT:DeviceControlApp rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:IT-System ; 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.""" . ### http://www.w3id.org/ecsel-dr-AT#Digital-Factory-System ecsel-dr-AT:Digital-Factory-System rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:IT-System ; 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 . ### http://www.w3id.org/ecsel-dr-AT#DigitalFactoryTwin ecsel-dr-AT:DigitalFactoryTwin rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:PLM2_Module ; 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 . ### http://www.w3id.org/ecsel-dr-AT#DocumentTypeDescription ecsel-dr-AT:DocumentTypeDescription rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:DataLanguage_XML-based . ### http://www.w3id.org/ecsel-dr-AT#EDIFACT-DataFormat ecsel-dr-AT:EDIFACT-DataFormat rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L2_DataSyntax ; 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 . ### http://www.w3id.org/ecsel-dr-AT#EDIFACT-Specification ecsel-dr-AT:EDIFACT-Specification rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:EDI_Specification . ### http://www.w3id.org/ecsel-dr-AT#EDIFACT_DELFOR ecsel-dr-AT:EDIFACT_DELFOR rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:EDIFACT-Specification ; 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:label "Delivery Forecast"@en . ### http://www.w3id.org/ecsel-dr-AT#EDIFACT_DELJIT ecsel-dr-AT:EDIFACT_DELJIT rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:EDIFACT-Specification ; rdfs:label "Delivery Forecast for Just in Time and Just in Sequence parts"@en . ### http://www.w3id.org/ecsel-dr-AT#EDIFACT_DESADV ecsel-dr-AT:EDIFACT_DESADV rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:EDIFACT-Specification ; rdfs:comment "EDIFACT message for despatch advise (delivery announcement)"@en ; rdfs:label "Despatch Advice"@de . ### http://www.w3id.org/ecsel-dr-AT#EDIFACT_ORDERS ecsel-dr-AT:EDIFACT_ORDERS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:EDIFACT-Specification ; rdfs:comment "EDIFACT message for purchase order(s)."@en ; rdfs:label "Orders"@en . ### http://www.w3id.org/ecsel-dr-AT#EDIFACT_ORDRSP ecsel-dr-AT:EDIFACT_ORDRSP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:EDIFACT-Specification ; rdfs:comment "EDIFACT message for Order Response."@en ; rdfs:label "Order response"@en . ### http://www.w3id.org/ecsel-dr-AT#EDI_Specification ecsel-dr-AT:EDI_Specification rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L5_DataSemantics . ### http://www.w3id.org/ecsel-dr-AT#ERP-System ecsel-dr-AT:ERP-System rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:IT-System ; rdfs:label "Enterprise Resource Planning System" . ### http://www.w3id.org/ecsel-dr-AT#ElectricDrive ecsel-dr-AT:ElectricDrive rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ActuatorDevice . ### http://www.w3id.org/ecsel-dr-AT#Enocean ecsel-dr-AT:Enocean rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_3_4_NetworkTechnology . ### http://www.w3id.org/ecsel-dr-AT#Ethernet_802_3 ecsel-dr-AT:Ethernet_802_3 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_1_2_NetAccessTechnology ; rdfs:comment """Ethernet ist eine Technik, die Software (Protokolle usw.) und Hardware (Kabel, Verteiler, Netzwerkkarten usw.) für kabelgebundene Datennetze spezifiziert, welche ursprünglich für lokale Datennetze (LANs) gedacht war und daher auch als LAN-Technik bezeichnet wird. Sie ermöglicht den Datenaustausch in Form von Datenframes zwischen den in einem lokalen Netz (LAN) angeschlossenen Geräten (Computer, Drucker und dergleichen). Derzeit sind Übertragungsraten von 1, 10, 100 Megabit/s (Fast Ethernet), 1000 Megabit/s (Gigabit-Ethernet), 2,5, 5, 10, 40, 50, 100, 200 und 400 Gigabit/s spezifiziert. In seiner ursprünglichen Form erstreckt sich das LAN dabei nur über ein Gebäude; Ethernet-Varianten über Glasfaser haben eine Reichweite von bis zu 70 km. Die Ethernet-Protokolle umfassen Festlegungen für Kabeltypen und Stecker sowie für Übertragungsformen (Signale auf der Bitübertragungsschicht, Paketformate). Im OSI-Modell ist mit Ethernet sowohl die physische Schicht (OSI Layer 1) als auch die Data-Link-Schicht (OSI Layer 2) festgelegt. Ethernet entspricht weitestgehend der IEEE-Norm 802.3. Es wurde ab den 1990ern zur meistverwendeten LAN-Technik und hat andere LAN-Standards wie Token Ring verdrängt oder, wie im Falle von ARCNET in Industrie- und Fertigungsnetzen oder FDDI in hoch verfügbaren Netzwerken, zu Nischenprodukten für Spezialgebiete gemacht. Ethernet kann die Basis für Netzwerkprotokolle, z. B. AppleTalk, DECnet, IPX/SPX oder TCP/IP, bilden. Für Anwendungen, in denen hohe Anforderungen an die Zuverlässigkeit der Kommunikation gestellt werden, kommt Echtzeit-Ethernet zum Einsatz."""@de , """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 . ### http://www.w3id.org/ecsel-dr-AT#FDDI ecsel-dr-AT:FDDI rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_1_2_NetAccessTechnology ; 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" , "The Fiber Distributed Data Interface (FDDI, colloquially called Fiber Optic Metro Ring) is a late-1980s standardized 100 Mbps network structure for local area networks (ANSI Standard X3T9.5). As a medium fiber optic cable in a double, counter-rotating ring with token access mechanism are used. In 1994, the FDDI standard was extended and the transmission also standardized over shielded (STP) and unshielded (UTP type 5) twisted copper cables (CDDI, C for Copper). FDDI was gradually supplanted by low-cost Ethernet technology. Market-leading network component manufacturers are no longer offering FDDI support for their products, so the technology is outdated"@en ; rdfs:label "Fiber Distributed Data Interface"@de . ### http://www.w3id.org/ecsel-dr-AT#FTP ecsel-dr-AT:FTP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; rdfs:label "File Transfer Protocol"@en . ### http://www.w3id.org/ecsel-dr-AT#FactoryLayoutPlanning ecsel-dr-AT:FactoryLayoutPlanning rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:PLM1_Module . ### http://www.w3id.org/ecsel-dr-AT#FactorySimulationSystem ecsel-dr-AT:FactorySimulationSystem rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Simulation-System . ### http://www.w3id.org/ecsel-dr-AT#Fieldbus_CP_Family ecsel-dr-AT:Fieldbus_CP_Family rdf:type owl:Class ; rdfs:comment """Beispiel für Feldbus der ersten Generation ist Profibus, Beispiel für Feldbus der zweiten Generation ist ProfiNet."""@de , "Ein Feldbus definiert einen kompletten Protokoll-Stack über die 7 SChichten des OSI-Schichtenmodells. Ggf. werden nicht alle Schichten belegt." , """Ein Feldbus ist ein Bussystem, das in einer Anlage Feldgeräte wie Messfühler (Sensoren) und Stellglieder (Aktoren) zwecks Kommunikation mit einem Automatisierungsgerät verbindet. Wenn mehrere Kommunikationsteilnehmer ihre Nachrichten über dieselbe Leitung senden, dann muss festgelegt sein, wer (Kennung) was (Messwert, Befehl) wann (Initiative) sagt. Hierfür gibt es normierte Protokolle. Die erste Generation der Feldbustechnik wurde in den 1980er Jahren entwickelt, um die bis dahin übliche Parallelverdrahtung binärer Signale sowie die analoge Signalübertragung durch digitale Übertragungstechnik zu ersetzen. Heute sind viele unterschiedliche Feldbussysteme mit unterschiedlichen Eigenschaften am Markt etabliert. Seit 1999 werden Feldbusse in der Norm IEC 61158 (Digital data communication for measurement and control - Fieldbus for use in industrial control systems) sowie durch die Norm IEC 61784 weltweit standardisiert. Die zweite Generation der Feldbustechnik basiert auf Echtzeit-Ethernet (Industrial Ethernet)."""@de ; rdfs:label "Fieldbus Communication Profile Family" . ### http://www.w3id.org/ecsel-dr-AT#Fieldbus_Car_Airplane ecsel-dr-AT:Fieldbus_Car_Airplane rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#Frame ecsel-dr-AT:Frame rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:DataTransmissionUnit ; rdfs:comment """Data transmission unit of ISO/OSI layer 2 (Data Link Layer). \"Envelope\", contain MAC addresses (Media Access Control)."""@en . ### http://www.w3id.org/ecsel-dr-AT#Gateway ecsel-dr-AT:Gateway rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:CommunicationDevice ; 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 , """Die Arbeitsweise eines Gateways ist je nach Schicht im OSI-Modell sehr unterschiedlich: Layer 1 Hier arbeiten Medienkonverter, welche z. B. elektrische in optische Signale umwandeln. Auch Powerline Adapter zählen zu den Gateways auf Layer 1. Layer 2 Auf dem Layer 2 findet die Übersetzung zwischen unterschiedlichen Netzwerktypen statt, z. B. zwischen Ethernet und Token Ring. Ab diesem Layer ist eine effektive Veränderung der transportierten Daten möglich. So werden die Header von Ethernet durch ein Token von Token Ring ersetzt und umgekehrt. Layer 3 In Netzwerken, welche eine Unterteilung in Subnetze wie bei IP-Adressen vornehmen, arbeiten hier die Router. Ein Router leitet Pakete zwischen den angeschlossenen Subnetzen weiter. Das eigentliche Routing verändert dabei keinerlei Daten auf Layer 3. Eine Ausnahme davon stellt Network Address Translation dar, welche Daten auf Layer 3 ändert. Layer 4 Im TCP/IP-Stack ist Port Address Translation ein häufiges Beispiel für ein Gateway. Dabei werden Portnummern von TCP oder UDP in den transportierten Paketen ausgetauscht. Ein anderes Beispiel für Layer 4 Gateways ist die Terminierung von TLS-Verbindungen. Das Gateway entschlüsselt dabei die ankommenden Pakete und leitet diese anschließend an ein anderes System weiter. Für die Weiterleitung kann dabei ebenfalls Verschlüsselung mittels TLS zum Einsatz kommen. Layer 5-7 Gateways auf diesen Layern nehmen eine Umsetzung zwischen unterschiedlichen Applikationsprotokollen vor, z. B. von Fax zu E-Mail oder von analoger Telefonie zu VoIP. Ein Gateway auf diesen Layern, das die Inhalte der Pakete untersucht und verändert, ohne eine Übersetzung in ein anderes Protokoll vorzunehmen, wird als Application Layer Gateway oder häufiger als Proxy bezeichnet. In der Praxis finden sich die unterschiedlichen Gateways oftmals in denselben Systemen. Bestes Beispiel dafür sind Firewalls. Selbst einfachste Firewalls decken mit ihren Funktionen die Layer 1 - 4 ab, bei teureren Geräten finden sich Funktionen für alle sieben Layer."""@de , """The way a gateway works differs greatly depending on the layer in the OSI model: Layer 1: Here are media converters in place, which e.g. convert electrical into optical signals. Powerline adapters are also layer 1 gateways. Layer 2: At Layer 2, the translation between different network types takes place, e.g. between Ethernet and Token Ring. From this layer an effective change of the transported data is possible. For example, the headers of Ethernet can be replaced by tokens of Token Ring and vice versa. Layer 3: In networks, which are subdivided into subnets like for IP addresses, routers are in place. A router forwards packets between the connected subnets. The actual routing does not change any data on Layer 3. An exception to this is Network Address Translation. Layer 4: In the TCP / IP stack, Port Address Translation is a common example of a gateway. This port numbers of TCP or UDP are exchanged in the transported packets. Another example of Layer 4 gateways is the termination of TLS connections. The gateway decrypts the incoming packets and forwards them to another system. For forwarding, encryption using TLS can also be used. Layer 5-7: Gateways on these layers implement a conversion between different application protocols, eg. from Fax to e-mail or from analogue telephone to VoIP. A gateway on these layers, which examines and modifies the contents of the packets without translating them into another protocol, is referred to as an application layer gateway or more commonly a proxy. In practice, the different gateways are often found in the same systems. The best example of this are firewalls. Even the simplest firewalls cover Layer 1 - 4 with their functions, with more expensive devices can be found functions for all seven layers. Änderung vorschlagen"""@en . ### http://www.w3id.org/ecsel-dr-AT#HTML ecsel-dr-AT:HTML rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L2_DataSyntax . ### http://www.w3id.org/ecsel-dr-AT#HTTP ecsel-dr-AT:HTTP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; rdfs:comment """HTTP is an application layer protocol designed within the framework of the Internet protocol suite. Its definition presumes an underlying and reliable transport layer protocol. – Transmission Control Protocol (TCP) is commonly used here. – However, HTTP can be adapted to use unreliable protocols such as the User Datagram Protocol (UDP), for example in HTTPU, and Simple Service Discovery Protocol (SSDP). • An HTTP session is a sequence of network request-response transactions. – An HTTP client initiates a request by establishing a Transmission Control Protocol (TCP) connection to a particular port on a server (typically port 80, occasionally port 8080. – An HTTP server listening on that port waits for a client's request message. Upon receiving the request, the server sends back a status line, such as \"HTTP/1.1 200 OK\", and a message of its own. The body of this message is typically the requested resource, although an error message or other information may also be returned."""@en , """HTTP methods are GET, POST, HEAD, OPTIONS, PUT, DELETE, TRACE, CONNCET. GET and HEAD are mandatory to be implemented by a HTTP server. HTTP is the basis for the architectural style REST."""@en , """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:label "Hypertext Transfer Protocol"@en . ### http://www.w3id.org/ecsel-dr-AT#HTTPS ecsel-dr-AT:HTTPS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; 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:label "Hypertext Transfer Protocol Secure"@en . ### http://www.w3id.org/ecsel-dr-AT#Hub ecsel-dr-AT:Hub rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:CommunicationDevice . ### http://www.w3id.org/ecsel-dr-AT#IEC ecsel-dr-AT:IEC rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:StandardisationOrganization . ### http://www.w3id.org/ecsel-dr-AT#IEC-Standard ecsel-dr-AT:IEC-Standard rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Standard ; rdfs:comment "standard maintained and published by IEC."@en ; rdfs:label "IEC standard"@en . ### http://www.w3id.org/ecsel-dr-AT#IEEE ecsel-dr-AT:IEEE rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:StandardisationOrganization . ### http://www.w3id.org/ecsel-dr-AT#IEEE-Standard ecsel-dr-AT:IEEE-Standard rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Standard . ### http://www.w3id.org/ecsel-dr-AT#IETF ecsel-dr-AT:IETF rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:StandardisationOrganization . ### http://www.w3id.org/ecsel-dr-AT#IETF-Standard ecsel-dr-AT:IETF-Standard rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Standard . ### http://www.w3id.org/ecsel-dr-AT#IMAP ecsel-dr-AT:IMAP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; 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:label "Internet Message Access Protocol"@en . ### http://www.w3id.org/ecsel-dr-AT#ISA ecsel-dr-AT:ISA rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:StandardisationOrganization ; rdfs:label "International Society of Automation (ISA)"@en . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_AutomationHierarchy ecsel-dr-AT:ISA-95_AutomationHierarchy rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:NetworkLayerModel ; rdfs:comment """ISA-95 ANSI/ISA-95 ist eine Norm für die Integration von Unternehmens- und Betriebsleitebene, die von der ISA herausgegeben wurde und wird auch als S95 oder SP95 bezeichnet. ISA-95 basiert auf ISA-88, erweitert diese von der Prozessleittechnik für den Batchbetrieb auf die Betriebsleittechnik, die auch für diskrete und kontinuierliche Fertigung anwendbar ist. Die folgenden Teile der Normenreihe wurden freigegeben: Teil 1 Models and Terminology[1] Teil 2 Object Model Attributes[2] Teil 3 Models of Manufacturing Operations Management[3] Teil 4 Object models and attributes of manufacturing operations management[4] Teil 5 Business-to-Manufacturing Transactions[5]"""@en , """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 . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_1_1 ecsel-dr-AT:ISA-95_Comm_1_1 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ISA-95_Communication ; rdfs:comment "Communication between devices on ISA-95 level 1 (intra-level 1-communication)"@de . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_1_2 ecsel-dr-AT:ISA-95_Comm_1_2 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ISA-95_Communication ; rdfs:comment "Communication between devices on ISA-95 level 1 and ISA-95 level 2 (inter-level-communication 1 - 2)"@de . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_1_3 ecsel-dr-AT:ISA-95_Comm_1_3 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ISA-95_CrossLayerCommunication . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_1_4 ecsel-dr-AT:ISA-95_Comm_1_4 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ISA-95_CrossLayerCommunication . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_2_2 ecsel-dr-AT:ISA-95_Comm_2_2 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ISA-95_Communication ; rdfs:comment "Communication between devices on ISA-95 level 2 (intra-level 2-communication)"@de . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_2_3 ecsel-dr-AT:ISA-95_Comm_2_3 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ISA-95_Communication ; rdfs:comment "Communication between devices on ISA-95 level 2 and ISA-95 level 3 (inter-level-communication 2 - 3)"@de . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_2_4 ecsel-dr-AT:ISA-95_Comm_2_4 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ISA-95_CrossLayerCommunication . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_3_3 ecsel-dr-AT:ISA-95_Comm_3_3 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ISA-95_Communication ; rdfs:comment "Communication between devices on ISA-95 level 3 (intra-level 3-communication)"@de . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_3_4 ecsel-dr-AT:ISA-95_Comm_3_4 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ISA-95_Communication ; rdfs:comment "Communication between devices on ISA-95 level 3 and ISA-95 level 4 (inter-level-communication 3 - 4)"@de . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_Comm_4_4 ecsel-dr-AT:ISA-95_Comm_4_4 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ISA-95_Communication ; rdfs:comment "Communication between devices on ISA-95 level 4 (intra-level 4-communication)"@de . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_Communication ecsel-dr-AT:ISA-95_Communication rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_CrossLayerCommunication ecsel-dr-AT:ISA-95_CrossLayerCommunication rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer ecsel-dr-AT:ISA-95_Layer rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer0_PhysicalProcess ecsel-dr-AT:ISA-95_Layer0_PhysicalProcess rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ISA-95_Layer . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer1_SensorsActuators ecsel-dr-AT:ISA-95_Layer1_SensorsActuators rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ISA-95_Layer . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer2_DistributedControl_SCADA ecsel-dr-AT:ISA-95_Layer2_DistributedControl_SCADA rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ISA-95_Layer . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer3_MES_LES ecsel-dr-AT:ISA-95_Layer3_MES_LES rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ISA-95_Layer . ### http://www.w3id.org/ecsel-dr-AT#ISA-95_Layer4_ERP ecsel-dr-AT:ISA-95_Layer4_ERP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ISA-95_Layer . ### http://www.w3id.org/ecsel-dr-AT#ISA-Standard ecsel-dr-AT:ISA-Standard rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Standard . ### http://www.w3id.org/ecsel-dr-AT#ISO ecsel-dr-AT:ISO rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:StandardisationOrganization . ### http://www.w3id.org/ecsel-dr-AT#ISO-Standard ecsel-dr-AT:ISO-Standard rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Standard . ### http://www.w3id.org/ecsel-dr-AT#IT-System ecsel-dr-AT:IT-System rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#IT-Vendor ecsel-dr-AT:IT-Vendor rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#IndustrialEthernet ecsel-dr-AT:IndustrialEthernet rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_1_2_NetAccessTechnology ; 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 . ### http://www.w3id.org/ecsel-dr-AT#IndustrialWLAN ecsel-dr-AT:IndustrialWLAN rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_1_2_NetAccessTechnology ; 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 . ### http://www.w3id.org/ecsel-dr-AT#IndustryPC ecsel-dr-AT:IndustryPC rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ControlDevice . ### http://www.w3id.org/ecsel-dr-AT#JSON ecsel-dr-AT:JSON rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L2_DataSyntax . ### http://www.w3id.org/ecsel-dr-AT#KPI-ML ecsel-dr-AT:KPI-ML rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:MarkupLanguage ; 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 . ### http://www.w3id.org/ecsel-dr-AT#LES ecsel-dr-AT:LES rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:IT-System ; rdfs:label "Logistics Execution System" . ### http://www.w3id.org/ecsel-dr-AT#LIMS ecsel-dr-AT:LIMS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:IT-System ; 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:label "Laboratory Information Management System"@de . ### http://www.w3id.org/ecsel-dr-AT#LoRaWAN ecsel-dr-AT:LoRaWAN rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_1_2_NetAccessTechnology ; rdfs:comment """Aufbau: Die Netz-Architektur ist sternförmig. Endgeräte kommunizieren mit Gateways, welche die Datenpakete an einen Netzwerkserver senden. Der Netzwerkserver verfügt über Schnittstellen, um an IoT Plattformen und Applikationen angebunden zu werden. LoRaWAN nutzt regional unterschiedliche Frequenzbereiche im ISM-Band. Unter anderem sind dies in Europa die Frequenzen 433 MHz (ISM-Band Region 1) und 868 MHz (SRD-Band Europa). In den USA ist hingegen das Band mit 915 MHz (ISM-Band Region 2) für die Datenübermittlung freigegeben. Die Reichweiten erstrecken sich von 2 km (Stadtgebiet) über 15 km (Vororte) bis zu 40 km (ländliche Gebiete). Ein weiterer großer Vorteil ist die Durchdringung von Gebäuden, da hier auch zu einem gewissen Grad unterirdische Räumlichkeiten versorgt werden können. Der Stromverbrauch von Endgeräten beträgt rund 10 mA und 100 nA im Ruhemodus. Das ermöglicht je nach Anwendungsfall eine Batterielebensdauer von 2 bis 15 Jahren. Die Kommunikation zwischen den Endgeräten und den Gateways erfolgt auf verschiedenen Frequenzkanälen mit unterschiedlichen Datenraten. Diese liegen zwischen 0,3 kbit/s und 50 kbit/s. Um eine hohe Effizienz bei Datentransfer und Energieverbrauch zu erreichen, nutzt LoRaWAN Frequenzspreizung. Interferenzen können so weitestgehend vermieden werden. Die Datentransferraten zu den Endgeräten passt der Netzwerkserver der jeweiligen Situation an (ADR = Adaptive Data Rate). Die Kommunikation im LoRaWAN ist zweifach mit 128 bit AES verschlüsselt, zum einen bis zum Netzwerkserver und zum anderen bis zum Anwendungsserver."""@de , """LoRa ist die Bezeichnung für das Funksystem, das bisher im The Things Network eingesetzt wird. LoRa wurde dafür entwickelt, Daten mittels Funk über weite Strecken und durch Hindernisse wie Wände und Häuser hindruch (bzw. daran vorbei) übertragen zu können. Dafür hat es z.B. im Vergleich mit dem altbekannten WLAN etwas andere Eigenschaften: Eine größere Reichweite, meist im Bereich zwischen 2 und 15 km; der Weltrekord liegt aktuell bei 702 km, wofür natürlich sehr gute Bedingungen herrschten und eine direkt Sichtverbindung zwischen Sender und Empfänger bestand. Dafür hat man aber eine wesentlich geringere Bandbreite zur Verfügung. Sprich es könne viel weniger Daten übertragen werden. Surfen in facebook oder Schreiben per WhatsApp geht nicht, aber z.B. alle fünf Minuten einen Temperaturwert wie 25,3 °C senden geht ganz gut. Vorteilhaft ist wiederum, dass für eine Übertragung sehr wenig Energie benötigt wird und ein gut gebauter Sensor mit einer Batterieladung auch mehrere Jahren laufen kann. LoRaWAN ist ein sogenanntes Netzwerkprotokoll, mit dem festgelegt wird, wie Datenpakete mit der LoRa-Funktechnik überragen weden. (Quelle: https://lora.ulm-digital.com/introduction)""" , "Long Range Wide Area Network (LoRaWAN) is a low-power wireless network protocol. The LoRaWAN specification is set by the LoRa Alliance, is freely available and utilizes Semtech Corporation's proprietary Chirp Spread Spectrum Modulation technique \"LoRa\". It is asymmetrically geared to the energy efficiency of IoT devices and achieves high ranges (> 10 km) for uplink communication, ie the transmission from the IoT device to the network. The data transfer rate ranges between 292 bps and 50 kilobits per second. Different operating shifts up to a quasi-continuous downlink communication are possible, the latter at the expense of energy efficiency."@en , "Long Range Wide Area Network (LoRaWAN) ist ein Low-Power-Wireless-Netzwerkprotokoll. Die LoRaWAN-Spezifikation wird von der LoRa Alliance festgelegt, ist frei verfügbar und nutzt die proprietäre Chirp Spread Spectrum Modulationstechnik „LoRa“ der Semtech Corporation. Sie ist asymmetrisch auf Energieeffizienz der IoT-Geräte ausgerichtet und erreicht hierbei hohe Reichweiten (>10 km) für die Uplink-Kommunikation, also das Senden vom IoT-Gerät an das Netz. Die Datenübertragungsrate rangiert zwischen 292 Bit/s und 50 Kilobit/s. Verschiedene Betriebsabstufungen bis hin zu einer quasi-kontinuierlichen Downlink-Kommunikation sind möglich, wobei letzteres auf Kosten der Energieeffizienz geht."@de , """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.""" . ### http://www.w3id.org/ecsel-dr-AT#MES ecsel-dr-AT:MES rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:IT-System ; rdfs:label "Maufacturing Execution System" . ### http://www.w3id.org/ecsel-dr-AT#MESA ecsel-dr-AT:MESA rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:StandardisationOrganization ; rdfs:comment "especially MESA XML Committee"@en . ### http://www.w3id.org/ecsel-dr-AT#MESA-Standard ecsel-dr-AT:MESA-Standard rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Standard . ### http://www.w3id.org/ecsel-dr-AT#MIS ecsel-dr-AT:MIS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:IT-System ; rdfs:label "Management Information System"@de . ### http://www.w3id.org/ecsel-dr-AT#MQTT ecsel-dr-AT:MQTT rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; rdfs:comment """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 , """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 . ### http://www.w3id.org/ecsel-dr-AT#MQTT-SN ecsel-dr-AT:MQTT-SN rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:MQTT_nonTCPIP_based ; 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:label "MQTT for Sensor Networks"@en , "MQTT für Sensorgeräte"@de . ### http://www.w3id.org/ecsel-dr-AT#MQTT_TCPIP ecsel-dr-AT:MQTT_TCPIP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:MQTT_TCPIP_based ; rdfs:comment """Specification The MQTT specification distinguishes between TCP / IP-based and non-TCP / IP networks. Here the TCP / IP-based variant is described. Main specification The protocol allows for a very simple way of observing behavior. It is particularly suitable for connections that allow only a small amount of administrative data. The OASIS standardization process is based on version 3.1 of the MQTT specification. 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. MQTT is typically used over TCP and has a 2-byte header. The first byte contains the message type (4 bits), the quality of service (2 bits) and a retain flag. There are the following message types:     CONNECT     CONNACK     PUBLISH     PUBACK     PUBREC     Pubrel     PUBCOMP     SUBSCRIBE     SUBACK     UNSUBSCRIBE     UNSUBACK     PINGREQ     PINGRESP     DISCONNECT The second byte contains the length of the remainder of the MQTT packet. This is followed by a variable part that contains the MQTT topic, ie the topic. Finally comes the payload, ie the data content that is published under the topic."""@en , """Spezifikation Die MQTT-Spezifikation unterscheidet TCP/IP-basierte und Nicht-TCP/IP-Netzwerke. Hier wird die TCP/IP-basierte Variante beschrieben. Haupt-Spezifikation Das Protokoll ermöglicht auf eine sehr einfache Art ein Beobachter-Verhaltensmuster. Es ist besonders geeignet für Verbindungen, die nur einen geringen Verwaltungsdatenanteil erlauben. Der OASIS-Standardisierungsprozess basiert auf Version 3.1 der MQTT-Spezifikation. 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. MQTT wird üblicherweise über TCP benutzt und hat einen 2-Byte-Header. Das erste Byte enthält den Nachrichtentyp (4 Bit), den Quality of Service (2 Bit) und ein Retain-Flag. Es gibt folgende Nachrichten-Typen: CONNECT CONNACK PUBLISH PUBACK PUBREC PUBREL PUBCOMP SUBSCRIBE SUBACK UNSUBSCRIBE UNSUBACK PINGREQ PINGRESP DISCONNECT Das zweite Byte enthält die Länge des restlichen MQTT-Pakets. Daran schließt sich ein variabler Teil an, der das MQTT-Topic, also das Thema enthält. Abschließend kommt der Payload, also der Dateninhalt, der unter dem Thema veröffentlicht wird."""@de , "https://de.wikipedia.org/wiki/MQTT" ; rdfs:label "Message Queue Telemetry Transport over TCP/IP infrastructure"@en . ### http://www.w3id.org/ecsel-dr-AT#MQTT_TCPIP_based ecsel-dr-AT:MQTT_TCPIP_based rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:MQTT . ### http://www.w3id.org/ecsel-dr-AT#MQTT_nonTCPIP_based ecsel-dr-AT:MQTT_nonTCPIP_based rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:MQTT . ### http://www.w3id.org/ecsel-dr-AT#MachineSimulationSystem ecsel-dr-AT:MachineSimulationSystem rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Simulation-System . ### http://www.w3id.org/ecsel-dr-AT#ManufacturingSimulationSystem ecsel-dr-AT:ManufacturingSimulationSystem rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Simulation-System . ### http://www.w3id.org/ecsel-dr-AT#MarkupLanguage ecsel-dr-AT:MarkupLanguage rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L5_DataSemantics . ### http://www.w3id.org/ecsel-dr-AT#MaterialFlowPlanning ecsel-dr-AT:MaterialFlowPlanning rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:PLM1_Module . ### http://www.w3id.org/ecsel-dr-AT#MaterialFlowSimulation ecsel-dr-AT:MaterialFlowSimulation rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:PLM1_Module . ### http://www.w3id.org/ecsel-dr-AT#Message ecsel-dr-AT:Message rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:DataTransmissionUnit ; 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 . ### http://www.w3id.org/ecsel-dr-AT#MessageBroker-System ecsel-dr-AT:MessageBroker-System rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:IT-System . ### http://www.w3id.org/ecsel-dr-AT#MicroController ecsel-dr-AT:MicroController rdf:type owl:Class ; owl:equivalentClass ecsel-dr-OOSMP:Microcontroller , ; rdfs:subClassOf ecsel-dr-AT:ControlDevice . ### http://www.w3id.org/ecsel-dr-AT#N3_TURTLE ecsel-dr-AT:N3_TURTLE rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L2_DataSyntax . ### http://www.w3id.org/ecsel-dr-AT#NetworkLayerModel ecsel-dr-AT:NetworkLayerModel rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#OASIS ecsel-dr-AT:OASIS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:StandardisationOrganization ; rdfs:label "Organization for the Advancement of Structured Information Standards"@en . ### http://www.w3id.org/ecsel-dr-AT#OASIS-Standard ecsel-dr-AT:OASIS-Standard rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Standard . ### http://www.w3id.org/ecsel-dr-AT#OCF ecsel-dr-AT:OCF rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:StandardisationOrganization ; rdfs:label "Open Connectivity Foundation"@en . ### http://www.w3id.org/ecsel-dr-AT#OCF-Standard ecsel-dr-AT:OCF-Standard rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Standard . ### http://www.w3id.org/ecsel-dr-AT#OMG ecsel-dr-AT:OMG rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:StandardisationOrganization ; rdfs:label "Object Management Group"@en . ### http://www.w3id.org/ecsel-dr-AT#OMG-Standard ecsel-dr-AT:OMG-Standard rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Standard . ### http://www.w3id.org/ecsel-dr-AT#OPC ecsel-dr-AT:OPC rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; rdfs:comment "OLE for Process Control (OPC) war der ursprüngliche Name für standardisierte Software-Schnittstellen, die den Datenaustausch zwischen Anwendungen unterschiedlichster Hersteller in der Automatisierungstechnik ermöglichen sollten. Durch die fortschreitende Weiterentwicklung dieser Schnittstellen und die damit einhergehende Abnahme der Relevanz des OLE-Objektsystems wurde der Standard im November 2011 in Open Platform Communications umbenannt. Deshalb wird heute zumeist die Bezeichnung OPC genutzt. Die aktuelle Generation von OPC wird OPC Unified Architecture (OPC UA) genannt."@de , """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 , """OPC ist der Versuch, industriellen Bussystemen und Protokollen eine universelle Möglichkeit zur Verständigung zu geben. Geschaffen wurde der Standard von der OPC Task Force, einem Zusammenschluss verschiedener großer Firmen der Automatisierungsindustrie wie Fisher-Rosemount, Intellution und Siemens, nachdem man erkannt hatte, welchen Aufwand die Anpassung der zahlreichen Herstellerstandards auf individuelle Steuerungs- und Überwachungs-Infrastrukturen verursacht hatte. Kurz nach der Veröffentlichung der OPC Specification Version 1.0 im August 1996 wurde die OPC Foundation gegründet, die bis heute zuständig ist für die Pflege und Verbreitung des Standards. Ihr gehören mittlerweile 448 (Stand: 8. Januar 2008) Unternehmen an. Heute ist OPC der Standard zur herstellerunabhängigen Kommunikation in der Automatisierungstechnik. Die Zertifizierungssoftware OPC Compliance Test, die den OPC-Mitgliedern kostenlos zur Verfügung gestellt wird, stellt die Kompatibilität sicher. Die Hersteller von OPC-Servern können damit ihre Server schon während der Entwicklung testen. Diese Software testet die vollständige OPC-Funktionalität, simuliert Fehlverhalten eines Clients und überprüft alle Fehlercodes. Zusätzlich werden noch logische Tests, Stress- und Performance-Tests durchgeführt. Diese Testreihe deckt mehr Tests ab, als man mit einem normalen Client erreicht. Nach bestandenem Test können die Hersteller die Ergebnisse an die OPC Foundation senden und erhalten das Zertifikat Compliance Tested. Es ist zu empfehlen, nur Server zu kaufen, die dieses Zertifikat besitzen. Einsatzgebiet OPC wird dort eingesetzt, wo Sensoren, Regler und Steuerungen verschiedener Hersteller ein gemeinsames Netzwerk bilden. Ohne OPC benötigten zwei Geräte zum Datenaustausch genaue Kenntnis über die Kommunikationsmöglichkeiten des Gegenübers. Erweiterungen und Austausch gestalten sich entsprechend schwierig. Mit OPC genügt es, für jedes Gerät genau einmal einen OPC-konformen Treiber zu schreiben. Idealerweise wird dieser bereits vom Hersteller zur Verfügung gestellt. Ein OPC-Treiber lässt sich ohne großen Anpassungsaufwand in beliebig große Steuer- und Überwachungssysteme integrieren. OPC unterteilt sich in verschiedene Unterstandards, die für den jeweiligen Anwendungsfall unabhängig voneinander implementiert werden können. OPC lässt sich damit verwenden für Echtzeitdaten (Überwachung), Datenarchivierung, Alarm-Meldungen und neuerdings auch direkt zur Steuerung (Befehlsübermittlung)."""@de , """Outdated technology! OPC was further developed to OPC UA. Here, the dependency from Microsofts DCOM technology was removed. At the same time, Microsoft itself developed .NET which offers support for OPC UA WebService Protocol."""@en , """https://de.wikipedia.org/wiki/Open_Platform_Communications: nice architecture picture with OPC Client, OPC Server and a propriarety fieldbus with DDC / PLC at the same server."""@en ; rdfs:label "OLE for Process Control"@en , "Open Platform Communications"@en . ### http://www.w3id.org/ecsel-dr-AT#OPC_UA ecsel-dr-AT:OPC_UA rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ServiceOrientedArchitecture ; rdfs:comment """Die OPC-UA-Architektur ist eine Service-orientierte Architektur (SOA), deren Struktur aus mehreren Schichten besteht. OPC-UA-Architektur Alle von OPC definierten grundlegenden Dienste (Base-Services) sind abstrakte Methodenbeschreibungen, die protokollunabhängig sind, und stellen die Grundlage für die gesamte OPC-UA-Funktionalität bereit. Durch die Transportschicht werden diese Methoden mittels eines Protokolls ausgeführt, das die Daten serialisiert/deserialisiert und über das Netz sendet. Momentan sind zwei Protokolle dafür vorgesehen: ein hoch optimiertes und performantes TCP-Protokoll mit Binärkodierung und ein auf Webservices basierendes Protokoll. Weitere Protokolle sind möglich und können bei Bedarf ergänzt werden. Das OPC-Informationsmodell ist nicht mehr nur eine Hierarchie aus Ordnern, Items und Properties. Es ist ein sogenanntes Full-Mesh-Network aus Nodes, mit dem neben den Nutzdaten eines Nodes auch Meta- und Diagnoseinformationen repräsentiert werden. Ein Node ähnelt einem Objekt aus der objektorientierten Programmierung. Ein Node kann Attribute besitzen, die gelesen werden können (Data Access (DA), Historical Data Access (HDA)). Es ist möglich Methoden zu definieren und aufzurufen. Eine Methode besitzt Aufrufargumente und Rückgabewerte. Sie wird durch ein Command aufgerufen. Weiterhin werden Events unterstützt, die versendet werden können (AE (Alarms & Events), DA DataChange), um bestimmte Informationen zwischen Geräten auszutauschen. Ein Event besitzt unter anderem einen Empfangszeitpunkt, eine Nachricht und einen Schweregrad. Die o. g. Nodes werden sowohl für die Nutzdaten als auch alle anderen Arten von Metadaten verwendet. Der damit modellierte OPC-Adressraum beinhaltet nun auch ein Typmodell, mit dem sämtliche Datentypen spezifiziert werden. OPC-UA-Kommunikationsarchitektur Die ursprüngliche Bindung an COM/DCOM hat zwar einen großen Beitrag zur Verbreitung von OPC geleistet, hatte jedoch auch entscheidende Nachteile: - Häufige Konfigurationsprobleme von DCOM - Keine konfigurierbaren Timeouts - Bindung an das Betriebssystem Windows - Sicherheitsschwächen, da die Authentifizierung über die lokale Benutzertabelle erfolgte - Keine Kontrolle, was passiert (COM/DCOM ist eine Blackbox, Entwickler haben keinen Quellcode und sind Fehlern ausgeliefert) Aus diesen und weiteren Gründen hat man sich dazu entschieden, einen eigenen Kommunikationsstack für OPC UA zu entwickeln, welcher COM/DCOM ersetzt. Die wichtigsten Merkmale dieses Kommunikationsstacks sind: - Neben einer portablen ANSI-C Implementierung werden sowohl eine C#- als auch eine Java-Implementierung unterstützt. - Skalierbarkeit von eingebetteter Steuerungssoftware bis hin zu betrieblichen bzw. Management-Informationssystemen - Der Stack kann sowohl für Multithreaded-Betrieb als auch für den Singlethreaded/Singletask-Betrieb kompiliert werden, was wichtig für die Portierung auf Embedded-Geräte ist. - Eine eigene Security-Implementierung, basierend auf den neuesten Standards - Konfigurierbarkeit von Timeouts für jeden Serviceaufruf - Chunking von großen Datenpaketen"""@de , """OPC UA devices (servers) expose a “view” of their internal data. The term view is used in the same manner as a database view. It may or may not represent the underlying data structures, but defines the server’s representation of externally accessible data. The OPC UA clients that read the data must understand the defined view. This means that the clients and servers must have high data coupling. A change in the server representation often requires a change in the client systems. This coupling is limited when the data types are simple, such as tagged values, but can be high for complex data, such as analyzers, printers, case packers, and filling machines. OPC UA is also high speed, providing a binary representation of data and relatively short message frames. This makes OPC UA suitable for real-time control and also for synchronized processes. OPC UA works best in situations where the devices are continuously connected and control high-speed synchronous processes. The OPC Foundation has recently released the first OPC UA 95 companion specification, which adds ISA-95 object model representations of equipment, personnel, material, and physical assets. This joint effort between the OPC Foundation, the ISA95 committee, and MESA illustrates how these standards can be used together in a federated system architecture."""@en , """OPC UA was released in 2009. It provides an industrial Ethernet, TCP/IP, and user datagram protocol (UDP)/IP-based, platform-independent, service-oriented communication architecture. It includes the functionality of the original OPC standard but uses standard Internet technology, security, and the ability to handle complex data. OPC UA has been internationalized through the IEC 62541 standards (Source: Dennis Brandl). An important advantage compared to OPC is that in OPC UA data sematics can be machine-readable described."""@en , "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:label "Open Platform Communications Unified Architecture"@en . ### http://www.w3id.org/ecsel-dr-AT#OPC_UA_BinaryProtocol ecsel-dr-AT:OPC_UA_BinaryProtocol rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; 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:label "Open Platform Communications Unified Architecture Binary Protocol"@en . ### http://www.w3id.org/ecsel-dr-AT#OSI_1_2_NetAccessTechnology ecsel-dr-AT:OSI_1_2_NetAccessTechnology rdf:type owl: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-AT#OSI_3_4_NetworkTechnology ecsel-dr-AT:OSI_3_4_NetworkTechnology rdf:type owl: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-AT#OSI_5_7_ApplicationProtocol ecsel-dr-AT:OSI_5_7_ApplicationProtocol rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#OSI_AL1_NetworkAccessLayer ecsel-dr-AT:OSI_AL1_NetworkAccessLayer rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_AggregatedLayer ; rdfs:label """Aggregation of ISO/OSI layer 1 and 2. Describes different techniques for point-to-point (node-to-node) data transfer. Examples: Ethernet, FDDI (Fiber Distributed Data Interface), PPP (Point-to-Point Protocol), WLAN, Wide-area wireless networks (WWAN): 2G, 3G, 4G, 5G. \"Physical infrastructure\" for data transmission / M2M communication."""@de , "Network Access Layer"@en , "Netzzugangsschicht"@de . ### http://www.w3id.org/ecsel-dr-AT#OSI_AL2_InternetLayer ecsel-dr-AT:OSI_AL2_InternetLayer rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_AggregatedLayer ; 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:label "Internet Layer"@en , "Internetschicht"@de . ### http://www.w3id.org/ecsel-dr-AT#OSI_AL3_TransportLayer ecsel-dr-AT:OSI_AL3_TransportLayer rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_AggregatedLayer ; 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:label "Transport Layer"@en , "Transportschicht"@de . ### http://www.w3id.org/ecsel-dr-AT#OSI_AL4_ApplicationLayer ecsel-dr-AT:OSI_AL4_ApplicationLayer rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_AggregatedLayer ; 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:label "Aggregated Application Layer"@en , "Anwendungsschicht"@de . ### http://www.w3id.org/ecsel-dr-AT#OSI_AggregatedLayer ecsel-dr-AT:OSI_AggregatedLayer rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#OSI_DetailedLayer ecsel-dr-AT:OSI_DetailedLayer rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#OSI_L1_PhysicalLink ecsel-dr-AT:OSI_L1_PhysicalLink rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_DetailedLayer ; 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:label "Datenübertragungsschicht"@de . ### http://www.w3id.org/ecsel-dr-AT#OSI_L2_DataLink ecsel-dr-AT:OSI_L2_DataLink rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_DetailedLayer ; 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:label "Data Link Layer"@en , "Sicherungsebene"@de . ### http://www.w3id.org/ecsel-dr-AT#OSI_L3_NetworkLayer ecsel-dr-AT:OSI_L3_NetworkLayer rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_DetailedLayer ; 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:label "Network Layer"@en , "Vermittlungsschicht"@de . ### http://www.w3id.org/ecsel-dr-AT#OSI_L4_TransportLayer ecsel-dr-AT:OSI_L4_TransportLayer rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_DetailedLayer ; 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:label "Transport Layer"@en , "Transportschicht"@de . ### http://www.w3id.org/ecsel-dr-AT#OSI_L5_SessionLayer ecsel-dr-AT:OSI_L5_SessionLayer rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_DetailedLayer ; 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:label "Session layer"@en , "Sitzungsschicht"@de . ### http://www.w3id.org/ecsel-dr-AT#OSI_L6_PresentationLayer ecsel-dr-AT:OSI_L6_PresentationLayer rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_DetailedLayer ; 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:label "Darstellungsschicht"@de , "Presentation layer"@en . ### http://www.w3id.org/ecsel-dr-AT#OSI_L7_ApplicationLayer ecsel-dr-AT:OSI_L7_ApplicationLayer rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_DetailedLayer ; 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:label "Anwendungsschicht"@de , "Application layer"@en . ### http://www.w3id.org/ecsel-dr-AT#OSI_Layer_Model_aggregated ecsel-dr-AT:OSI_Layer_Model_aggregated rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:NetworkLayerModel . ### http://www.w3id.org/ecsel-dr-AT#OSI_Layer_Model_detailed ecsel-dr-AT:OSI_Layer_Model_detailed rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:NetworkLayerModel . ### http://www.w3id.org/ecsel-dr-AT#OSI_TransportProtocol ecsel-dr-AT:OSI_TransportProtocol rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#OWL ecsel-dr-AT:OWL rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L4_SemanticsRepresentation ; rdfs:label "Web Ontology Language"@de . ### http://www.w3id.org/ecsel-dr-AT#Ontology ecsel-dr-AT:Ontology rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L5_DataSemantics . ### http://www.w3id.org/ecsel-dr-AT#PLC ecsel-dr-AT:PLC rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ControlDevice . ### http://www.w3id.org/ecsel-dr-AT#PLM-System ecsel-dr-AT:PLM-System rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:IT-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:label "Product Lifecycle Management System" . ### http://www.w3id.org/ecsel-dr-AT#PLM-System-FirstGeneration ecsel-dr-AT:PLM-System-FirstGeneration rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:PLM-System . ### http://www.w3id.org/ecsel-dr-AT#PLM-System-SecondGeneration ecsel-dr-AT:PLM-System-SecondGeneration rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:PLM-System . ### http://www.w3id.org/ecsel-dr-AT#PLM1_Module ecsel-dr-AT:PLM1_Module rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:PLM-System-FirstGeneration . ### http://www.w3id.org/ecsel-dr-AT#PLM1_System_Suite ecsel-dr-AT:PLM1_System_Suite rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:PLM-System-FirstGeneration . ### http://www.w3id.org/ecsel-dr-AT#PLM1_Vendor ecsel-dr-AT:PLM1_Vendor rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:PLM-System-FirstGeneration . ### http://www.w3id.org/ecsel-dr-AT#PLM2_Module ecsel-dr-AT:PLM2_Module rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:PLM-System-SecondGeneration . ### http://www.w3id.org/ecsel-dr-AT#PLM2_System_Suite ecsel-dr-AT:PLM2_System_Suite rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:PLM-System-SecondGeneration . ### http://www.w3id.org/ecsel-dr-AT#PLM2_Vendor ecsel-dr-AT:PLM2_Vendor rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:PLM-System-SecondGeneration . ### http://www.w3id.org/ecsel-dr-AT#PL_Phase1_Development ecsel-dr-AT:PL_Phase1_Development rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ProductLifecyclePhase ; 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 . ### http://www.w3id.org/ecsel-dr-AT#PL_Phase2_Maintenance_Improvement ecsel-dr-AT:PL_Phase2_Maintenance_Improvement rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ProductLifecyclePhase ; 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 . ### http://www.w3id.org/ecsel-dr-AT#PL_Phase3_Production ecsel-dr-AT:PL_Phase3_Production rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ProductLifecyclePhase ; 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 . ### http://www.w3id.org/ecsel-dr-AT#PL_Phase4_Usage_Maintenance ecsel-dr-AT:PL_Phase4_Usage_Maintenance rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ProductLifecyclePhase ; 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 . ### http://www.w3id.org/ecsel-dr-AT#Packet ecsel-dr-AT:Packet rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:DataTransmissionUnit ; rdfs:comment """Data transmission unit of ISO/OSI Layer 3 (Network Layer). \"Letter\", contains IP address"""@en . ### http://www.w3id.org/ecsel-dr-AT#ProductDataManagement-Module ecsel-dr-AT:ProductDataManagement-Module rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:PLM1_Module . ### http://www.w3id.org/ecsel-dr-AT#ProductLifecyclePhase ecsel-dr-AT:ProductLifecyclePhase rdf:type owl: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-AT#ProductionCellPlanning ecsel-dr-AT:ProductionCellPlanning rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:PLM1_Module . ### http://www.w3id.org/ecsel-dr-AT#Proxy ecsel-dr-AT:Proxy rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:CommunicationDevice ; 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 . ### http://www.w3id.org/ecsel-dr-AT#RDF ecsel-dr-AT:RDF rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:DataLanguage_SemanticWebStackBased ; rdfs:label "Resource Description Framework"@de . ### http://www.w3id.org/ecsel-dr-AT#RDF-GraphStore ecsel-dr-AT:RDF-GraphStore rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Database-System . ### http://www.w3id.org/ecsel-dr-AT#RDFS ecsel-dr-AT:RDFS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L4_SemanticsRepresentation ; rdfs:label "Resource Description Framework Schema"@de . ### http://www.w3id.org/ecsel-dr-AT#RDFa ecsel-dr-AT:RDFa rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L2_DataSyntax . ### http://www.w3id.org/ecsel-dr-AT#REST ecsel-dr-AT:REST rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ServiceOrientedArchitecture ; rdfs:comment "REST is not a complete Service-oriented architecture, but an architecture style that enables systems to show SoA properties." , "Representational State Transfer (REST) is the software architectural style of the World Wide Web. Thus we may regard REST more as an architecture than a protocol. It's based on HTTP and supports a few commande over HTTP enabling SOA properties. (Delsing, IoT Automation, Chapter 1.6.3)"@de ; rdfs:label "Representational State Transfer"@de . ### http://www.w3id.org/ecsel-dr-AT#RFID ecsel-dr-AT:RFID rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_1_2_NetAccessTechnology ; rdfs:label "Radio Frequency Identification" . ### http://www.w3id.org/ecsel-dr-AT#RackFeeder ecsel-dr-AT:RackFeeder rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ActuatorDevice ; rdfs:comment "Gerät zur Materialbewegung in einem automatisierten Hochregallager."@de ; rdfs:label "Regalbediengerät"@de . ### http://www.w3id.org/ecsel-dr-AT#RelationalDatabase-System ecsel-dr-AT:RelationalDatabase-System rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Database-System . ### http://www.w3id.org/ecsel-dr-AT#Repeater ecsel-dr-AT:Repeater rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:CommunicationDevice . ### http://www.w3id.org/ecsel-dr-AT#RobotCellPlanning ecsel-dr-AT:RobotCellPlanning rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:PLM1_Module . ### http://www.w3id.org/ecsel-dr-AT#RosettaNet-Specification ecsel-dr-AT:RosettaNet-Specification rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:EDI_Specification . ### http://www.w3id.org/ecsel-dr-AT#Router ecsel-dr-AT:Router rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:CommunicationDevice ; 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:label "Router"@en . ### http://www.w3id.org/ecsel-dr-AT#SCADA-System ecsel-dr-AT:SCADA-System rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:IT-System ; rdfs:label "BDE-System"@de , "Betriebsdatenerfassungs-System"@de , "Supervisory Control And Data Aquisision System" . ### http://www.w3id.org/ecsel-dr-AT#SCTP ecsel-dr-AT:SCTP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_TransportProtocol ; rdfs:comment "Das Stream Control Transmission Protocol (SCTP) ist ein zuverlässiges, verbindungsorientiertes Netzwerkprotokoll. Es gehört zur Transportschicht und setzt auf einem potenziell unzuverlässigen, verbindungslosen Paketdienst auf."@de , """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 . ### http://www.w3id.org/ecsel-dr-AT#SECS ecsel-dr-AT:SECS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; 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:label "Communication Protocol of the SECS/GEM protocol standard."@en , "SEMI Equipment Communications Standard"@en . ### http://www.w3id.org/ecsel-dr-AT#SECS_GEM ecsel-dr-AT:SECS_GEM rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ServiceOrientedArchitecture ; 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:label "SEMI Equipment Communications Standard / Generic Equipment Model"@en . ### http://www.w3id.org/ecsel-dr-AT#SMQTT ecsel-dr-AT:SMQTT rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:MQTT_TCPIP_based ; 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 . ### http://www.w3id.org/ecsel-dr-AT#SMQTT-SN ecsel-dr-AT:SMQTT-SN rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:MQTT_nonTCPIP_based ; 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 . ### http://www.w3id.org/ecsel-dr-AT#SMTP ecsel-dr-AT:SMTP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol . ### http://www.w3id.org/ecsel-dr-AT#SOAP ecsel-dr-AT:SOAP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ServiceOrientedArchitecture ; 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 . ### http://www.w3id.org/ecsel-dr-AT#SOSA ecsel-dr-AT:SOSA rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Ontology . ### http://www.w3id.org/ecsel-dr-AT#SPARQL_Language ecsel-dr-AT:SPARQL_Language rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:DataLanguage_SemanticWebStackBased . ### http://www.w3id.org/ecsel-dr-AT#SPARQL_protocol ecsel-dr-AT:SPARQL_protocol rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ServiceOrientedArchitecture ; rdfs:comment "Protocol for the transmission of SPARQL queries and SPARQL updates between a client and a RDF graph store on a server."@de . ### http://www.w3id.org/ecsel-dr-AT#SSN ecsel-dr-AT:SSN rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Ontology . ### http://www.w3id.org/ecsel-dr-AT#STOMP ecsel-dr-AT:STOMP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; 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 : (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:label "Streaming Text Oriented Message Protocol"@en . ### http://www.w3id.org/ecsel-dr-AT#Segment ecsel-dr-AT:Segment rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:DataTransmissionUnit ; 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 . ### http://www.w3id.org/ecsel-dr-AT#SenML ecsel-dr-AT:SenML rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:MarkupLanguage ; rdfs:comment "Sensor Modelling Language" . ### http://www.w3id.org/ecsel-dr-AT#SensML ecsel-dr-AT:SensML rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:MarkupLanguage . ### http://www.w3id.org/ecsel-dr-AT#SensorDevice ecsel-dr-AT:SensorDevice rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Device . ### http://www.w3id.org/ecsel-dr-AT#ServiceDataLanguage ecsel-dr-AT:ServiceDataLanguage rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L5_DataSemantics . ### http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitecture ecsel-dr-AT:ServiceOrientedArchitecture rdf:type owl:Class ; rdfs:label "Service Oriented Architecture Protocols"@de . ### http://www.w3id.org/ecsel-dr-AT#ServiceOrientedArchitectureImplementation ecsel-dr-AT:ServiceOrientedArchitectureImplementation rdf:type owl: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-AT#ServiceOrientedArchitecture_FunctionPattern ecsel-dr-AT:ServiceOrientedArchitecture_FunctionPattern rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#Simulation-System ecsel-dr-AT:Simulation-System rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:IT-System . ### http://www.w3id.org/ecsel-dr-AT#SoA_Client ecsel-dr-AT:SoA_Client rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ServiceOrientedArchitecture_FunctionPattern ; 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 . ### http://www.w3id.org/ecsel-dr-AT#SoA_Publisher ecsel-dr-AT:SoA_Publisher rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ServiceOrientedArchitecture_FunctionPattern ; 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 . ### http://www.w3id.org/ecsel-dr-AT#SoA_Server ecsel-dr-AT:SoA_Server rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ServiceOrientedArchitecture_FunctionPattern ; rdfs:comment """\"Role\" or function of an software (application) system that offers one or several services to other systems. Other names: Service Producer,"""@en . ### http://www.w3id.org/ecsel-dr-AT#SoA_ServiceBroker ecsel-dr-AT:SoA_ServiceBroker rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ServiceOrientedArchitecture_FunctionPattern . ### http://www.w3id.org/ecsel-dr-AT#SoA_ServiceRepository ecsel-dr-AT:SoA_ServiceRepository rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ServiceOrientedArchitecture_FunctionPattern . ### http://www.w3id.org/ecsel-dr-AT#SoA_Subscriber ecsel-dr-AT:SoA_Subscriber rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ServiceOrientedArchitecture_FunctionPattern . ### http://www.w3id.org/ecsel-dr-AT#Standard ecsel-dr-AT:Standard rdf:type owl:Class ; owl:equivalentClass ecsel-dr-RAMI40:Standard . ### http://www.w3id.org/ecsel-dr-AT#StandardisationOrganization ecsel-dr-AT:StandardisationOrganization rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#StationaryRobot ecsel-dr-AT:StationaryRobot rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ActuatorDevice . ### http://www.w3id.org/ecsel-dr-AT#SupplyChainSimulationSystem ecsel-dr-AT:SupplyChainSimulationSystem rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Simulation-System . ### http://www.w3id.org/ecsel-dr-AT#Switch ecsel-dr-AT:Switch rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:CommunicationDevice . ### http://www.w3id.org/ecsel-dr-AT#TCP ecsel-dr-AT:TCP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_TransportProtocol . ### http://www.w3id.org/ecsel-dr-AT#TCP_IP ecsel-dr-AT:TCP_IP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_3_4_NetworkTechnology . ### http://www.w3id.org/ecsel-dr-AT#TTP_A ecsel-dr-AT:TTP_A rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_Car_Airplane ; 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:label "Time Triggered Protocol Class A"@de . ### http://www.w3id.org/ecsel-dr-AT#TTP_C ecsel-dr-AT:TTP_C rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Fieldbus_Car_Airplane ; 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:label "Time Triggered Protocol Class C"@de . ### http://www.w3id.org/ecsel-dr-AT#TokenRing ecsel-dr-AT:TokenRing rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_1_2_NetAccessTechnology ; 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 . ### http://www.w3id.org/ecsel-dr-AT#ToolingMachine ecsel-dr-AT:ToolingMachine rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ActuatorDevice . ### http://www.w3id.org/ecsel-dr-AT#TransportRobot ecsel-dr-AT:TransportRobot rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ActuatorDevice ; 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:label "Transportroboter"@de . ### http://www.w3id.org/ecsel-dr-AT#UDP ecsel-dr-AT:UDP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_TransportProtocol . ### http://www.w3id.org/ecsel-dr-AT#UDS ecsel-dr-AT:UDS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; rdfs:label "Unified Diagnostic Services"@de . ### http://www.w3id.org/ecsel-dr-AT#UML ecsel-dr-AT:UML rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:MarkupLanguage ; rdfs:label "Unified Modelling Language" . ### http://www.w3id.org/ecsel-dr-AT#W3C ecsel-dr-AT:W3C rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:StandardisationOrganization . ### http://www.w3id.org/ecsel-dr-AT#W3C-Standard ecsel-dr-AT:W3C-Standard rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:Standard . ### http://www.w3id.org/ecsel-dr-AT#W3C_Data_Knowledge_Stack ecsel-dr-AT:W3C_Data_Knowledge_Stack rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:NetworkLayerModel ; 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 . ### http://www.w3id.org/ecsel-dr-AT#W3C_L1_WebPlatform ecsel-dr-AT:W3C_L1_WebPlatform rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#W3C_L2_DataSyntax ecsel-dr-AT:W3C_L2_DataSyntax rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#W3C_L3_KnowledgeRepresentation ecsel-dr-AT:W3C_L3_KnowledgeRepresentation rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#W3C_L4_SemanticsRepresentation ecsel-dr-AT:W3C_L4_SemanticsRepresentation rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#W3C_L5_DataSemantics ecsel-dr-AT:W3C_L5_DataSemantics rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-AT#WADL ecsel-dr-AT:WADL rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:MarkupLanguage ; 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.""" . ### http://www.w3id.org/ecsel-dr-AT#WAP ecsel-dr-AT:WAP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:CommunicationDevice ; rdfs:label "Wireless Access Point" . ### http://www.w3id.org/ecsel-dr-AT#WIMAX_802_16 ecsel-dr-AT:WIMAX_802_16 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_1_2_NetAccessTechnology . ### http://www.w3id.org/ecsel-dr-AT#WLAN_802_11 ecsel-dr-AT:WLAN_802_11 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_1_2_NetAccessTechnology ; 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 , "Wireless Local Area Network"@en . ### http://www.w3id.org/ecsel-dr-AT#WPAN_802_15_4 ecsel-dr-AT:WPAN_802_15_4 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_1_2_NetAccessTechnology ; rdfs:comment "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 , """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 . ### http://www.w3id.org/ecsel-dr-AT#WSDL ecsel-dr-AT:WSDL rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:MarkupLanguage ; 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)." , """WSDL ist eine Metasprache, mit deren Hilfe die angebotenen Funktionen, Daten, Datentypen und Austauschprotokolle eines Webservice beschrieben werden können. Es werden im Wesentlichen die Operationen definiert, die von außen zugänglich sind, sowie die Parameter und Rückgabewerte dieser Operationen. Im Einzelnen beinhaltet ein WSDL-Dokument funktionelle Angaben zu: der Schnittstelle Zugangsprotokoll und Details zum Deployment Alle notwendigen Informationen zum Zugriff auf den Service, in maschinenlesbarem Format Nicht enthalten sind hingegen: Quality-of-Service-Informationen Taxonomien/Ontologien zur semantischen Einordnung des Services Beschreibungselemente Aufbau einer WSDL-Datei Services werden durch sechs XML-Hauptelemente definiert: types (Datentypen) Definition der Datentypen, die zum Austausch der messages benutzt werden. message (Nachricht) Abstrakte Definitionen der übertragenen Daten, bestehend aus mehreren logischen Teilen, von denen jeder mit einer Definition innerhalb eines Datentypsystems verknüpft ist. portType (Schnittstellentypen) Eine Menge von abstrakten Operationen (vier Typen von ausgetauschten Nachrichten): One-way: Der Service bekommt eine Input-Message vom Client. Request-response: Der Service bekommt einen Request (Input-Message) vom Client und sendet eine Antwort (Output-Message). Solicit-response: Der Service sendet eine Message und erwartet eine Antwort vom Client. Notification: Der Service sendet eine Output-Message. In WSDL 2.0 wurde die Bezeichnung zu Interface geändert. binding (Bindung) Bestimmt das konkrete Protokoll und Datenformat für die Arbeitsschritte und Nachrichten, die durch einen bestimmten Port-Typ gegeben sind. port (Port) Spezifiziert eine Adresse für eine Bindung, also eine Kommunikationsschnittstelle, üblicherweise ein URI. In WSDL 2.0 wurde die Bezeichnung zu Endpoint geändert. service (Service) Fasst die Menge von Ports eines Port-Typs zusammen. Zudem werden diese sechs Hauptelemente in die Gruppe der abstrakten und konkreten Definitionen eingeteilt. Abstrakte Definitionen: Types Messages PortTypes (ab WSDL 2.0: Interfaces) Konkrete Definitionen: Bindings Ports (ab WSDL 2.0: Endpoints) Services Die Definition von konkreten Inhalten unterscheidet WSDL von den bestehenden Schnittstellenbeschreibungssprachen wie IDL. Diese hatten die Schnittstellen bisher nur abstrakt beschrieben. Anwendung WSDL wird häufig in Kombination mit SOAP und dem XML Schema verwendet, um Webservices im Internet anzubieten. Ein Client, der einen Webservice aufruft, kann WSDL lesen, um zu bestimmen, welche Funktionen auf dem Server verfügbar sind. Alle verwendeten speziellen Datentypen sind in der WSDL-Datei in XML-Form eingebunden. Der Quellcode, der zum Zusammensetzen der gesendeten Objekte auf der Client-Seite notwendig ist, kann automatisiert aus der WSDL-Datei generiert werden. Der Client kann nun SOAP verwenden, um eine in WSDL gelistete Funktion letztlich aufzurufen.""" . ### http://www.w3id.org/ecsel-dr-AT#WebAddress ecsel-dr-AT:WebAddress rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L1_WebPlatform . ### http://www.w3id.org/ecsel-dr-AT#WebApplicationProtocol ecsel-dr-AT:WebApplicationProtocol rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L1_WebPlatform . ### http://www.w3id.org/ecsel-dr-AT#WirelessHART ecsel-dr-AT:WirelessHART rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_3_4_NetworkTechnology ; rdfs:comment "Highway Addressable Remote Transducer (HART) is a standard, widely used communication system for building industrial fieldbuses. It enables the digital communication of several users (field devices) via a common data bus. HART focuses on the widely used 4/20 mA standard (for the transmission of analogue sensor signals). Existing lines of the older system can be used directly and both systems can be operated in parallel. The HART was developed by Rosemount in the 1980s for their field devices. In 1989, the HART standard was launched by the HART Communication Foundation (HCF). Since 2007, HART has been part of the fieldbus standard IEC 61158. The headquarters of the HART Communication Foundation in Europe is Basel (Switzerland)."@en , """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.""" . ### http://www.w3id.org/ecsel-dr-AT#X400 ecsel-dr-AT:X400 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; rdfs:comment """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 , """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 ; rdfs:label "Message Handling System (MHS)"@de , "X.400"@de . ### http://www.w3id.org/ecsel-dr-AT#XHTML ecsel-dr-AT:XHTML rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L2_DataSyntax . ### http://www.w3id.org/ecsel-dr-AT#XML ecsel-dr-AT:XML rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:W3C_L2_DataSyntax ; rdfs:label "Extended Markup Language" . ### http://www.w3id.org/ecsel-dr-AT#XML-Schema ecsel-dr-AT:XML-Schema rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:DataLanguage_XML-based . ### http://www.w3id.org/ecsel-dr-AT#XMPP ecsel-dr-AT:XMPP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; rdfs:comment "Supported by the XMPP community. Used by large companies for Push notifications, instant messaging and chat. (Delsing)"@de , """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 ; rdfs:label "Extensible Messaging and Presence Protocol"@en . ### http://www.w3id.org/ecsel-dr-AT#Z-Wave ecsel-dr-AT:Z-Wave rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_3_4_NetworkTechnology ; 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 . ### http://www.w3id.org/ecsel-dr-AT#ZigBee ecsel-dr-AT:ZigBee rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_3_4_NetworkTechnology ; rdfs:comment """Die Spezifikation beschreibt ein Framework für Funknetze. ZigBee baut auf dem Standard IEEE 802.15.4 auf und erweitert dessen Funktionalität insbesondere um die Möglichkeit des Routings und des sicheren Schlüsselaustausches. Im IEEE-802.15.4-Standard sind die PHY-Schicht und die MAC-Schicht definiert. ZigBee erweitert diesen Protokollstapel um die Schichten NWK und APL. Wobei zu beachten ist, dass es sich bei ZigBee um ein Framework handelt und eine Anwendung in die APL-Schicht eingebettet wird. Die Einsatzmöglichkeiten von ZigBee sind vielfältig, zum Beispiel in der Gebäude-Automation, im medizinischen Bereich, für Steuerungsanlagen und für alle Arten von Sensormessungen. Die ZigBee-Spezifikation stellt dem Entwickler drei verschiedene Gerätearten (ZigBee Devices) zur Verfügung. Mit diesen Geräten wird ein ZigBee Wireless Personal Area Network (WPAN) aufgebaut. Man unterscheidet drei Rollen, die ein ZigBee-Gerät erfüllen kann: Endgerät (ZigBee End Device, ZED) Geräte wie zum Beispiel Steuerungs- oder Sensormodule werden meist mit Batterien betrieben. Diese können als ZigBee-Endgeräte implementiert werden und benötigen nur einen Teil der Funktionen der ZigBee-Spezifikation. Sie nehmen nicht am Routing im Netzwerk teil und können in einen Schlafmodus gehen. Sie melden sich an einem Router ihrer Wahl an und treten so dem ZigBee-Netzwerk bei. Sie können ausschließlich mit dem Router kommunizieren, über den sie dem Netzwerk beigetreten sind. Werden Daten an ein solches Endgerät geschickt und dieses befindet sich im Schlafmodus, speichert der Router diese Pakete, bis das Endgerät sie abruft. Router (ZigBee-Router, ZR) ZigBee-Router nehmen am Routing der Pakete durch das Netzwerk teil. Sie benötigen einen größeren Funktionsumfang und damit auch etwas mehr Hardwareressourcen. ZigBee-Router treten einem Netzwerk bei, indem sie sich an einem im Netzwerk befindlichen Router anmelden. Das Routing im Netzwerk erfolgt entweder entlang eines sich so bildenden Baumes (Stackprofil ZigBee) oder durch dynamisches Routing als Meshnetzwerk (Stackprofil ZigBee PRO). Tritt ein Funkmodul über einen Router dem Netzwerk bei, vergibt dieser diesem eine 16-Bit-Kurzadresse (engl. short address). Bei Meshnetzwerken erfolgt dies zufällig. Auftretende Adresskonflikte müssen erkannt und dann behoben werden. Koordinator (ZigBee coordinator, ZC) Ein ZigBee-Koordinator startet das Netzwerk mit festgelegten Parametern. Nach dem Start übernimmt er dieselben Aufgaben wie ein ZigBee-Router. Adressierung Die Identifizierung eines Netzwerks erfolgt über eine 64-Bit erweiterte PAN-ID. Um unnötigen Protokolloverhead zu vermeiden, wählt der Koordinator allerdings für ein PAN bei dessen Start eine 16-Bit-PAN-ID. Jedes Funkmodul besitzt eine eindeutige 64-Bit-IEEE-Adresse. Beim Eintritt in ein Netzwerk bekommt es allerdings ebenfalls eine 16-Bit-Kurzadresse zugewiesen. Bei stochastischer Adressvergabe müssen Adresskonflikte aufgelöst werden. Um Daten an ein anderes Funkmodul im selben Netzwerk zu senden, genügt damit die Angabe der 16-bit-Kurzadresse. Allerdings werden zusätzlich verschiedene Anwendungsobjekte über Endpunkte adressiert. Dieses Verfahren ähnelt dem TCP-Port bei TCP/IP. Jedem Knoten stehen 255 Endpunkte zur Verfügung. Für die Anwendungslogik sind die Endpunkte 1 bis 240 vorgesehen. Endpunkt 255 ist für Broadcast an alle Endpunkte reserviert. Die Endpunkte 241 bis 254 sind für spätere spezielle Aufgaben reserviert. An den Endpunkt 0 gerichtete Daten sind für das (ZDO) ZigBee Device Object, welches die Steuerung der Netzwerkaufgaben übernimmt."""@de , """Konkurrenz Im Bereich Heimautomation und M2M steht ZigBee in direkter Konkurrenz zu Z-Wave. Für beide Protokolle gibt es eine Reihe OSGi-basierter Framework-Lösungen, die über das reine Protokoll hinausgehende Heimautomatisierungsfunktionen beinhalten, wie zum Beispiel einen Geräteabstraktionslayer. Darüber hinaus steht ZigBee im Bereich der Heimautomation in Konkurrenz zu Enocean, das anders als ZigBee und Z-Wave durch die Betonung des Energy-Harvesting batterielose Sensoren ermöglicht. Im Bereich Medizintechnik ist als Konkurrenzstandard Bluetooth bzw. die Spezifikation der Continua Health Allianz erwähnenswert."""@de , "https://de.wikipedia.org/wiki/ZigBee"@de . ### http://www.w3id.org/ecsel-dr-AT#ZigBee_IP ecsel-dr-AT:ZigBee_IP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_3_4_NetworkTechnology ; 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 . ### http://www.w3id.org/ecsel-dr-AT#ZigBee_RF4CE ecsel-dr-AT:ZigBee_RF4CE rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_3_4_NetworkTechnology ; 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:label "Radio Frequency for Consumer Electronics"@en . ### http://www.w3id.org/ecsel-dr-AT#auto-gration-Specification ecsel-dr-AT:auto-gration-Specification rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:ServiceDataLanguage ; 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.""" . ### http://www.w3id.org/ecsel-dr-AT#uPnP ecsel-dr-AT:uPnP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_5_7_ApplicationProtocol ; rdfs:comment """Application protocol for discovery of other devices in a network. Alternative to mDNS, PhysicalNet and HyperCat. (https://www.postscapes.com/internet-of-things-protocols/)"""@en , "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 , "uPnP is supported by the Open Connectivity Foundation with early adopters like Philips and Samsung. Consumer product communication has been the target field of applications. We find it widely used in home appliances like TV sets and streaming devices. (Delsing)"@de . ### http://www.w3id.org/ecsel-dr-AT#2G_GPRS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_1_2_NetAccessTechnology ; rdfs:comment """Second generation of Wireless Wide Area Data Transmission Networks. Uses GSM radio infrastructure."""@en ; rdfs:label "General Packaged Radio Service"@en . ### http://www.w3id.org/ecsel-dr-AT#3G_UMTS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_1_2_NetAccessTechnology ; 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:label "Universal Mobile Telecommunications System"@en . ### http://www.w3id.org/ecsel-dr-AT#4G_LTE rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_1_2_NetAccessTechnology ; rdfs:comment """Fourth generation of wireless wide area data transmission networks. Minimal size of radio transport block: subframe with length of 1ms"""@en ; rdfs:label "Long Term Evolution"@en . ### http://www.w3id.org/ecsel-dr-AT#5G rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_1_2_NetAccessTechnology ; 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 , """First mobile data technology with real-time ability: latency requirement: 1 millisecond end-to-end transmission! Data transmission rate increased by factor 10^3 compared to LTE (but low latency is much more important as it enables autonomous car driving with outside control / data processing."""@en ; rdfs:label "5G"@en . ### http://www.w3id.org/ecsel-dr-AT#6LoWPAN rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-AT:OSI_3_4_NetworkTechnology ; 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 , """Einordnung des Standards ins OSI-Modell: Die Hauptkomponente des 6LoWPAN-Protokolls ist der 6LoWPAN-Adaption-Layer, der auf der Vermittlungsebene (--> Ebene 3!) des OSI-Modells arbeitet und Aufgaben wie Header-Komprimierung, Paket-Fragmentierung und -defragmentierung, sowie Routing in Mesh-Netzwerken übernimmt. Für Ebene 1 und 2 wird der Standard IEEE 802.15.4 genutzt. Die Ebenen 3 und 4 sind zentral für diesen Standard. Ebene 3: IPv6 und 6LoWPAN Adaption Layer for Routing and De-/Fragmentierung Ebene 4: TCP oder UDP Ebene 5 und 6: nicht explizit genutzt Ebene 7: 6LoWPAN-spezifische Anwendung (socket interface)"""@de ; rdfs:label "IPv6 over Low Power Wireless Personal Area Network"@de . ### http://www.w3id.org/ecsel-dr-OM#Action rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ) ] . ### http://www.w3id.org/ecsel-dr-OM#Allocation rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-OM#ContactPersonData rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-OM#Customer rdf:type owl:Class ; owl:equivalentClass . ### http://www.w3id.org/ecsel-dr-OM#CustomerData rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-OM#CustomerPlant rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-OM#CustomerPlantData rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-OM#DemandFulfillement rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-OM#OpenOrder rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-OM#OpenOrderBook rdf:type owl:Class ; owl:equivalentClass . ### http://www.w3id.org/ecsel-dr-OM#OrderChangeRequest rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-OM#OrderConfirmation rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-OM#OrderLineItem rdf:type owl:Class ; owl:equivalentClass . ### http://www.w3id.org/ecsel-dr-OM#Supplier rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-OM#SupplierData rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-OM#Supply rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-OM#UserAction rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ) ] . ### http://www.w3id.org/ecsel-dr-OOSMP#AdditionalPowerManagement ecsel-dr-OOSMP:AdditionalPowerManagement rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:comment "A semiconductor product which is used within the context of additional power management" ; skos:prefLabel "Additional Power Management" . ### http://www.w3id.org/ecsel-dr-OOSMP#AngleSensor ecsel-dr-OOSMP:AngleSensor rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:MagneticPositionSensor ; 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." ; skos:prefLabel "Angle Sensor" . ### http://www.w3id.org/ecsel-dr-OOSMP#ApplicationArea ecsel-dr-OOSMP:ApplicationArea rdf:type owl:Class ; owl:equivalentClass ; rdfs:comment "A way in which something can be used for a particular purpose" ; skos:prefLabel "Application Area" . ### http://www.w3id.org/ecsel-dr-OOSMP#ApplicationLevel1 ecsel-dr-OOSMP:ApplicationLevel1 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:ApplicationArea ; rdfs:comment "The top application level which can have several sub application levels (application level 2)" ; rdfs:isDefinedBy ecsel-dr-OOSMP:InfineonTechnologiesAG_Organization ; skos:prefLabel "Application Level 1" . ### http://www.w3id.org/ecsel-dr-OOSMP#ApplicationLevel2 ecsel-dr-OOSMP:ApplicationLevel2 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:ApplicationArea ; 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:isDefinedBy ecsel-dr-OOSMP:InfineonTechnologiesAG_Organization ; skos:prefLabel "Application Level 2" . ### http://www.w3id.org/ecsel-dr-OOSMP#ApplicationLevel3 ecsel-dr-OOSMP:ApplicationLevel3 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:ApplicationArea ; rdfs:comment "The lowest application level which can be assigned to super application levels (application level 2)" ; rdfs:isDefinedBy ecsel-dr-OOSMP:InfineonTechnologiesAG_Organization ; skos:prefLabel "Application Level 3" . ### http://www.w3id.org/ecsel-dr-OOSMP#BusinessLine ecsel-dr-OOSMP:BusinessLine rdf:type owl:Class ; rdfs:subClassOf org:OrganizationalUnit ; rdfs:comment "A business line is an organizational unit that can be assigned to a division and can have one or more product lines." ; skos:prefLabel "Business Line" ; ecsel-dr-OOSMP:abbreviation "BL" . ### http://www.w3id.org/ecsel-dr-OOSMP#CompletelyLeadFreeStatus ecsel-dr-OOSMP:CompletelyLeadFreeStatus rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-OOSMP:CompletelyLeadFree_Status ecsel-dr-OOSMP:NotCompletelyLeadFree_Status ) ] ; rdfs:subClassOf ecsel-dr-OOSMP:SemiconductorProductStatus ; rdfs:comment "This status determines whether a semiconductor product is lead free or not." ; skos:prefLabel "Completely Lead Free Status" . ### http://www.w3id.org/ecsel-dr-OOSMP#DesignTarget ecsel-dr-OOSMP:DesignTarget rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-OOSMP:Allrounder_DesignTarget ecsel-dr-OOSMP:EasyToDesign_DesignTarget ecsel-dr-OOSMP:FlexibleToDesign_DesignTarget ) ] ; 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\"." ; skos:prefLabel "Design Target" . ### http://www.w3id.org/ecsel-dr-OOSMP#DigitalBarometricPressureSensor ecsel-dr-OOSMP:DigitalBarometricPressureSensor rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:PressureSensor ; 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." ; skos:prefLabel "Digital Barometric Pressure Sensor" . ### http://www.w3id.org/ecsel-dr-OOSMP#DiscretePowerStage ecsel-dr-OOSMP:DiscretePowerStage rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:comment "A semiconductor product which is used within a discrete power stage" ; skos:prefLabel "Discrete Power Stage" . ### http://www.w3id.org/ecsel-dr-OOSMP#Division ecsel-dr-OOSMP:Division rdf:type owl:Class ; owl:equivalentClass ; rdfs:subClassOf org:OrganizationalUnit ; 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." ; skos:altLabel "Lead Division" ; skos:prefLabel "Division" ; ecsel-dr-OOSMP:abbreviation "DIV" . ### http://www.w3id.org/ecsel-dr-OOSMP#GateDriver ecsel-dr-OOSMP:GateDriver rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:comment "A semiconductor product which is used as a gate driver" ; skos:prefLabel "Gate Driver" . ### http://www.w3id.org/ecsel-dr-OOSMP#HallSwitch ecsel-dr-OOSMP:HallSwitch rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:MagneticPositionSensor ; 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." ; skos:prefLabel "Hall Switch" . ### http://www.w3id.org/ecsel-dr-OOSMP#HalogenFreeStatus ecsel-dr-OOSMP:HalogenFreeStatus rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-OOSMP:HalogenFree_Status ecsel-dr-OOSMP:NotHalogenFree_Status ) ] ; rdfs:subClassOf ecsel-dr-OOSMP:SemiconductorProductStatus ; rdfs:comment "This status determines whether a semiconductor product is halogen free or not." ; skos:prefLabel "Halogen Free Status" . ### http://www.w3id.org/ecsel-dr-OOSMP#Industry ecsel-dr-OOSMP:Industry rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:ApplicationArea ; rdfs:comment "An application area on top level (corresponing to application level 1) which can have several sub application levels (main application)" ; rdfs:isDefinedBy ecsel-dr-OOSMP:InfineonTechnologiesAG_Organization ; skos:prefLabel "Industry" . ### http://www.w3id.org/ecsel-dr-OOSMP#IntegratedPressureSensor ecsel-dr-OOSMP:IntegratedPressureSensor rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:PressureSensor ; 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." ; skos:prefLabel "Integrated Pressure Sensor" . ### http://www.w3id.org/ecsel-dr-OOSMP#IntegrationLevel ecsel-dr-OOSMP:IntegrationLevel rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-OOSMP:Discrete_SolutionIntegrationLevel ecsel-dr-OOSMP:FullyIntegrated_SolutionIntegrationLevel ecsel-dr-OOSMP:IntegratedControllerDriver_SolutionIntegrationLevel ecsel-dr-OOSMP:IntegratedDriverPowerStage_SolutionIntegrationLevel ecsel-dr-OOSMP:IntegratedPowerStage_SolutionIntegrationLevel ) ] ; 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\"." ; skos:prefLabel "Integration Level" . ### http://www.w3id.org/ecsel-dr-OOSMP#IntelligentPowerModule ecsel-dr-OOSMP:IntelligentPowerModule rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:comment "A semiconductor product which is used as intelligent power module" ; skos:prefLabel "Intelligent Power Module" . ### http://www.w3id.org/ecsel-dr-OOSMP#LinearHallSensor ecsel-dr-OOSMP:LinearHallSensor rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:MagneticPositionSensor ; 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.""" ; skos:prefLabel "Linear Hall Sensor" . ### http://www.w3id.org/ecsel-dr-OOSMP#MagneticCurrentSensor ecsel-dr-OOSMP:MagneticCurrentSensor rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:Sensor ; rdfs:comment "A high-precision current sensor for industrial applications based on Infoneon proven Hall technology. The core-less concept significantly reduces footprint compared with existing solutions. Infineon´s TLI4970 is an easy-to-use, fully digital solution that does not require external calibration or additional parts such as A/D converters, 0 pAmps or reference voltage. It thus significantly reduces overall implementation effort as well as PCB space and cost." , "A magnetic current sensor is a sensor which measures magnetic current." ; skos:prefLabel "Magnetic Current Sensor" . ### http://www.w3id.org/ecsel-dr-OOSMP#MagneticPositionSensor ecsel-dr-OOSMP:MagneticPositionSensor rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:Sensor ; rdfs:comment "A magnetic position sensor is a sensor which measures magnetic positions." ; skos:prefLabel "Magnetic Position Sensor" . ### http://www.w3id.org/ecsel-dr-OOSMP#MagneticSpeedSensor ecsel-dr-OOSMP:MagneticSpeedSensor rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP: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." ; skos:prefLabel "Magnetic Speed Sensor" . ### http://www.w3id.org/ecsel-dr-OOSMP#MainApplication ecsel-dr-OOSMP:MainApplication rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:ApplicationArea ; 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:isDefinedBy ecsel-dr-OOSMP:InfineonTechnologiesAG_Organization ; skos:prefLabel "Main Application" . ### http://www.w3id.org/ecsel-dr-OOSMP#MainPowerDeviceType ecsel-dr-OOSMP:MainPowerDeviceType rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-OOSMP:IGBT_MainPowerDeviceType ecsel-dr-OOSMP:MOSFET_MainPowerDeviceType ecsel-dr-OOSMP:Relay_MainPowerDeviceType ) ] ; 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\"." ; skos:prefLabel "Main Power Device Type" . ### http://www.w3id.org/ecsel-dr-OOSMP#Microcontroller ecsel-dr-OOSMP:Microcontroller rdf:type owl:Class ; owl:equivalentClass ; rdfs:subClassOf ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:comment "A semiconductor product which is used as microcontroller" ; skos:prefLabel "Microcontroller" . ### http://www.w3id.org/ecsel-dr-OOSMP#Microphone ecsel-dr-OOSMP:Microphone rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:Sensor ; 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." ; skos:prefLabel "Microphone" . ### http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution ecsel-dr-OOSMP:MotorControlAndDriveSolution rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:SemiconductorSolution ; rdfs:comment "A motor control and drive solution is a semiconductor solution which function is to drive and control a motor." ; skos:prefLabel "Motor Control and Drive Solution" . ### http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution_DCLinkVoltage155 ecsel-dr-OOSMP:MotorControlAndDriveSolution_DCLinkVoltage155 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:comment "Motor control and drive solution with DC link voltage equal to 155.0." ; skos:prefLabel "Motor Control and Drive Solution With DC Link Voltage 155.0" . ### http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution_ElectricPowerMax200 ecsel-dr-OOSMP:MotorControlAndDriveSolution_ElectricPowerMax200 rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:comment "Motor control and drive solution with maximum electric power equal to 200.0." ; skos:prefLabel "Motor Control and Drive Solution With Electric Power Max 200.0" . ### http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution_IndustrialQualification ecsel-dr-OOSMP:MotorControlAndDriveSolution_IndustrialQualification rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:comment "Motor control and drive solution with a industrial qualification." ; skos:prefLabel "Motor Control and Drive Solution With Industrial Qualification" . ### http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution_WithSensor ecsel-dr-OOSMP:MotorControlAndDriveSolution_WithSensor rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:comment "Motor control and drive solution with sensor" . ### http://www.w3id.org/ecsel-dr-OOSMP#MotorControlAndDriveSolution_WithoutSensor ecsel-dr-OOSMP:MotorControlAndDriveSolution_WithoutSensor rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:MotorControlAndDriveSolution ; rdfs:comment "Motor control and drive solution without a sensor" ; skos:prefLabel "Motor Control and Drive Solution Without Sensor" . ### http://www.w3id.org/ecsel-dr-OOSMP#MotorType ecsel-dr-OOSMP:MotorType rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-OOSMP:BrushedDC_MotorType ecsel-dr-OOSMP:Induction_MotorType ecsel-dr-OOSMP:PMSM_BLDC_MotorType ecsel-dr-OOSMP:PermanentMagnetStepper_MotorType ecsel-dr-OOSMP:SwitchedReluctance_MotorType ) ] ; 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\"." ; skos:prefLabel "Motor Type" . ### http://www.w3id.org/ecsel-dr-OOSMP#MountingStyle ecsel-dr-OOSMP:MountingStyle rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-OOSMP:SMDSMT_MountingStyle ecsel-dr-OOSMP:ThroughHole_MountingStyle ) ] ; rdfs:comment "Each sensor has a specific mounting style. A mounting style can either be a \"SMDSMT\" or \"Through Hole\"." ; skos:prefLabel "Mounting Style" . ### http://www.w3id.org/ecsel-dr-OOSMP#OPNStatus ecsel-dr-OOSMP:OPNStatus rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-OOSMP:ActiveAndPreferred_OPNStatus ecsel-dr-OOSMP:Active_OPNStatus ecsel-dr-OOSMP:Discontinued_OPNStatus ecsel-dr-OOSMP:NotForNewDesign_OPNStatus ) ] ; rdfs:subClassOf ecsel-dr-OOSMP:SemiconductorProductStatus ; 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\"." ; skos:prefLabel "OPN Status" . ### http://www.w3id.org/ecsel-dr-OOSMP#PackingType ecsel-dr-OOSMP:PackingType rdf:type owl:Class ; 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\"." ; skos:prefLabel "Packing Type" . ### http://www.w3id.org/ecsel-dr-OOSMP#PhysicalProduct ecsel-dr-OOSMP:PhysicalProduct rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP: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." ; skos:prefLabel "Physical Product" . ### http://www.w3id.org/ecsel-dr-OOSMP#PressureSensor ecsel-dr-OOSMP:PressureSensor rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:Sensor ; rdfs:comment "A pressure sensor is a sensor which measures pressure." ; skos:prefLabel "Pressure Sensor" . ### http://www.w3id.org/ecsel-dr-OOSMP#PriceIndication ecsel-dr-OOSMP:PriceIndication rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-OOSMP:HighPrice_PriceIndication ecsel-dr-OOSMP:LowPrice_PriceIndication ecsel-dr-OOSMP:MediumPrice_PriceIndication ) ] ; rdfs:comment "A price indication helps the customer to evaluate the price of an item. A price indication can be \"high\", \"low\", or \"medium\"." ; skos:prefLabel "Price Indication" . ### http://www.w3id.org/ecsel-dr-OOSMP#Product ecsel-dr-OOSMP:Product rdf:type owl:Class ; owl:equivalentClass ecsel-dr-PROD: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)." , "A solution is a combination of products which is sold to a customer. Thereby, a solution solves a problem or fulfills a customer need." ; skos:prefLabel "Product" . ### http://www.w3id.org/ecsel-dr-OOSMP#ProductLine ecsel-dr-OOSMP:ProductLine rdf:type owl:Class ; owl:equivalentClass ; rdfs:subClassOf org:OrganizationalUnit ; rdfs:comment "A product line is an organizational unit that can be assigned to a business line and directly owns/is responsible for products." ; skos:altLabel "Product Line" ; ecsel-dr-OOSMP:abbreviation "PL" . ### http://www.w3id.org/ecsel-dr-OOSMP#Qualification ecsel-dr-OOSMP:Qualification rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-OOSMP:Automotive_Qualification ecsel-dr-OOSMP:Industrial_Qualification ) ] ; rdfs:comment "If a product/solution has a certain qualification, the product/solution fulfills the standards of this certain industry." ; skos:prefLabel "Qualification" . ### http://www.w3id.org/ecsel-dr-OOSMP#Radar ecsel-dr-OOSMP:Radar rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:Sensor ; 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." ; skos:prefLabel "Radar" . ### http://www.w3id.org/ecsel-dr-OOSMP#RoHSCompliantStatus ecsel-dr-OOSMP:RoHSCompliantStatus rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-OOSMP:NotRoHSCompliant_Status ecsel-dr-OOSMP:RoHSCompliant_Status ) ] ; rdfs:subClassOf ecsel-dr-OOSMP:SemiconductorProductStatus ; rdfs:comment "This status determines whether a product is RoHS compliant or not." ; skos:prefLabel "RoHS Compliant Status" . ### http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProduct ecsel-dr-OOSMP:SemiconductorProduct rdf:type owl:Class ; owl:equivalentClass ; rdfs:subClassOf ecsel-dr-OOSMP:PhysicalProduct ; rdfs:comment "A semiconductor product is a physical product that is produced and sold within the semiconductor industry." ; skos:prefLabel "Semiconductor Product" . ### http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorProductStatus ecsel-dr-OOSMP:SemiconductorProductStatus rdf:type owl:Class ; rdfs:comment "A semiconductor product can have different product states which describe the product characteristics more closely." ; skos:prefLabel "Semiconductor Product Status" . ### http://www.w3id.org/ecsel-dr-OOSMP#SemiconductorSolution ecsel-dr-OOSMP:SemiconductorSolution rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:Solution ; rdfs:comment "A semiconductor solution is combination of semiconductor products and is sold within the seminconductor industry." ; skos:prefLabel "Semiconductor Solution" . ### http://www.w3id.org/ecsel-dr-OOSMP#SensingType ecsel-dr-OOSMP:SensingType rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-OOSMP:WithSensor_SensingType ecsel-dr-OOSMP:WithoutSensor_SensingType ) ] ; rdfs:comment "The sensing type of a semiconductor solution determines whether a semiconductor solution contains a sensor (\"WithSensor\") or not (\"WithoutSensor)." ; skos:prefLabel "Sensing Type" . ### http://www.w3id.org/ecsel-dr-OOSMP#Sensor ecsel-dr-OOSMP:Sensor rdf:type owl:Class ; owl:equivalentClass , ecsel-dr-RAMI40:Sensor ; rdfs:subClassOf ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:comment "A semiconductor product which is used as sensor" ; skos:prefLabel "Sensor" . ### http://www.w3id.org/ecsel-dr-OOSMP#SensorMainApplication ecsel-dr-OOSMP:SensorMainApplication rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:ApplicationArea ; 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:isDefinedBy ecsel-dr-OOSMP:InfineonTechnologiesAG_Organization ; skos:prefLabel "Sensor Main Application" . ### http://www.w3id.org/ecsel-dr-OOSMP#SensorSubApplication ecsel-dr-OOSMP:SensorSubApplication rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:ApplicationArea ; 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:isDefinedBy ecsel-dr-OOSMP:InfineonTechnologiesAG_Organization ; skos:prefLabel "Sensor Sub Application" . ### http://www.w3id.org/ecsel-dr-OOSMP#SmartDriver ecsel-dr-OOSMP:SmartDriver rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:SemiconductorProduct ; rdfs:comment "A semiconductor product which is used as smart driver" ; skos:prefLabel "Smart Driver" . ### http://www.w3id.org/ecsel-dr-OOSMP#Solution ecsel-dr-OOSMP:Solution rdf:type owl:Class ; 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." ; skos:prefLabel "Solution" . ### http://www.w3id.org/ecsel-dr-OOSMP#SubApplication ecsel-dr-OOSMP:SubApplication rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:ApplicationArea ; rdfs:comment "An application area on lowest level (corresponing to application level 3) which can be assigned to super application levels (main application)" ; rdfs:isDefinedBy ecsel-dr-OOSMP:InfineonTechnologiesAG_Organization ; skos:prefLabel "Sub Application" . ### http://www.w3id.org/ecsel-dr-OOSMP#Topology ecsel-dr-OOSMP:Topology rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-OOSMP:HBridge_Topology ecsel-dr-OOSMP:HalfBridge_Topology ecsel-dr-OOSMP:HighSide_Topology ecsel-dr-OOSMP:LowSide_Topology ecsel-dr-OOSMP:Relay_Topology ecsel-dr-OOSMP:_3Phase_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\"." ; skos:prefLabel "Topology" . ### http://www.w3id.org/ecsel-dr-OOSMP#_3DMagneticSensor ecsel-dr-OOSMP:_3DMagneticSensor rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-OOSMP:MagneticPositionSensor ; 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.""" ; skos:prefLabel "3D Magnetic Sensor" . ### http://www.w3id.org/ecsel-dr-PMV#AND rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:comment """All incoming pathways required to proceed along the flow All outgoing pathways must be followed Used to divide/rejoin tasks/flows which happen in parallel with another, rather than in a strict sequence""" , "All outgoing process paths must be followed." , "The connector is responsible for splitting the control flow in at least two different branches, which are executed parallely where all branches must be followed." ; rdfs:isDefinedBy "https://www.epc-standard.org/collaborate/AND-Split" ; rdfs:label "AND" ; skos:altLabel "and" . ### http://www.w3id.org/ecsel-dr-PMV#ApplicationSystemType rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy "https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=156532992" ; rdfs:label "Application system type" ; skos:altLabel "applic system type" . ### http://www.w3id.org/ecsel-dr-PMV#BP rdf:type owl:Class ; rdfs:subClassOf [ owl:intersectionOf ( [ rdf:type owl:Class ; owl:unionOf ( [ rdf:type owl:Restriction ; owl:onProperty ; owl:minQualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass ] [ rdf:type owl:Restriction ; owl:onProperty ; owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass ] ) ] ) ; rdf:type owl:Class ] ; 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." ; rdfs:label "Business Process" ; skos:altLabel "BP" , "busi process" . ### http://www.w3id.org/ecsel-dr-PMV#BPActivity rdf:type owl:Class ; rdfs:subClassOf ; 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:label "Business Process Activity" ; skos:altLabel "BP Activity" , "busi process activ" . ### http://www.w3id.org/ecsel-dr-PMV#BPFlow rdf:type owl:Class ; 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.""" ; rdfs:label "Business Process Flow" ; skos:altLabel "Event-driven process chain" , "busi process flow" . ### http://www.w3id.org/ecsel-dr-PMV#BPLandscape rdf:type owl:Class ; rdfs:subClassOf [ owl:intersectionOf ( [ rdf:type owl:Class ; owl:unionOf ( [ rdf:type owl:Restriction ; owl:onProperty ; owl:minQualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass [ rdf:type owl:Class ; owl:unionOf ( ) ] ] [ rdf:type owl:Restriction ; owl:onProperty ; owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass ] ) ] ) ; rdf:type owl:Class ] ; rdfs:comment "A Business Process Landscape is a detailed overview of a specific Core- or Enabler Process." ; rdfs:label "Business Process Landscape" ; skos:altLabel "BP Landscape" , "busi process landscap" . ### http://www.w3id.org/ecsel-dr-PMV#ComputerHardware rdf:type owl:Class ; rdfs:subClassOf terms:PhysicalResource ; 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:isDefinedBy "http://www.businessdictionary.com/definition/hardware.html" ; rdfs:label "Computer Hardware" ; skos:altLabel "comput hardwar" . ### http://www.w3id.org/ecsel-dr-PMV#Connector rdf:type owl:Class ; owl:equivalentClass ; rdfs:subClassOf ; 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:isDefinedBy "https://www.epc-standard.org/collaborate/Operator" ; rdfs:label "Connector" ; skos:altLabel "Rule" , "connector" . ### http://www.w3id.org/ecsel-dr-PMV#EndEvent rdf:type owl:Class ; rdfs:subClassOf ; owl:disjointWith ; 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:label "End Event" . ### http://www.w3id.org/ecsel-dr-PMV#EnvironmentalData rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "Additional information to a process like work schedule, production plans, etc." ; rdfs:label "Environmental Data" ; skos:altLabel "environment data" . ### http://www.w3id.org/ecsel-dr-PMV#Event rdf:type owl:Class ; rdfs:subClassOf ; 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)." , "An event illustrates the fact that 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. " , "The event is a passive element since it represents a change of state but does not cause it. Furthermore it can characterize the conditions and the results of an activity, which in turn triggers the next function. An event with no incoming arc is called start event, while an event with no outgoing arc is called end event." ; rdfs:isDefinedBy "https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=156532993" , "https://www.epc-standard.org/collaborate/Event" ; rdfs:label "Event" ; skos:altLabel "Status" , "event" . ### http://www.w3id.org/ecsel-dr-PMV#Function rdf:type owl:Class ; owl:equivalentClass ; rdfs:subClassOf ; rdfs:comment "The function type represents several action elements as task, process interfaces or business process activities." , "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:isDefinedBy "https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=156532993" , "https://www.epc-standard.org/collaborate/Function" ; rdfs:label "Function" ; skos:altLabel "function" . ### http://www.w3id.org/ecsel-dr-PMV#FunctionObject rdf:type owl:Class ; rdfs:comment "In IndustryPrint 5, function objects are used to model the decomposition of a process." ; rdfs:label "Function Object" ; skos:altLabel "function object" . ### http://www.w3id.org/ecsel-dr-PMV#HumanOutput rdf:type owl:Class ; owl:equivalentClass ; rdfs:subClassOf foaf:Person ; 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:label "Human Output" ; skos:altLabel "Role" , "human output" . ### http://www.w3id.org/ecsel-dr-PMV#IFXProcessFramework rdf:type owl:Class ; rdfs:subClassOf [ owl:intersectionOf ( [ rdf:type owl:Restriction ; owl:onProperty ; owl:minQualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass ] ) ; rdf:type owl:Class ] ; rdfs:comment "IPF is the structured overview of all IFX Core and Enabler Processes. It contains 4 Core Processes and 6 Enabler Processes." ; rdfs:label "Infineon Process Framework" ; skos:altLabel "infineon process framework" . ### http://www.w3id.org/ecsel-dr-PMV#Input rdf:type owl:Class ; 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." ; rdfs:isDefinedBy "http://www.businessdictionary.com/definition/input.html" ; rdfs:label "Input" ; skos:altLabel "input" . ### http://www.w3id.org/ecsel-dr-PMV#JoinRule rdf:type owl:Class ; rdfs:subClassOf [ owl:intersectionOf ( [ rdf:type owl:Class ; owl:unionOf ( [ rdf:type owl:Restriction ; owl:onProperty ; owl:minQualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass ] [ rdf:type owl:Restriction ; owl:onProperty ; owl:minQualifiedCardinality "2"^^xsd:nonNegativeInteger ; owl:onClass ] ) ] [ rdf:type owl:Class ; owl:unionOf ( [ rdf:type owl:Restriction ; owl:onProperty ; owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass ] [ rdf:type owl:Restriction ; owl:onProperty ; owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass ] ) ] ) ; rdf:type owl:Class ] , [ owl:intersectionOf ( [ rdf:type owl:Restriction ; owl:onProperty ; owl:minQualifiedCardinality "2"^^xsd:nonNegativeInteger ; owl:onClass ] [ rdf:type owl:Restriction ; owl:onProperty ; owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass ] ) ; rdf:type owl:Class ] ; owl:disjointWith ; 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." ; rdfs:label "Join Rule" ; skos:altLabel "join rule" . ### http://www.w3id.org/ecsel-dr-PMV#MachineResource rdf:type owl:Class ; rdfs:subClassOf terms:PhysicalResource ; rdfs:comment "Semi or fully automated device that magnifies human physical and/or mental capabilities in performing one or more operations." ; rdfs:isDefinedBy "http://www.businessdictionary.com/definition/machine.html" ; rdfs:label "Machine Resource" ; skos:altLabel "machin resourc" . ### http://www.w3id.org/ecsel-dr-PMV#Material rdf:type owl:Class ; owl:equivalentClass ; rdfs:subClassOf terms:PhysicalResource , , ; 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:isDefinedBy "http://www.businessdictionary.com/definition/material.html" ; rdfs:label "Material" ; skos:altLabel "materi" . ### http://www.w3id.org/ecsel-dr-PMV#Model rdf:type owl:Class ; rdfs:comment "One striking commonality between EPC meta models is the Process. One process may contain an unlimited number of elements, but a process element is always linked to a specific process. If a process contains an interface, it is always linked to one specific process and represents a refinement of a normal function." , "To graphically depict functional and process decomposition, function objects are diagramed on models in IndustryPrint 5." ; rdfs:isDefinedBy "https://www.epc-standard.org/collaborate/Process" ; rdfs:label "Model" ; skos:altLabel "model" . ### http://www.w3id.org/ecsel-dr-PMV#ModelElement rdf:type owl:Class ; 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." , "Represents an object in the EPC model. Includes all elements used in the modelling procedure of an EPC diagram." , "Represents process flow elements except for modelling function objects." ; rdfs:isDefinedBy "https://www.epc-standard.org/collaborate/Process_element" ; rdfs:label "Model Element" , "ModelElement" ; skos:altLabel "model element" . ### http://www.w3id.org/ecsel-dr-PMV#ModellingFunctionObject rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "Function objects are used to model the decomposition of the process flow." ; rdfs:label "Modelling Function Object" ; skos:altLabel "model function object" . ### http://www.w3id.org/ecsel-dr-PMV#OR rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:comment "At least one of the possible process paths must be followed." , "It is responsible for splitting the control flow up in at least two different branches, due to an nonexclusive choice where one or several branches can be followed." , """One or more incoming pathways required to proceed along the flow One or more outgoing pathways must be followed Used only when neither XOR nor AND can be used to better illustrate flow Has the weakest logic and should be used as sparingly as absolutely possible""" ; rdfs:isDefinedBy "https://www.epc-standard.org/collaborate/OR-Split" ; rdfs:label "OR" ; skos:altLabel "or" . ### http://www.w3id.org/ecsel-dr-PMV#OtherServices rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "Collection of other services used as input to a production process or which are created during a production process." ; rdfs:label "Other Services" ; skos:altLabel "servic" . ### http://www.w3id.org/ecsel-dr-PMV#Output rdf:type owl:Class ; rdfs:comment "The amount of energy, work, goods, or services produced by a machine, factory, company, or an individual in a period." ; rdfs:isDefinedBy "http://www.businessdictionary.com/definition/output.html" ; rdfs:label "Output" ; skos:altLabel "output" . ### http://www.w3id.org/ecsel-dr-PMV#Process rdf:type owl:Class ; owl:equivalentClass ; rdfs:subClassOf ; rdfs:comment "A collection of subprocesses that meet a specific business objective. E.g. Perform Sourcing or Purchase Materials and Services" ; rdfs:label "Process" ; skos:altLabel "process" . ### http://www.w3id.org/ecsel-dr-PMV#ProcessDiagram rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "The first level of process decomposition that is comprised of subprocesses that depict a business objective." ; rdfs:label "Process Diagram" ; skos:altLabel "Process Diagram (L2)" , "process diagram" . ### http://www.w3id.org/ecsel-dr-PMV#ProcessGroup rdf:type owl:Class ; owl:equivalentClass ; rdfs:subClassOf ; 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:label "Process Group" ; skos:altLabel "process group" . ### http://www.w3id.org/ecsel-dr-PMV#ProcessGroupMap rdf:type owl:Class ; rdfs:subClassOf ; 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:label "Process Group Map" ; skos:altLabel "Process Group Map (L1)" , "process group map" . ### http://www.w3id.org/ecsel-dr-PMV#ProcessInterface rdf:type owl:Class ; rdfs:subClassOf , , ; 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" , """Process interfaces connect several process models on the same process hierarchical level by linking the EPCs according to their shared events (also known as \"horizontal navigation\"). They thus facilitate process structuring and navigation by keeping models concise and easy-to-read. Functionality: Jump function to next process (e.g. EPC, VAC), typically at the end of process branches. In the EPC flow there is an Event directly before.""" ; rdfs:isDefinedBy "https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=156532993" ; rdfs:label "Process Interface" ; skos:altLabel "Interface" , "process interfac" . ### http://www.w3id.org/ecsel-dr-PMV#ProcessType rdf:type owl:Class ; rdfs:subClassOf ; 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:label "Process Type" ; skos:altLabel "process type" . ### http://www.w3id.org/ecsel-dr-PMV#ProcessTypeMap rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "A set of process types and related process groups that define the enterprise for a particular industry/sector." ; rdfs:label "Process Type Map" ; skos:altLabel "Process Type Map (L0)" , "process type map" . ### http://www.w3id.org/ecsel-dr-PMV#Role rdf:type owl:Class ; owl:equivalentClass ; rdfs:subClassOf foaf:Person ; rdfs:comment "Business Role (Person) that performs task." , "Object to describe the role. Type of responsibility is defined by the linkage between function or activity and role. IFX options: carries out, contribute, must be informed." ; rdfs:label "Role" ; skos:altLabel "role" . ### http://www.w3id.org/ecsel-dr-PMV#Rule rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "Rules allow to model alternative, exclusive alternative and parallel process flows." ; rdfs:isDefinedBy "https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=156532993" ; rdfs:label "Rule" ; skos:altLabel "Connector" , "rule" . ### http://www.w3id.org/ecsel-dr-PMV#Screen rdf:type owl:Class ; 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." ; rdfs:label "Screen" ; skos:altLabel "Transaction" , "screen" . ### http://www.w3id.org/ecsel-dr-PMV#SplitRule rdf:type owl:Class ; rdfs:subClassOf [ owl:intersectionOf ( [ rdf:type owl:Class ; owl:unionOf ( [ rdf:type owl:Restriction ; owl:onProperty ; owl:minQualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass ] [ rdf:type owl:Restriction ; owl:onProperty ; owl:minQualifiedCardinality "2"^^xsd:nonNegativeInteger ; owl:onClass ] ) ] [ rdf:type owl:Class ; owl:unionOf ( [ rdf:type owl:Restriction ; owl:onProperty ; owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass ] [ rdf:type owl:Restriction ; owl:onProperty ; owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass ] ) ] ) ; rdf:type owl:Class ] , [ owl:intersectionOf ( [ rdf:type owl:Restriction ; owl:onProperty ; owl:minQualifiedCardinality "2"^^xsd:nonNegativeInteger ; owl:onClass ] [ rdf:type owl:Restriction ; owl:onProperty ; owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass ] ) ; rdf:type owl:Class ] ; rdfs:comment "Rule element that splits the control flow into several branches. Has one incoming path and several (at least two) outgoing paths." ; rdfs:label "Split Rule" ; skos:altLabel "split rule" . ### http://www.w3id.org/ecsel-dr-PMV#StartEvent rdf:type owl:Class ; rdfs:subClassOf ; 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:label "Start Event" . ### http://www.w3id.org/ecsel-dr-PMV#StructuralFunctionObject rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "Function objects are used to model the decomposition of the structure of a process." ; rdfs:label "Structural Function Object" ; skos:altLabel "structur function object" . ### http://www.w3id.org/ecsel-dr-PMV#Subprocess rdf:type owl:Class ; rdfs:subClassOf ; 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:label "Subprocess" ; skos:altLabel "subprocess" . ### http://www.w3id.org/ecsel-dr-PMV#SubprocessDiagram rdf:type owl:Class ; rdfs:subClassOf ; 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:label "Subprocess Diagram" ; skos:altLabel "Subprocess Diagram (L3)" , "subprocess diagram" . ### http://www.w3id.org/ecsel-dr-PMV#Task rdf:type owl:Class ; owl:equivalentClass ; rdfs:subClassOf , , ; rdfs:comment "A Task is an instruction of a work package to create the output." , "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:label "Task" ; skos:altLabel "Process step" , "task" . ### http://www.w3id.org/ecsel-dr-PMV#TechnicalTerm rdf:type owl:Class ; rdfs:subClassOf foaf:Document ; 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:label "Technical Term" ; skos:altLabel "technic term" . ### http://www.w3id.org/ecsel-dr-PMV#TechnicalTermInputElement rdf:type owl:Class ; rdfs:subClassOf [ owl:intersectionOf ( [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] ) ; rdf:type owl:Class ] ; rdfs:comment "Denotes the input element to a function in the process flow." ; rdfs:label "Technical Term Input Element" ; skos:altLabel "technic term input element" . ### http://www.w3id.org/ecsel-dr-PMV#TechnicalTermOutputElement rdf:type owl:Class ; rdfs:subClassOf [ owl:intersectionOf ( [ rdf:type owl:Restriction ; owl:onProperty ; owl:someValuesFrom ] ) ; rdf:type owl:Class ] ; rdfs:comment "Denotes the output element of a function in the process flow." ; rdfs:label "Technical Term Output Element" ; skos:altLabel "technic term output element" . ### http://www.w3id.org/ecsel-dr-PMV#VACD rdf:type owl:Class ; 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.""" ; rdfs:isDefinedBy "https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=156532992" ; rdfs:label "Value-added chain diagram" ; skos:altLabel "VACD" , "valu - ad chain diagram" . ### http://www.w3id.org/ecsel-dr-PMV#XOR rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Class ; owl:unionOf ( ) ] ; rdfs:comment "Exactly one of the possible process paths must be followed." , "It is responsible for splitting the control flow in at least two different branches, due to an exclusive choice where exactly one of the branches is followed." , """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:isDefinedBy "https://www.epc-standard.org/collaborate/XOR-Split" ; rdfs:label "XOR" ; skos:altLabel "Exclusive OR" , "xor" . ### http://www.w3id.org/ecsel-dr-PRIMA#Category rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ) ] . ### http://www.w3id.org/ecsel-dr-PRIMA#CentralFunction rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-PRIMA#Certification rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-PRIMA#Division rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-PRIMA#IFXPRIMAProject rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PRIMA#Project rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-PRIMA#ProjectManager rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PRIMA#ProjectOwner rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PRIMA#ProjectStatus rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ) ] . ### http://www.w3id.org/ecsel-dr-PRIMA#ProjectTeamMember rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PRIMA#Region rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-PRIMA#Role rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-PRIMA#SubProject rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-PRIMA#Task rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-PRIMA#Training rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-PRIMA#WorkPackage rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-PROD#CPNSpec ecsel-dr-PROD:CPNSpec rdf:type owl:Class ; rdfs:subClassOf owl:Thing . ### http://www.w3id.org/ecsel-dr-PROD#DREP ecsel-dr-PROD:DREP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-PROD:PlanningElement ; rdfs:comment "Die-Representative: supply element; where the package is not yet decided" . ### http://www.w3id.org/ecsel-dr-PROD#FPOS ecsel-dr-PROD:FPOS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-PROD:PlanningElement ; rdfs:comment "Fabrication Position: product & manufacturing route; where it is produced - coarse" . ### http://www.w3id.org/ecsel-dr-PROD#FinishedProduct ecsel-dr-PROD:FinishedProduct rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-PROD:Product ; owl:disjointWith ecsel-dr-PROD:SKU , ecsel-dr-PROD:SalesProduct ; rdfs:comment "end result of the manufacturing process" . ### http://www.w3id.org/ecsel-dr-PROD#NonShippableProduct ecsel-dr-PROD:NonShippableProduct rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-PROD:Product ; rdfs:comment "NonShippableProduct are those finishedProductNumbers that are not allowed to be shipped to a given customer" . ### http://www.w3id.org/ecsel-dr-PROD#NotReleasedProduct ecsel-dr-PROD:NotReleasedProduct rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-PROD:Product ; rdfs:comment "NotReleasedProduct are those finishedProductNumbers that are not allowed to be shipped to any customer" . ### http://www.w3id.org/ecsel-dr-PROD#Organization ecsel-dr-PROD:Organization rdf:type owl:Class ; rdfs:subClassOf owl:Thing ; rdfs:comment "An organization is en entity comprising multiple people. In SSC, this class mainly refers to businesses." ; rdfs:isDefinedBy "http://www.example.org/semanticSupplyChain/" . ### http://www.w3id.org/ecsel-dr-PROD#PPOS ecsel-dr-PROD:PPOS rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-PROD:PlanningElement ; rdfs:comment """Plan Position: capacity and demand planning element """ . ### http://www.w3id.org/ecsel-dr-PROD#PlanningElement ecsel-dr-PROD:PlanningElement rdf:type owl:Class ; rdfs:subClassOf owl:Thing ; owl:disjointWith ecsel-dr-PROD:Product . ### http://www.w3id.org/ecsel-dr-PROD#Product ecsel-dr-PROD:Product rdf:type owl:Class ; owl:equivalentClass ; rdfs:subClassOf owl:Thing ; rdfs:isDefinedBy . ### http://www.w3id.org/ecsel-dr-PROD#RfP ecsel-dr-PROD:RfP rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-PROD:PlanningElement ; rdfs:comment "Required for Plan: planning product being not capacity relevant" . ### http://www.w3id.org/ecsel-dr-PROD#SKU ecsel-dr-PROD:SKU rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-PROD:Product ; owl:disjointWith ecsel-dr-PROD:SalesProduct ; rdfs:comment "finished product by storage location; called DC BauNumber" . ### http://www.w3id.org/ecsel-dr-PROD#SalesProduct ecsel-dr-PROD:SalesProduct rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-PROD:Product ; rdfs:comment """sellable product; It can be identified by salesProductNumber """ . ### http://www.w3id.org/ecsel-dr-PWR#Abstract rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment """Any Entity that cannot be located in space-time. Example: mathematical entities: formal semantics elements, regions within dimensional spaces, etc.\"""" ; rdfs:isDefinedBy """World Wide Web Consortium SSN DUL https://www.w3.org/2005/Incubator/ssn/wiki/DUL_ssn#Abstract\"""" . ### http://www.w3id.org/ecsel-dr-PWR#ApplicationArea rdf:type owl:Class ; rdfs:comment "The different application ares that the product can be used." . ### http://www.w3id.org/ecsel-dr-PWR#Blocking_Capability rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Blocking Capability" . ### http://www.w3id.org/ecsel-dr-PWR#Blocking_Voltage rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Break Down/Blocking Voltage" . ### http://www.w3id.org/ecsel-dr-PWR#CommunicationServices rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Constant_Resistance rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#ConsumerDiscretionary rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#ConsumerStaples rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Control_Method rdf:type owl:Class ; rdfs:comment "It is the method used to turn on, turn off , increaseing, and decreasing output current/voltage." ; rdfs:isDefinedBy "Power Electronic book" ; rdfs:label "Control Method" . ### http://www.w3id.org/ecsel-dr-PWR#Depletion_Mode rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Depletion Mode" . ### http://www.w3id.org/ecsel-dr-PWR#Deployment rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy """World Wide Web Consortium SSN http://www.w3.org/2005/Incubator/ssn/ssnx/ssn#Deployment""" . ### http://www.w3id.org/ecsel-dr-PWR#Deployment-related_Process rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy """World Wide Web Consortium SSN http://www.w3.org/2005/Incubator/ssn/ssnx/ssn#DeploymentRelatedProcess""" ; rdfs:label "Deployment-related Process" . ### http://www.w3id.org/ecsel-dr-PWR#Device rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy """rdfs:isDefinedBy \"World Wide Web Consortium SSN http://www.w3.org/2005/Incubator/ssn/ssnx/ssn#Device\"""" . ### http://www.w3id.org/ecsel-dr-PWR#Device_Configuration rdf:type owl:Class ; rdfs:label "Device Configuration" . ### http://www.w3id.org/ecsel-dr-PWR#Device_Elements rdf:type owl:Class ; rdfs:label "Device Elements" . ### http://www.w3id.org/ecsel-dr-PWR#Documents rdf:type owl:Class ; owl:equivalentClass foaf:Document ; rdfs:subClassOf ; 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:isDefinedBy """Friend of a friend ontology http://xmlns.com/foaf/spec/#term_Document\"""" . ### http://www.w3id.org/ecsel-dr-PWR#Drain rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Drain-Source_Voltage rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Drain-Source Voltage" . ### http://www.w3id.org/ecsel-dr-PWR#DrainCurrent rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Drain Current" . ### http://www.w3id.org/ecsel-dr-PWR#Drain_Voltagea rdf:type owl:Class ; rdfs:subClassOf , ; rdfs:label "Gate-Source Voltage" . ### http://www.w3id.org/ecsel-dr-PWR#Electric_Vehicle_Charging rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Electric Vehicle Charging" . ### http://www.w3id.org/ecsel-dr-PWR#ElectronicComponents rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Energy rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Energy_Storage rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Energy Storage" . ### http://www.w3id.org/ecsel-dr-PWR#Enhancement rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Enhancement Mode" . ### http://www.w3id.org/ecsel-dr-PWR#Entity rdf:type owl:Class ; rdfs:comment "Anything: real, possible, or imaginary, which some modeller wants to talk about for some purpose." ; rdfs:isDefinedBy """World Wide Web Consortium SSN DUL https://www.w3.org/2005/Incubator/ssn/wiki/DUL_ssn#Entity""" . ### http://www.w3id.org/ecsel-dr-PWR#Financial rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Gate rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#GateDriver rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-PWR#GeometricDimension rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "\"Describes the Dimensions of any Physical Object (Length, Wisth, Height)\"" ; rdfs:isDefinedBy "DefinedBy \"IFX\"" ; rdfs:label "Geometric Dimension" . ### http://www.w3id.org/ecsel-dr-PWR#Healthcare rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Height rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Industrials rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#IndutrialSector rdf:type owl: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""" ; rdfs:isDefinedBy "http://umbel.org/umbel/rc/" . ### http://www.w3id.org/ecsel-dr-PWR#Infineon_Device rdf:type owl:Class ; owl:equivalentClass ; rdfs:subClassOf ; 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:label "Amplication (switching) Device" . ### http://www.w3id.org/ecsel-dr-PWR#InformationEntity rdf:type owl:Class ; rdfs:subClassOf ; rdfs:isDefinedBy """World Wide Web Consortium SSN DUL https://www.w3.org/2005/Incubator/ssn/wiki/DUL_ssn#InformationEntity\"""" ; rdfs:label "Information Entity" . ### http://www.w3id.org/ecsel-dr-PWR#InformationTechnology rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Information_Object rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy """\"World Wide Web Consortium SSN DUL https://www.w3.org/2005/Incubator/ssn/wiki/DUL_ssn#InformationObject\"""" ; rdfs:label "Information Object" . ### http://www.w3id.org/ecsel-dr-PWR#Interface rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "A common boundary or interconnection between systems, equipment, concepts, or human beings" ; owl:incompatibleWith "IFX" . ### http://www.w3id.org/ecsel-dr-PWR#Junction_Temperature rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Junction Temperature" . ### http://www.w3id.org/ecsel-dr-PWR#Leakage_Current rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Leakage Current" . ### http://www.w3id.org/ecsel-dr-PWR#Length rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Materials rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Maximum_Junction_Temperature rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Maximum Junction Temperature" . ### http://www.w3id.org/ecsel-dr-PWR#Microcontroller rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#N-Channel_Configuration rdf:type owl:Class ; rdfs:subClassOf ; owl:disjointWith ; rdfs:label "N-Channel Configuration" . ### http://www.w3id.org/ecsel-dr-PWR#Object rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "Any physical, social, or mental object, or a substance" ; rdfs:isDefinedBy """World Wide Web Consortium SSN DUL https://www.w3.org/2005/Incubator/ssn/wiki/DUL_ssn#Object\"""" . ### http://www.w3id.org/ecsel-dr-PWR#Off-State_Region rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Off-State Region" . ### http://www.w3id.org/ecsel-dr-PWR#On-State_Power_loss rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "On-State Power Loss" . ### http://www.w3id.org/ecsel-dr-PWR#On-State_Region rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "On-State Region" . ### http://www.w3id.org/ecsel-dr-PWR#On-State_Resistance rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "On-State Resistance" . ### http://www.w3id.org/ecsel-dr-PWR#On-State_Voltage rdf:type owl:Class ; owl:equivalentClass [ owl:intersectionOf ( [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] ) ; rdf:type owl:Class ] , [ owl:intersectionOf ( [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] ) ; rdf:type owl:Class ] ; rdfs:subClassOf ; rdfs:label "On-State Voltage" . ### http://www.w3id.org/ecsel-dr-PWR#Operating_Property rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Operating Property" . ### http://www.w3id.org/ecsel-dr-PWR#Operation_Mode rdf:type owl:Class ; rdfs:label "Operation Mode" . ### http://www.w3id.org/ecsel-dr-PWR#P-channel_Configuration rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "P-Channel Configuration" . ### http://www.w3id.org/ecsel-dr-PWR#Package rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy "IFX" . ### http://www.w3id.org/ecsel-dr-PWR#Physical_Object rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Physical Object" . ### http://www.w3id.org/ecsel-dr-PWR#Platform rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy """rdfs:isDefinedBy \"World Wide Web Consortium SSN http://www.w3.org/2005/Incubator/ssn/ssnx/ssn#Platform\"""" . ### http://www.w3id.org/ecsel-dr-PWR#PowerConverters rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Price rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Process rdf:type owl:Class ; owl:equivalentClass ; 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." ; rdfs:isDefinedBy """World Wide Web Consortium SSN http://www.w3.org/2005/Incubator/ssn/ssnx/ssn#Process""" ; rdfs:label "Process" . ### http://www.w3id.org/ecsel-dr-PWR#Process_Input rdf:type owl:Class ; rdfs:comment "Any information that is provided a Procedure for its use." ; rdfs:isDefinedBy """World Wide Web Consortium SSN http://www.w3.org/2005/Incubator/ssn/ssnx/ssn#ProcessInput""" ; rdfs:label "Process Input" . ### http://www.w3id.org/ecsel-dr-PWR#Process_Output rdf:type owl:Class ; rdfs:comment "Any information that is reported from a Procedure." ; rdfs:isDefinedBy """World Wide Web Consortium SSN http://www.w3.org/2005/Incubator/ssn/ssnx/ssn#ProcessOutput""" ; rdfs:label "Process Output" . ### http://www.w3id.org/ecsel-dr-PWR#Products rdf:type owl: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)""" ; rdfs:isDefinedBy """The Web Vocabulary for E-Commerce Good Relations http://www.heppnetz.de/ontologies/goodrelations/v1.html#ProductOrService""" . ### http://www.w3id.org/ecsel-dr-PWR#Property rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Quality rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy """World Wide Web Consortium SSN DUL https://www.w3.org/2005/Incubator/ssn/wiki/DUL_ssn#Quality""" . ### http://www.w3id.org/ecsel-dr-PWR#RealEstate rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Region_of_Operation rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Region of Operation" . ### http://www.w3id.org/ecsel-dr-PWR#Resistance rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-PWR#Saturation_Region rdf:type owl:Class ; rdfs:subClassOf ; owl:disjointWith ; rdfs:label "Saturation Region" . ### http://www.w3id.org/ecsel-dr-PWR#Semiconductors rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Sensors rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#SiC_MOSFET rdf:type owl:Class ; 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." ; rdfs:label "SiC MOSFET" . ### http://www.w3id.org/ecsel-dr-PWR#Situation rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy """World Wide Web Consortium SSN DUL https://www.w3.org/2005/Incubator/ssn/wiki/DUL_ssn#Situation""" . ### http://www.w3id.org/ecsel-dr-PWR#Social_Object rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy """World Wide Web COnsortium SSN http://www.w3.org/2005/Incubator/ssn/ssnx/ssn#Observation""" ; rdfs:label "Social Object" . ### http://www.w3id.org/ecsel-dr-PWR#Solar_Energy rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Solar Energy" . ### http://www.w3id.org/ecsel-dr-PWR#Source rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Switcher rdf:type owl:Class ; rdfs:label "Switcher" . ### http://www.w3id.org/ecsel-dr-PWR#SwitchingValue rdf:type owl:Class ; rdfs:subClassOf ; 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:label "SwitchingValue" . ### http://www.w3id.org/ecsel-dr-PWR#Switching_Frequency rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Switching Frequency" . ### http://www.w3id.org/ecsel-dr-PWR#System rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy """World Wide Web Consortium SSN http://www.w3.org/2005/Incubator/ssn/ssnx/ssn#System\"""" . ### http://www.w3id.org/ecsel-dr-PWR#TheDeviceOutput rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "the device output is a piece of information (value), the value itself being represented by an The device function value." ; rdfs:label "SiC MOSFET Output" . ### http://www.w3id.org/ecsel-dr-PWR#The_Application_Voltage rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "The Application Voltage" . ### http://www.w3id.org/ecsel-dr-PWR#The_method_of_the_device_function rdf:type owl:Class ; rdfs:subClassOf ; 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:label "Switching" . ### http://www.w3id.org/ecsel-dr-PWR#The_process_name_of_the_device_function rdf:type owl:Class ; rdfs:subClassOf ; 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:isDefinedBy """Only the defintion of the Sensor process: sensing (Sensing is a process that results in the estimation, or calculation, of the value of a phenomenon.) is defined by W3C SSN http://www.w3.org/2005/Incubator/ssn/ssnx/ssn#Sensing""" ; rdfs:label "The Process used in the Device Function" . ### http://www.w3id.org/ecsel-dr-PWR#Threshold_Voltage rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Threshold Voltage" . ### http://www.w3id.org/ecsel-dr-PWR#Utilities rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Variable_Resistance rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Variable Resistance" . ### http://www.w3id.org/ecsel-dr-PWR#Voltage rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-PWR#Voltage-Controlled rdf:type owl:Class ; rdfs:subClassOf ; rdfs:isDefinedBy "by applying the voltage between Gate and Sourcet o turn on, turn off the MOSFET, and increaseing, decreasing the MOSFET output current." , "rdfs:isDefinedBy" . ### http://www.w3id.org/ecsel-dr-PWR#Weight rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Width rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#ElectronicEquipment,Instruments&Components rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "ElectronicEquipment,Instruments&Components" . ### http://www.w3id.org/ecsel-dr-PWR#Negative_(-) rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Negative (-)" . ### http://www.w3id.org/ecsel-dr-PWR#Postive_(+) rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Positive (+)" . ### http://www.w3id.org/ecsel-dr-PWR#SemiconductorProduct(its_name)_DataSheet rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "SiC MOSFET DataSheet" . ### http://www.w3id.org/ecsel-dr-PWR#Semiconductors&SemiconductorEquipment rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Software&Services rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#TechnologyHardware&Equipment rdf:type owl:Class ; rdfs:subClassOf . ### http://www.w3id.org/ecsel-dr-PWR#Triode/Constant_Resistance_Region rdf:type owl:Class ; rdfs:subClassOf , [ rdf:type owl:Restriction ; owl:onProperty ; owl:allValuesFrom ] ; rdfs:label "Triode/Constant Resistance Region" . ### http://www.w3id.org/ecsel-dr-RAMI40#Admin_Shell ecsel-dr-RAMI40:Admin_Shell rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-RAMI40#Asset ecsel-dr-RAMI40:Asset rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-RAMI40#Date ecsel-dr-RAMI40:Date rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-RAMI40#Dimension ecsel-dr-RAMI40:Dimension rdf:type owl:Class ; rdfs:comment "Abstract class to describe the three different dimensions of RAMI4.0" ; rdfs:label "Dimension" . ### http://www.w3id.org/ecsel-dr-RAMI40#EnergyEfficiency ecsel-dr-RAMI40:EnergyEfficiency rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-RAMI40:Submodel . ### http://www.w3id.org/ecsel-dr-RAMI40#Expression_Semantic ecsel-dr-RAMI40:Expression_Semantic rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-RAMI40:Confirmation ecsel-dr-RAMI40:Measurement ecsel-dr-RAMI40:Requirement ) ] . ### http://www.w3id.org/ecsel-dr-RAMI40#I4.0Component ecsel-dr-RAMI40:I4.0Component rdf:type owl: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)""" ; rdfs:isDefinedBy "https://www.plattform-i40.de/I40/Navigation/EN/Service/Glossary/glossary.html" . ### http://www.w3id.org/ecsel-dr-RAMI40#MESConnection ecsel-dr-RAMI40:MESConnection rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-RAMI40:Submodel . ### http://www.w3id.org/ecsel-dr-RAMI40#Machine ecsel-dr-RAMI40:Machine rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-RAMI40:Asset ; skos:definition "A machine is ordered, designed, commissioned, operated, serviced, converted and recycled." ; skos:preLabel "Machine" . ### http://www.w3id.org/ecsel-dr-RAMI40#Measure ecsel-dr-RAMI40:Measure rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-RAMI40#RAMI_Hierarchy_Level_Dimension ecsel-dr-RAMI40:RAMI_Hierarchy_Level_Dimension rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-RAMI40:Connected_World ecsel-dr-RAMI40:Control_Device ecsel-dr-RAMI40:Enterprise ecsel-dr-RAMI40:Field_Device ecsel-dr-RAMI40:Product ecsel-dr-RAMI40:Station ecsel-dr-RAMI40:Work_Center ) ] ; rdfs:subClassOf ecsel-dr-RAMI40:Dimension ; rdfs:seeAlso ; skos:definition "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." ; skos:preLabel "RAMI Hierarchy Level Dimension" . ### http://www.w3id.org/ecsel-dr-RAMI40#RAMI_IT_Layer_Dimension ecsel-dr-RAMI40:RAMI_IT_Layer_Dimension rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-RAMI40:Asset ecsel-dr-RAMI40:Business ecsel-dr-RAMI40:Communication ecsel-dr-RAMI40:Functional ecsel-dr-RAMI40:Information ecsel-dr-RAMI40:Integration ) ] ; rdfs:subClassOf ecsel-dr-RAMI40:Dimension ; rdfs:label "RAMI IT Layer Dimension" . ### http://www.w3id.org/ecsel-dr-RAMI40#RAMI_Life_Cycle_Dimension ecsel-dr-RAMI40:RAMI_Life_Cycle_Dimension rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-RAMI40:Instance ecsel-dr-RAMI40:Type ) ] ; rdfs:subClassOf ecsel-dr-RAMI40:Dimension ; rdfs:label "RAMI Life Cycle Dimension" ; rdfs:seeAlso "http://www.zvei.org/en/subjects/Industry-40/Pages/The-Reference-Architectural-Model-RAMI-40-and-the-Industrie-40-Component.aspx" ; skos:definition "It describes the different Life Cycle and Value Stream layers for the RAMI model according to the IEC 62890 Standard." ; skos:preLabel "RAMI Layer" , "RAMI Life Cycle Dimension" . ### http://www.w3id.org/ecsel-dr-RAMI40#Sensor ecsel-dr-RAMI40:Sensor rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-RAMI40#SensorMeasurement ecsel-dr-RAMI40:SensorMeasurement rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-RAMI40:Submodel . ### http://www.w3id.org/ecsel-dr-RAMI40#Standard ecsel-dr-RAMI40:Standard rdf:type owl:Class ; rdfs:isDefinedBy ; skos:definition "Standards that are used to describe the actual I4.0 Asset. Defined in the STO ontology" ; skos:preLabel "Standard" . ### http://www.w3id.org/ecsel-dr-RAMI40#StandardVersion ecsel-dr-RAMI40:StandardVersion rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-RAMI40:Version . ### http://www.w3id.org/ecsel-dr-RAMI40#Standard_Organisation ecsel-dr-RAMI40:Standard_Organisation rdf:type owl: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#Structure ecsel-dr-RAMI40:Structure rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-RAMI40:Submodel . ### http://www.w3id.org/ecsel-dr-RAMI40#Submodel ecsel-dr-RAMI40:Submodel rdf:type owl:Class ; rdfs:comment "Describe the different types of Data related to the I4.0 Asset" . ### http://www.w3id.org/ecsel-dr-RAMI40#TransportInterface ecsel-dr-RAMI40:TransportInterface rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-RAMI40:Submodel . ### http://www.w3id.org/ecsel-dr-RAMI40#UsedDate ecsel-dr-RAMI40:UsedDate rdf:type owl:Class ; rdfs:subClassOf ecsel-dr-RAMI40:Date . ### http://www.w3id.org/ecsel-dr-RAMI40#Version ecsel-dr-RAMI40:Version rdf:type owl:Class . ### http://www.w3id.org/ecsel-dr-RAMI40#View ecsel-dr-RAMI40:View rdf:type owl:Class ; owl:equivalentClass [ rdf:type owl:Class ; owl:oneOf ( ecsel-dr-RAMI40:Business ecsel-dr-RAMI40:Construction ecsel-dr-RAMI40:Function ecsel-dr-RAMI40:Location ecsel-dr-RAMI40:Performance ) ] ; rdfs:comment "Different views associated to the Administration Shell via the Submodels" ; rdfs:isDefinedBy "https://www.plattform-i40.de/I40/Redaktion/DE/Downloads/Publikation/hm-2018-trilaterale-coop.html" . ### http://www.w3id.org/ecsel-dr-SCP#AATP rdf:type owl:Class ; rdfs:label "AATP"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#AP_FCST rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "AP_FCST"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#ATP rdf:type owl:Class ; rdfs:label "ATP"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#AggregatedCapacity rdf:type owl:Class ; rdfs:label "AggregatedCapacity"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#BottleneckResource rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "BottleneckResource"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#BufferStockOrders rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "BufferStockOrders"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#CLM rdf:type owl:Class ; rdfs:label "CLM"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#CapacityBottleneck rdf:type owl:Class ; rdfs:label "CapacityBottleneck"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#Confirmation rdf:type owl:Class ; rdfs:label "Confirmation"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#ConsignmentOrders rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "ConsignmentOrders"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#Customers rdf:type owl:Class ; rdfs:label "Customers"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#DB rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "DB"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#DC rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "DC"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#EDIForecast rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "EDIForecast"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#Forecast rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "Forecast"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#GeneralCustomers rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "GeneralCustomers"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#HP_Forecast rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "HP_Forecast"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#MarketingDemands rdf:type owl:Class ; rdfs:label "MarketingDemands"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#MaxStock rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "MaxStock"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#MinStock rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "MinStock"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#NP_Forecast rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "NP_Forecast"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#OP_Forecast rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "OP_Forecast"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#OpenOrderBook rdf:type owl:Class ; rdfs:label "OpenOrderBook"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#OperationalDemand rdf:type owl:Class ; rdfs:label "OperationalDemand"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#OrderLineItem rdf:type owl:Class ; rdfs:label "OrderLineItem"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#Orders rdf:type owl:Class ; rdfs:label "Orders"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#OrdersReschedule rdf:type owl:Class ; rdfs:label "OrdersReschedule"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#PrioritizedDemand rdf:type owl:Class ; rdfs:label "PrioritizedDemand"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#PrioritizedOrders rdf:type owl:Class ; rdfs:label "PrioritizedOrders"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#PrivateCustomers rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "PrivateCustomers"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#Promise rdf:type owl:Class ; rdfs:label "Promise"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#RampUpStock rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "RampUpStock"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#ResourceCapacity rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "ResourceCapacity"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#RetainedStock rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "RetainedStock"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#SSO_Stocks rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "SSO_Stocks"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#SafetyStock rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "SafetyStock"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#SalesDemands rdf:type owl:Class ; rdfs:label "SalesDemands"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#StandardOrders rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "StandardOrders"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#Stocks rdf:type owl:Class ; rdfs:label "Stocks"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#SupplyDemandMatch rdf:type owl:Class ; rdfs:label "SupplyDemandMatch"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#SupplyPicture rdf:type owl:Class ; rdfs:label "SupplyPicture"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#TargetAllocation rdf:type owl:Class ; rdfs:label "TargetAllocation"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#WIP rdf:type owl:Class ; rdfs:subClassOf ; rdfs:label "WIP"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#nEWs rdf:type owl:Class ; rdfs:label "nEWs"@iri-based . ### http://www.w3id.org/ecsel-dr-SCP#ordersScheduleLine rdf:type owl:Class ; rdfs:label "ordersScheduleLine"@iri-based . ### http://www.w3id.org/ecsel-dr-SO#Bottlenecks rdf:type owl: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#Capacity rdf:type owl: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#Chemical_Polishing rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Current_WIP rdf:type owl: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#Cycle_Time_Committment rdf:type owl: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#Delivery_Commitment rdf:type owl: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#Demand_Snapshot rdf:type owl:Class ; rdfs:comment "The “Demand” entity stores redundant demand at every product level. (snapshot entity)"@en . ### http://www.w3id.org/ecsel-dr-SO#Deposition rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Development rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "[Priority Class] these lots have the same maxium waiting time as standard lots, however they are put before the standard lots."@en . ### http://www.w3id.org/ecsel-dr-SO#Diffusion rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Dry_Etching rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#EPA rdf:type owl:Class ; rdfs:comment "The EPA is a product identifier referring to the associated process."@en . ### http://www.w3id.org/ecsel-dr-SO#Equipment rdf:type owl: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-SO#Equipment_Group rdf:type owl: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#Event_Calendar rdf:type owl: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#Fab rdf:type owl: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#Furnace rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "each furnace consists of two chambers with one tool in each chamber."@en . ### http://www.w3id.org/ecsel-dr-SO#Furnace_Process rdf:type owl: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#Hot rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Implantation rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Lithography rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Lot rdf:type owl: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#Lot_Event rdf:type owl: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#Lot_Size rdf:type owl: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#Mask rdf:type owl: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#Material_Transfer rdf:type owl: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#Operation rdf:type owl: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#Operator rdf:type owl: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#Owner rdf:type owl: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-SO#Planning_Work_Center rdf:type owl: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#Plant rdf:type owl: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#Priority_Classes rdf:type owl: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-SO#Process rdf:type owl: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#Process_Class rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Process_Flow rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Process_Group rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Process_Line rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Product rdf:type owl: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-SO#Product_Class rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Product_Group rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Product_Level rdf:type owl: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-SO#Product_Level_2 rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "The product levels 3 to 1 are aggregated levels that are based on information from product level 4. (hierarchal aggregation level)"@en . ### http://www.w3id.org/ecsel-dr-SO#Product_Level_3 rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Product_Line rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Product_Number rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "The product number is a unique identifier of a product. The scope is limited to finished products only."@en . ### http://www.w3id.org/ecsel-dr-SO#Production_Requests rdf:type owl:Class ; rdfs:comment "Production requests definte what the facilities need to produce when and in what quantity."@en . ### http://www.w3id.org/ecsel-dr-SO#Productive rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Purge rdf:type owl: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#Release_Plan rdf:type owl: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#Robot rdf:type owl: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#Rocket rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Route rdf:type owl: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#Shift rdf:type owl: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#Simulation_Part rdf:type owl: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-SO#Simulation_Route rdf:type owl: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-SO#Sputtering rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Supply_Chain rdf:type owl: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#Target_Costs rdf:type owl: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#Target_Revenue rdf:type owl: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#Target_Service_Level rdf:type owl: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#Technology rdf:type owl:Class ; rdfs:subClassOf ; 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#Tempering rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Time_Constraints rdf:type owl: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#Timecoupling rdf:type owl:Class ; rdfs:subClassOf ; 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 . ### http://www.w3id.org/ecsel-dr-SO#Tool rdf:type owl: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-SO#WIP_Station rdf:type owl: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-SO#Wet_Etching rdf:type owl:Class ; rdfs:subClassOf ; rdfs:comment "Wet Etching is the process of removing material-etching, through the use of chemical activity."@en . ### http://www.w3id.org/ecsel-dr-SO#Workshop rdf:type owl:Class ; rdfs:comment "The overall organizational working structures within the fabs is described in the entity “Workshop”. (master entity)"@en . ### http://xmlns.com/foaf/0.1/Agent foaf:Agent rdf:type owl:Class ; 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.\"""" ; rdfs:label "Agent" . ### http://xmlns.com/foaf/0.1/Document foaf:Document rdf:type owl:Class . ### http://xmlns.com/foaf/0.1/Person foaf:Person rdf:type owl:Class . ################################################################# # Individuals ################################################################# ### http://www.opengis.net/def/uom/ISO-8601/0/Gregorian rdf:type owl:NamedIndividual . ### http://www.w3.org/2006/time#unitMonth time:unitMonth rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OM#Accepted rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OM#AcceptedWithChange rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OM#Pull rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OM#Push rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OM#Reconfirm rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OM#Rejected rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#ActiveAndPreferred_OPNStatus ecsel-dr-OOSMP:ActiveAndPreferred_OPNStatus rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#Active_OPNStatus ecsel-dr-OOSMP:Active_OPNStatus rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#Allrounder_DesignTarget ecsel-dr-OOSMP:Allrounder_DesignTarget rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#Automotive_Qualification ecsel-dr-OOSMP:Automotive_Qualification rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#BrushedDC_MotorType ecsel-dr-OOSMP:BrushedDC_MotorType rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#CompletelyLeadFree_Status ecsel-dr-OOSMP:CompletelyLeadFree_Status rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#Discontinued_OPNStatus ecsel-dr-OOSMP:Discontinued_OPNStatus rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#Discrete_SolutionIntegrationLevel ecsel-dr-OOSMP:Discrete_SolutionIntegrationLevel rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#EasyToDesign_DesignTarget ecsel-dr-OOSMP:EasyToDesign_DesignTarget rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#FlexibleToDesign_DesignTarget ecsel-dr-OOSMP:FlexibleToDesign_DesignTarget rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#FullyIntegrated_SolutionIntegrationLevel ecsel-dr-OOSMP:FullyIntegrated_SolutionIntegrationLevel rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#HBridge_Topology ecsel-dr-OOSMP:HBridge_Topology rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#HalfBridge_Topology ecsel-dr-OOSMP:HalfBridge_Topology rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#HalogenFree_Status ecsel-dr-OOSMP:HalogenFree_Status rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#HighPrice_PriceIndication ecsel-dr-OOSMP:HighPrice_PriceIndication rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#HighSide_Topology ecsel-dr-OOSMP:HighSide_Topology rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#IGBT_MainPowerDeviceType ecsel-dr-OOSMP:IGBT_MainPowerDeviceType rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#Induction_MotorType ecsel-dr-OOSMP:Induction_MotorType rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#Industrial_Qualification ecsel-dr-OOSMP:Industrial_Qualification rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#IntegratedControllerDriver_SolutionIntegrationLevel ecsel-dr-OOSMP:IntegratedControllerDriver_SolutionIntegrationLevel rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#IntegratedDriverPowerStage_SolutionIntegrationLevel ecsel-dr-OOSMP:IntegratedDriverPowerStage_SolutionIntegrationLevel rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#IntegratedPowerStage_SolutionIntegrationLevel ecsel-dr-OOSMP:IntegratedPowerStage_SolutionIntegrationLevel rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#LowPrice_PriceIndication ecsel-dr-OOSMP:LowPrice_PriceIndication rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#LowSide_Topology ecsel-dr-OOSMP:LowSide_Topology rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#MOSFET_MainPowerDeviceType ecsel-dr-OOSMP:MOSFET_MainPowerDeviceType rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#MediumPrice_PriceIndication ecsel-dr-OOSMP:MediumPrice_PriceIndication rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#NotCompletelyLeadFree_Status ecsel-dr-OOSMP:NotCompletelyLeadFree_Status rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#NotForNewDesign_OPNStatus ecsel-dr-OOSMP:NotForNewDesign_OPNStatus rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#NotHalogenFree_Status ecsel-dr-OOSMP:NotHalogenFree_Status rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#NotRoHSCompliant_Status ecsel-dr-OOSMP:NotRoHSCompliant_Status rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#PMSM_BLDC_MotorType ecsel-dr-OOSMP:PMSM_BLDC_MotorType rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#PermanentMagnetStepper_MotorType ecsel-dr-OOSMP:PermanentMagnetStepper_MotorType rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#Relay_MainPowerDeviceType ecsel-dr-OOSMP:Relay_MainPowerDeviceType rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#Relay_Topology ecsel-dr-OOSMP:Relay_Topology rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#RoHSCompliant_Status ecsel-dr-OOSMP:RoHSCompliant_Status rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#SMDSMT_MountingStyle ecsel-dr-OOSMP:SMDSMT_MountingStyle rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#SwitchedReluctance_MotorType ecsel-dr-OOSMP:SwitchedReluctance_MotorType rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#ThroughHole_MountingStyle ecsel-dr-OOSMP:ThroughHole_MountingStyle rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#WithSensor_SensingType ecsel-dr-OOSMP:WithSensor_SensingType rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#WithoutSensor_SensingType ecsel-dr-OOSMP:WithoutSensor_SensingType rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-OOSMP#_3Phase_Topology ecsel-dr-OOSMP:_3Phase_Topology rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-PRIMA#Autobahn rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-PRIMA#Expedition rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-PRIMA#Idea rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-PRIMA#Implemented rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-PRIMA#InPreperation rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-PRIMA#Mission rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-PRIMA#OnHold rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-PRIMA#Running rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-PRIMA#Withdrawn rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Asset ecsel-dr-RAMI40:Asset rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Business ecsel-dr-RAMI40:Business rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Communication ecsel-dr-RAMI40:Communication rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Confirmation ecsel-dr-RAMI40:Confirmation rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Connected_World ecsel-dr-RAMI40:Connected_World rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Construction ecsel-dr-RAMI40:Construction rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Control_Device ecsel-dr-RAMI40:Control_Device rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Enterprise ecsel-dr-RAMI40:Enterprise rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Field_Device ecsel-dr-RAMI40:Field_Device rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Function ecsel-dr-RAMI40:Function rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Functional ecsel-dr-RAMI40:Functional rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Information ecsel-dr-RAMI40:Information rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Instance ecsel-dr-RAMI40:Instance rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Integration ecsel-dr-RAMI40:Integration rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Location ecsel-dr-RAMI40:Location rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Measurement ecsel-dr-RAMI40:Measurement rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Performance ecsel-dr-RAMI40:Performance rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Product ecsel-dr-RAMI40:Product rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Requirement ecsel-dr-RAMI40:Requirement rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Station ecsel-dr-RAMI40:Station rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Type ecsel-dr-RAMI40:Type rdf:type owl:NamedIndividual . ### http://www.w3id.org/ecsel-dr-RAMI40#Work_Center ecsel-dr-RAMI40:Work_Center rdf:type owl:NamedIndividual . [ rdf:type foaf:Agent ; foaf:name "W3C/OGC Spatial Data on the Web Working Group"@en ] . [ rdf:type foaf:Agent ; foaf:name "W3C/OGC Spatial Data on the Web Working Group"@en ] . [ rdf:type foaf:Agent ; foaf:name "W3C/OGC Spatial Data on the Web Working Group"@en ] . [ rdf:type foaf:Agent ; foaf:name "W3C/OGC Spatial Data on the Web Working Group"@en ] . [ rdf:type foaf:Agent ; foaf:name "W3C/OGC Spatial Data on the Web Working Group"@en ] . [ rdf:type foaf:Agent ; foaf:name "W3C/OGC Spatial Data on the Web Working Group"@en ] . [ rdf:type foaf:Agent ; foaf:name "W3C/OGC Spatial Data on the Web Working Group"@en ] . [ rdf:type foaf:Agent ; foaf:name "W3C/OGC Spatial Data on the Web Working Group"@en ] . [ rdf:type foaf:Agent ; foaf:name "W3C/OGC Spatial Data on the Web Working Group"@en ] . [ rdf:type foaf:Agent ; foaf:name "W3C/OGC Spatial Data on the Web Working Group"@en ] . [ rdf:type foaf:Agent ; foaf:name "W3C/OGC Spatial Data on the Web Working Group"@en ] . [ rdf:type foaf:Agent ; foaf:name "W3C/OGC Spatial Data on the Web Working Group"@en ] . [ rdf:type foaf:Agent ; foaf:name "W3C/OGC Spatial Data on the Web Working Group"@en ] . [ xsd:pattern "--(0[1-9]|1[0-9]|20)(Z|(\\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))?" ] . [ xsd:pattern "---(0[1-9]|[1-9][0-9])(Z|(\\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))?" ] . [ xsd:pattern "-?([1-9][0-9]{3,}|0[0-9]{3})(Z|(\\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))?" ] . ################################################################# # Annotations ################################################################# ecsel-dr-RAMI40:Asset skos:definition "Clearly identifiable asset for the Administration Shell" ; skos:altLabel "Object" ; skos:preLabel "Asset" ; skos:altLabel "Entity" ; skos:note "Objects may be known in the form of a type or of an instance. An object in the planning phase is known as a type" . ################################################################# # General axioms ################################################################# [ rdf:type owl:AllDisjointClasses ; owl:members ( ) ] . [ rdf:type owl:AllDisjointClasses ; owl:members ( ) ] . [ rdf:type owl:AllDisjointClasses ; owl:members ( ) ] . [ rdf:type owl:AllDisjointClasses ; owl:members ( ) ] . [ rdf:type owl:AllDisjointClasses ; owl:members ( ) ] . [ rdf:type owl:AllDisjointClasses ; owl:members ( ) ] . [ rdf:type owl:AllDisjointClasses ; owl:members ( ) ] . [ rdf:type owl:AllDisjointClasses ; owl:members ( ecsel-dr-PROD:DREP ecsel-dr-PROD:FPOS ecsel-dr-PROD:PPOS ecsel-dr-PROD:RfP ) ] . [ rdf:type owl:AllDisjointClasses ; owl:members ( ) ] . [ rdf:type owl:AllDisjointClasses ; owl:members ( ecsel-dr-RAMI40:RAMI_Hierarchy_Level_Dimension ecsel-dr-RAMI40:RAMI_IT_Layer_Dimension ecsel-dr-RAMI40:RAMI_Life_Cycle_Dimension ) ] . ################################################################# # Rules ################################################################# rdf:type swrl:Variable . rdf:type swrl:Variable . rdf:type swrl:Variable . [ rdf:type swrl:Imp ; swrl:body [ rdf:type swrl:AtomList ; rdf:first [ rdf:type swrl:ClassAtom ; swrl:classPredicate org:OrganizationalUnit ; swrl:argument1 ] ; rdf:rest [ rdf:type swrl:AtomList ; rdf:first [ rdf:type swrl:IndividualPropertyAtom ; swrl:propertyPredicate ecsel-dr-OOSMP:hasSubUnit ; swrl:argument1 ; swrl:argument2 ] ; rdf:rest [ rdf:type swrl:AtomList ; rdf:first [ rdf:type swrl:IndividualPropertyAtom ; swrl:propertyPredicate ecsel-dr-OOSMP:hasSubUnit ; swrl:argument1 ; swrl:argument2 ] ; rdf:rest rdf:nil ] ] ] ; swrl:head [ rdf:type swrl:AtomList ; rdf:first [ rdf:type swrl:IndividualPropertyAtom ; swrl:propertyPredicate ecsel-dr-OOSMP:hasSubUnit ; swrl:argument1 ; swrl:argument2 ] ; rdf:rest rdf:nil ] ] . [ rdf:type swrl:Imp ; swrl:body [ rdf:type swrl:AtomList ; rdf:first [ rdf:type swrl:ClassAtom ; swrl:classPredicate org:OrganizationalUnit ; swrl:argument1 ] ; rdf:rest [ rdf:type swrl:AtomList ; rdf:first [ rdf:type swrl:IndividualPropertyAtom ; swrl:propertyPredicate ecsel-dr-OOSMP:subUnitOf ; swrl:argument1 ; swrl:argument2 ] ; rdf:rest [ rdf:type swrl:AtomList ; rdf:first [ rdf:type swrl:IndividualPropertyAtom ; swrl:propertyPredicate ecsel-dr-OOSMP:subUnitOf ; swrl:argument1 ; swrl:argument2 ] ; rdf:rest rdf:nil ] ] ] ; swrl:head [ rdf:type swrl:AtomList ; rdf:first [ rdf:type swrl:IndividualPropertyAtom ; swrl:propertyPredicate ecsel-dr-OOSMP:subUnitOf ; swrl:argument1 ; swrl:argument2 ] ; rdf:rest rdf:nil ] ] . [ rdf:type swrl:Imp ; swrl:body [ rdf:type swrl:AtomList ; rdf:first [ rdf:type swrl:ClassAtom ; swrl:classPredicate ecsel-dr-OOSMP:ApplicationArea ; swrl:argument1 ] ; rdf:rest [ rdf:type swrl:AtomList ; rdf:first [ rdf:type swrl:IndividualPropertyAtom ; swrl:propertyPredicate ecsel-dr-OOSMP:hasSubApplicationArea ; swrl:argument1 ; swrl:argument2 ] ; rdf:rest [ rdf:type swrl:AtomList ; rdf:first [ rdf:type swrl:IndividualPropertyAtom ; swrl:propertyPredicate ecsel-dr-OOSMP:hasSubApplicationArea ; swrl:argument1 ; swrl:argument2 ] ; rdf:rest rdf:nil ] ] ] ; swrl:head [ rdf:type swrl:AtomList ; rdf:first [ rdf:type swrl:IndividualPropertyAtom ; swrl:propertyPredicate ecsel-dr-OOSMP:hasSubApplicationArea ; swrl:argument1 ; swrl:argument2 ] ; rdf:rest rdf:nil ] ] . [ rdf:type swrl:Imp ; swrl:body [ rdf:type swrl:AtomList ; rdf:first [ rdf:type swrl:ClassAtom ; swrl:classPredicate ecsel-dr-OOSMP:ApplicationArea ; swrl:argument1 ] ; rdf:rest [ rdf:type swrl:AtomList ; rdf:first [ rdf:type swrl:IndividualPropertyAtom ; swrl:propertyPredicate ecsel-dr-OOSMP:subApplicationAreaOf ; swrl:argument1 ; swrl:argument2 ] ; rdf:rest [ rdf:type swrl:AtomList ; rdf:first [ rdf:type swrl:IndividualPropertyAtom ; swrl:propertyPredicate ecsel-dr-OOSMP:subApplicationAreaOf ; swrl:argument1 ; swrl:argument2 ] ; rdf:rest rdf:nil ] ] ] ; swrl:head [ rdf:type swrl:AtomList ; rdf:first [ rdf:type swrl:IndividualPropertyAtom ; swrl:propertyPredicate ecsel-dr-OOSMP:subApplicationAreaOf ; swrl:argument1 ; swrl:argument2 ] ; rdf:rest rdf:nil ] ] . ### Generated by the OWL API (version 4.5.9.2019-02-01T07:24:44Z) https://github.com/owlcs/owlapi