[bt-spec] BTP Issue 31 : Absense of rationale confuses normative text.

[BTP issues maintainer <peter.furniss@choreology.com>]

This issue has been added to the BTP issue list

BTP Issue 31 : Absense of rationale confuses normative text.

Submitter: Bill Cox, (for all BEA members)
Submitter's identification: issue J
Category: editorial
Detail:
The Draft attempts to describe BTP (as of 0.9) without explanation and
without explicit rationale in many places.  This is one of a number of
factors that makes the Draft and BTP difficult to understand. Most other
specifications make a distinction between rationale, examples, and normative
text.
Proposed Remedy:
Include rationale in a typographically distinct manner throughout the Draft.
This should be grounded in minutes of meetings.

---

To comment on this issue, please follow-up to this announcement on the bt-spec@lists.oasis-open.org (replying to this message should automatically send your message to that list).

The current draft, with line numbers is available in pdf format and word format.

To add a new issue, please email to Peter Furniss peter.furniss@choreology.com. It helps if you propose a category (technical, minor technical, editorial, minor editorial).