W3C home > Mailing lists > Public > public-i18n-core@w3.org > October to December 2006

Re: FYI: BCP 47 URI

From: Felix Sasaki <fsasaki@w3.org>
Date: Sat, 30 Dec 2006 22:22:37 +0900
Message-ID: <4596681D.5050708@w3.org>
To: Martin Duerst <duerst@it.aoyama.ac.jp>
Cc: Richard Ishida <ishida@w3.org>, public-i18n-core@w3.org

Martin Duerst wrote:
> As I have mentioned in another thread on a specific case, I think
> that the best reference for BCP 47 is
> http://www.ietf.org/rfc/bcp/bcp47.txt, totally independently of what
> the RFC Editor will answer when it eventually answers you, because
> that way, you clearly show that BCP 47 was created and is maintained
> by the IETF, which is way more important than the fact that it is
> copy-edited by the RFC Editor.

+1 .

Felix

> 
> Regards,     Martin.
> 
> At 17:34 06/12/13, Richard Ishida wrote:
>> Hi Martin,
>>
>> I've been in contact with the RFC editor folks about which URI to use, and
>> we are awaiting their final proposal.  There seem to be two in the running
>> at the moment, but they both point to the same document.
>>
>> Note also, that I have asked our liaison to the IETF to not only prompt them
>> on this, but to also suggest that the top line say *which* RFCs have been
>> concatenated on that page.
>>
>> Cheers,
>> RI
>>
>>
>> ============
>> Richard Ishida
>> Internationalization Lead
>> W3C (World Wide Web Consortium)
>>
>> http://www.w3.org/People/Ishida/
>> http://www.w3.org/International/
>> http://people.w3.org/rishida/blog/
>> http://www.flickr.com/photos/ishida/
>>
>>
>>> -----Original Message-----
>>> From: public-i18n-core-request@w3.org 
>>> [mailto:public-i18n-core-request@w3.org] On Behalf Of Martin Duerst
>>> Sent: 13 December 2006 07:38
>>> To: Felix Sasaki; public-i18n-core@w3.org
>>> Subject: Re: FYI: BCP 47 URI
>>>
>>>
>>> The same is true for http://www.ietf.org/rfc/bcp/bcp47.txt.
>>>
>>> I suggest we use the one at www.ietf.org. This makes it clear 
>>> that it is the IETF that has approved the relevant documents 
>>> as BCP. The file at rfc-editor is more 'original' in the 
>>> sense that the rfc-editor does a final editing pass (in 
>>> coordination with the authors) and publishes the documents, 
>>> and the IETF site mirrors them. But this is only after the 
>>> IETF (in this case the LTRU WG) creates them and (via the 
>>> IESG) approves them.
>>>
>>> Regards,   Martin.
>>>
>>> At 09:15 06/12/13, Felix Sasaki wrote:
>>>> ... at http://www.rfc-editor.org/rfc/bcp/bcp47.txt says now:
>>>>
>>>> "[Note that this file is a concatenation of more than one RFC.]"
>>>>
>>>> - Felix
>>>
>>> #-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
>>> #-#-#  http://www.sw.it.aoyama.ac.jp       
>>> mailto:duerst@it.aoyama.ac.jp     
>>>
>>>
> 
> 
> #-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
> #-#-#  http://www.sw.it.aoyama.ac.jp       mailto:duerst@it.aoyama.ac.jp     
> 
> 
Received on Saturday, 30 December 2006 13:23:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 October 2008 10:18:51 GMT