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

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

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GFxPy-0003O6-MP; Wed, 23 Aug 2006 14:25:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GFxPx-0003Nj-Bi; Wed, 23 Aug 2006 14:25:33 -0400
Received: from osprey.verisign.com ([216.168.239.75]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFxPv-0003yI-VX; Wed, 23 Aug 2006 14:25:33 -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 k7NIPcgS012778; Wed, 23 Aug 2006 14:25:38 -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 14:25:29 -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 14:25:28 -0400
Message-ID: <046F43A8D79C794FA4733814869CDF07916DC2@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: AcbG2thVvYrm3bJ9S8aQt/CtonsstQABqp5u
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "Andrew Newton" <andy@hxr.us>
X-OriginalArrivalTime: 23 Aug 2006 18:25:29.0970 (UTC) FILETIME=[8350F520:01C6C6E1]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: e472ca43d56132790a46d9eefd95f0a5
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="===============1739169222=="
Errors-To: crisp-bounces@ietf.org

Remember when 3470 was written.  RelaxNG et al. were still quite new and unproven.  Even XML Schema was pretty new, but the general sentiment was that it was "better" than DTDs.  If I had to write it over again the only thing I'd be inclined to change would be adding a sentence to emphasize the "use what makes sense" point.

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.

-Scott- 

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

Hollenbeck, Scott wrote:
> Andy,
> 
> I don't really think that 3470 has been the cause of confusion. If anything, it has helped to reduce confusion.  The real problem has been that people don't know that it exists, or they haven't really read it.  As you noted, the situation with RelaxNG,  for example,  is typically clarified once people read what the document actually says.
> 
> (Sorry for top-posting.  I'm doing this from my Treo.)
> 
> -Scott-
> (One of the authors of 3470)

Scott,

3470 talks about XML Schema in about 8 separate places, many of which are 
"here is a recommended way of doing X in XML Schema".  With the exception of 
DTDs, all other schema languages are only mentioned in a small paragraph 
that can be paraphrased as saying, "There are other schema languages." 
Given the now vast number of IETF specifications using XML Schema, it is 
easy for one to conclude that XML Schema is the IETF way, even if 
unofficially in the way that re-using TXT records can cause headaches.

But given you are one of the authors of 3470, perhaps you can answer the 
question at hand.  Does 3470 recommend using xml:lang over something like 
<attribute name="lang" type="language"/> in XML Schema, even though the 
content of both is defined by RFC 3066?  Is the qualification of the element 
name necessary in understanding RFC 3066?  Or is the guidance more general, 
in that XML content that is human language be attributed with 3066 language 
tags so that it might be interpreted in language-dependent contexts?

-andy


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