<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Dear Tara,<br>
<br>
indeed, there is a recursive definition avoiding thsemantically
flattenablee circularity that you mention:<br>
An OMS is flattenable iff it is either a basic OMS or it is an
extension, union, translation, module extraction, approximation,
filtering, or import (= reference of named OMS) of flattenable
OMS. Otherwise, it is elusive. This means indeed that elusive is
just non-flattenable.<br>
This also means that you have to do an import analysis in order to
determine flattenability: all the imported OMS must be
flattenable, otherwise the given OMS cannot be flattenable. Put
differently: one single elusive component makes an OMS elusive.<br>
<br>
Besides this syntactic notion of flattenability, there is also a
semantic one:<br>
<br>
semantically flattenable <=> logically equivalent to
a basic OMS<br>
<br>
The crucial property is:<br>
<br>
flattenable => semantically flattenable<br>
<br>
The converse is not true: also some (but not all) elusive OMS are
semantically flattenable.<br>
<br>
Best, Till<br>
<br>
P.S.<br>
In the DOL document, I have added:<br>
<br>
\termdefinition{flattenable OMS}<br>
{OMS that can be seen, by purely syntactical means, to be
logically <br>
equivalent to a basic OMS}<br>
\begin{note}<br>
More precisely, an OMS is flattenable if and only if it is either
a basic OMS or it is an \termref{extension}, \termref{union},
translation, \termref{module extraction}, \termref{approximation},
\termref{filtering}, or reference of named OMS involving only
flattenable OMS. <br>
\end{note}<br>
<br>
\termdefinition{elusive OMS}<br>
{OMS that is not \termref{flattenable}}<br>
<br>
<br>
Am 10.09.2014 19:00, schrieb Tara Athan:<br>
</div>
<blockquote cite="mid:541083AA.3070704@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">I am still not too clear on the
concept of "flattenable" defined as<br>
<br>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div class="page" title="Page 12">
<div class="section" style="background-color: rgb(100.000000%,
100.000000%, 100.000000%)">
<div class="layoutArea">
<div class="column">
<ol start="0" style="list-style-type: none">
<li>
<p><span style="font-size: 12.000000pt">flattenable
= can be flattened to a basic OMS</span></p>
</li>
</ol>
<span style="font-size: 12.000000pt">This doesn't help
much since "flattened" is not defined.<br>
</span>
<p>I see something of a recursive definition:<br>
a basic OMS is flattenable<br>
a focused OMS with all flattenable components is
flattenable<br>
</p>
<p>and some OMS, e.g. OMS reductions, are "elusive"
which I presume to mean non-flattenable?<br>
</p>
<p>Could someone please explain to me what makes an OMS
"flattenable"?<br>
</p>
<p>Thanks, Tara<br>
</p>
</div>
</div>
</div>
</div>
<title>The Distributed Ontology, Modeling and Specification
Language (DOL) Language overview</title>
<br>
<br>
On 9/10/14 11:04 AM, Till Mossakowski wrote:<br>
</div>
<blockquote cite="mid:5410688E.2060004@iws.cs.uni-magdeburg.de"
type="cite">
<pre wrap="">please find attached the slides for the meeting
Best, Till
Am 09.09.2014 23:10, schrieb Till Mossakowski:
</pre>
<blockquote type="cite">
<pre wrap="">[sorry, have sent this earlier but to the old address...]
Dear all,
our next OntoIOp team conference call (n.63) is coming up this
Wednesday, Sept-10.
The topics are (in this order):
- preperation of the OMG meeting starting on Sept. 15
- chapter 9 of the document (abstract syntax)
- chapter 10 of the document (concrete syntax)
The document is attached.
All the best,
Till
= OntoIOp team-confcall (n.63) - Wed 2014.09.10 =
<
* Date: Wed 10-Sept-2014
* start-time: 8:00am PDT / 11:00 pm EDT / 4:00pm BST / 5:00pm CEST /
5:00pm SAST / 0:00am [+1] KST / 15:00 UTC
** ref. world clock -
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=10&year=2014&hour=8&min=0&sec=0&p1=224">http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=10&year=2014&hour=8&min=0&sec=0&p1=224</a>
* Duration: 1~1.5 Hrs.
* shared-file workspace:
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://ontolog.cim3.net/file/work/OntoIOp/Team_confcall/2014-09-10_team-confcall_n.63/">http://ontolog.cim3.net/file/work/OntoIOp/Team_confcall/2014-09-10_team-confcall_n.63/</a>
* chat-workspace: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://webconf.soaphub.org/conf/room/ontoiop_20140910">http://webconf.soaphub.org/conf/room/ontoiop_20140910</a>
Remarks:
* the session may be recorded for archival purposes. Unless
otherwise documented, participants agrees to this by virtue of
their participation at the session.
* In case we have to mute everyone (due to extraneous noise or echo)
- Mute control: *7 to un-mute ... *6 to mute
Dial-in:
* Phone (US): +1 (206) 402-0100
... when prompted enter Conference ID: 843758#
* Skype: "join.conference"
... when prompted enter Conference ID: 843758#
** in case your skype connection to "joinconference" is not holding
up, try using (your favorite POTS or VoIP line, etc.) either your
phone, skype-out or google-voice and
call the US dial-in number: +1 (425) 440-5100
... when prompted enter Conference ID: 843758#
** some local numbers may be available (in the US, Australia, Canada &
UK) - see: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://instantteleseminar.com/Local/">http://instantteleseminar.com/Local/</a>
** for Windows Skype users: Can't find Skype Dial pad? ... it may be
under the "Call" dropdown menu as "Show Dial pad"
** for Linux Skype users: if the dialpad button is not shown in the
call window you need to press the "d" hotkey to enable it. (--CLange)
Talk to you all then!
</pre>
</blockquote>
<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>