W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 1997

RE: Open Requirements Issues

From: Dylan Barrell <dbarrell@opentext.ch>
Date: Fri, 6 Jun 1997 09:32:22 -0400
Message-ID: <01BC725C.8A5F7280@cassius.opentext.ch>
To: "ejw@ics.uci.edu" <ejw@ics.uci.edu>, "'Terry Allen'" <tallen@sonic.net>, "w3c-dist-auth@w3.org" <w3c-dist-auth@w3.org>
I would like to see some slightly better international support

1)  The server should support the notion of document language versions (similar in concept to renditions) and should always produce the language version corresponding to the language of the user's client, the explicit language version requested by the client (i.e. it should be possible to explicitly address a particular language version) or the default language.
2)  The client should be able to specify its preferred languages in order of preference and the server should present from the existing language versions the one highest on the client's list. Failing this the default language should be presented.
3)  It should be possible to specify to the server which language version is the default (master version)
4)  When asking for a list of objects in a collection it should be possible to obtain a list of all the different language versions of each resource (the default should simply return the list of default language resources)
5)  It should be possible to lock only a particular language version of a resource or all languages
6)  There must be a way of indicating which nodes in the version graph for each language can be considered equivalent (there might be a different number of versions for each language version)


From:  Terry Allen[SMTP:tallen@sonic.net]
Sent:  Donnerstag, 5. Juni 1997 23:27
To:  ejw@ics.uci.edu; w3c-dist-auth@w3.org
Subject:  Re: Open Requirements Issues

>We definitely need some words on this topic, however my lack of experience
in this area hinders my ability to construct a good requirement.  Something
along the lines of, "All fields which might be displayed to a human user of
client software should be fully international."  I'd appreciate some
assistance for good wording of "fully international" -- something along the
lines of "supports iso character set standard XXX" might work.
How about "nothing in this specification shall be interpreted to
inhibit internationalization".  As for the character set, the IAB
view is ISO 10646.


  Terry Allen    Electronic Publishing Consultant    tallen[at]sonic.net
    Davenport and DocBook:  http://www.ora.com/davenport/index.html
          T.A. at Passage Systems:  terry.allen[at]passage.com 
Received on Friday, 6 June 1997 09:35:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:10 UTC