RE: A proposal for two additional properties for LOCN

Yes, but that pattern puts restrictions on outbound properties from ex:CRS.
I understood that the discussion related to whether the inbound property ex:crs should have a (global) range defined,
such that the target of a ex:crs would always be inferred to be a ex:CRS .

From: Ghislain Atemezing [mailto:auguste.atemezing@eurecom.fr]
Sent: Monday, 8 September 2014 7:29 PM
To: Cox, Simon (L&W, Highett)
Cc: janowicz@ucsb.edu; public-locadd@w3.org Mailing list
Subject: Re: A proposal for two additional properties for LOCN

Hi Simon,


What does it look like in OWL2? (preferably using Turtle)

Something like the following axioms below ?

[ ex:CRS a owl:Class;
            rdfs:label "CRS"@en ;
            rdfs:subClassOf [ a owl:Restriction;
                                    owl:someValuesFrom ex:Extent;
                                    owl:onProperty ex:domainOfValidity ];
            .


ex:domainOfValidity a owl:ObjectProperty ;
            rdfs:label "domain of validity"@en ;
            rdfs:range ex:Extent ;
            .

ex:Extent a owl:Class, rdfs:Class;
            rdfs:label "Extent"@en ;
            rdfs:comment "region or interval of time where the reference is valid"@en ;
            .
]

Ghislain