Welcome to the WoLERY
W3C has created a number of recommendations and other documents
related to OWL and RDF. These documents were created under the auspices of
specifically and narrowly chartered working groups.
Once a working group has reached the end of it's charter, it is
disbanded. Unfortunately, this means that if errors and ommisions
are discovered in a document after the working group has expired, even
if they are purely typographical, there is no way to correct the
recommendations without rechartering a new working group. Chartering
such a working group can be a difficult and time-consuming process.
At this time there are no W3C working groups whose charter covers
the ongoing maintenance of OWL and RDF related documents. This leaves
no ready mechanism in place for addressing important issues such the handling
of RDF 1.1 simple literals in OWL 2.
Until a working
group exists, the WHO-WG stands watch to guard the realms of OWLs.
Mission Statement
Aims
- Prepare corrected versions of relevant OWL and RDF
recommendations, incorporating listed errata, and correcting or
highlighting known ommisions and ambiguities.
- Collect or prepare documents for existing OWL extensions, such
as the
Manchester and FSS syntaxes for SWRL
- Produce documents that can readily be taken up by appropriately
chartered W3 working groups.
Principles
But if someone lays their hand on you, don't accept their pull request.
Initial Issues
There are several high priority issues affecting OWL 2, particularly
those related to the RDF 1.1 elimination of plain literals and their
replacement with simple literals.
OWL 2.0.1
- Merge in errata.
- Clarify which axioms allow duplicate terms to be removed (the
DisjointUnionOf problem)
- Known errors in OWL 2.0 AS/FSS spec, Primer.
- Note problem caused by removal of plain literals from
RDF.
- Add rdf:langString to OWL datatype map.
- Add OWL compatible XSD 1.1 types to the datatype map as suggested by Bijan Parsia.
- Describe how rdf:langString can be translated to OWL 2.0
compatible constructs.
- Clarify whether or not xsd:string may be removed when
serializing to non-rdf formats.
RDF 1.1.1
- Define rdf:langRange facet for rdf:langString?
- Add text to PlainLiteral spec noting that plain literal
concept is obsolete.
- Add text deprecating rdf:PlainLiteral?
- Correct extended matching examples in rdf:PlainLiteral.
SPARQL 1.1.1
- Update SPARQL Entailment Regimes document to RDF 1.1 .
Future Work
- Ontology of OWL2 reasoner features and extensions to
allow selection of reasoners at a finer level than OWL 2 Profile
(e.g. datatypes support; SWRL support; CWA support; axiom combos not
supported; aproximate reasoning; probalistic reasoning etc.)?
- Reviewing/Revising Integrity Constraint Verification specification for
possible advancement?
- Support for literals with higher arities (e.g. intervals;
numbers with units; strings with language tags).
Mathjax check
Checking to see if the site is fixed and functional
$$
Y = \lambda f.(\lambda x. f(x x))(\lambda x.f(x x))
$$
Identity management
The following lines should handle identity management:
\begin{align}
\forall x. x = x && \text{reflexivity}\\
\forall x,y,z. (x = y \wedge y = z \rightarrow x = z) && \text{transitivity}\\
\forall x,y.(x = y \rightarrow y = x) && \text{symmetry}\\
\forall x,y.(x = y \rightarrow \forall \Phi. (\Phi(x) \leftrightarrow \Phi(y))) && \text{indiscernibility of identicals}\\
\forall x,y.( \forall \Phi. (\Phi(x) \leftrightarrow \Phi(y)) \rightarrow x = y) && \text{identity of indiscernibles}
\end{align}
Emergency Unicorns
$$
(\text{=1}\thinspace\mathsf{hasPart}.\mathsf{Horn}) \sqcap \mathsf{Horse}
$$