Mapping Stability/Storage (was Re: M-Label or MVALID, and dangers with mappings?)
patrik at frobbit.se
Sat Apr 11 18:07:10 CEST 2009
On 11 apr 2009, at 17.57, Mark Davis wrote:
> Breaking these apart, because they are very different topics.
> I'm sympathetic to the goal, but the problem is what is meant by
> memory, APIs, modules, threads, processes, communication protocols,
> bodies, IM messages, hrefs, ...? See my email of a few weeks ago. It
> be better to focus on the transmitting of IDNAs
Long(er) term. Say longer than "direct communication" (where you can
have negotiation on features).
> I think what we can say is programs SHOULD convert to the canonical
> form before transmitting to other IDNA-aware programs, and to the A-
> form before transmitting to non-IDNA-aware programs. (The above
> isn't formal
> language, but you can see what I mean.)
Yes I do. And this "transmitting to other programs" is I think what I
mean by "storage". You "leave" the data somewhere, and someone else
will pick it up later.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://www.alvestrand.no/pipermail/idna-update/attachments/20090411/f46377fc/attachment.pgp
More information about the Idna-update