[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [regrep] RE: Discovered numerous broken links in Regrep CSdocuments
Thank you Chet and Farrukh for figuring this out! I think we are good to go forward as well. 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 29, 2011 2:42 PM To: Robin Cover Cc: Breininger, Kathryn R; regrep@lists.oasis-open.org; Farrukh Najmi Subject: Re: [regrep] RE: Discovered numerous broken links in Regrep CS documents Kathryn, Farrukh & members of the TC - I reviewed this specific problem with Farrukh and it appears to be a side-effect of the way we are creating the published versions of files in .odt format. The text Robin found does not occur in the work product submitted to TC Administration. My apologies for the error. Fortunately it is only one instance in one file and is easily remedied. Please let me know if you have any questions. Best regards, /chet On Mon, Aug 29, 2011 at 1:29 PM, Robin Cover <robin@oasis-open.org> 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.ph >> p >> >> > > > > -- > Robin Cover > OASIS, Director of Information Services Editor, Cover Pages and XML > Daily Newslink > Email: robin@oasis-open.org > Staff bio: http://www.oasis-open.org/people/staff/robin-cover > Cover Pages: http://xml.coverpages.org/ > Newsletter: http://xml.coverpages.org/newsletterArchive.html > Tel: +1 972-296-1783 > -- /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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]