+1 from me to separating it out. In Woden we could really use IRI - WSDL 2.0 spec uses them, but we're having to work around this since JSE 6 dropped it.
Question about incubation though - you say IRI is part of abdera so does IRI require a graduation vote to get into jakarta commons? BTW: IMHO jakarta commons would be a great place for it - as long as we can keep the impl small. Cheers, Jeremy On 11/20/06, James M Snell <[EMAIL PROTECTED]> wrote:
I forwarded the note over to that mailing list. I have no particular preference where it ends up. - James Garrett Rooney wrote: > On 11/20/06, James M Snell <[EMAIL PROTECTED]> wrote: >> All, >> >> As part of the Abdera incubation project I've implemented support for >> IRIs that includes unicode normalization, IDNA, punycode, etc. This >> code duplicates a subset of what is provided by ICU [1] in a much >> smaller package. The intention (tho not the current reality) has been >> to make it so that if ICU was present, it's unicode and IDNA >> implementation would be used instead. >> >> In any case, I was wondering if there would be interest in separating >> the Abdera IRI implementation out into it's own commons project so that >> it can be available for more than just Abdera. Use of IRIs is growing >> and there are currently no other implementations available to Java >> developers that do not depend on ICU. > > I'm definately +1 on moving the IRI implementation out of Abdera and > into a more generically useful library, but I wonder if [EMAIL PROTECTED] is > the most appropriate place. Since there's nothing web-service > specific in needing to use IRIs, perhaps Jakarta Commons would be a > more appropriate home. > > -garrett > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
