ontology-summit
[Top] [All Lists]

Re: [ontology-summit] Ontology Summit 2013

To: Ontology Summit 2013 discussion <ontology-summit@xxxxxxxxxxxxxxxx>
From: joseph simpson <jjs0sbw@xxxxxxxxx>
Date: Sun, 9 Dec 2012 21:53:17 -0800
Message-id: <CAPnyebx8Dc8vNvM9yN3GV4391cfYEdgd3S+mx=ZjtYJDbYqosQ@xxxxxxxxxxxxxx>
Jack...........

Interesting observation .....
  
  " Why do some people say that an algorithm is not an ontology?"

Some algorithms and ontologies may share common properties...

In general this constructs are different.............

Have fun and be good to yourself,

Joe

On Fri, Dec 7, 2012 at 9:01 AM, Jack Ring <jring7@xxxxxxxxx> wrote:
Yea, verily.
In fact the _expression_ of a system whether in an early stage model or a deployable stage materialization (but representable as an algorithm albeit large and complex) is equivalent to an ontology --- Operands and Operators arranged 'just so' such that when enabled with resources and triggered by stimulus an acceptable response occurs.
Why do some people say that an algorithm is not an ontology?
Jack Ring
On Dec 7, 2012, at 9:27 AM, John F Sowa wrote:

> On 12/6/2012 11:47 PM, Michael Gruninger wrote:
>> "Ontology Evaluation Across the Ontology Lifecycle"
>
> That's an important topic.  But the lifecycle of an ontology is
> co-extensive with the lifecycle of any application or system that
> uses or is based on that ontology.
>
> This morning, I sent replies to two email lists that most people
> on this list subscribe to.
>
>  1. To Nancy W. on IAOA, I made the point that you can't separate
>     the ontology of a system from its architecture or design.
>
>  2. To Rich C. on Ontolog Forum:  "Imagine an IT department that had
>     one group doing the architecture, a second group doing the design,
>     a third group doing the ontology, and a fourth group doing the
>     implementation."
>
> Amanda responded,
>> Sadly, John, some of us don't have to imagine this; we can remember it!
>
> I would relate that point to evaluation:  a critical issue in a good
> ontology is its accuracy in reflecting the design and/or architecture
> of the system.
>
> There are aspects and modules that could be distinguished.  For
> example, the complete ontology of a system might combine multiple
> modules or microtheories.  But the complete ontology of a system
> and its complete architecture must be closely coordinated.
>
> Any evaluation of an ontology must address these issues.
>
> John
>
> _________________________________________________________________
> 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/OntologySummit2013/
> Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2013
> Community Portal: http://ontolog.cim3.net/wiki/


_________________________________________________________________
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/OntologySummit2013/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2013
Community Portal: http://ontolog.cim3.net/wiki/



--
Joe Simpson

Sent From My DROID!!

_________________________________________________________________
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/OntologySummit2013/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2013  
Community Portal: http://ontolog.cim3.net/wiki/     (01)
<Prev in Thread] Current Thread [Next in Thread>