OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xri-editors message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [xri-editors] starting on i18n

Yes, as we discussed on our call yesterday, I think a good first start
would be a document that addresses:
a) the general functional requirements of I18N for URI schemes
b) the key challenges involved in meeting these requirements
c) the proposed strategy for how the XRI TC should meet these
challenges, and 
d) a list of tasks that need to be completed in order to carry out this
strategy and complete the I18N section of the spec doc.
-----Original Message-----
From: Wachob, Gabe [mailto:gwachob@visa.com]
Sent: Wednesday, June 04, 2003 10:15 AM
To: Nat Sakimura (E-mail)
Cc: 'xri-editors@lists.oasis-open.org'
Subject: [xri-editors] starting on i18n
    I wanted to start thinking about what needs to go in the section on
internationalization. What do we need to discuss?
    I was thinking perhaps that we should discuss the general functional
requirements related to internationalization and how they are
implemented using the IRI framework as applied to our URI scheme. Maybe
we have to make a distinction between the thing we resolve (a
post-unicode encoded URI) vs. an IRI which is mappable into an XRI URI.
    Nat- I think we need to examine the IRI proposal and figure out
whether we can use it directly, or take portions of it to describe the
process of encoding i18n characters, as well as addressing other i18n

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]