15 separate appearance ontology from cityrdf#16
Conversation
…-ontology and added missing classes from common.
| owl:onProperty appont:opList ], | ||
| [ a owl:Restriction ; | ||
| owl:onClass appont:DoubleBetween0and1 ; | ||
| owl:onProperty appont:opList ; |
There was a problem hiding this comment.
appont:opList is not actual now, please see the 2 latest commits. It is just appont:list.
There was a problem hiding this comment.
Originally it was:
core:DoubleBetween0and1List a owl:Class ;
rdfs:label "DoubleBetween0and1List"@en ;
rdfs:subClassOf [ a owl:Restriction ;
owl:allValuesFrom core:DoubleBetween0and1 ;
owl:onProperty <https://www.opengis.net/ont/citygml/common/list> ],
[ a owl:Restriction ;
owl:onClass core:DoubleBetween0and1 ;
owl:onProperty <https://www.opengis.net/ont/citygml/common/list> ;
owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ] ;
skos:definition "DoubleBetween0and1List is a basic type that represents a list of double values greater or equal than 0 and less or equal than 1. The type is used for color encoding, for example."@en .
common:list rdf:type owl:ObjectProperty; rdfs:label "list"@en .
Now this ObjectProperty is in the appearance ontology:
appont:opList rdf:type owl:ObjectProperty; rdfs:label "list"@en .
appont:DoubleBetween0and1List a owl:Class ;
rdfs:label "DoubleBetween0and1List"@en ;
rdfs:subClassOf [ a owl:Restriction ;
owl:allValuesFrom appont:DoubleBetween0and1 ;
owl:onProperty appont:opList ],
[ a owl:Restriction ;
owl:onClass appont:DoubleBetween0and1 ;
owl:onProperty appont:opList ;
owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ] ;
skos:definition "DoubleBetween0and1List is a basic type that represents a list of double values greater or equal than 0 and less or equal than 1. The type is used for color encoding, for example."@en .
| owl:onProperty appont:referencePoint ], | ||
| owl:onProperty appont:mimeType ], | ||
| [ a owl:Restriction ; | ||
| owl:allValuesFrom gmlowl:Point ; | ||
| owl:onProperty appont:referencePoint ], | ||
| owl:onProperty appont:mimeType ], |
There was a problem hiding this comment.
don't understand why referencePoint becomes mimeType. Look at the owl:allvaluesFrom - they use gmlowl:Point
There was a problem hiding this comment.
| rdfs:domain appont:TexCoordGen ; | ||
| rdfs:range appont:TransformationMatrix3x4 ; | ||
| skos:definition "Specifies the 3x4 transformation matrix that defines the transformation between world coordinates and texture coordinates."@en . | ||
| appont:opList rdf:type owl:ObjectProperty; rdfs:label "list"@en . |
There was a problem hiding this comment.
So you now have appont:list and appont:opList in one file and you try to differentiate them, correct?
There was a problem hiding this comment.
yes, this is correct. appont:list is owl:DatatypeProperty and appont:opList is owl:ObjectProperty
…eferencedTexture restrictions.
|
This topic is relevant to the OGC GeoSPARQL Standards Working Group in the context of the following issues: |
#15