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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx message

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


Subject: Issue 133: Duplicate text in fault section


Here is my proposed text. The first paragraph gets struck, the new sentence is in bold.

 

I’ll send by EOD unless I get a fault.

 

Replace:

The faults defined in this section fall into one of two categories; those faults that are the result of

messages or operations within a specific Sequence and those faults that are not. By their nature the

CreateSequenceRefused, UnknownSequence, and WSRMRequired faults cannot be correlated with a

Sequence. All other faults defined in this section relate to the processing of WS-RM protocol messages or

messages containing WS-RM header blocks targeted at a specific Sequence and are collectively referred

to as "Sequence faults".

 

Faults for the CreateSequence message exchange are treated as defined in WS-Addressing.

CreateSequenceRefused is a possible fault reply for this operation. UnknownSequence is a fault

generated by endpoints when messages carrying RM header blocks targeted at unrecognized or

terminated Sequences are detected. All other faults in this section relate to the processing of RM header

blocks targeted at known Sequences and are collectively referred to as Sequence faults. Entities that

generate Sequence faults SHOULD send those faults to the same [destination] as

<wsrm:SequenceAcknowledgement> messages. These faults are correlated using the Sequence

identifier carried in the detail.

 

With:

Faults for the CreateSequence message exchange are treated as defined in WS-Addressing.

CreateSequenceRefused is a possible fault reply for this operation. UnknownSequence is a fault

generated by endpoints when messages carrying RM header blocks targeted at unrecognized or

terminated Sequences are detected. WSRMRequired is a fault generated by endpoints that require the

use of WS-RM and receive a message that did not use the protocol. All other faults in this section

relate to the processing of RM header blocks targeted at known Sequences and are collectively

referred to as Sequence faults. Entities that generate Sequence faults SHOULD send those faults

to the same [destination] as <wsrm:SequenceAcknowledgement> messages. These faults are

correlated using the Sequence identifier carried in the detail.

 

 

Marc Goodner

Technical Diplomat

Microsoft Corporation

Tel: (425) 703-1903

Blog: http://spaces.msn.com/mrgoodner/

From: Marc Goodner [mailto:mgoodner@microsoft.com]
Sent: Wednesday, June 07, 2006 5:27 PM
To: ws-rx@lists.oasis-open.org
Subject: [ws-rx] NEW Issue: Duplicate text in fault section

 

Title: Duplicate text in fault section

 

Description:

In Section 4  of WS-RM the first two paragraphs of this section are practically duplicates of each other.

 

Target: core

 

Type: editorial

 

Proposal:  

The first paragraph can be stricken by adding a one sentence description of WSRMRequired after the second sentence of the second paragraph in Section 4.

 



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