Skip to content

Conversation

@ENEN-DTR
Copy link

These changes address ambiguous descriptions in the sections

  • 1.6.1,
  • 7.1.2.7.7,
  • 7.1.2.11.2,
  • 7.1.2.3.2,
  • 7.1.2.7.9,
  • 7.1.2.8.8,
  • 7.1.2.10.5.

All these are linguistic improvements to avoid ambiguities. It introduces the definition of scheme according to RFC 3986, section 3.1 to the BRs. It also clarifies that no methods other than those listed in the respective descriptions are permitted.

D-Trust had an incident due to the current language of the BRs and its interpretation. The changes are intended to help avoid such misinterpretations in the future. Please see: https://bugzilla.mozilla.org/show_bug.cgi?id=1884714

Changes in the sections 1.6.1, 7.1.2.7.7, 7.1.2.11.2, 7.1.2.3.2; 7.1.2.7.9; 7.1.2.8.8 and 7.1.2.10.5.
@ENEN-DTR ENEN-DTR requested a review from a team as a code owner July 12, 2024 11:26
Removed <br>.
Changes in accordance to review
@ENEN-DTR
Copy link
Author

@clintwilson; @CBonnell: I'm not happy with the term "Scheme" as it is also used also in different contexts. Would it be better to use "URI Scheme" instead so that it's not confused with the general term "scheme"?

@clintwilson
Copy link
Member

@clintwilson; @CBonnell: I'm not happy with the term "Scheme" as it is also used also in different contexts. Would it be better to use "URI Scheme" instead so that it's not confused with the general term "scheme"?

Agreed, I think "URI Scheme" as a defined term is a good idea for this update as well.

Introduction of the term `URI Scheme` to avoid misunderstandings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants