RE: comment

I've just been looking into how to handle content negotiation, and I 
haven't seen any implementation where content identified by a single
URL can handle multiple languages without redirection.  In other words,
if my file has Dutch content, and I'm a French user, I need to be sent
to another URL with the French version of that content (usually by the
language extension on the filename).  That other resource would have the
property values (like DAV:comment) in the correct language, presumably.

Therefore, I think there is no need to worry about internationalization
of string properties of a resource--they're going to be localized.  This
change should be reversed.

--Eric

> -----Original Message-----
> From: ietf-dav-versioning-request@w3.org
> [mailto:ietf-dav-versioning-request@w3.org]On Behalf Of
> Tim_Ellison@uk.ibm.com
> Sent: Tuesday, January 23, 2001 5:17 AM
> To: ietf-dav-versioning@w3.org
> Subject: DAV:comment
> 
> 
> 
> 
> 
> >   23.1.1 DAV:comment
> >     Why do we have an extra DAV:string element?
> >     Why can you have any number of them (how would a client
> >    choose which one to display)?
> >
> > This was a change requested by Yaron to support
> > internationalization.  You can have the comment
> > string in multiple languages this way.
> 
> I'll defer to those who are much more HTTP/XML-versed than I am, but I
> would imagine that this would be a matter of content negotiation between
> the client and server.
> 
> Tim
> 
> 
>

Received on Tuesday, 23 January 2001 12:29:47 UTC