|
m e e t i n g . a c t i v i t i e s
|
|
| |
- Good news: A VERY basic algorithm is in place. The algorithm does some checks like:
- check for matching process specifications
- check if role are NOT the same. No lookup of ebXML Business Process to check whether role exists.
- ThisPartyActionBinding - asynchronous: check if each CanSend has a matching CanReceive element
- ThisPartyActionBinding - synchronous: CanSend and CanReceive can have recursively other CanSend, CanReceives. Check if they match.
- no checks yet for certificates and security (list of trusted certificate issuers)
- check DeliveryChanels (retrieved from CanSend-CanReceive pairs)
- check Transport pairs -- e.g TransportSender Protocol has to be the same as TransportReceiver Protocol
- check DocExchange pairs -- e.g ebXMLSenderBinding has to be the same as ebXMLReceiverBinding
- some basic attribute text matches: e.g Protocol "HTTP" has to match to other "HTTP" protocol
- Current affairs: What the algorithm does not do yet:
- Rewriting algorithm: Removing "copy and paste" code with methods, some more OO.
- Multiplicity giving head work atm: CPP can have MULTIPLE PartyInfo with MULTIPLE CollaborationRoles where as CPA has exactly 2 PartyInfos with MULTIPLE CollaborationRoles. E.g From two CPPs it is possible to get more than one CPA!
- Writing a log entry to the conflict log (XML file?) for each mismatch with a) conflict element/attribute of CPP 1 (including value), b)conflict element of CPP2 (including value), c) possible solution? d) a comment?
- Algorithm does not write to a new CPA, only prints "match", "no match". BUT algorithm has to create a new CPA.
- If there is a mismatch the algorithm does exit. BUT algorithm has to go ahead if a mismatch occurs.
- The MSH will have to parse and act accordingly to the CPA. The CPA formation algorithm e.g does not to know what HTTP or SSL is.
- have to get up-to-date what's going on various ebXML mailing lists, other "open" ebXML projects. Have to get in contact with some other peer people.
- Outlook:
- Level One (algorithm which finds matches and writes them to the CPA)
- Level One with Negotiation Description Document
- THEN level three (instead of level 2) where the "conflict log" presents "some" web-based workflow for parties to discuss/fill out conflicting elements.
- Because level two (automated negotiation) is the academic interesting part I have to get quickly there.
- NOIE
- I am in contact with Steve Capell.
- They setup the Open Source ebXML Registry/Repository.
- The toolbox (MyYob, Quicken plugin) will have some "fixed" values for the CPPs.
- Some CPA formation process will be necessary for the Australian ebXML project.
- Questions:
- Do you know if some ebXML project members are "hanging out" in some chat forums like IRC (Internet Relay Chat) or is email and phone conference the main communication vehicles?
|
|
|