From 7f9be261999b72575ee5467af8751160a1f7ae45 Mon Sep 17 00:00:00 2001 From: Fabio Bonelli Date: Wed, 26 Aug 2026 10:58:15 +0200 Subject: [PATCH] doc(spec): recommend the E.164 format for the phone key The key asked only for an international prefix, so catalogs get a different mix of spaces and separators from every file. E.164 gives one canonical shape. 1.0 makes it a requirement. See #70. --- docs/standard/schema.core.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/standard/schema.core.rst b/docs/standard/schema.core.rst index 565a3c8..b88915f 100644 --- a/docs/standard/schema.core.rst +++ b/docs/standard/schema.core.rst @@ -842,8 +842,9 @@ A Contact is an object with the following properties: contact. It must be an email address of where the technical contact can be directly reached; do NOT populate this key with mailing-lists or generic contact points like “info@acme.inc”. -- ``phone`` - phone number (with international prefix). This has to be - a string. +- ``phone`` - phone number. It SHOULD include the international + prefix, following the `E.164 `_ + format (e.g. ``+3923113215112``). This has to be a string. - ``affiliation`` - This key contains an explicit affiliation information for the technical contact. In case of multiple maintainers, this can be used to create a relation between each