This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In the intro of WS-Enum there's a bit that says: In its simplest form, WS-Enumeration defines a single operation, Pull, which allows a data source, in the context of a specific enumeration, to produce a sequence of XML elements in the body of a SOAP message. In the submitted version of the spec this was true because Enumerate() was not required to be supported. In the latest version of the spec Enumerate() is no longer optional. So the above paragraph should be changed to something more like: In its simplest form, WS-Enumeration defines an operation, Enumerate, used to establish the creation of an enumeration session and a single operation, Pull, which allows a data source, in the context of a specific enumeration, to produce a sequence of XML elements in the body of a SOAP message. Also, in the next paragraph, there's a sentence that reads: This specification defines such an operation, Enumerate, that data sources MAY implement for starting a new enumeration of a data source. Based on recent changes the MAY should be a MUST. Proposal: see above
In its simplest form, WS-Enumeration defines an operation, Enumerate, used to establish the creation of an enumeration session and another operation, Pull, which allows a data source, in the context of a specific enumeration, to produce a sequence of XML elements in the body of a SOAP message.
Proposal: new paragraph: In its simplest form, WS-Enumeration defines an operation, Enumerate, used to establish the creation of an enumeration session and another operation, Pull, which allows a data source, in the context of a specific enumeration, to produce a sequence of XML elements in the body of a SOAP message. and in following para s/MAY/MUST/: This specification defines such an operation, Enumerate, that data sources *MAY* implement for starting a new enumeration of a data source.
resolved with comment #2