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

Andrew Newton <andy@hxr.us> Wed, 23 August 2006 17:37 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GFwfF-0003qb-7M; Wed, 23 Aug 2006 13:37:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GFwfD-0003qS-Uq; Wed, 23 Aug 2006 13:37:15 -0400
Received: from zeke.toscano.org ([69.31.8.124] helo=zeke.ecotroph.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFwf7-0004KX-Nq; Wed, 23 Aug 2006 13:37:15 -0400
Received: from [127.0.0.1] ([::ffff:208.50.38.5]) (AUTH: LOGIN anewton) by zeke.ecotroph.net with esmtp; Wed, 23 Aug 2006 13:37:07 -0400 id 0158819D.44EC9245.00006D2A
Message-ID: <44EC9239.6040805@hxr.us>
Date: Wed, 23 Aug 2006 13:36:57 -0400
From: Andrew Newton <andy@hxr.us>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Subject: Re: [Crisp] Last Call Comments on common-transport-03
References: <046F43A8D79C794FA4733814869CDF07916DBF@dul1wnexmb01.vcorp.ad.vrsn.com>
In-Reply-To: <046F43A8D79C794FA4733814869CDF07916DBF@dul1wnexmb01.vcorp.ad.vrsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
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>
Errors-To: crisp-bounces@ietf.org

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