Re: [Crisp] Last Call Comments on common-transport-03

"Hollenbeck, Scott" <shollenbeck@verisign.com> Wed, 23 August 2006 20:51 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GFzhJ-000069-6e; Wed, 23 Aug 2006 16:51:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GFzhI-00005p-Ir; Wed, 23 Aug 2006 16:51:36 -0400
Received: from osprey.verisign.com ([216.168.239.75]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFzhH-00027O-7m; Wed, 23 Aug 2006 16:51:36 -0400
Received: from dul1wnexcn02.vcorp.ad.vrsn.com (dul1wnexcn02.vcorp.ad.vrsn.com [10.170.12.139]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id k7NKpg70027674; Wed, 23 Aug 2006 16:51:42 -0400
Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 23 Aug 2006 16:51:32 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: Re: [Crisp] Last Call Comments on common-transport-03
Date: Wed, 23 Aug 2006 16:51:31 -0400
Message-ID: <046F43A8D79C794FA4733814869CDF07916DC3@dul1wnexmb01.vcorp.ad.vrsn.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Crisp] Last Call Comments on common-transport-03
Thread-Index: AcbG6QDBhOZ5FbbMTiaeO4abf5IEOwADOi1c
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "Andrew Newton" <andy@hxr.us>
X-OriginalArrivalTime: 23 Aug 2006 20:51:32.0580 (UTC) FILETIME=[EA3D2240:01C6C6F5]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: Marcos Sanz/Denic <sanz@denic.de>, iesg@ietf.org, crisp@ietf.org
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/crisp>, <mailto:crisp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:crisp@ietf.org>
List-Help: <mailto:crisp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/crisp>, <mailto:crisp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0519356292=="
Errors-To: crisp-bounces@ietf.org

Yes, there were first generation schema tools that had problems.  I don't think that's the case now, though.

-Scott-

 -----Original Message-----
From: 	Andrew Newton [mailto:andy@hxr.us]
Sent:	Wednesday, August 23, 2006 03:19 PM Eastern Standard Time
To:	Hollenbeck, Scott
Cc:	Marcos Sanz/Denic; iesg@ietf.org; crisp@ietf.org
Subject:	Re: [Crisp] Last Call Comments on common-transport-03

Hollenbeck, Scott wrote:
> xml:lang: We didn't harp on that because tool support for it was mixed at the time.  I personally believe that it should be used today in new specs  instead of creating a new attribute to carry the same info, but I don't see the need to change an older spec if a "custom" attribute was used.  That's what I had to do in EPP,for example.

Let me get this straight.  When specifying EPP, there were XML processors 
that were not capable of properly parsing the content of an xml:lang 
attribute but were capable of parsing the content of a lang attribute?  If 
anything, this tells me that the use of xml:lang, at least in the scope of 
XSDs, should not be recommended.

-andy


_______________________________________________
Crisp mailing list
Crisp@ietf.org
https://www1.ietf.org/mailman/listinfo/crisp