Martin and Alex,
First, I'd like to say that the GoodRelations specification that Alex
cited is much better designed than most OWL ontologies I have seen:
Note that the UML diagram is just an approximation of the formal
account of GoodRelations.
Yes, I noticed that point. But I didn't understand why you used the
word 'approximation'. Is the UML version a subset? Or is it actually
inconsistent with the OWL version? If it's a subset, then I recommend
UML for the normative statement. (UML has been defined in Common
Logic. That makes it just as formal as OWL, but far more readable.)
A cleaned-up notation for OWL (i.e., one that dumps the XML brackets)
could be used for details not captured by the UML diagram. An even
better solution is to design a version of controlled English to specify
those details. The combination of UML + controlled English could be
compiled into the current version of OWL, if anybody wanted that.
But the fatal flaw that has plagued the Semantic Web from the beginning
was the decision to make the XML serialization the normative version.
I realize that there are often good reasons for embedding isolated
RDF triples in a document and even better reasons for RDFa tags.
But I would love to see examples where anybody found it useful
to embed isolated OWL statements in any document.
As just a tiny example of the fatal flaw, look the following comment:
A single comment, embedded in a document by itself, might require that
amount of detail. But in every language designed for both computer
efficiency and human readability, such declarations are stated once
at the top and *never* repeated again.
The file for the GoodRelations ontology takes 1862 lines (126K bytes).
A good language could define the 37 classes in a tenth of that size.
There is no excuse for the unreadable and inefficient bloat.
The reason that eClassOWl is so big is that it is the aim of properly
representing a standard of 30,000 classes and 5,000 properties in OWL DL.
Cyc has 600,000 concepts. I'm sure that a comprehensive ontology for
business and finance would require that many. Multiplying the eClassOWL
specification by 20 would produce terabytes of OWL.
While the constraints of OWL blow up the size of the specification a
little bit, the main reason for the size of the ontology is the size
of the underlying standard.
A factor of 10 is not "a little bit".
As for syntax, note that GoodRelations data can be expressed using a
variety of syntactical forms, including OData, JSON-LD, etc. see
Nobody designs multiple alternatives for a good notation. This
multiplicity is a sign that the current situation is untenable.
... given that GoodRelations is a *Web* ontology I currently
don't see the real benefit; at least it's not a priority.
developer would ever serialize in XML.
Bottom line: It's time for a serious rethinking of the SW strategy.
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx