<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 9/19/14 10:20 AM, Till Mossakowski
wrote:<br>
</div>
<blockquote cite="mid:541C3BB9.9010004@iws.cs.uni-magdeburg.de"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Dear Tara,<br>
<br>
Am 11.09.2014 17:14, schrieb Tara Athan:<br>
</div>
<blockquote cite="mid:5411BC39.1010203@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
* I am confused about the term "structured OMS". The glossary
definition of structured OMS is<br>
<br>
\termdefinition{structured OMS\synonym focused OMS}<br>
{\termref{OMS} that results from other \termref{OMS} by
\termref{import}, \termref{union}, \termref{combination},
\termref{renaming} or other structuring operations}<br>
\begin{note}<br>
The term ``focused OMS'' emphasizes the fact that the OMS,
while possibly<br>
involving many OMS as parts, has a single resulting
\termref{logical theory}.<br>
This is in contrast to \termref{distributed OMS}, which do not
have<br>
such a unique result, but rather comprise a network of OMS and<br>
\termref{mappings}. See \cite{MossakowskiTarlecki09}.<br>
\end{note}<br>
<br>
As I read this, a basic OMS cannot be structured OMS - it is
not the result of a structuring operation applied to another
OMS.<br>
<br>
Elsewhere, the phrase "sentence or structured OMS" is used,
suggesting that it is considered a structuring operation when
a number of sentences are joined together in a basic OMS, so
that a basic OMS would be a structured OMS.<br>
<br>
It seems more natural to me that structured and basic OMS
would be a disjoint partition of OMS. All OMS languages that I
know have an internal operation for jointly asserting
sentences as a logical theory, while the other kinds of
structuring operations are not universal.<br>
<br>
</div>
</blockquote>
OK, agreed.<br>
<br>
<blockquote cite="mid:5411BC39.1010203@gmail.com" type="cite">
<div class="moz-cite-prefix"> * If the term "distributed OMS" is
replaced by "OMS network", then the question arises as to what
OMS are not focused. <br>
</div>
</blockquote>
I would keep "distributed OMS" as a synonym for "OMS network".
<blockquote cite="mid:5411BC39.1010203@gmail.com" type="cite">
<div class="moz-cite-prefix"> <br>
The current definition of OMS is<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
{set of expressions (like \termref{non-logical symbols},
\termref{sentences} and \termref{structuring} elements) in a
given \termref{OMS language} (or several such languages)}% <br>
<br>
I think it would better to define OMS as a 'collection' of
expressions rather than a set. Saying something 'is a' set
does not leave room for additional structure.<br>
<br>
So here's my proposal<br>
<br>
\termdefinition{OMS}<br>
{collection of expressions (like \termref{non-logical
symbols}, \termref{sentences} and \termref{structuring}
elements) in a given \termref{OMS language} (or several such
languages).}<br>
<br>
\termdefinition{focused OMS}<br>
{\termref{OMS} that has a single resulting \termref{logical
theory}.}<br>
<br>
\termdefinition{structured OMS}<br>
{\termref{OMS} that results from other \termref{OMS} by
\termref{import}, \termref{union}, \termref{combination},
\termref{renaming} or other structuring operations}<br>
\begin{note}<br>
An OMS is either a basic or structured OMS.<br>
\end{note}<br>
</div>
</blockquote>
agreed, except that I prefer to say "A *focused* OMS is either a
basic or structured OMS."
<blockquote cite="mid:5411BC39.1010203@gmail.com" type="cite">
<div class="moz-cite-prefix"> Finally, I see that the present
approach is to consider queries as a subclass of OMSs. It is
unclear to me how the inclusion of a query into a structured
and focused OMS would affect the "single resulting logical
theory". <br>
<br>
Does it make sense to consider a query as an OMS, but not a
focused OMS, which could be a component of a structured OMS
(which would then also be not focused?<br>
</div>
</blockquote>
<br>
currently, queries are part of OMS networks (= distributed OMS).<br>
I cannot see why they should become part of structured OMS. How
would they then affect the model class of the structuted OMS?<br>
</blockquote>
This comes back to what is the defining concept for the term
"structured OMS". The name suggests it is simply an OMS with
structure (whatever that means). There is, I imagine, some
category-theoretical way to distinguish a structure from a network.<br>
<br>
Given that we are now allowing OMS which are simply queries, then it
seems reasonable to me that there could also be queries with
structure, or hybrid assertion-query OMS with structure.<br>
<br>
Here are some use cases, where the relationship between the
components seem to me to be tighter than what I would expect in an
'OMS network':<br>
1. It is not uncommon to have a set of queries.<br>
For example if a query language does not support disjunction, then
this may be emulated by applying two queries and taking the 'union'
of the results.<br>
<br>
2. In certain query languages, query results can depend on the order
of application, so a sequence of queries is a relevant construct.<br>
<br>
3. Translation between query languages is a reasonable operation to
support.<br>
<br>
4. I can certainly imagine forming a combination query using
multiple query languages, dependent on a translation between the
query languages.<br>
<br>
5. Query rewriting is a technique developed in the database world
that may be relevant for querying structured OMS, and, somewhat out
of scope for OntoIOp, is important for supporting OBDA.<br>
<br>
6. There are a number of languages, especially in the LP realm, that
allow assertions (and other performatives that modify the theory,
such as retractions) to be interlaced with queries. <br>
<br>
Tara<br>
<blockquote cite="mid:541C3BB9.9010004@iws.cs.uni-magdeburg.de"
type="cite"> <br>
Best, Till<br>
<br>
<blockquote cite="mid:5411BC39.1010203@gmail.com" type="cite">
<div class="moz-cite-prefix"> Tara<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_________________________________________________________________
To Post: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="mailto:ontoiop-forum@ovgu.de">mailto:ontoiop-forum@ovgu.de</a>
Message Archives: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://listserv.ovgu.de//pipermail/ontoiop-forum">https://listserv.ovgu.de//pipermail/ontoiop-forum</a>
Config/Unsubscribe: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://listserv.ovgu.de/mailman/listinfo/ontoiop-forum">https://listserv.ovgu.de/mailman/listinfo/ontoiop-forum</a>
Community Files (open): <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://interop.cim3.net/file/pub/OntoIOp/">http://interop.cim3.net/file/pub/OntoIOp/</a>
Community Wiki: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://ontoiop.org">http://ontoiop.org</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">
_________________________________________________________________
To Post: <a class="moz-txt-link-freetext" href="mailto:ontoiop-forum@ovgu.de">mailto:ontoiop-forum@ovgu.de</a>
Message Archives: <a class="moz-txt-link-freetext" href="https://listserv.ovgu.de//pipermail/ontoiop-forum">https://listserv.ovgu.de//pipermail/ontoiop-forum</a>
Config/Unsubscribe: <a class="moz-txt-link-freetext" href="https://listserv.ovgu.de/mailman/listinfo/ontoiop-forum">https://listserv.ovgu.de/mailman/listinfo/ontoiop-forum</a>
Community Files (open): <a class="moz-txt-link-freetext" href="http://interop.cim3.net/file/pub/OntoIOp/">http://interop.cim3.net/file/pub/OntoIOp/</a>
Community Wiki: <a class="moz-txt-link-freetext" href="http://ontoiop.org">http://ontoiop.org</a>
</pre>
</blockquote>
<br>
</body>
</html>