OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: [regrep] ebRS v2.03


All,

Here is the final version – currently labled ebRS v2.03.  Once again, two copies…”ebRS v2.03 changes in view” and “ebRS v2.03 changes NOT in view”.

Upon approval by the TC, this version will be renamed v2.1. 

-Anne Fischer

 

Listed below are the changes in ebRS v2.03:

- lines 3608, 3609, 3617, 3627: added urn:uuid prefix in id attribute in section 8.4.2 example

- lines 692, 969, 1010, 1038, 1069: correct spelling of "Uavailable"

- line 1000: change "updated" to "approved"

- line 1028: change "updated" to "deprecated"

- lines 1148, 1149: change "is done via contentURI as explained in Section 8.4" to "is accomplished using the technique explained in Section 8.4"

- lines 1150, 1151: Take out "the whole hierarchy of"?

- lines 2162, 2394, 2614; In order to be consistent with the rest of the spec keep fonts for warnings Italic, but don't Bold them

- line 2989: replace "If not, raise exception: object attribute error" with "If not, raise exception: registry object attribute error"

- line 3074: insert a new numbered paragraph after line 3074

For every EmailAddressFilter XML element, the leftArgument attribute of any containing SimpleClause shall identify a public attribute of the EmailAddress UML class defined in [ebRIM]. If not, raise exception: email address attribute error. The EmailAddressFilter returns a set of identifiers for EmailAddress instances whose attribute values evaluate to True for the Clause predicate.

 –––––-Changes in Section 8.4.2---------------------

-Delete lines containing “Content-Transfer-Encoding” in example.

-line 3583: Replace "CPP" with "Collaboration Protocol Profile"

-bullet @ line 3576: Replace: "… as the value of the Content-ID header field for the mime-part that contains …"

With: "…  as the value of the Content-ID header parameter for the mime multipart that contains… "

-bullet @ line 3578 Replace: "In case of [ebMS] transport, use the ID for each RegistryObject instance that describes the repository item in the Reference element for that object in the Manifest element of the ebXMLHeader."

With: "In case of [ebMS] transport, use the ID of the ExtrinsicObject instance in the Reference element for that object in the Manifest element of the ebXMLHeader."

-Added at the end of the first paragraph of section 8.4.2:  "Note that the boundary parameter in the Content-Type headers in the example below are meant to be illustrative not prescriptive."

-Replaced example in 8.4.2

-------------Changes in Section 9.2.2-----------

-Bullet @ line 3694 Replace: "The second through nth body part must be the content."

With: "The second body part must be the content."

-Line 3695 Replace: "The packaging of the payload signature with one payload is as follows:"

With: "The packaging of the payload signature with two payload is as shown in example in <cross reference to 8.4.2 make sure it is hyper-linked>"

-Example at 3697-3792: Removed entirely since it is replaced by a example in 8.4.2.

-Line 3804-3805 Replace: "The packaging of the ds:Signature element  in the SOAP header field  is shown below."

With: "The packaging of the ds:Signature element  in the SOAP header field  is shown in <cross reference to 8.4.2 make sure it is hyper-linked>."

-Example at 3806-3828: Removed entirely since it is replaced by a example in 8.4.2.

––––––Section 9.3––––––-

-Line 3793: After the 1st sentence “Message headers can be signed and are referred to as a header signature.” , add the following:

“When a request is sent by a Registered User, the Registration Authority may use the pre-established contract or a default policy to determine whether the response contains a header signature. .  When a request is sent by a Registery Guest, the Registration Authority may use a default policy to determine whether the response contains a header signature.”

-Begin new paragraph with “This section specifies the requirements for generation, …..”

Attachment: RS v2.03.zip
Description: Zip compressed data



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC