[regext] Picking XML namespaces

Martin Thomson <martin.thomson@gmail.com> Sun, 04 November 2018 05:39 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 133B2130DCF for <regext@ietfa.amsl.com>; Sat, 3 Nov 2018 22:39:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bbm6L5PfjSTp for <regext@ietfa.amsl.com>; Sat, 3 Nov 2018 22:39:00 -0700 (PDT)
Received: from mail-oi1-x244.google.com (mail-oi1-x244.google.com [IPv6:2607:f8b0:4864:20::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 507421271FF for <regext@ietf.org>; Sat, 3 Nov 2018 22:39:00 -0700 (PDT)
Received: by mail-oi1-x244.google.com with SMTP id k19-v6so4800756oic.11 for <regext@ietf.org>; Sat, 03 Nov 2018 22:39:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=KB3uDz2eIvhsPOXTvoOFRuRDk+98pAWB+ctqx7fbYsE=; b=AdrcDFLcSNUIRVKLT8H3p9On/cvkl6QbFZWGBCxC8mOnB8DttxHaXja2fcocVggBaX AXEPgfNNp/0URc1dJeATqGJyFANRnY9L3/KEEOIjpQQG5E1SD65JeAHB9t7HhdhnLYS7 YPKo8c0XRkqb/m+/X75R+D2dTRUiMNS6m4E0Nc4/DBSuSgkrXzCkF1PccbCQkPcPEB4j kZ1H2sBD0KUiaAjzo2tixzntAz35JPGSO/5GPibXq1dNvMClPI6PTSbSAeN22K7QLjI3 XLRpk6X1ON1GqCXpDladOtai0ZQqgrKr4JDqDO7Lzg3jEdOX8Tf6iHfsFbKWoq0mOZeH heIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=KB3uDz2eIvhsPOXTvoOFRuRDk+98pAWB+ctqx7fbYsE=; b=UGAC/JOIQpSHND1MR6WpsNlR6D2b+vkWTuGwB38y5ZKdoG5BqRPnlxkOhSfT72kYL4 DH7mVUXf1pFjjw7mBUijSsv5SUGE+G6CZMa3mcj1nUM24BmBMwKwhc656XVOcqKz+CM6 kDXlrrxCakeQl3yJldwbVUQBUSBQIIY/6zPOJczC/Gdw6uSGK4KCFqPL3EN8ymTVriq9 M9eXawC3KaaSC2QGF3at66EvfJWxTe+2lIKbEYlTIRUF87dg6ICid+RcgQ9Yr9rPILjO fwV6uIgukM8d10KpF9sYh2+mRbGCFZRhXItDPM0sDYAEubzI5hGIIAVwOp56vAPni9n7 GbOg==
X-Gm-Message-State: AGRZ1gJ6ayjmY/EN6iitMHJFepq0mtlx7Py0QIY9xEZycars5PJATyLd FpTvlM0zKKYwF5veyHfWY3RfYZf6oR0KPyr+XF7UdTMGdK4=
X-Google-Smtp-Source: AJdET5eqciNkJvShXHgZ/Ve5CVyd/otkBfV+p8qHdHrOP+1YAtifRvah0LMF0COnFFolRfELgY8dhMxTlpMINdMmoLQ=
X-Received: by 2002:aca:5407:: with SMTP id i7-v6mr10506985oib.344.1541309939489; Sat, 03 Nov 2018 22:38:59 -0700 (PDT)
MIME-Version: 1.0
From: Martin Thomson <martin.thomson@gmail.com>
Date: Sun, 04 Nov 2018 12:38:48 +0700
Message-ID: <CABkgnnVALJ7kB-LpUFq3BtmMfNtVHbxfOaiQceKjN4gRZ3NRYw@mail.gmail.com>
To: regext@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/EZz6aoQVMbr_mQPN5Sqmprqk-vk>
Subject: [regext] Picking XML namespaces
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2018 05:39:02 -0000

Folks,

I'm seeing an increase in EPP registrations for the XML namespace and
schema registries.

In the past, the names this group have selected are quite generic.

I would like to request that this group include a label in the names
that it uses.  Other users of these registries carefully scope the
names they use to avoid conflict, but this group has not done that.

I realize that there is an established pattern here that would need to
change, which is a little disruptive, but I think that it would be
respectful to other users of the registry to start using scoped names
for new registrations.

That is, in the most recent document I've been asked to review:

urn:ietf:params:xml:ns:changePoll-1.0

becomes

urn:ietf:params:xml:ns:epp:changePoll-1.0

And future documents follow the same pattern.  This is consistent with
other uses of this registry.