MODIFIED [MUST] Charter: The WG specifications must be simple to understand and implement correctly. The language defined by the WG specifications must be simple use.
MODIFIED [SHOULD] Charter: The WG specifications must be compatible with existing Web infrastructure.
DELETE (Adequately covered by DR013 now) [SHOULD] JS: Specification shall be as lightweight as possible, keeping parts that are mandatory to a minimum.
DELETE (Good goal, but unnecessary as a requirement) [SHOULD] JS: Optional parts of the specification should be orthogonal to each other allowing non-conflicting configurations to be implemented.
DELETE (Merged into DR013) [SHOULD] YF: Facilitate the creation of simple applications (fast and easy writing for simple apps).
DELETE or MOVE (May raise intractable semantic issues; belongs in a different category if we keep it) [SHOULD] YF: Be possible to compare easily two WSDL web services
DELETE (Adequately covered by "simple" in DR013) [SHOULD] YF: Since WSD is intended to be a foundation service description language, its definition should remain simple and stable over time. Explicit use of modularity and layering in the resulting design will help assure longevity. Such a framework will allow subsequent extension of the design while leaving the foundation of the design intact.
DELETE (Adequately covered by "correct" in DR013) [SHOULD] YF: The WSD specification must clearly identify conformance requirements in a way that enables the conformance of an implementation of the specification to be tested (see also the W3C Conformance requirements (W3C members only)).
Charter: Focus must be put on simplicity, modularity and decentralization. (Last discussed 21 Feb 2002. Replaced with DR013, DR102, DR027.)
JS: Be simple to understand and implement correctly; comparable to other widespread Web solutions. (Last discussed 21 Feb 2002. Replaced with DR013.)