|
Title |
Minutes of the meeting |
|
Date |
14/2/2002 |
|
Source |
Fabio Bellifemine, TILab |
- Fabio Bellifemine
- Dominic Greenwood
- Frank McCabe
- David Levine
- Makoto
- Stephan Cranefield
- Alfredo Garro
- Heikki Helin
- Ion Constantinescu
- Tim Mc Fadden
- Bernard Burg
- Heimo Laamanen
- Steve Willmott
- Monique Calisti
- Henri Brouchoud
- present the X2S workplan
o approved
- propose to the BoD a chairman and one (or more) co-chairs
o chairman Fabio, co-chairs Jonathan, Steve
- identify the specifications that might eventually go from X2S
Action Point:request to chat@fipa.org the implementations of each FIPA specs and the will to share experience and feedback with this TC
Action Point:ask to Ontology TC advice on the Ontology Service specs (are they going to change the old specs?)
- identify the state-of-implementations for these specs
- recommend to FIPA to clarify the criteria for going from X2S
o alternatives:
§ 2 distinct implementations that interoperate (current rule according to most meeting participants)
· distinct = implemented by 2 different developers
§ a TC chair submitting the necessary specifications via email to the Architecture Board mailing list one month before the next scheduled FIPA meeting (current rule according to the f-out-00004F document)
§ 1 black-box software module that allows to test compliance
§ 1 reference implementation
§ mathematical/logical proof
§ membership approved
- define the template for providing contribution to this activity
- recommend to FIPA that the BoD provide a mechanism for maintaining / evolving standard specifications (i.e. an official and public known procedure for revising specs, e.g. unofficial bake-offs, ...)
- request to the BoD to give the official procedure for promotion from X to S, as currently specified by the FIPA documents, or clarify it if needed
o requirements of the formal vote process:
§ the process must converge
§ we must allow FIPA principal members to give comments
§ example: having a comment period and then a vote
o PROPOSAL:
|
19/10 |
20/10 |
1w |
4w |
1w |
1w |
2w |
|
X2S to FAB |
FAB & BoD to Secretariat |
Secretariat to package specs to members in electronic format |
comment period |
conference call to decide if/not go to vote |
organize the vote |
voting period |
- pending issues
o should we consider some comm. acts as an exceptional case (i.e. promoting to standard only a subset of the communicative acts)?
§ who use the FP and RE?
o interaction protocols (AUML)
o who use all the attributes of the message structure (e.g. reply-with, in-reply-to)?
o setup an issue-tracking system (Ion volunteers to setup and maintiaining it)
- how do we tackle the problem
o open process for comments up to 1 week before the 26th meeting
o TC tackles the specs on a per-group of document basis
- define the action points between this meeting and next one
o Ion to setup the tracking system
o Jacquie to setup the reflector
o Fabio to send e-mail to chat and open to comments for all
o by e-mail the main aim is to generate the issues and not to solve the issues
o in order to focus the activity of the membership between now and the next meeting, we announce that the agenda for the next meeting will be focused on the following specs:
§ no. 61 ACLMessage structure
§ no. 67 Message Transport Service
§ libraries
§ IIOP, HTTP MTPs
Subscription list for x2s@fipa.org
- scranefield@infoscience.otago.ac.nz
- ion.constantinescu@epfl.ch
- fgm@fla.fujitsu.com
- bernard
- steve
- heimo.laamanen@sonera.com
- henri.brouchoud@francetelecom.com
Legenda: X – experimental; P – Preliminary; I – Informative; Y – will be considered by the X2S TC
|
|
|
Type of Component |
Status |
Implem. |
X2S |
|
01 |
Abstract Architecture |
various |
X |
JAS RI |
Y |
|
07 |
Content Language Library |
library |
X I |
n.a. |
Y |
|
08 |
SL Content Language |
CL |
X |
JADE[1] ZEUS (SL-0) |
Y |
|
09 |
CCL Content Language |
CL |
X |
EPFL |
|
|
10 |
KIF Content Language |
CL |
X |
|
|
|
11 |
RDF Content Language |
CL |
X |
|
|
|
14 |
Nomadic Application Support |
service |
X |
Crumpet |
|
|
23 |
Agent Management |
service |
X |
JADE FIPA-OS |
Y |
|
25 |
Interaction Protocol Library |
library |
X I |
n.a. |
Y |
|
26 |
Request Interaction Protocol |
IP |
X |
JADE FIPA-OS |
Y |
|
27 |
Query Interaction Protocol |
IP |
X |
JADE FIPA-OS |
Y |
|
28 |
Request When Interaction Protocol |
IP |
X |
JADE |
|
|
29 |
Contract Net Interaction Protocol |
IP |
X |
JADE |
Y |
|
30 |
Iterated Contract Net Interaction Protocol |
IP |
X |
|
|
|
31 |
English Auction Interaction Protocol |
IP |
X |
|
Y |
|
32 |
Dutch Auction Interaction Protocol |
IP |
X |
|
Y[2] |
|
33 |
Brokering Interaction Protocol |
IP |
X |
JADE |
|
|
34 |
Recruiting Interaction Protocol |
IP |
X |
JADE |
|
|
36 |
Propose Interaction Protocol |
IP |
X |
JADE |
|
|
37 |
Communicative Act Library |
performatives |
X |
JADE FIPA-OS |
Y |
|
61 |
ACL Message Structure |
? |
X |
JADE FIPA-OS |
Y |
|
67 |
Agent Message Transport Service |
various |
X |
JADE FIPA-OS |
Y |
|
69 |
ACL Message Representation in Bit-Efficient Encoding |
ACLCodec |
X |
Sonera add-on used by JADE & FIPA-OS |
|
|
70 |
ACL Message Representation in String |
ACLCodec |
X |
JADE FIPA-OS |
Y |
|
71 |
ACL Message Representation in XML |
ACLCodec |
X |
EPFL add-on used by JADE |
|
|
75 |
Agent Message Transport Protocol for IIOP |
MTP |
X |
JADE FIPA-OS ZEUS |
Y |
|
76 |
Agent Message Transport Protocol for WAP |
MTP |
X |
|
N |
|
79 |
Agent Software Integration |
Service |
X |
|
|
|
80 |
Personal Travel Assistance |
Application |
X I |
Siemens |
|
|
81 |
Audio/Visual Entertainment and Broadcasting |
Application |
X I |
low priority |
|
|
82 |
Network Management and Provisioning |
Application |
X I |
low priority |
|
|
83 |
Personal Assistance |
Application |
X I |
low priority |
|
|
84 |
Agent Message Transport Protocol for HTTP |
MTP |
X |
EPFL add-on used by JADE FIPA-OS |
Y |
|
85 |
Agent Message Transport Envelope Representation in XML |
EnvelopeCodec |
X |
EPFL add-on used by JADE FIPA-OS |
Y |
|
86 |
Ontology Service |
service |
X |
Comtec |
? |
|
87 |
Mobility |
service |
P |
|
N |
|
88 |
Agent Message Transport Envelope Representation in Bit-Efficient Encoding |
EnvelopeCodec |
|
Sonera |
|
|
89 |
Policies and Domains |
various |
P |
|
N |
|
90 |
|
|
|
|
|
|
91 |
Device Ontology |
application |
P |
FIPA-OS |
|
|
92 |
Message Buffering Service |
service |
P |
|
N |
|
93 |
Message Interoperability Service |
service |
P |
|
N |
At a minimum the description of the problem is required but filling all the fields of this template would simplify the evaluation and decision-making process.
Please be as precise and specific as possible (e.g. use line numbers or section numbers).
The following resolutions have been adopted:
- the TC recommends the FAB to approve the X2S workplan and recommends the BoD to ratify the creation of the new X2S TC
- the TC recommends FIPA to setup the new e-mail reflector x2s@fipa.org to carry-on the X2S activity
- the TC has approved the following process to fulfill its mandate: a request for comments will be kept open until one week before the 26th meeting; the decision process and the analysis activity will be focused on a per-document basis. All comments arriving before this date will be taken into account.
- the TC has approved the template for submitting comments. The template is reported in the minutes of the meeting
- based on the information available at the meeting about the state of the implementations, the TC has identified the following set of core specifications that will be the subject of its activity: Abstract Architecture (no. 1), Content Language Library (no. 7), SL Content Language (no. 8), Agent Management (no. 23), IP Library (no. 25), Request IP (no. 26), Query IP (no. 27), Contract-Net IP (no. 29), English-Auction IP (no. 31), Dutch-Auction IP (no. 32), Communicative Act Library (no. 37), ACL Message Structure (no. 61), MTS (no. 67), ACL String Encoding (no. 70), IIOP MTP (no. 75), HTTP MTP (no. 84), XML Envelope Encoding (no. 85). The TC intends to collect more information in the future and, if possible, increase the list of analysed specifications.
- the TC recommends FIPA to review and clarify the criteria for proposing promotion of ‘experimental’ specification to the ‘standard’ status. A number of alternatives have been identified and reported in the minutes of the meeting.
- the TC recommends FIPA that the BoD define an official mechanism for the maintenance and the evolution of the standard specifications
- the TC requests the BoD to clarify the official vote procedure from promotion of the specs from ‘experimental’ to ‘standard’ status. A proposal has been worked out and it is reported in the minutes of the meeting.
- the TC appoints Ion Constantinescu as the responsible for identifying, setting, and maintaining an issue-tracking system and gratefully thanks him for volunteering and accepting this role
- the TC recommends FIPA to issue the minutes of the meeting as an official FIPA document
- the TC thanks all those people who actively contributed to the meeting and all the participants: Fabio Bellifemine, Dominic Greenwod, Frank Mc Cabe, David Levine, Makoto, Stephan Cranefield, Alfredo Garro, Heikki Helin, Ion Constantinescu, Tim Mc Fadden, Bernard Burg, Heimo Laamanen, Steve Willmott, Monique Calisti, Henri Brouchoud.