Open mmaltsev opened 6 years ago
Could you point out explicitly from where you derived the properties isBasedOn
, isSectorSpecificFor
, usesSameDataModelAs
, and isPartOf
?
sto:IEC_61499 isBasedOn sto:IEC_61131 (second sentence from the top) sto:IEC_62264 isBasedOn sto:ISA-95 (second sentence from the top) sto:W3C_OWL isBasedOn sto:W3C_RDF (can't remember now, might be just general knowledge) sto:W3C_SPARQL isBasedOn sto:W3C_RDF (can't remember now, might be just general knowledge)
sto:IEC_61511 isSectorSpecificFor sto:IEC_61508 (sector - "process") (section Process industries
)
sto:IEC_62061 isSectorSpecificFor sto:IEC_61508 (sector - "manufacturing/machineries") (section Machinery
)
sto:IEC_61360 usesSameDatamodelAs sto:ISO_13584 (last sentence of the article)
sto:W3C_RIF isPartOf "the infrastructure for the semantic web" (second sentence of the rdfs:comment
object)
sto:W3C_OWL isPartOf "the infrastructure for the semantic web" (second sentence of the rdfs:comment
object)
Studying the property
sto:relatedTo
I found out that according to the resources where the relations themselve are described (wiki, dbpedia, official pages), relations can be of very different types. Below you can find the list of relation that were identified manualy:In the STO, the property
relatedTo
is described as symmetric and transitive one but if we'll look at the identified relations, i.e.isBasedOn
, we can see that this property is clearly not symmetric (sto:IEC_61499 isBasedOn sto:IEC_61131
is True butsto:IEC_61131 isBasedOn sto:IEC_61499
is False).I believe that a more specific interpretation of the property
sto:relatedTo
can help us in constructing the landscape.