ebXML   masters by research in Computer Science  by Sacha Schlegel
   http://www.schlegel.li/ebXML/index.html    is the homepage of this project.

 M E E T I N G
 
m e e t i n g . h e a d e r  
  
date:    May 26th, 2003
week:    22
report:    x out of y
location:    School of Computing at Curtin University
Building 314, Level 4 Meeting room Andrew Marriott
person:    Andrew Marriott, supervisor (7675)
Don Reid, supervisor
Sacha Schlegel, student (2967)
 
m e e t i n g . a c t i v i t i e s  
  
  • Presentation of Level 1 and architecture of level 2,3
  • Level 1:
    • Invocation of algorithm
    • Screen output of algorithm
    • Examination of draft CPA
    • Examination of conflict file (maybe write an xsl file)
    • Problems of level 1 (referencing problem).
    • No NDD support.
    • Web-Interface. Future uploading of CPP's and soap/xml-rpc interface.
  • Architecture for level 2,3:
    • Architecture: Business Service Interface, Messaging System, Security System, Audit-Log System, Collaboration Manager, Concrete Collaboration Manager, Security Manager, Business Process Manager, Messaging Manager, Audit-Log Manager, Document Manager (including human interfaces).
    • Config file : - transport protocol a) soap, b) xml-rpc
    • Config file : - user interface a) text, b) dialog based, c) web (future), d) gnome2-app (future)
    • Admin tool for debugging, testing.
    • Running through sample negotiation (according to negotiation business process specification, which is referenced in the Negotiation Collaboration Protocol Agreement.
  • Communicated with Mr. Sachs, Chair of the ebXML CPPA-Negotiation group. Inconsitencies in NCPA and NBPS
  • Outlook this week:
    • Creation of negotiation messages (- raw message structure), soap-envelope, soap-header, soap-body, soap-attachement.
    • Kick start of negotiation for level 3, provide draft cpa and conflict file into negotiation. user selection of conflict elements plus selection of add element, remove element, accept element, update element (and attributes of course).
    • Thinking about paper, thesis writing.
  • Question: How to get user input for creation of a negotiation (or any other) message. How to create it. Data in xml but have do deal with data in memory (visitor pattern (or child, parent, next)to get all elements. - comparing to email, webforms (user has to fill out form, fields).
 
m e e t i n g . n o t e s  
Question of how to present the draft CPA of level 1? CPA is invalid because it is only a draft but still it should be presentable in some way. Check with openebxml for a stylesheet.  -  done  -  The openebxml site has a package which provides some stylesheets, arguable though if useful.
Is there a visualisation tool for the CPP's, CPA's?
How much work is it to add missing elements in CPA?
Missing elements should be listed in the conflict file.
Could a draft CPA and the conflict file become a valid CPA?
Someone has to test level one and check the quality of the draft CPA. Get in contact with HongKong, Sweden, Srilankan team. or other experts in general.
Have a list of things implmeneted - get a list of principals. then show what is implemented and what isn't. for thesis mainly.
Level 1 if backporting, then create a new "recommended" CPP. And the first thing in the negotiation aftwards is to agree on the changes of the CPP.
improve web interface plus get data of who connects to and store their cpps plus, log etc.
Fix the /tmp path and permissions.
  
 
m e e t i n g . t o . d o . l i s t  
  
  
  
  
  
  


© Sacha Schlegel@2003!