Dear vocabulary developers,
I hope this is the right place to address this..?
My ontology editor (Topbraid Composer) needs an incredible amount of time (> 20mins) to open the RDF files that were provided in the Core Location Vocabulary. This might be caused by the fact that these RDF files contain elements that are not RDF native syntax and that the file was not created with an ontology editor but with some generalistic XML model design tool? (This is my assumption).
I hope this will be fixed in the next release.
Otherwise fantastic work, I would very much like to use these vocabularies if this issue is addressed.
PS: I tested also with Protege 3.4.7, works fine, no problems here...
PS2: I have attached image of TBC screen when opening Locn RDF. It says it is importing, but I think it is converting things
PS3: after the eventual loading the Locn v1.00 in TBC (Standard edition) and saving it, the tool has created native RDF from it (this file is attached too, please remove the txt extension for use, this was added for allowing upload)