From 2b3147fc767332edb88dd30d65d5c705fe4a5eb2 Mon Sep 17 00:00:00 2001
From: Philippe Ombredanne <pombredanne@nexb.com>
Date: Tue, 24 Dec 2024 19:32:04 +0100
Subject: [PATCH] Clarify namespace for mlflow type

mlflow used a reference to an "empty" namespace and was at
odds to use this definition with other types.
This clarifies that mlflow does not use a namespace and remove the reference to "empty" namespace.

Reference: https://github.com/package-url/purl-spec/pull/373
Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
---
 PURL-TYPES.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/PURL-TYPES.rst b/PURL-TYPES.rst
index 64a1342..a7d32d6 100644
--- a/PURL-TYPES.rst
+++ b/PURL-TYPES.rst
@@ -416,7 +416,7 @@ mlflow
   - AWS Databricks: ``https://dbc-<alphanumeric>-<alphanumeric>.cloud.databricks.com/api/2.0/mlflow``
   - GCP Databricks: ``https://<numbers>.<number>.gcp.databricks.com/api/2.0/mlflow``
 
-- The ``namespace`` is empty.
+- There is no ``namespace``.
 - The ``name`` is the model name. Case sensitivity depends on the server implementation:
 
   - Azure ML: it is case sensitive and must be kept as-is in the package URL.