RM v2.1 PSD02 ready
|
Hello,
The “pre-PSD” can be found under https://github.com/oslc-op/oslc-specs/releases/tag/untagged-40b8102c05f3fa132447. It contains the ZIP file with the resources to be published.
If there are no big comments, I will open the PGB vote. Chet, Paul, do you think we could have an OASIS review finished in the 14 days for the vote, please?
-- –Andrew. |
|
|
|
Chet Ensign
Thanks Andrew. I opened https://github.com/oasis-open-projects/administration/issues/5 to track this. Paul, can you review the package and share any feedback? Thx, /chet On Mon, Sep 9, 2019 at 12:44 PM Andrii Berezovskyi <andriib@...> wrote:
--
/chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393 |
|
|
|
Hello Paul,
Did you have a chance to review the PSD for the Requirement Management spec? Thank you in advance.
-- –Andrew.
Från:
Chet Ensign <chet.ensign@...>
Thanks Andrew. I opened https://github.com/oasis-open-projects/administration/issues/5 to track this.
Paul, can you review the package and share any feedback?
Thx,
/chet
On Mon, Sep 9, 2019 at 12:44 PM Andrii Berezovskyi <andriib@...> wrote:
--
Chet Ensign Chief Technical Community Steward
|
|
|
|
Thanks Paul,
- the link to the OASIS Open Projects log was malformed, missing the initial "https:" in the link https://docs.oasis-open-projects.org/templates/logo/open-projects-logo.png
This is actually a feature, not a bug! It instructs the browser to fetch the image via the same protocol as the page itself.
- the links to the "Previous stage" should use http instead of https in this case, since the earlier files were installed with http links. When the HTML is retrieved using https, it is unable to load the associated .css file, so the document is poorly presented.
Fill fix. By the way, if you change the CSS URIs to be like the “malformed” URI I used, the mixed-content problems will go away 😉
- (editorial) - in Part 2: Vocabulary, I would expect that the first two definition blocks under Section 2.1.2 (Requirement and RequirementCollection) should be placed under 2.1.1, since they are Classes rather than Properties.
Makes sense. Will fix in ReSpec 2.1.11.
-- –Andrew.
Från:
Paul Knight <paul.knight@...>
Replying to all here, although this may not make it to all the lists...
I reviewed the two HTML files in the ZIP file rm-2.1-psd02_20190910.zip.
These both look good. I only noted a couple of items, plus an editorial comment:
- the link to the OASIS Open Projects log was malformed, missing the initial "https:" in the link https://docs.oasis-open-projects.org/templates/logo/open-projects-logo.png
- the links to the "Previous stage" should use http instead of https in this case, since the earlier files were installed with http links. When the HTML is retrieved using https, it is unable to load the associated .css file, so the document is poorly presented.
- (editorial) - in Part 2: Vocabulary, I would expect that the first two definition blocks under Section 2.1.2 (Requirement and RequirementCollection) should be placed under 2.1.1, since they are Classes rather than Properties.
Again, these look very good - it looks like you have gotten your Respec process set up nicely to prepare the OSLC files very quickly after the group approves them.
Best regards, Paul
On Tue, Sep 17, 2019 at 3:56 PM Andrii Berezovskyi <andriib@...> wrote:
-- Paul Knight....Document Process Analyst...mobile: +1 781-883-1783 OASIS - Advancing open standards for the information society |
|
|
|
Actually, the // trick is no longer needed: https://www.paulirish.com/2010/the-protocol-relative-url/, will fix
The vocabulary grouping fix is proposed under https://github.com/oasis-tcs/tab-respec/issues/17
-- –Andrew.
Från:
<oslc-op-pgb@...> på uppdrag av Andrii Berezovskyi <andriib@...>
Thanks Paul,
- the link to the OASIS Open Projects log was malformed, missing the initial "https:" in the link https://docs.oasis-open-projects.org/templates/logo/open-projects-logo.png
This is actually a feature, not a bug! It instructs the browser to fetch the image via the same protocol as the page itself.
- the links to the "Previous stage" should use http instead of https in this case, since the earlier files were installed with http links. When the HTML is retrieved using https, it is unable to load the associated .css file, so the document is poorly presented.
Fill fix. By the way, if you change the CSS URIs to be like the “malformed” URI I used, the mixed-content problems will go away 😉
- (editorial) - in Part 2: Vocabulary, I would expect that the first two definition blocks under Section 2.1.2 (Requirement and RequirementCollection) should be placed under 2.1.1, since they are Classes rather than Properties.
Makes sense. Will fix in ReSpec 2.1.11.
-- –Andrew.
Från:
Paul Knight <paul.knight@...>
Replying to all here, although this may not make it to all the lists...
I reviewed the two HTML files in the ZIP file rm-2.1-psd02_20190910.zip.
These both look good. I only noted a couple of items, plus an editorial comment:
- the link to the OASIS Open Projects log was malformed, missing the initial "https:" in the link https://docs.oasis-open-projects.org/templates/logo/open-projects-logo.png
- the links to the "Previous stage" should use http instead of https in this case, since the earlier files were installed with http links. When the HTML is retrieved using https, it is unable to load the associated .css file, so the document is poorly presented.
- (editorial) - in Part 2: Vocabulary, I would expect that the first two definition blocks under Section 2.1.2 (Requirement and RequirementCollection) should be placed under 2.1.1, since they are Classes rather than Properties.
Again, these look very good - it looks like you have gotten your Respec process set up nicely to prepare the OSLC files very quickly after the group approves them.
Best regards, Paul
On Tue, Sep 17, 2019 at 3:56 PM Andrii Berezovskyi <andriib@...> wrote:
-- Paul Knight....Document Process Analyst...mobile: +1 781-883-1783 OASIS - Advancing open standards for the information society |
|
|