Re: [VCARDDAV] AD review of draft-ietf-vcarddav-carddav-07.txt

[Alexey Melnikov <[e-mail]>]

Julian Reschke wrote:

> Alexey Melnikov wrote:
>
>> ...
>> [...]
>>
>>   5.  Well-defined internationalization support through standard HTTP.
>>
>> This is a bit misleading, because this is or isn't true depending
>> on which HTTP feature you mean here.
>> ...
>
> I think it's generally not true, unless we talk about payloads.
>
> So I think the I18N support is due to XML and WebDAV's use of it.

Exactly.

I was thinking at first that this was referencing to something like 
Accept-Language, but it doesn't.

>>  ...
>> 6.2.1.  CARDDAV:addressbook-description Property
>>
>>   Name:  addressbook-description
>>
>>   Namespace:  urn:ietf:params:xml:ns:carddav
>>
>>   Purpose:  Provides a human-readable description of the address book
>>      collection.
>>
>> BCP 18 (RFC 2277), section 4.2 applies to elements carrying human 
>> readable text.
>> Any human readable text needs to be [optionally] accompanied by RFC 
>> 4646 language tags.
>>
>> You even use of xml:lang in your example later in this section. 
>> However the definition doesn't allow for this attribute:
>>
>>   Definition:
>>
>>       <!ELEMENT addressbook-description (#PCDATA)>
>>       <!-- PCDATA value: string -->
>
> > ...
>
> The DTDs are incomplete; see for instance 
> <http://greenbytes.de/tech/webdav/draft-ietf-vcarddav-carddav-07.html#rfc.section.2.p.3>. 
>
>
> xml:lang is explicitly mentioned in RFC 4918, see 
> <http://greenbytes.de/tech/webdav/rfc4918.html#rfc.section.4.3.p.3>.

I found that. But if use of xml:lang is implicitly allowed, then the 
description should still have some description on how I18N can be achieved.