Re: [cmis-comment] Comment on CMIS Errata

[Patrick Durusau <patrick@durusau.net>]

Florian,

On 6/23/2011 12:18 PM, Florian Müller wrote:

4E03675D.90808@alfresco.com" type="cite">

Hi Patrick,

Thank you for your comment.

Thanks for the quick response!

There are a couple of points I need to clarify:

4E03675D.90808@alfresco.com" type="cite">

I have checked the HTML version of the original specification. The W3C link checker found 11 "broken links". 

Yes, but the W3C link checker counts *multiple* instances of the same broken link as *one* broken link. I assume in the hopes that simple cut and paste can resolve each error.

Take for example: http://docs.oasis-open.org/ns/cmis/link/200901/acl

It is *broken* at lines: 14787, 22329, 22613, 22899, 23144, 23366

I count that as *six* broken links because any user will get a 404 at each of those locations.

4E03675D.90808@alfresco.com" type="cite">

- 9 of them are namespace URLs. They are looking like links but they are not. They are unique identifiers.

Well, but in checking further, they are broken *unique identifiers.*

I tried to find a couple of broken links but both Word and my browser reported they were not present.

Then I did view source:

*a href="http://docs.oasis-open.org/ns/cmis/link/200901/allowableactions">http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions</a*

But the namespace is for:

*http://docs.oasis-open.org/ns/cmis/link/200908/*

So either the namespace declaration on the cover page is wrong or the link is wrong.

As an implementer, I would not know which one.

4E03675D.90808@alfresco.com" type="cite">

- 1 link points to a document that has been removed AFTER the specification had been ratified.

Which one of the 32 is that?

4E03675D.90808@alfresco.com" type="cite">

- 1 link is an artifact that has been generated during the conversion from the Word document to HTML.
  Since the HTML version is not authoritative, this shouldn't be an issue.

??

I wasn't aware that MS Word generates incorrect hyperlinks.

I did spot check and the authoritative version appears to be the source of the broken links in both the HTML and the PDF.

As far as I am aware, MS Word faithfully reproduces correct as well as broken links that are given to it.

4E03675D.90808@alfresco.com" type="cite">

In summary, there were no substantive link errors to correct in the CMIS Errata.

The divergence from the declared namespaces by these links I think makes this more than failure to proof for 404 errors.

BTW, has this issue come up before? I can't speak for other TCs but in the ODF TC, where we had thousands of links, even working drafts were checked for correct linkage.

Hope you are having a great day!

Patrick

4E03675D.90808@alfresco.com" type="cite">

Regards,

Florian


-----Original Message-----

From: Patrick Durusau [mailto:patrick@durusau.net]
Sent: Wednesday, June 22, 2011 6:11 PM
To: cmis-comment@lists.oasis-open.org
Subject: [cmis-comment] Comment on CMIS Errata

Greetings!

On behalf of the Technical Advisory Board at OASIS I have a comment and
a couple of questions about the CMIS errata,
http://docs.oasis-open.org/cmis/CMIS/v1.0/errata-01/csprd01/cmis-spec-v1.0-errata-01-csprd01.doc

I was checking the errata and happened to run the original spec (HTML
version) through the W3C link checker.

It reports thirty-two (32) 404 links in the original specification.

I checked the CMIS JIRA listing of reported comments and did not find
any prior report of these broken links in the JIRA tracking system.

Has this standard proceeded to this point with no report of 30+ links
that were logged as errors in JIRA?

All of these could be fixed as errata since a 404 could not have
substantive meaning for an application, other than to be a 404 and I
don't think any of these links were meant to convey 404ness.

TC's can choose to fix whatever errors they like but it is a poor
reflection on OASIS for either these errors to have remained undetected
until this point or if they were known, to not be fixed in this errata
release.

Hope everyone is having a great day!

Patrick

-- 
Patrick Durusau
patrick@durusau.net
Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau