RE: Review comments

Thanks Andrii for the feedback. I dealt with it as best I can.

 

The main issue remains the content concerning “Resource Formats”. This issue remains open in Core, so I have still not deal with that section until we decide in Core.

Martin! I promised to share the issue about it:
https://issues.oasis-open.org/browse/OSLCCORE-142

 

Otherwise, when dealing with your feedback on the content (as opposed to formatting issues), I avoided making the change if (1) your suggestion differed from CM –which
 we are using as a reference template and (2) your suggestion differ from the RM 2.0.

 

See below for the formatting-related issues you raised.

 

regards

______________________________

Jad El-khoury,
PhD

KTH Royal Institute of Technology

School of Industrial Engineering and Management, Mechatronics Division

Brinellvägen 83, SE-100 44 Stockholm, Sweden

Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45

,
www.kth.se

 

From:  [mailto:]
On Behalf Of Andrii Berezovskyi

Sent: 05 April 2018 16:02

To: 

Subject: [oslc-domains] 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)

 

Jad: Fixed

 

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

 

Jad: Fixed

 

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)

 

Jad: I trust that we fix these details in the end.

 

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.

 

Jad: I believe we are using open-services.net in a number of places. Won’t fix unless we want to do this systematically.

 

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

Jad: Won’t fix. Who said the namespace has to be dereferenceable.

 

#6 (additional artifacts): Both URLs are dead

Jad: I trust that we fix these details in the end.

 

#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/

Jad: the stylesheets have relative path, so cannot change to https.

 

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