OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [regrep] RE: Discovered numerous broken links in Regrep CS documents



I am ok if we move ahead as-is (without re-defining them) . It seems this is a tool  problem that not does impact the specification content.



On Mon, Aug 29, 2011 at 11: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




--
CEO CheckMi
Chair OASIS BCM Tech Committee
President BTUSAR Dive Team
Producer Shore Adventure
Cell (usa) (732) 497-CARL {2275}
CarlMattocks@CheckMi.com
Information Risk Checks > Secure Continuous Service


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]