Re: Revised proposal: "DSMLv2-compliant" entitiies and working groupscope

[Christine Tomlinson <chris.tomlinson@sun.com>]

The 'searchResponse' defined in Batch.xsd is the same 'searchResponse'
element defined in the baseline proposal. It was moved to the 'batch' namespace
since it represents a grouping of core DSMLv2 elements.

We would also rewrite usages of 'dsmlEnvelopeRequest' to 'batch:request' and so forth.

Otherwise I believe that we are in concurrence with the text (of course we reserve the right to revise and extend our remarks).

ciao,
Christine Tomlinson

Jeff Parham wrote:

 (1) A DSMLv2-compliant entity is an element of type dsmlEnvelopeRequest, dsmlEnvelopeResponse, dsmlRequest, or dsmlResponse that satisfies the rules (XML schema and other guidelines) to be published in the working group's specification.[Jeff Parham] Noticeably absent is the searchResponse from Sun's batch.xsd.  I don't yet see the need for it, but if necessary we can revise this later to include it.(2) One or more DSMLv2-compliant entities may be embedded in an XML document.

(3) The DSMLv2 transports being defined by this working group -- the file (LDIF replacement) transport and the SOAP transport -- require dsmlEnvelopeRequest or dsmlEnvelopeResponse as the document type.

(4) The flow and focus of the DSMLv2 specication will continue to beon interactions that utilize the dsmlEnvelopeRequest and dsmlEnvelopeResponse as root documents. Interactions that do not utilize the dsmlEnvelopeRequest and dsmlEnvelopeResponse elementsmay be detailed in future transport specifications, allowing for maximum flexibility in these yet-to-be-defined transports while letting the working group concentrate on refining and giving examples for the already-defined transports.

(5) The scope of the DSMLv2 working group is to deliver a specification detailing the DSMLv2 grammar (dsmlEnvelopeRequest, dsmlEnvelopeResponse, dsmlRequest, and dsmlResponse and their contents), the file transport, and the SOAP transport.  Work beyond this scope -- additional transports, entities, etc. -- is left to individual vendors and future versions of the DSML specification.

-J