DR 700: 3 reqs in one; too long; too prescriptive?

IMO, the following requirement should be split into 3 separate
requirements.

Furthermore, I think the bullet point are worth remembering (in the
issue list?), but do not belong to the requirement document itself;
i.e. they are food for thought, not prescriptions in themselves.


DR700a
              The XP specification must define a mechanism or
              mechanisms that allow applications to submit
              application-specific content or information for delivery
by
              XP. In forming the standard for the mechanisms, the XP
              specification may consider support for:
                   - carrying application specific payloads inside the

                   XP envelope,
                   - referring to application specific payloads
outside
                   the XP envelope,
                   - carrying nested XP envelopes as application
                   specific data within the XP envelope,
                   - referring to XP envelopes as application specific

                   data outside the XP envelope,
                   - extending the message by extension of the XP
                   envelope itself.

DR700b
              To manage the mechanisms, the XP specification must
              define a set of directives which will unambiguously
              indicate to an XP processor which extensions are
              optional and which are mandatory so that it can:
                   - process all of the extensions in an XP envelope
or
                   fail,
                   - process a subset of the extensions in an XP
                   envelope or fail.

DR700c
              In both cases above, the XP processor must fail in a
              standard and predictable fashion.

Jean-Jacques.

Received on Wednesday, 15 November 2000 11:05:50 UTC