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

 


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-domains message

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


Subject: Review comments


Hi,

 

The document versions I am submitting a review for:

 

https://cdn.rawgit.com/oasis-tcs/oslc-domains/7c0a0de57f2368fbb3fdf74b40906445c045c256/rm/requirements-management-spec.html

https://cdn.rawgit.com/oasis-tcs/oslc-domains/7c0a0de57f2368fbb3fdf74b40906445c045c256/rm/requirements-management-vocab.html

 

§1 Verify the validity of the documents, formatting etc.

 

Issue #1: invalid rm-spec.html: https://validator.w3.org/nu/?doc=https%3A%2F%2Fcdn.rawgit.com%2Foasis-tcs%2Foslc-domains%2F7c0a0de57f2368fbb3fdf74b40906445c045c256%2Frm%2Frequirements-management-spec.html (errors 6..18)

 

Issue #2: warnings for old HTML features in vocab-spec.html https://validator.w3.org/nu/?doc=https%3A%2F%2Fcdn.rawgit.com%2Foasis-tcs%2Foslc-domains%2F7c0a0de57f2368fbb3fdf74b40906445c045c256%2Frm%2Frequirements-management-vocab.html

 

Issue #3: wrong/missing spec URIs

 

"This version" should be "N/A (unpublished draft)" - but I can tell you later how to cheat it with a preassigned git tag

"Latest version" should be either 2.0 (http://open-services.net/bin/view/Main/RmSpecificationV2) the last 2.1 draft reviewed by the TC.

"Latest editor draft" should be https://rawgit.com/oasis-tcs/oslc-domains/master/rm/requirements-management-spec.html (plus an extra error that the current last editor's draft's URL is dead)

 

Issue #4: (Related work) the http://open-services.net/bin/view/Main/RmSpecificationV2 is not guaranteed to be stable, the proposal is to register a new https://w3id.org/ for linking to it from the OASIS spec. OASIS may later change the W3ID URI if the http://open-services.net/bin/view/Main/RmSpecificationV2 goes down.

 

#5: (RDF Namespaces): http://open-services.net/ns/core/rm# returns 404. The proposal is to get a W3ID for it as well.

 

#6 (additional artifacts): Both URLs are dead

 

#7 (HTTPS mixed content): the HTTP schema on the CSS file URIs causes the green padlock to fail to appear. Please either change all URIs to HTTPS or use https://www.paulirish.com/2010/the-protocol-relative-url/

 

The rest of the document is reviewed using the W3C Web Annotation standard (https://www.w3.org/blog/news/archives/6156 and https://web.hypothes.is/blog/annotation-is-now-a-web-standard/):

 

https://via.hypothes.is/https://cdn.rawgit.com/oasis-tcs/oslc-domains/7c0a0de57f2368fbb3fdf74b40906445c045c256/rm/requirements-management-spec.html

 

 

/Andrew

 

P.S. My eyes can't read such long lines of text. I just published a Chrome/FF style that helps you narrow down the spec to something readable: https://userstyles.org/styles/157767/respec-my-eyes

 



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