Disposition of Comments on RFC 3066bis - Private Use/Conformance

Addison Phillips [wM] aphillips at webmethods.com
Tue Jul 13 21:57:45 CEST 2004


Sorry, meant to type "draft-04". Still bleary from the 26 hours in the
(gentle) hands of Aeroflot.

Addison

Addison P. Phillips
Director, Globalization Architecture
webMethods | Delivering Global Business Visibility
http://www.webMethods.com
Chair, W3C Internationalization (I18N) Working Group
Chair, W3C-I18N-WG, Web Services Task Force
http://www.w3.org/International

Internationalization is an architecture.
It is not a feature.

> -----Original Message-----
> From: Mike Ksar [mailto:mikeksar at microsoft.com]
> Sent: 2004年7月13日 12:23
> To: aphillips at webmethods.com; ietf-languages at alvestrand.no
> Cc: Harald Tveit Alvestrand
> Subject: RE: Disposition of Comments on RFC 3066bis - Private
> Use/Conformance
>
>
> Addison,
>
> Thanks for responding.  Where is draft 05?  I thought we are
> still reviewing draft 04!!  Something is broken in this process.
>
> Mike Ksar
>
>
>
> -----Original Message-----
> From: Addison Phillips [wM] [mailto:aphillips at webmethods.com]
> Sent: Tuesday, July 13, 2004 12:18 PM
> To: Mike Ksar; ietf-languages at alvestrand.no
> Cc: Harald Tveit Alvestrand
> Subject: RE: Disposition of Comments on RFC 3066bis - Private
> Use/Conformance
>
> All,
>
> Just back from 12 days in Russia, without (realistic) Internet
> connectivity.
>
> Mike,
>
> 1. The issues list on my website is not up to date.
>
> 2. The text in the document already says (I think) what you want
> it to say. Please refer to draft-05 for the best version of said
> text. To follow your analogy, as with Unicode, you are required
> to accept well-formed language tags that use private use subtags,
> but you are not required to understand them or generate them, and
> you are allowed to ignore them altogether for the purposes of
> matching (other processing is not described, but presumably
> follows the "allowed to ignore").
>
> 3. Presumably the "last call" will close shortly and the IESG
> will make some sort of decision about the document. Since there
> has been a lot of feedback and changes during this last call, it
> is possible that there will follow another last call to ensure
> that adequate stability has been reached.
>
> Addison
>
> Addison P. Phillips
> Director, Globalization Architecture
> webMethods | Delivering Global Business Visibility
> http://www.webMethods.com
> Chair, W3C Internationalization (I18N) Working Group
> Chair, W3C-I18N-WG, Web Services Task Force
> http://www.w3.org/International
>
> Internationalization is an architecture.
> It is not a feature.
>
> > -----Original Message-----
> > From: ietf-languages-bounces at alvestrand.no
> > [mailto:ietf-languages-bounces at alvestrand.no]On Behalf Of Mike Ksar
> > Sent: 2004年7月12日 10:50
> > To: ietf-languages at alvestrand.no
> > Cc: Harald Tveit Alvestrand
> > Subject: FW: Disposition of Comments on RFC 3066bis - Private
> > Use/Conformance
> >
> >
> > It seems that my earlier emails have not been posted to the correct
> > alias.  I am resending.  I apologize to those who already saw my email.
> >
> > Mike Ksar
> >
> > -----Original Message-----
> > From: ietf-languages-bounces at alvestrand.no
> > [mailto:ietf-languages-bounces at alvestrand.no] On Behalf Of Mike Ksar
> > Sent: Sunday, July 11, 2004 6:48 PM
> > To: Mark Davis; Doug Ewell; ietf-languages at iana.org
> > Subject: Disposition of Comments on RFC 3066bis - Private
> > Use/Conformance
> >
> > Mark,
> >
> > I reviewed the list of issues that were posted to draft 4 but I failed
> > to see my feedback on excluding private use tags from the conformance
> > clause.  I even included specific text on this when I sent my comments.
> > If the answer to this question is hidden, please highlight it.
> >
> > This is an important issue and it should be addressed as part of your
> > "disposition of comments".  What I suggested is similar to what has been
> > done for private use area of 10646/Unicode.  All private use characters
> > in 10646/Unicode are not part of the conformance clause.  Private Use
> > should be based on an agreement between sender and receiver only.
> >
> > I would be more than happy to re-forward that.
> >
> > Can you please specify what is the timeline for continuing to develop
> > RFC 3066bis, what are the next steps in this process at IETF and when is
> > it expected to be published.
> >
> > Mike Ksar
> >
> > ________________________________
> >
> > From: ietf-languages-bounces at alvestrand.no on behalf of Mark Davis
> > Sent: Sun 7/11/2004 5:50 PM
> > To: Mark Davis; Doug Ewell; ietf-languages at iana.org
> > Subject: Re: Sample IANA language subtag registry
> >
> >
> >
> > I waded through the email, and put some responses on
> > http://www.macchiato.com/misc/3066bis.html. Please let me know if you
> > have
> > any further feedback.
> >
> > ?Mark
> >
> > _______________________________________________
> > Ietf-languages mailing list
> > Ietf-languages at alvestrand.no
> > http://www.alvestrand.no/mailman/listinfo/ietf-languages
> >
> >
> > _______________________________________________
> > Ietf-languages mailing list
> > Ietf-languages at alvestrand.no
> > http://www.alvestrand.no/mailman/listinfo/ietf-languages
> > _______________________________________________
> > Ietf-languages mailing list
> > Ietf-languages at alvestrand.no
> > http://www.alvestrand.no/mailman/listinfo/ietf-languages



More information about the Ietf-languages mailing list