[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (EBXMLMSG-89) D.2.1 PMode Notation
Pim van der Eijk created EBXMLMSG-89: ---------------------------------------- Summary: D.2.1 PMode Notation Key: EBXMLMSG-89 URL: https://issues.oasis-open.org/browse/EBXMLMSG-89 Project: OASIS ebXML Messaging Services TC Issue Type: Improvement Reporter: Pim van der Eijk This section introduces a syntax "[u]" for user messages and "[s]" for "(pull} signals". For a user messages there may be multiple types of signals: pull, error, receipt. These have different configurations, so there needs to be a way to differentiate them. For example, syntax "[r]", "[p]", "[e]". With such a syntax, some other parameters could be dropped. For example: PMode[1].ErrorHandling.Report.ReceiverErrorsTo Could be expressed as PMode[1][e].Protocol.Address To express that an error is to be signed, we could use parameters: PMode[1][e].Security.X509.* This is the approach taken in CPPA3 with its concept of ebMS3Channel. It is more general and more expressive. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]