Hello Fred!
Yes, switching is certainly confusing. (I can buy the "time of
minting" as a way to partition a URI space, but other than that
ontology URI:s reasonably have to be static and persistent until
something different/backwards-incompatible comes along to replace that
vocabulary.)
> I guess it is why I like the new OWL 2 versioning system...
>> 2. Every use of rdfs:isDefinedBy (and the two rdfs:seeAlso) have
>> xsd:anyURI-datatyped literals as objects instead of actual URI:s.
>> Isn't that an error?
>>
> This is a good question. I am not sure if it is an error. I should have
> to read a couple of things, but it should means that this value is a
> URI, so the URI of a resource (in the sense of an object property).
As they're given, they are only typed literals -- i.e. a self-denoting
thing which doesn't work as a resource identifier as real URI:s to
(the ones enclosed in <...> in turtle). It's a subtle but important
difference.
> I think that everything will depends on how triple store & such system
> would interpret a xsd:anyURI datatype (as a resource URI or a literal of
> type xsd:anyURI?)
>
> But to make it un-ambiguous, I will simply remove these datatypes :)
Sounds good. :) That is, if you mean change them from literals to
URI:s? I.e., in turtle, from:
rdfs:isDefinedBy "
http://purl.org/ontology/bibo/"^^xsd:anyURI
to:
rdfs:isDefinedBy <
http://purl.org/ontology/bibo/>
>> 4. There are a lot of statements about terms from other vocabularies.
>> I suspect many are "imported" for reasoners and/or Protegé to
>> function? But at least rdf:value being an owl:ObjectProperty seems
>> wrong, doesn't it?
>>
> Yes and not. I stopped using the owl:import statement and was simply
> re-defining re-used terms within BIBO. The reason is that weird things
> were imported, and imported ontologies were badly described in some
> cases. For these reasons, I removed any import statement, and I
> re-defined terms needed within BIBO.
I see. I've had thoughts about how to solve such things myself. I
recently came upon this interesting approach to it:
<
http://sparqlpedia.org/rdfex/>
I figure one could just as well manually "cherry-pick" terms into a
custom resource and import that. I'm not sure about the soundness of
constructing "subset ontologies" and importing those though. Just some
thoughts. *If* it seems ok, perhaps Bibo would benefit from extracting
the external parts into just that, a "bibo-ext" vocabulary, and import
that instead of directly including the parts in the source of bibo? (I
think one should ask the semweb list or pendantic-web or similar..
Wasn't there some de-facto official "rdfs/owl vocabulary developer
list" set up somewhere?)
The strangeness in either case is that the imported stuff aren't
defined by the imported resource, so there would be no semantic
relation to it at all. And I don't really think owl:imports
semantically means an (imperative) "include", but more like "uses
definitions from". (The same thing really goes for the currently
inlined stuff; albeit they're part of the same "graph" resulting from
parsing the document..)
However, I think the weird things you've found in those ontologies
should be reported to their authors (and CC:ed to the
<
http://pedantic-web.org/> group, which is dedicated to all things
strange in public RDF), to ideally be able to relate bibo to them via
just owl:imports.
> So, I will fix this stuff, and will update soon!
Great; thanks! (I'd be happy to check out a draft or similar if you want to.)
Best regards,
Niklas