Leo, I see the confusion. Two things are happening here.
As you said in a separate email to me ...
The
initial problem is that if you just download any of these
ontologies in github (by right clicking on the file and
selecting Save Link As), you get an html file with
“github” references everywhere.
If
you instead select the file in github just by left clicking
on it, and then select the Raw tab, you get the raw file in
your browser window, which you can then save as an
apparently true ttl/ofn/owl file. Then you can load it into
Protégé.
I am attaching the Turtle version (as a .txt file to get
through people's email filters, I hope that it works) to try
to avoid the agony of downloading from GitHub without forking.
Let me note also that there are NO classes, data or
object properties in this ontology. There are only annotation
properties that can be used on classes, data and object
properties. Since I need this all to be usable in reasoning
applications, I started with defining and documenting
annotation properties. I try to note this in a comment on the
ontology (but I should probably expand the comment). I am
also working on a metadata-properties ontology which defines
some of the annotation properties as data and object
properties. This will allow (for example) validating
dateTime values and referencing objects/individuals in
relations (as opposed to using literal values).
So, for example, I define an exactMatch annotation property
that is used to describe how a class or property semantically
aligns with another class, property, vocabulary, etc. Again,
this has to be done using an annotation property or I fall
into OWL Full. This is obviously totally inadequate to do
anything significant, but it is a start as a documentation
tool. (There is also a property called closeMatch - as in
SKOS - but what really does that mean? How close is "close"?
)
Separately, I am working on a more formal approach to mapping
but starting with documentation is where I am.
Hope this helps to clarify things,
