Merge branch 'master' into 39-colon-quoting #376

- Also updated the canonical_purl value for the new colon ':' test object
Reference: #376
Reference: #39
Signed-off-by: John M. Horan <[email protected]>

meetings/2025-02-05.md

@@ -0,0 +1,38 @@
+# Agenda for the PURL community meeting on 2025-02-05
+
+- **Host**: Remote
+- **Dates and times**:
+    - 17:00 to 18:00 UTC
+    - 18:00 to 19:00 CEST (Europe/Brussels)
+    - 12:00 to 13:00 EDT (America/New_York)
+    - 09:00 to 10:00 PDT (America/Los Angeles)
+    - 02:00 to 03:00 JST (Tokyo, Japan)
+
+- **Attendee information**:
+  - https://meet.google.com/ydj-qwbs-iiv
+  - [Meeting invite](https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=MWliM3RyZXRpdmI4NXFoYXR1MzRkdmg0a3ZfMjAyNTAxMjJUMTcwMDAwWiBjX2Q4YjE1NDIwZGZmMTdiNzk1OWUyOWE1MWFlMzI0MDk1MWNiZTM4ZGIxZGFlNDU5NzJhODVjOWE3MTEyMDQyMDVAZw&tmsrc=c_d8b15420dff17b7959e29a51ae3240951cbe38db1dae45972a85c9a711204205%40group.calendar.google.com&scp=ALL)
+
+## Agenda items
+- Opening of the meeting and welcome
+- Meetings will follow the Ecma TC54 Code of Conduct https://github.com/Ecma-TC54/tg2/blob/main/CODE_OF_CONDUCT.md
+- Minutes of the 2025-01-22 meeting -- https://github.com/package-url/purl-spec/blob/master/meetings/2025-01-22.md
+- Overview of current core spec updating
+    - GitHub project board https://github.com/orgs/package-url/projects/1/views/1
+    - component-focused encoding etc.  https://docs.google.com/spreadsheets/d/1biOCUY4eCqQaYmfGDHVrASV9igYEzct6
+    - master issues/PRs https://docs.google.com/spreadsheets/d/1H2QAcADLaMNgcR5BMK7bQxzH5D3X-SdO
+
+## Attendees
+- Philippe Ombredanne, creator of PURL, Lead maintainer of AboutCode, TC54-TG2 convener
+- John Horan, AboutCode
+- Martin Prpic, Red Hat
+
+## Notes
+- Meeting minutes are being kept and will be published, but the meeting is not being recorded.
+- Our code of conduct (link in agenda above) applies to this meeting.
+- Philippe, Martin and John reviewed the 'scheme' and 'type' PRs in detail.
+    - Discussion of using negatives like NOT in the spec – when used sparingly, NOT is clearer and more concise than rewording to avoid the term.
+    - Consider whether, and if so how, to address encoding in the spec, e.g., streamline or remove the "Character encoding" section and address encoding in the "How to parse a purl string in its components" section, with details in the FAQ.
+    - Martin will explore how the draft FAQ can be improved, perhaps converting it to a cleaner, more concise set of clarifications rather than the current question/answer structure.
+    - John will clean up the draft FAQ in the 'scheme' and 'type' PRs to remove placeholder entries, update the test-suite-data.json file as needed for the 'type' PR, implement the various suggested changes for the 'scheme' and 'type' PRs, and then turn to the 'qualifiers' update.
+
+- The meeting was adjourned.

test-suite-data.json

@@ -623,10 +623,22 @@
     "subpath": null,
     "is_invalid": false
   },
+  {
+    "description": "ensure namespace allows multiple segments",
+    "purl": "pkg:bintray/apache/couchdb/[email protected]",
+    "canonical_purl": "pkg:bintray/apache/couchdb/[email protected]",
+    "type": "bintray",
+    "namespace": "apache/couchdb",
+    "name": "couchdb-mac",
+    "version": "2.3.0",
+    "qualifiers": null,
+    "subpath": null,
+    "is_invalid": false
+  },
   {
     "description": "invalid encoded colon : between scheme and type",
     "purl": "pkg%3Amaven/org.apache.commons/io",
-    "canonical_purl": null,
+    "canonical_purl": "pkg:maven/org.apache.commons/io",
     "type": "maven",
     "namespace": "org.apache.commons",
     "name": "io",