ISSUE-78

OWL LitEL++

REJECTED: OWL-Lite as EL++

State:

CLOSED

Product:

Raised by:

Bijan Parsia

Opened on:

2007-11-28

Description:

(On behalf of Carsten Lutz.)

In my opinion, the fragment EL++ sticks out from the other ones for
an important reason: it is (truely tractable and) used for a lot of
practically very relevant ontologies. Examples:

- SNOMED, a commercial medical ontology underlying the standardization
  of medical terminology in the health systems of US, UK, etc.

- NCI, the national cancer institutes medical ontology

- Gene Ontology

In OWL 1.0, there was an "OWL Light" version of OWL. The idea was to
provide a lightweight version of OWL for which reasoning is simpler,
but then it was ill-designed (reasoning actually wasn't simpler), and
deprecated in OWL 1.1.

I would like to advocate having a new OWL Light, which is EL++. My
main reason for proposing this is that having an official name with
"OWL" in it is likely to increase the visibility of this fragment *a
lot*. This is good for two reasons:

1. We open up the OWL world for ontology developers that want to work
   with a tractable languages. There are quite some developers who
   insist on tractability (to name only one example, the SNOMED people).

2. Just by choosing the proper name, we can make stronger claims about
   the relationship between OWL and a number of important ontologies.
   For example, when we choose EL++ as OWL Light, we can then claim
   that SNOMED is written in OWL Light, which may again draw attention
   to OWL Light and OWL in general.

In summary, I feel that we have a real chance here to truely extend
the scope and visibility of OWL, simply by choosing a name. Note that
in contrast "being one of the 27 tractable fragments of OWL" sounds
much less convincing. Or in yet other words: the current "tractable
fragments" document does not standardize anything, it rather has an
informative character. To standardize something, you cannot list all
options, but you have to make a *decision*. This is what I advocate.

Note that I do not insist on the name "OWL Light". Other options
such as "OWL Poly" may be fine as well, but it should have OWL in
it, and there shouldn't be 5 other fragments that also have OWL
names (for otherwise the effect described above vanishes again).

Disclaimer: With EL++, I am advocating my own work here. I believe
that my arguments are objective, but still you should know this.

Related Actions Items:

• ACTION-87 on Alan Ruttenberg to Write draft OWL Lite resolution, checking that it will have same semantics in 1.1 - due 2008-02-20, closed

Related emails:

1. Proposal to close ISSUE-78: OWL-Lite as EL++ (from alanruttenberg@gmail.com on 2008-03-17)
2. Re: status of ISSUE-79 ? (from clu@tcs.inf.tu-dresden.de on 2008-03-17)
3. status of ISSUE-79 ? (from alanruttenberg@gmail.com on 2008-03-16)
4. Re: ISSUE-78 (OWL LitEL++): OWL-Lite as EL++ (from bcg@cs.man.ac.uk on 2007-11-28)
5. Re: ISSUE-79 (EL++): REPORTED: EL++ Variants (from bcg@cs.man.ac.uk on 2007-11-28)
6. Re: ISSUE-78 (OWL LitEL++): OWL-Lite as EL++ (from hendler@cs.rpi.edu on 2007-11-28)
7. ISSUE-79 (EL++): REPORTED: EL++ Variants (from sysbot+tracker@w3.org on 2007-11-28)
8. ISSUE-78 (OWL LitEL++): OWL-Lite as EL++ (from sysbot+tracker@w3.org on 2007-11-28)

Related notes:

Display change log