how to handle ambiguous prefixes

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

how to handle ambiguous prefixes

Varanka, Dalia
Hello
I want to create properties that use the same prefix, though different IRIs, from two different vocabularies/ontologies. The Open Geospatial Consortium (OGC) standard for GeoSPARQL applies geo: for SPARQL graph patterns.  That same geo: prefix is used by W3C for geographic coordinate properties.  When I add a new property in the Object Property hierarchy, the W3C IRI auto-completes.  I don't know how to add the OGC geo: prefix without deleting the W3C specification.  Would anyone have any ideas?
Dalia

--
Dalia Varanka
U.S. Geological Survey
1400 Independence Road
Rolla, MO 65401 USA

Tel. 573.308.3897
ORCID: 0000-0003-2857-9600 

_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
Reply | Threaded
Open this post in threaded view
|

Re: how to handle ambiguous prefixes

Matthew Horridge-2
Administrator
Hi Dalia,

Unfortunately, you cannot override this behaviour, which you should be able to do.  I’ve filed an issue here:


Cheers,

Matthew


On 29 Nov 2018, at 14:01, Varanka, Dalia <[hidden email]> wrote:

Hello
I want to create properties that use the same prefix, though different IRIs, from two different vocabularies/ontologies. The Open Geospatial Consortium (OGC) standard for GeoSPARQL applies geo: for SPARQL graph patterns.  That same geo: prefix is used by W3C for geographic coordinate properties.  When I add a new property in the Object Property hierarchy, the W3C IRI auto-completes.  I don't know how to add the OGC geo: prefix without deleting the W3C specification.  Would anyone have any ideas?
Dalia

--
Dalia Varanka
U.S. Geological Survey
1400 Independence Road
Rolla, MO 65401 USA

Tel. 573.308.3897
ORCID: 0000-0003-2857-9600 
_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user


_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user