Re: [regrep] RE: Discovered numerous broken links in Regrep CSdocuments

[Farrukh Najmi <farrukh@wellfleetsoftware.com>]

Hi Robin,

Thank you for pointing out this issue. I have logged it under:

     http://jira.wx.ll.mit.edu/browse/REGREPTC-188

Note that above error is not caught when one searches for "Error: 
Reference source not found" in the Open Office source.
The best I have found is to search for it in the HTML converted text. We 
would welcome any suggestions for how to look for this class of error in 
future.

Also, the previous unresolvable link issue is logged under:

     http://jira.wx.ll.mit.edu/browse/REGREPTC-187


I feel that both these issues are fairly minor and that they do not 
warrant going through another round of CSD, Public Review, CS before we 
move to COS.
Based on past performance, going through a cycle like above would likely 
mean ~4 month delay which is not justifiable considering the minor 
nature of the issues involved.

We want a high quality OASIS standard as much as you do. As a practical 
matter, if we keep taking 4 month schedule hits on these minor issue we 
will never get done. So instead, I feel we should track the issue and if 
the issue is trivial or minor we should keep moving forward.

BTW, There are many downstream activities that we are blocked on (e.g. 
getting Statements of Use, Candidate OASIS Standard Ballot Request etc.) 
while we are waiting for CS01 to be posted. It is my understanding that 
the CS01 bundle has been handed off to you for posting by Chet last 
week. I would be grateful if you can tell us when we could see CS01 posted.

Thank you for your valuable help and guidance.


On 08/29/2011 01:29 PM, Robin Cover wrote:
> I'm not intending to comment on the broken links situation.
>
> I did note that the specification (prose documents) do have
> some other issues that the TC might want to consider for
> QA.
>
> For example, do you want to see this ratified in an OASIS
> Standard?
>
> "Error: Reference source not foundError: Reference source not
> foundError: Reference source not found"
>
> 1.2.3 RegistryExceptionType
>
> The RegistryExceptionType is the abstract base type for all exception
> or fault messages sent by the server to the client in response to a
> client request. Error: Reference source not foundError: Reference
> source not foundError: Reference source not found...
>
> Cheers,
>
> -rcc
>
> On Mon, Aug 29, 2011 at 10:00 AM, Breininger, Kathryn R
> <kathryn.r.breininger@boeing.com>  wrote:
>> Yes, I believe we need to fix these before we move forward.
>>
>>
>>
>> Kathryn Breininger
>> Manager, Standards Authoring, Release,&  Technical Orders
>> Product Standards Office
>> Boeing Research&  Technology
>> The Boeing Company
>>
>> MC 62-LC
>> 425-965-0242 desk
>> 425-512-4281 cell
>> 425-237-4582 fax
>>
>> How are we doing?  Please click on the attached link to take the Product Standards Office Customer Satisfaction Survey.
>> PSO Customer Survey
>>
>> -----Original Message-----
>> From: Chet Ensign [mailto:chet.ensign@oasis-open.org]
>> Sent: Monday, August 22, 2011 10:36 AM
>> To: regrep@lists.oasis-open.org; Farrukh Najmi; Breininger, Kathryn R
>> Cc: TCA
>> Subject: Discovered numerous broken links in Regrep CS documents
>>
>> Hi Farrukh, hi Kathryn,
>>
>> In preparing the Committee Specification files for the 3 parts of Regrep V4.0, we found numerous broken links. 44 were found in Part 2 and there are some in the other files as well.
>>
>> Some are broken internal links to different sections of the document.
>>
>> In Part 2 ebRS, there are many links in function documentation that do not work. See for example, 2.6 Canonical Query:
>> ClassificationSchemeSelector where the link behind "canonical query ClassificationSchemeSelector" doesn't work. It points to the URI http://docs.oasis-open.org/regrep/v4.0/canonical/SubmitObjectsRequest_Queries.xml
>> however neither the subdirectory /canonical/ nor the XML exists. (You can find these in the previous CSD and see the problem there.)
>>
>> Do you have a link checker that you can use to identify broken links?
>>
>> Do you want to pull this back from promotion to CS and fix these now?
>>
>> Please let me know how you want to proceed.
>> --
>>
>> /chet
>> ----------------
>> Chet Ensign
>> Director of Standards Development and TC Administration
>> OASIS: Advancing open standards for the information society http://www.oasis-open.org
>>
>> Primary: +1 973-378-3472
>> Mobile: +1 201-341-1393
>>
>> Follow OASIS on:
>> LinkedIn:    http://linkd.in/OASISopen
>> Twitter:        http://twitter.com/OASISopen
>> Facebook:  http://facebook.com/oasis.open
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC that
>> generates this mail.  Follow this link to all your TCs in OASIS at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>
>>
>
>


-- 
Regards,
Farrukh Najmi

Web: http://www.wellfleetsoftware.com