Re: [regrep] Update on CSD01

[Farrukh Najmi <farrukh@wellfleetsoftware.com>]

Here are some examples of issues identified thus far...

• All Documents
  
• Fix all [XXX] citations to conform to OASIS citation guidelines
• Overview (part 0)
• 1.1 and 1.2 are duplicated
• 1.3 Normative in heading needs to be bold
• 1.3 Fix formatting issues in references

• Section 1.8 Core Specification Documents
      "ebXML RegRep consists of two core specification documents:.... [...]
  
      - The two hyperlinks are broken (HTTP status 404)
      - You should probably remove the hyperlinks OR use the latest-version URIs
         viz.,
         http://docs.oasis-open.org/regrep/regrep-core/v4.0/regrep-core-rim-v4.0.html
         http://docs.oasis-open.org/regrep/regrep-core/v4.0/regrep-core-rs-v4.0.html
  
       If you use the version-specific URIs (/csd01/  /csd02/ etc) they will break
       with each revision, and for a CSD republished as a CSPRD, that's a problem.

• ebRIM (Part 1)

• Yellow text in section 2.7.2

We are grateful to Robin for catching these but this is really our job as TC member to do.

So please lets get the magnifying glass out and start looking for the remaining issues. A couple of hours of your time will go a long way. Thank you.


On 05/05/2011 10:24 AM, Farrukh Najmi wrote:

4DC2B32A.7060807@wellfleetsoftware.com" type="cite">
Dear Colleagues,

We are grateful to OASIS and specifically Robin Cover for doing a thorough job of quality control on our CSD01 document upload request task:

    http://tools.oasis-open.org/issues/browse/TCADMIN-454

The documents have been revised for quality control per OASIS process and posted at:

    http://docs.oasis-open.org/regrep/regrep-core/v4.0/csd01/

In the process Robin has identified some minor fit-and-finish issues. These are not technical spec issues. For a list of these issues please see:

    http://tools.oasis-open.org/issues/browse/TCADMIN-454

We have the following choice now:

1. Continue with the 30 day review of the posted CSD01 and then fix the issues and do another 15day review
2. Do not go for a 30 day review and instead do a WD2-1 (draft CSD02), approve it and approve its 30 day review and repeat the process with a Document Upload Request
   

Based on his guidance, Kathryn and I feel that we should do option (2). Please speak up via email on this thread right away if you feel otherwise.

Here is the proposed plan for us between now and our next meeting on Thu May 12, 12PM ET:

• All - Review the documents at the following links with a fine-tooth comb and send any issues to list. Please note that this is the strongest feedback Robin has provided us that the TC needs to do this to avoid further rework which costs OASIS and the TC a lot of valuable time. So please do your best to do a look through the following documents spotting for issues:
  
  part 0 Overview - http://docs.oasis-open.org/regrep/regrep-core/v4.0/csd01/regrep-core-overview-v4.0-csd01.odt
  part 1 ebRIM - http://docs.oasis-open.org/regrep/regrep-core/v4.0/csd01/regrep-core-rim-v4.0-csd01.odt
  part 2 ebRS - http://docs.oasis-open.org/regrep/regrep-core/v4.0/csd01/regrep-core-rs-v4.0-csd01.odt
  
  
• Farrukh - Fix spec artifacts to issues identified by OASIS and TC members in real time and publish WD2-1 by Sun May 8, 2011
• All - Review WD2-1 and attend TC meeting the on Thu May 12, 12PM ET to be prepared to vote on the motions to approve WD2-1 as CSD02 and for CSD02 to be published for a 30 day review
• Farrukh - Make document upload request for WD02-1

Kathryn, please let me know if I missed something.

-- 
Regards,
Farrukh Najmi

Web: http://www.wellfleetsoftware.com

-- 
Regards,
Farrukh Najmi

Web: http://www.wellfleetsoftware.com