ontology-summit
[Top] [All Lists]

[ontology-summit] Fwd: Ontologies are not algorithms

To: Ontology Summit 2012 <ontology-summit@xxxxxxxxxxxxxxxx>
From: Peter Yim <peter.yim@xxxxxxxx>
Date: Wed, 1 Feb 2012 16:41:55 -0800
Message-id: <CAGdcwD3quDpd_hSMAe28cfdchwdub5QethkXfAci+T6gygH89A@xxxxxxxxxxxxxx>
Dear Leo, Jack and All,    (01)

I agree with Nicola's
(ref. http://ontolog.cim3.net/forum/ontology-summit/2012-02/msg00007.html )    (02)

> [NG] ... In any way, this is not a topic to be addressed in this summit.
> So, if people are still interested, I would suggest them to move the 
>discussion
> to the general Ontolog list.    (03)

... and am moving this conversation to the [ontolog-forum] mailing list.    (04)

ALL: please pick up the conversation from there (if folks would still
want to delve in the subject matter).    (05)

Thanks in advance. =ppy    (06)

p.s. if you are not subscribed to the [ontolog-forum] list (i.e. not a
member of the Ontolog community,) please refer to membership details
at: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
--    (07)


---------- Forwarded message ----------
From: Obrst, Leo J. <lobrst@xxxxxxxxx>
Date: Wed, Feb 1, 2012 at 3:33 PM
Subject: Re: [ontology-summit] Ontologies are not algorithms
[was:   Ontolgizing rain & snow]
To: Ontology Summit 2012 discussion <ontology-summit@xxxxxxxxxxxxxxxx>    (08)


And by the way, rules do  the heavy-lifting in reasoning over
ontologies and their instances. But rules (axioms, inference rules,
consequence relations) are just as declarative as ontologies, i.e.,
ontologies expressed in a logic, thereby being a “logical theory”, use
the declarative apparatus of logic.    (09)



So the transformation I spoke of are transformations from one
declarative representation to another (mostly or entirely) declarative
representation. Otherwise, humans do all the programming imperatively,
looking only at the ontologies, conceptual models, conceptual schemas
as “guidance”. And from that process, there are many algorithms that
could be created, perhaps infinitely many, depending on the
space/complexity of the computation.    (010)



I hope this helps to clarify things.    (011)



Thanks,    (012)

Leo    (013)



From: Obrst, Leo J.
Sent: Wednesday, February 01, 2012 6:27 PM
To: Ontology Summit 2012 discussion
Subject: RE: [ontology-summit] Ontologies are not algorithms [was:
Ontolgizing rain & snow]    (014)



Jack,    (015)



Algorithms are ways to do things. How.    (016)

Ontologies, as a subclass of declarative methods, are ways to describe
things. What.    (017)



>From an ontology, one can spawn multiple algorithms that use the
ontology, but this requires a set of transformations from the
declarative to the imperative. And it will be multiple, because for
any statement of what to do there are many ways how to do it.    (018)



If you are working in a declarative paradigm, then the way to do it is
is to apply declarative transformations as far as you can, to get
close to a runtime how that preserves the what as much as possible.    (019)



E.g., from a first-order ontology, you use knowledge compilation
techniques (examples: reduce to Horn Logic approximations, use
implicants/implicatures, etc.; there are a range of tools available,
but this is another partial research thread). Or you simply use a
first-order reasoner that uses the ontology directly; however, FOL
reasoners will be slower than other reasoners, because they deal with
more expressive logical expressions.    (020)



Logic programming (Prolog, Answer Set Programming), by circumscribing
the FOL syntax, along with potentially using some non-declarative
constructs (the “cut” operator, ordering restrictions, a form of
negation that is not quite logical, i.e., negation by finite failure),
etc., can closely preserve the ontology and approximate its
declarative entailments, etc., in more efficient runtime reasoning.    (021)



But if you want to transform an ontology to an imperative algorithm:
good luck. Mostly these transformations are done by human programmers.
One can talk about semantics-preserving programs, etc., but it’s
pretty much ad hoc-land. One can annotate programs (like
“documentation”) as to what the imperative constructs are supposed to
mean, but it is really a very loose correlation.    (022)



That’s the difference.    (023)



Thanks,    (024)

Leo    (025)



From: ontology-summit-bounces@xxxxxxxxxxxxxxxx
[mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Jack
Ring
Sent: Wednesday, February 01, 2012 5:48 PM
To: Ontology Summit 2012 discussion
Subject: Re: [ontology-summit] Ontologies are not algorithms [was:
Ontolgizing rain & snow]    (026)



Dear Nicola,    (027)

Thanks for the response.    (028)



I am aware of several kinds of computational ontologies. I was
interested in a specific example of what you had in mind when
declaring that an ontology is not equivalent to an algorithm.    (029)



Ontologies that I have seen express semantic equivalences and other
relationships. Some are even loaded with first order predicates that
look very much like spaghetti code (which I thought was banned in the
1980's).    (030)



However, I am not interested in arguing the point. The simple fact is
that systems and systems engineering need semantic transformers. If
ontologies don't do semantic transforms (e.g. AP233) then there may be
some residual utility in ontologies in Big Systems but not the degree
I had hoped.    (031)



Jack Ring    (032)

ps. 'algorithm' predates computer science by several centuries.    (033)



On Feb 1, 2012, at 2:57 PM, Nicola Guarino wrote:    (034)



Dear Jack,    (035)



            sorry for this late answer to your request. There are
various definitions of (computational) ontologies adopted by the
community, it shouldn't be difficult for you to find them, as well as
actual examples of ontologies.    (036)



            Speaking for myself, I spent a good fraction of my
research career trying to clarify, in a rigorous way, what a
computational ontology is (see for instance the paper by Daniel Oberle
and myself on the Handbook of Ontologies, 2nd edition). Basically, I
agree with the most popular definition "An ontology is a specification
of a conceptualisation", which requires however a careful
clarification of what a conceptualisation is (but this is a long
story, although discussed in various papers). In logical terms, an
ontology is just a logical theory expressing a set of meaning
postulates.    (037)



            In my opinion, none of the current definitions of a
computational ontology is compatible with the idea that ontologies are
algorithms. If you want to use classing terms of computer science, you
can perhaps compare an ontology to a data structure, but not to an
algorithm.    (038)



            In any way, this is not a topic to be addressed in this
summit. So, if people are still interested, I would suggest them to
move the discussion to the general Ontolog list.    (039)



Best,    (040)



Nicola    (041)





On 31 Jan 2012, at 04:14, Jack Ring wrote:    (042)



Gee, I made a very explicit statement in my brief last week ---- that
ontology is algorithm --- and you and Nicola immediately and clearly
disagreed. I followed up with a request foer an example; of an
ontology so we could get down to specifics but have not yet received
one. Meanwhile an example of Cyc ontology appeared and I gave some
specifics from a systemist viewpoint.
If you think that emergence, a very important phenomenon in systems,
and system models is not a core issue for ontologists to deal with
then I guess the intersection of SE and ontology in this forum may
turn out to be only the transform from drawing (pump 102) to purchase
order (sku2058), i.e., engineering of systems.    (043)

On Jan 30, 2012, at 6:18 PM, Obrst, Leo J. wrote:    (044)

Jack, it's not that this is not interesting, and I get the metaphor,
but everyone needs to make the metaphor explicit. Otherwise, it seems
we are veering all over the place and not focusing on our themes for
THIS Summit. The next summit or a future summit can address
human-nature co-systems, and even this summit can, where it is
appropriate to our focus.    (045)



Make it explicit what the contribution is, focus. We simply don't have
the open-endedness of the whole Ontolog Forum, where nearly anything
and everything goes.    (046)



Thanks,    (047)

Leo    (048)



-----Original Message-----    (049)

From: ontology-summit-bounces@xxxxxxxxxxxxxxxx
[mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Jack
Ring    (050)

Sent: Monday, January 30, 2012 7:29 PM    (051)

To: Ontology Summit 2012 discussion    (052)

Subject: Re: [ontology-summit] Ontolgizing rain & snow [was: Track 1&2
Joint Mission and Session Abstracts]    (053)



Leo,    (054)

Apologies for the ambiguities. The subject is not rain and snow. Those
are the metaphors. The subject is emergence and the special confusions
of triple-point systems.    (055)



OBTW, perhaps ecologies are systems only in the minds of humans. if
you don't want to take up natural vs. human-imputed systems this year
so be it. However it is already a big confusion in the societal demand
for systems. For example sponsors do not know that more than 90% or
Mother Nature's experiments fail.    (056)



On Jan 30, 2012, at 5:20 PM, Obrst, Leo J. wrote:    (057)



Sure, human engineered systems also contain humans. That's what
systems engineering is all about. And teleological arguments do show
correspondences to human-engineered systems (function of the heart in
the human body). But remember we are addressing human-engineered
systems. Ecologies are systems and are wider than human-engineered
systems, but obviously also affect the latter.  Perhaps ecologies,
especially human-influenced ecologies are super-systems, and we should
address these here, but I think we are veering off.    (058)



I suggest just like we are not addressing natural ecologies, at least
not in this summit. Or at the least: not in this thread yet. We are
ontologizing rain and snow.    (059)



Thanks,    (060)

Leo    (061)



-----Original Message-----    (062)

From: ontology-summit-bounces@xxxxxxxxxxxxxxxx
[mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Jack
Ring    (063)

Sent: Monday, January 30, 2012 7:01 PM    (064)

To: Ontology Summit 2012 discussion    (065)

Subject: Re: [ontology-summit] Ontolgizing rain & snow [was: Track 1&2
Joint Mission and Session Abstracts]    (066)



I think you will have a difficult time explaining why natural systems
are not human-presumed systems. And closer to reality, yet, if human
engineered systems contain N humans as active components then what?    (067)



On Jan 30, 2012, at 4:55 PM, Obrst, Leo J. wrote:    (068)



Folks, this might be a discussion thread more appropriate for the more
general [ontolog-forum], since it doesn't really address human
engineered systems, but instead natural systems.    (069)



What do you think?    (070)



Thanks,    (071)

Leo    (072)



-----Original Message-----    (073)

From: ontology-summit-bounces@xxxxxxxxxxxxxxxx
[mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Jack
Ring    (074)

Sent: Monday, January 30, 2012 6:24 PM    (075)

To: Ontology Summit 2012 discussion    (076)

Subject: Re: [ontology-summit] Ontolgizing rain & snow [was: Track 1&2
Joint Mission and Session Abstracts]    (077)



Doug, Thank you for this. As is probably obvious by now or will be by
the end of this message I am not a practicing ontologist.    (078)

I am struck by several presumptions and gaps in the Cyc example.
Perhaps I just can't read right or perhaps these are not proper
ontology stuff. As I said in the last track, I am not sure I am
looking for ontology as the means for systemist interoperability.
Perhaps I seek some yet-to-be-conceived semiotic transformer. At any
rate, humor me regarding the following:    (079)

The example doesn't say where rain comes from. Mentions clouds but
clouds are not rain or they wouldn't be "up there."    (080)

I am looking for the notion of emergence. Rain happens after raindrops
occur. Why do raindrops occur? And why snowflakes rather than
raindrops? And why not mention fog as well? And Relative Humidity?    (081)



OBTW, rain water is not fresh. Raindrops condense on particles, every
raindrop has one therefor rainwater is laden with particles
(especially ones resulting from cloud seeding).    (082)

OBTW, Raindrops fall on me in Arizona while the sun is shining. No
storm evident. Just an occlusion of a low and high pressure trough
waaay up there.    (083)

I am not trying to be smart alecky here. It is just that systems work
challenges you to think beyond the active entities and consider the
not's as well. Otherwise Unintended Consequences are born.    (084)



I maliciously mentioned rain and snow because H2O has a triple point,
vapor, liquid, solid depending on pressure, temperature, etc., Not all
substances have such triple point. Methinks "SYSTEM" does which is the
root of much confusion therefore a challenge for ontologists.    (085)



Thanks for your attention.    (086)

Jack    (087)



On Jan 26, 2012, at 10:58 AM, doug foxvog wrote:    (088)



Matthew West wrote:    (089)



I understand your view. How shall you handle rain and snow?    (090)



Rain & snow refer to physical precipitation particles, the precipitation in    (091)

bulk, the process that produces the precipitation, storms as events, and    (092)

storms as objects.    (093)



Cyc's representation of these different, but related things (leaving out    (094)

comments and some additional statements) includes:    (095)



(isa PrecipitationParticle ExistingObjectType)    (096)

(genls PrecipitationParticle Particle)    (097)

(genls PrecipitationParticle InanimateObject-Natural)    (098)



(isa RainProcess ProcessType)    (099)

(genls RainProcess PrecipitationProcess)    (0100)



(isa SnowProcess ProcessType)    (0101)

(genls SnowProcess PrecipitationProcess)    (0102)



(isa Rainwater ExistingStuffType)    (0103)

(genls Rainwater (LiquidFn Water-Fresh))    (0104)



(isa SnowMob ExistingStuffType)    (0105)

(genls SnowMob (SolidFn Water))    (0106)



(isa Snowflake ExistingObjectType)    (0107)

(genls Snowflake PrecipitationParticle)    (0108)

(genls (MobFn Snowflake) SnowMob)    (0109)



(isa Raindrop ExistingObjectType)    (0110)

(genls Raindrop PrecipitationParticle)    (0111)

(genls Raindrop Rainwater)    (0112)



(relationAllExists outputsGenerated PrecipitationProcess    (0113)

                    (MobFn PrecipitationParticle))    (0114)

(relationAllExists outputsGenerated RainProcess (MobFn Raindrop))    (0115)

(relationAllExists outputsGenerated SnowProcess (MobFn Snowflake))    (0116)



(isa StormAsObject ExistingObjectType)    (0117)

(genls StormAsObject InanimateObject-Natural)    (0118)

(relationAllExists physicalParts StormAsObject CloudInSky)    (0119)



(isa RainStormAsObject ExistingObjectType)    (0120)

(genls RainStormAsObject StormAsObject)    (0121)

(relationAllExists physicalParts StormAsObject CloudInSky)    (0122)

(relationAllExists physicalParts StormAsObject (MobFn Raindrop))    (0123)



(isa SnowStormAsObject ExistingObjectType)    (0124)

(genls SnowStormAsObject StormAsObject)    (0125)

(relationAllExists physicalParts StormAsObject CloudInSky)    (0126)

(relationAllExists physicalParts SnowStormAsObject (MobFn Snowflake))    (0127)



(not (relationExistsAll doneBy PrecipitationProcess StormAsObject))    (0128)

(comment    (0129)

(not (relationExistsAll doneBy PrecipitationProcess StormAsObject))    (0130)

"A StormAsObject would include Duststorms, which don't (necessarily)    (0131)

include precipitation.")    (0132)



(relationExistsAll doneBy RainProcess RainStormAsObject)    (0133)

(relationExistsAll doneBy SnowProcess SnowStormAsObject)    (0134)



(isa StormAsEvent ExistingObjectType)    (0135)

(genls StormAsEvent ImmediateWeatherProcess)    (0136)



(isa RainStormAsEvent ExistingObjectType)    (0137)

(genls RainStormAsEvent StormAsEvent)    (0138)

(relationAllExists subprocesses RainStormAsEvent RainProcess)    (0139)

(relationAllExists doneBy RainStormAsEvent RainStormAsObject)    (0140)



(isa SnowStormAsEvent ExistingObjectType)    (0141)

(genls SnowStormAsEvent StormAsEvent)    (0142)

(relationAllExists subprocesses SnowStormAsEvent SnowProcess)    (0143)

(relationAllExists doneBy SnowStormAsEvent SnowStormAsObject)    (0144)



(isa SnowStormAsObject ExistingObjectType)    (0145)

(genls SnowStormAsObject StormAsObject)    (0146)

(relationAllExists physicalParts SnowStormAsObject (MobFn Snowflake))    (0147)





Jack    (0148)

On Jan 26, 2012, at 6:09 AM, Matthew West wrote:    (0149)



The main problem here is one of different people using terms    (0150)

differently. Hardly an ontological problem per se, but certainly a    (0151)

problem that causes confusion in developing ontologies.    (0152)



This is always a problem for ontologists.  The different meanings have    (0153)

to be teased apart.    (0154)



Interestingly as a 4 dimensionalist I don't recognise endurants at all,    (0155)

but I do recognise activities, physical objects, and participants. Under    (0156)

this world view all individuals (including activities, physical objects    (0157)

and participants) are spatiotemporal extents, and you discover that an    (0158)

activity consists of its participants, where a participant is the state    (0159)

of a physical object that participates in some activity. So I recognise    (0160)

the things you talk about. However, I would assign the term "system" to    (0161)

the physical object the participant is a state of.    (0162)



I would not restrict the term "system" merely to physical objects.  But    (0163)

having multiple clearly defined concepts which different people use that word    (0164)

for in different contexts, is fine.  They just need different URIs.    (0165)



-- doug    (0166)



Regards    (0167)



Matthew West    (0168)

Information  Junction    (0169)

Tel: +44 1489 880185    (0170)

Mobile: +44 750 3385279    (0171)

Skype: dr.matthew.west    (0172)

matthew.west@xxxxxxxxxxxxxxxxxxxxxxxxx    (0173)

http://www.informationjunction.co.uk/    (0174)

http://www.matthew-west.org.uk/    (0175)



This email originates from Information Junction Ltd. Registered in    (0176)

England and Wales No. 6632177.    (0177)

Registered office: 2 Brookside, Meadow Way, Letchworth Garden City,    (0178)

Hertfordshire, SG6 3JE.    (0179)

...    (0180)







_________________________________________________________________    (0181)

Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/    (0182)

Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/    (0183)

Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx    (0184)

Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/    (0185)

Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012    (0186)

Community Portal: http://ontolog.cim3.net/wiki/    (0187)





_________________________________________________________________    (0188)

Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/    (0189)

Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/    (0190)

Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx    (0191)

Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/    (0192)

Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012    (0193)

Community Portal: http://ontolog.cim3.net/wiki/    (0194)



_________________________________________________________________    (0195)

Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/    (0196)

Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/    (0197)

Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx    (0198)

Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/    (0199)

Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012    (0200)

Community Portal: http://ontolog.cim3.net/wiki/    (0201)





_________________________________________________________________    (0202)

Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/    (0203)

Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/    (0204)

Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx    (0205)

Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/    (0206)

Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012    (0207)

Community Portal: http://ontolog.cim3.net/wiki/    (0208)



_________________________________________________________________    (0209)

Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/    (0210)

Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/    (0211)

Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx    (0212)

Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/    (0213)

Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012    (0214)

Community Portal: http://ontolog.cim3.net/wiki/    (0215)





_________________________________________________________________    (0216)

Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/    (0217)

Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/    (0218)

Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx    (0219)

Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/    (0220)

Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012    (0221)

Community Portal: http://ontolog.cim3.net/wiki/    (0222)



_________________________________________________________________    (0223)

Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/    (0224)

Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/    (0225)

Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx    (0226)

Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/    (0227)

Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012    (0228)

Community Portal: http://ontolog.cim3.net/wiki/    (0229)



_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/
Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012
Community Portal: http://ontolog.cim3.net/wiki/    (0230)



*** WARNING *** old address guarino@xxxxxxxxxx not operational any more
new address is guarino@xxxxxxxxxxxxxxxx
Web site also changed to www.loa.istc.cnr.it.    (0231)

--------------------------------------------------------------------------------------------
Nicola Guarino
Head, Laboratory for Applied Ontology (LOA), ISTC-CNR
Institute for Cognitive Sciences and Technologies
National Research Council
Via alla Cascata, 56/C
38100 Povo (Trento), Italy
-------------------------------------------------------------------------------------------
Editor in Chief, Applied Ontology (IOS Press)
www.applied-ontology.org    (0232)

President, Int. Association for Ontology and its Applications (IAOA)
www.iaoa.org
-------------------------------------------------------------------------------------------    (0233)

office:        +39 0461 314871                        fax:
+39 0461 314875
secretary: +39 0461 314842-878
mobile:     +39 338 980 3912
skype:        nicolguar
web site:   http://loa.istc.cnr.it    (0234)







_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/
Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012
Community Portal: http://ontolog.cim3.net/wiki/    (0235)





_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/
Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012
Community Portal: http://ontolog.cim3.net/wiki/    (0236)

_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/   
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/  
Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012  
Community Portal: http://ontolog.cim3.net/wiki/     (0237)
<Prev in Thread] Current Thread [Next in Thread>