[Cellar] namespace considerations for ebml's definition of EBML Schema

Dave Rice <dave@dericed.com> Thu, 16 July 2020 18:03 UTC

Return-Path: <dave@dericed.com>
X-Original-To: cellar@ietfa.amsl.com
Delivered-To: cellar@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54DA63A0A82 for <cellar@ietfa.amsl.com>; Thu, 16 Jul 2020 11:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.118
X-Spam-Level:
X-Spam-Status: No, score=-1.118 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 lMQh5fFMjhrE for <cellar@ietfa.amsl.com>; Thu, 16 Jul 2020 11:02:59 -0700 (PDT)
Received: from server172-5.web-hosting.com (server172-5.web-hosting.com [68.65.122.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9CB33A0A3F for <cellar@ietf.org>; Thu, 16 Jul 2020 11:02:59 -0700 (PDT)
Received: from cpe-69-203-78-204.nyc.res.rr.com ([69.203.78.204]:53397 helo=[192.168.0.177]) by server172.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <dave@dericed.com>) id 1jw8De-002kcC-Sy for cellar@ietf.org; Thu, 16 Jul 2020 14:02:59 -0400
From: Dave Rice <dave@dericed.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9625DF02-2888-4981-BDAE-65EF1F111AD8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Message-Id: <3E54D46B-6D44-4095-9A5A-D9FB7CDB0F90@dericed.com>
Date: Thu, 16 Jul 2020 14:02:53 -0400
To: Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-OutGoing-Spam-Status: No, score=-0.2
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server172.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dericed.com
X-Get-Message-Sender-Via: server172.web-hosting.com: authenticated_id: dave@dericed.com
X-Authenticated-Sender: server172.web-hosting.com: dave@dericed.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/sjBIv89OEFAflkGl37e1bukxazQ>
Subject: [Cellar] namespace considerations for ebml's definition of EBML Schema
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cellar>, <mailto:cellar-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar/>
List-Post: <mailto:cellar@ietf.org>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cellar>, <mailto:cellar-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jul 2020 18:03:01 -0000

Hi cellar,
This is a late comment in regards to the EBML document, but I’m considering this dialogue.

>>>>>>> Begin forwarded message:
> 
> From: Karen Moore <kmoore@amsl.com>
> Subject: [AD - Murray] Re: AUTH48 [KC][SW]: RFC 8794 <draft-ietf-cellar-ebml-17.txt> NOW AVAILABLE
> Date: July 16, 2020 at 1:53:35 PM EDT
> To: "Murray S. Kucherawy" <superuser@gmail.com>om>, Steve Lhomme <slhomme@matroska.org>rg>, Dave Rice <dave@dericed.com>om>, Moritz Bunkus <moritz@bunkus.org>
> Cc: RFC System <rfc-editor@rfc-editor.org>rg>, Alexey Melnikov <aamelnikov@fastmail.fm>fm>, cellar-ads@ietf.org, cellar-chairs@ietf.org, Steven Villereal <villereal@gmail.com>
> 
>>>>>>>> 3) In the XML Schema for EBML Schema, the URL https://ietf.org/cellar/ebml <https://ietf.org/cellar/ebml>
>>>>>>>> is provided, but it doesn't seem to be a valid site. Please confirm that this
>>>>>>>> is okay.
>>>>>>>> -->
>>>>>>> 
>>>>>>> I don't suppose we could host it on the IETF website. I'm not sure if
>>>>>>> a valid URL is necessary here, this is just a marker for a namespace.
>>>>>>> I think it only needs to be unique so that it's not mistaken with an
>>>>>>> XSD with a same name.

Within the EBML Schema example xml and the EBML Schema XSD the value of https://ietf.org/cellar/ebml <https://ietf.org/cellar/ebml> is used as an undefined and stand-in namespace. From reviewing other RFCs which define XML Schemas, I see that they don’t use this style of URL but instead use a URN guided by RFC2648.

Should we consider adding a section such as the one quoted below and changing from https://ietf.org/cellar/ebml to urn:ietf:params:xml:ns:ebml?

> ### `<EBMLSchema>` Namespace
> 
> The namespace URI for elements defined by this specification is a URN as
> defined by [@!RFC2141] that uses the namespace identifier 'ietf' defined by
> [@!RFC2648] and extended by [@!RFC3688]. This URN is:
> 
> ```
> urn:ietf:params:xml:ns:ebml
> ```

and changing from https://ietf.org/cellar/ebml to urn:ietf:params:xml:ns:ebml. This would follow the recommendation at https://tools.ietf.org/html/rfc3470#section-4.9 <https://tools.ietf.org/html/rfc3470#section-4.9>.

Dave Rice