While I agree that FIPA may be useful, the ACL Message Structure does not
seem to be uniformly applicable. Other than the usual attributes of a
message (sender, receiver, etc.), ACL adds (formal) language, encoding,
ontology and protocol. If one is using web services (i.e., REST or SOAP),
then the protocol and encoding are specified in the WADL or WSDL, so they
would not be in the message. This just leaves the formal language and
ontology. Many of the OOR methods specify an ontology (or ontology
version). However, this ontology is the ontology being operated on (e.g.,
stored or retrieved), not the ontology of the message itself (e.g., OMV).
The ontology of the message is usually determined by which method is being
invoked. Similarly, the formal language is the language of the message,
not the language of the ontology being operated on. While some methods may
require additional parameters to specify a formal language and/or an
ontology, I suggest that they be added on a case-by-case basis. (01)
-- Ken (02)
On Sat, 18 Sep 2010, Cameron Ross wrote: (03)
> During yesterday's OOR meeting, Immanuel proposed that we design the OOR as a
> collection of disparate web services. There was some agreement with this
> proposal. We also discussed some of the challenges with supporting multiple
> representation languages.
> Perhaps we could adapt some of the ideas used within the FIPA architecture to
> help achieve these objectives. Specifically, the FIPA ACL Message Structure
> Specification may have some value
> (http://www.fipa.org/specs/fipa00061/SC00061G.html). Basically, FIPA ACL
> messages carry with them meta-data describing the language, encoding and
> ontology associated with the payload. I'm not sure that the performatives or
> the control of conversation aspects make sense for OOR, but the meta-data
> describing the pay load might.
> Just a thought.
Message Archives: http://ontolog.cim3.net/forum/oor-forum/
Shared Files: http://ontolog.cim3.net/file/work/OOR/
Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository (01)