- From: Niket Patwardhan <niket@verity.com>
- Date: Wed, 15 Sep 1999 23:45:38 -0700
- To: www-webdav-dasl-request@w3.org
- Cc: www-webdav-dasl@w3.org
>Date: Tue, 14 Sep 1999 14:24:18 -0700 (PDT) >From: Niket Patwardhan <npatward@verity.com> >To: npatward@miracle.verity.com >Subject: DASL > But it is not a client problem if the property contains values in multiple languages. It should be a 5xx error. Also, if you think of the text as another property of the document, you can see that there is no reason why a property should not have multiple languages in it. (Think Canada, or the EEC - they are required to produce documents in multiple languages!) >At 10:28 AM 6/30/98 PDT, John Stracke wrote: >>Jim Davis wrote: >> >>> If the property values are stored in Danish, you get the Danish >>> sort, no matter what the Content-Language is. >> >>Excuse me, I know this is an ugly question, but I really don't know the >answer: >>suppose some properties are in Danish and some are in Japanese? > >If all values of property foo are in Danish, and all values of prop bar are >in Nihongo, no problem. But if one property contains values in multiple >languages, this is a problem. We can't meaningfully compare values using >the underlying languages, as such comparisons are undefined. Nor will it >help to simply declare one language in the Content-Language header. > >This is why the DASL charter excludes such cross-language comparisons. > >I suppose this means we need to define the error code to be returned should >this condition arise. I suppose 400 (Bad Request) should be used, unless >there's need for a more specific code. >
Received on Thursday, 16 September 1999 02:49:09 UTC