[DR306] : splitting and specifying

In my view, this requirement, while containing valuable ideas needs
some rewording to specify it.

First, there is two requirements in one: one about the ease to deploy,
the other about the spectrum of deployment. So this requirement should
be split in two.

Second, we have to decide on the MUST/SHOULD in the first sentence. I
would suggest keeping the MUST.

Third, the current wording about the ease of deployement, referring
to XML namespaces and XML schemas may appear to be inconsistent with
DR309 about implementations using only a minimal amount of XML
infrastructure. What I think is meant is that deploying XP without
a full XML infrastructure (even with no XML infrastructure) should be
possible, but that deploying it with a full XML infrastructure should
be easy.

So I would suggest to replace DR306 by two requirements:


- DR306a:
The XML Protocol and applications of the XML Protocol MUST be easy to
deploy. This deployment should be even easier in systems already
supporting XML technologies (for example XML namespaces and XML
schemas).

- DR306b: 
The design of the protocol architecture MUST be sensitive to the issues
arising in the full spectrum of deployment environments ranging from
resource constrained embedded devices (appliances) through high
performance service engines.


Hervé Ruellan.

Received on Wednesday, 15 November 2000 11:30:23 UTC