Thank you for your reply. Our e next step of PROMCODE is approval of OASIS Standard in including public review and consent ballot for OASIS Standard. If it is OK, I would like to move forward with the current specification document for the next step. After it becomes an OASIS Standard, we will use Errata process to make the change following the process described in the OASIS TC process. The change is non-material for sure. Please let me know if you see any problem.
Tom
2021/10/26 23:22ãChet Ensign <chet.ensign@oasis-open.org>ãããã:Hi Tom,I believe these all are OASIS Standards now - or soon will be, correct? If that is the case, this can be handled with errata. Let me know if you need details on how that is handled./chetOn Tue, Oct 26, 2021 at 1:53 AM Tsutomu Kamimura <tomk@nanzan.jp> wrote:Andrew,We need to decide if an action is needed or not on this. I have created a revised version of the html file that addresses the issue. But, if the revision is needed, we will probably have to go through steps of OASIS process to do special majority vote and to publish the revision. As mentioned in my previous note, other OSLC work will have to do it also. Our TC will meet this week. Please give us your guidance by Wednesday of this week if possible.Chet,If this revision is needed, it will impact a number of OSLC documents including Core, CM, CCM, RM and AM. Revision is on the value of ID attribute of some section tags of html files When you see an each revised document by a browser, the actual content you see is exactly the same as the current one. If the revision is needed, what is the process we need use, request a special majority vote to approve CS with no material change, publish an errata, or something else?Regards,Tom2021/10/22 23:27ãTsutomu Kamimura <tomk@nanzan.jp>ãããã:Andrew,This problem is not limited to CM and PROMCODE. I looked at others quickly and found that the value of ID attributes for sections of resources in html files are not assigned in uniform way. So, the problem of not finding a right section by a browser for URL of âspec document URL#resource nameâ exists in Core, CCM, RM, and AM. The only one that works is QM. So, you need to look at the issue to see if this is really required for OSLC specification document. Let me know what you think.Tom2021/10/22 22:45ãChet Ensign <chet.ensign@oasis-open.org>ãããã:Hi Andrew, hi Tom,Tom, good catch. Andrew - yes; fixing broken links can be done via an errata./chetOn Fri, Oct 22, 2021 at 8:37 AM Andrii Berezovskyi <andriib@kth.se> wrote:Thanks Tom,
Sadly, you found a defect in the CM OS: https://github.com/oslc-op/oslc-specs/blob/master/specs/cm/change-mgt-shapes.html#L316 The id on that line (and others) should have been capitalized. I will check with Chet if we are allowed to update it as part of errata process.
/Andrew
From: Tsutomu Kamimura <tomk@nanzan.jp>
Sent: 22 October 2021 11:00:12
To: Andrii Berezovskyi
Subject: Re: [oslc-promcode-comment] PROMCODE spec commentsAndrew,
I looked at OSLC CM document and found out that it has the same problem.
For resource Enhancement, the following url takes a browser to the section on Enhancement resource
But, the following does not work.
The reason is the following. For each section that describes a resource such as Enhancement, Respec generates a html section with ID attribute with the string of the name of resource in lower case with <section id="enhancement" typeof="bibo:Chapter" resource="#enhancement" rel="bibo:Chapterâ>. That is the reason that the first url above can take a browser to the right section. Since there is no section that has its ID attribute with âEnhancementâ, the second url above does not work.
So, the problem is not specific to PROMCODE. I donât think it is a requirement on OSLC specification documents. What do you think?
Tom
2021/10/22 15:01ãTsutomu Kamimura <tomk@nanzan.jp>ãããã:
Andrew,
Thank you for pointing this out to us. This appears to be more complex problem than a simple typo. It is likely caused by the code generated by Pandoc/Respec. and the modification Paut Knight did for us to make the document format in line with the latest OASIS template. We will investigate further for a possible solution.
Tom
2021/10/22 0:19ãAndrii Berezovskyi <andriib@kth.se>ãããã:
Dear PROMCODE editors,I would like to comment that the Part 3 contains wrong anchors that would not allow browsers to scroll to the right part of the document. It would be great to fix that. Example:should be(the latter link does not work properly, as you can see)Part 2 contains correct anchors.Congratulations on reaching the CS milestone! Hope my comments are small enough to be addressed before you proceed to the next stage.Best regards,Andrew BerezovskyiOSLC OP PGB co-chair
--
Chet Ensign
Chief Technical Community StewardOASIS Open
+1 201-341-1393
chet.ensign@oasis-open.org
www.oasis-open.org --
Chet Ensign
Chief Technical Community StewardOASIS Open
+1 201-341-1393
chet.ensign@oasis-open.org
www.oasis-open.org _._,_._,_
Links:You receive all messages sent to this group.
View/Reply Online (#670) | Reply To Group | Reply To Sender | Mute This Topic | New Topic
Your Subscription | Contact Group Owner | Unsubscribe [tomk@nanzan.jp]
_._,_._,_