[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: New Issues (from IIC)
Mike Kass and I identified the following new issues during the course of reviewing the conformance specification. Section 4.2.3.2.5, Line 1325 "@location MUST be an XPointer" is too ambiguous. Need a more explicit specification of the allowed XPointer format(s). Also, include a real example at line 1336, instead of saying "URI of ds:Signature". Section 4.2.3.4, Lines 1345-6 The statement Short Description "MUST NOT be used in the content of the Error element" does not make sense. Error is a complex type, so it has no data content. If this was intended to refer to the content of the Error/Description element, line 1331 says this is vendor- defined, so why make this prohibition? Suggest removing the bullet. Section 9.2, Lines 2047-50 This describes the error condition in which SyncReply is present, but does not describe the case in which Reliable Messaging is not used, or is not in once-and-only-once mode (missing either DuplicateElimination or AckRequested toPartyMSH, as required by lines 1999-2000). Suggest adding a new paragraph after line 2050 for this case, with same errorCode and Error. Section 4.2.3.2.5, Lines 1326-7 What are the possible Payload Container error cases that must cause such an error to be reported? (This might not be a spec issue, but more of a request from IIC for guidance. In other words, how can we test that errors of this type are properly reported?) --Pete Pete Wenzel <pete@seebeyond.com> SeeBeyond Standards & Product Strategy +1-626-471-6311 (US-Pacific)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]