[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Collaboration Services (was: Business Service Interface)
Hi, Yep. Sequencing is a little strict and does not bring out the concept very well. I am using the term "ordering" (which means temporal ordering) as the term for this when talking with the business. Also there is the explicit ordering (means there is some information in the XML document to reflect ordering) and implicit (there is no ordering specific information in the XML document) ordering. Sequence Numbers and timeStamp are two methods to achieve explicit ordering. On similar lines, we might have to introduce concepts of business level connection and business level session. The point is, as the XML pipeline will carry many different business documents, the ordering might be needed only for a certain sub-set. This would be further complicated by many machines talking to many other machines. So a shared business level connection/session might needed. On a general note, we could explore possibilities of a separate track on these inter BP/collaboration issues. I think Bob raised this idea couple of weeks ago. cheers -----Original Message----- From: Bob Haugen [mailto:linkage@interaccess.com] Sent: Sunday, October 22, 2000 11:43 AM To: 'ebxml-tp@lists.ebxml.org' Cc: 'ebXML-BP@llists.ebxml.org' Subject: RE: Collaboration Services (was: Business Service Interface) <Bob Haugen> I also think that in many (if not most) of those cases, the sequence is not managable by sequence numbers or any other document-local rules, but requires interaction with something like actual business objects at one or both ends of the collaboration. .. In other words, sequencing of business collaborations may require collaboration software with some business intelligence, it may not be manageable exclusively by sequence numbers or linked lists. </Bob Haugen> <Nikola Stojanovic> I don't know whether "the sequence" and "sequencing" would be the best terms (I might rather use something like "Temporal constraints between (Economic, Business?) Events"), but I strongly agree with the assertions: "is not manageable by sequence numbers or any other document-local rules" and "it may not be manageable exclusively by sequence numbers or linked lists". </Nikola Stojanovic> Thanks for the feedback, Nikola. I agree that sequencing is not the best term; I just used it to hark back to the previous threads on that subject. Re: >(Economic,Business?) Events In the ebXML metamodel, EconomicEvents are transfers of EconomicResources from one Partner to another, for example a shipment or payment. EconomicEvents are subtypes of BusinessEvents, which cover almost any other event of managerial interest. The reason for specializing EconomicEvents is that they have special behavior and relationships, for example, EconomicEvents may fulfill EconomicCommitments, e.g. shipments may fulfill orders. Regards, Bob
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC