Request to add an item to the 1/11 PGB Meeting agenda


Andreas Freund
 

Dear All, I would like to add an agenda item to the 1/11 PGB meeting:

Clarification on a MUST requirement for Project Specification: The requirement "Headings MUST have URLs that won't change, including fragment identifiers." implies that numbered headings are not allowed because adding/updating/removing headings will change the URL. However, the OASIS project specification template explicitly contains headings with numbers which can easily change even if the heading name remains the same. Is this requirement to be understood in conjunction with "Any requirement obsoleted since a previous version of the Project Specification MUST have a URL that resolves to somewhere explicitly stating the requirement is gone" expanded to Headings? This would allow a URL to be included in the obsolete or changed section heading pointing to the new section. Albeit such an approach could create a lot of redirecting sections over time.

Thank you in advance.

Cheers,
Andreas


Daniel Burnett
 

Added.

From: eea-community-projects-pgb@... <eea-community-projects-pgb@...> on behalf of Andreas Freund via lists.oasis-open-projects.org <a.freundhaskel=gmail.com@...>
Sent: Tuesday, January 10, 2023 11:59 AM
To: eea-community-projects-pgb@... <eea-community-projects-pgb@...>
Subject: [eea-community-projects-pgb] Request to add an item to the 1/11 PGB Meeting agenda
 
Dear All, I would like to add an agenda item to the 1/11 PGB meeting:

Clarification on a MUST requirement for Project Specification: The requirement "Headings MUST have URLs that won't change, including fragment identifiers." implies that numbered headings are not allowed because adding/updating/removing headings will change the URL. However, the OASIS project specification template explicitly contains headings with numbers which can easily change even if the heading name remains the same. Is this requirement to be understood in conjunction with "Any requirement obsoleted since a previous version of the Project Specification MUST have a URL that resolves to somewhere explicitly stating the requirement is gone" expanded to Headings? This would allow a URL to be included in the obsolete or changed section heading pointing to the new section. Albeit such an approach could create a lot of redirecting sections over time.

Thank you in advance.

Cheers,
Andreas