Re: [ire] CSV woes: unused namespaces?

"Gould, James" <JGould@verisign.com> Fri, 04 October 2013 13:39 UTC

Return-Path: <JGould@verisign.com>
X-Original-To: ire@ietfa.amsl.com
Delivered-To: ire@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DE1221F9BCE for <ire@ietfa.amsl.com>; Fri, 4 Oct 2013 06:39:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1lhL6rrhmRPc for <ire@ietfa.amsl.com>; Fri, 4 Oct 2013 06:39:13 -0700 (PDT)
Received: from exprod6og110.obsmtp.com (exprod6og110.obsmtp.com [64.18.1.25]) by ietfa.amsl.com (Postfix) with ESMTP id A542F21F9C7D for <ire@ietf.org>; Fri, 4 Oct 2013 06:31:51 -0700 (PDT)
Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob110.postini.com ([64.18.5.12]) with SMTP ID DSNKUk7DRkuHaz4Rs6Yi5nxLPmZ+hKY90k7H@postini.com; Fri, 04 Oct 2013 06:31:53 PDT
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id r94DVlnr027898 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 4 Oct 2013 09:31:47 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Fri, 4 Oct 2013 09:31:46 -0400
From: "Gould, James" <JGould@verisign.com>
To: Klaus Malorny <Klaus.Malorny@knipp.de>, "ire@ietf.org" <ire@ietf.org>
Thread-Topic: [ire] CSV woes: unused namespaces?
Thread-Index: AQHOwO1XGLgZhPIBsU+T1uGKiezaLJnkikQA
Date: Fri, 4 Oct 2013 13:31:46 +0000
Message-ID: <CE7434FB.4FC80%jgould@verisign.com>
In-Reply-To: <524E9963.5010609@knipp.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.6.130613
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EE7B90D0ADF3CB41ACB951E10DFD6D82@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [ire] CSV woes: unused namespaces?
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ire>, <mailto:ire-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ire>
List-Post: <mailto:ire@ietf.org>
List-Help: <mailto:ire-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ire>, <mailto:ire-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Oct 2013 13:39:32 -0000

Klaus,

Each of the XSD's referenced in the I-D includes a set of IANA URI
requests for both urn:ietf:params:xml:ns (e.g.
urn:ietf:params:xml:ns:rdeCsv-1.0) and urn:ietf:params:xml:schema (e.g.
urn:ietf:params:xml:schema:rdeCsv-1.0).  The  urn:ietf:params:xml:schema
URI's are used to register the schemas and the urn:ietf:params:xml:ns
URI's are used within the XML documents that use that schema.  The field
definitions for the CSV model within the XML manifest file follow the same
convention that is used for the XML model, where there is a schema that
contains the definitions and a namespace URI that is used within the XML
manifest file.  In the case of the CSV model, the fields define the format
of the CSV files that would be used by a CSV validator.  There is a level
of indirection with the fields, since they are directly validated using an
XML parser in the XML manifest file and they include a type attribute,
with a XSD type value, that is validated by a CSV validator in the
referenced CSV files.   I don't believe there is any substantial
difference between the XML and CSV models when it comes to the IANA URI
requests.  Let me know if I'm missing something from your question.

Thanks,

-- 
 
JG
 

 
James Gould
Principal Software Engineer
jgould@verisign.com
 
703-948-3271 (Office)
12061 Bluemont Way
Reston, VA 20190
VerisignInc.com




On 10/4/13 6:33 AM, "Klaus Malorny" <Klaus.Malorny@knipp.de>; wrote:

>
>
>Hi,
>
>just another discovery: It seems to be that the specification* contains
>IANA 
>namespace applications in section 11 that are actually not used in any
>way, 
>namely all those starting with "urn:ietf:params:xml:schema:". I expected
>the 
>elements defining the fields of the CSV files to use these (as one could
>regard 
>this as a schema definition), but this is not the case. It would be nice
>if 
>someone could clarify this.
>
>Regards,
>
>Klaus
>
>
>* http://tools.ietf.org/html/draft-arias-noguchi-dnrd-objects-mapping-05
>_______________________________________________
>ire mailing list
>ire@ietf.org
>https://www.ietf.org/mailman/listinfo/ire