Fwd: work product review from OASIS re: PRD01 submission

["G. Ken Holman" <gkholman@CraneSoftwrights.com>]

Fellow CLRTC members,

Based on feedback received this week from the OASIS administration, 
I've had to make editorial changes to the public review draft 
according to the instructions copied below.

No content was added or removed, but it had to be rearranged in order 
to have a normative introduction.  Our introduction was informative, 
so I moved the informative bits of the introduction to a new section 
and left normative bits in.

Again, zero technical changes were made ... all editing was editorial.

Here is the latest submission I've prepared for OASIS administration 
to post as the public review draft:

      http://www.oasis-open.org/committees/document.php?document_id=34501

Please let me know if you have any questions or comments.  Meanwhile, 
I'll tell them of its availability.

. . . . . . . . . . . Ken

>From: Mary McRae <mary.mcrae@oasis-open.org>
>Subject: work product review
>Date: Tue, 29 Sep 2009 12:37:14 -0400
>Cc: Sabine Ocker <sabine.ocker@oasis-open.org>
>To: "G. Ken Holman" <gkholman@CraneSoftwrights.com>
>
>The following issues have been idientified in the submitted work
>products and must be corrected before they can be uploaded to 
>docs.oasis-open.org  and the Public Review announced:
>
>1. URIs
>a. Missing heading "Specification URIs"
>b. Remove directory (1st entry)
>c. One of the 3 must be declared as authoritative on the spec - I
>think you want the html version; you need to add (Authoritative) after
>the html url
>d. Previous Version - not noted. The heading should be there, with the
>reference 'N/A'
>e. Latest Version - these is a unique name that will always bring you
>to the most recent version of the spec and should be version-agnostic
>(suggestion: removed prd01from the directory name)
>
>2. Since Crane Softwrights is an Associate Member, you can't use the
>company name.
>G Ken Holman, Associate
>You can, however, use your email address.
>
>3. namespaces - remove the explanatory line. In actuality, a namespace
>document must be created that identifies each of the individual
>resources; neither the namespace document itself nor the actual
>resources will physically live at that location.
>
>4. template sequence. Note that Section 1 must contain the following:
>(copied from the template)
>--------------
>1. Introduction
>1.1 Terminology
>
>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to be
>interpreted as described in [RFC2119].
>
>1.2 Normative References
>[RFC2119]
>S. Bradner, Key words for use in RFCs to Indicate Requirement 
>Levels, http://www.ietf.org/rfc/rfc2119.txt , IETF RFC 2119, March 1997.
>
>1.3 Non-Normative References
>[Reference]
>[Full reference citation]
>
>---------------
>
>5. References - must be split into Normative and Non-Normative
>References
>Format for OASIS references: (missing approval Month YYYY)
>
>
>I would offer to make the changes for you but since you're authoring
>in Docbook I'll leave it to you.
>
>
>
>Regards,
>
>Mary
>
>Mary P McRae
>Director, Standards Development
>Technical Committee Administrator
>OASIS: Advancing open standards for the information society
>email: mary.mcrae@oasis-open.org
>web: www.oasis-open.org
>twitter: fiberartisan  #oasisopen
>phone: 1.603.232.9090
>
>Standards are like parachutes: they work best when they're open.


--
Upcoming: hands-on code list, UBL, XSLT, XQuery and XSL-FO classes
in Copenhagen Denmark and Washington DC USA, October/November 2009
Interested in other classes?  http://www.CraneSoftwrights.com/o/i/
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/o/
Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video
Video lesson:    http://www.youtube.com/watch?v=PrNjJCh7Ppg&fmt=18
Video overview:  http://www.youtube.com/watch?v=VTiodiij6gE&fmt=18
G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/o/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal