Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

SUO: RE: SUO Comment #3




Dear James,

The point to be careful of in the comment below is not to interpret the
requirement as meaning that the SUO should not contain anything that cannot
be "compiled" into a more restrictive format such as XML. Otherwise there is
no problem.

Regards  
      Matthew
============================================
Matthew West
Asset Information Management
Shell Services International
H3229, Shell Centre, London, SE1 7NA, UK.
Tel: +44 207 934 4490 Fax: 7929
E-mail: Matthew.R.West@is.shell.com
http://www.shellservices.com/
============================================

> -----Original Message-----
> From: Schoening, James R CECOM DCSC4I
> [mailto:James.Schoening@mail1.monmouth.army.mil]
> Sent: 14 August 2000 23:10
> To: Standard-Upper-Ontology (E-mail)
> Subject: SUO: SUO Comment #3
> 
> 
> 
> H. Sofia Pinto [sofia@gia.ist.utl.pt] voted to ABSTAIN, with 
> the following
> comment:
> 
> "I'm not sure if the SUO should have as its explicit purpose 
> that it must be
> 
> suitable for compilation to more restricted forms such as XML 
> or database 
> schema. It is desirable that it is suitable for such 
> compilation but is it
> "must 
> have" requirement? "
> 
> This comment references the following item in the Purpose:
> 
> *	The ontology will be suitable for "compilation" to more 
> restricted
> forms such as XML or database schema. This will enable 
> database developers
> to define new data elements in terms of a common ontology, 
> and thereby gain
> some degree of interoperability with other compliant systems. 
> 
> Chair's note: If this remains as is, the first sentence 
> above, "The ontology
> will be suitable for "compilation" to more restricted forms 
> such as XML or
> database schema," should be moved to the Scope, but the rest  
> should remain
> in the Purpose.
> 
> Any responses to this comment?.
> 
> Jim Schoening
> Chair, IEEE SUO Study  Group
> 
> ==============================================================
> 
> The original Scope and Purpose is as follows:
> 
> Scope of Proposed Project:
> (The Scope describes what is being done, including the 
> technical boundaries
> of the project.)
> This standard will specify the syntax and semantics of a 
> general-purpose
> upper level ontology. An ontology is a set of terms and 
> formal definitions.
> This will be limited to the upper level, which provides definition for
> general-purpose terms and provides a structure for compliant 
> lower level
> domain ontologies. It is estimated to contain between 1000 
> and 2500 terms
> plus roughly ten definitional statements for each term. It is 
> intended to
> provide the foundation for ontologies of much larger size and 
> more specific
> scope.
>  
> Purpose of Proposed Project:
> (The Purpose describes why the standard needs to be developed 
> and who will
> benefit.)
> *	The standard will be suitable for automated logical inference to
> support knowledge-based reasoning applications. 
> *	This standard will enable the development of a large (20,000+)
> general-purpose standard ontology of common concepts to be 
> developed, which
> will provide the basis for middle-level domain ontologies and 
> lower-level
> application ontologies. 
> *	The ontology will be suitable for "compilation" to more 
> restricted
> forms such as XML or database schema. This will enable 
> database developers
> to define new data elements in terms of a common ontology, 
> and thereby gain
> some degree of interoperability with other compliant systems. 
> *	Owners of existing systems will be able to map existing data
> elements just once to a common ontology, and thereby gain a degree of
> interoperability with other representations that are 
> compliant with the SUO.
> 
> *	Domain-specific ontologies which are compliant with the 
> SUO will be
> able to interoperate (to some degree) by virtue of the shared 
> common terms
> and definitions. 
> *	Applications of the ontology will include: 
> *	     E-commerce applications from different domains 
> which need to
> interoperate at both the data and semantic levels. 
> *	     Educational applications in which students learn 
> concepts and
> relationships directly from, or expressed in terms of, a 
> common ontology.
> This will also enable a standard record of learning to be kept. 
> *	     Natural language understanding tasks in which a 
> knowledge based
> reasoning system uses the ontology to disambiguate among likely
> interpretations of natural language statements.
> 
> ===============
>