Add missing anchors B.6.4, B.15.3; Swap HTTP cases

[bact]

• Remove "Annex" in the title, re-run heading numbering
  • See comments starting from here
• Add missing anchors B.6.4 and B.15.3 (now 5.4 and 14.3, after re-numbering)
• Put B.15.2 (14.2) anchor to the right heading
• Make link to SPDX License List
• Add internal links to guidelines
• Put some special characters example inside `...` to differentiate
• HTTP cases in B.14.1 and B.14.2 (13.1 and 13.2)
  • Protocol names (HTTP and HTTPS) should be in UPPERCASE (they are initialisms)
  • The schema names at the first part of URL ("http://" and "https://", which will be the actual texts to be compared) should be in lowercase -- see https://www.rfc-editor.org/rfc/rfc9110.html#name-http-related-uri-schemes

[zvr]

Since you are making changes, you might as well remove all the numbering; this is not an "Annex" here

[bact]

Since you are making changes, you might as well remove all the numbering; this is not an "Annex" here

Please explain more please.

Do you mean to remove all the existing heading numbering?

[bact]

@zvr just to make sure before making changes, do you mean to

• Remove the "Annex" word from the title
• Convert existing heading numbering from "B.1, B.2, B.2.1, B.2.2" to "1, 2, 2.1, 2.2" ?

Thank you

[zvr]

Yes, the whole text can be simplified to something like:

# SPDX license list matching guidelines

The SPDX License List Matching Guidelines provide guidelines ...

## How these guidelines are applied

### Purpose

To ensure consistent results ...

### Guideline: official license headers

The matching guidelines apply to license and exception text, ...

[jlovejoy]

Thanks for this @bact and @zvr !

(good catch on updating the numbering - now we are back to the numbering we had had for years prior :)

I just had one question on HTTP v. http caps changes

[bact]

@jlovejoy on HTTP, please see this comment #2537 (comment)

[swinslow]

LGTM, thanks @bact and all!