IRI

[James M Snell <ja...@gmail.com>]

Due to an unfortunate naming decision on my part, there is an interface
in org.apache.abdera.model called IRI that represents elements with IRI
values.  This conflicts, however with the new IRI implementation class I
checked in last week.  The solution is to change the name of the model
interface to something more appropriate like IRIElement.  However, I
didn't want to go changing the name of a core model interface without
checking in.

- James

Re: IRI

[Harris Boyce III <ha...@gmail.com>]

Could someone possibly review the comments that Somasegar made [1]
regarding IDN/IRI support within .NET Framework 2.0?  If the
IRNMapping class does not provide the necessary functionality, this
will most-likely be my starting point as it seems just about
everything revolves around URIs, IRIs, and XML...

Thanks,

Harris

[1] http://blogs.msdn.com/somasegar/archive/2005/09/23/472126.aspx

On 9/26/06, Garrett Rooney <ro...@electricjellyfish.net> wrote:
> On 9/26/06, James M Snell <ja...@gmail.com> wrote:
> > The only other name option I can think of that would be relevant would
> > be "AtomURI" which is the term used in the Atom spec.. but that stinks
> > also.  The only consolation I can think of is that, hopefully, folks
> > aren't going to be working directly with the element object any way. :-)
>
> Yeah, in that case it really doesn't matter, so I'm +1 on you naming
> it whatever you want ;-)
>
> -garrett
>

Re: IRI

[Garrett Rooney <ro...@electricjellyfish.net>]

On 9/26/06, James M Snell <ja...@gmail.com> wrote:
> The only other name option I can think of that would be relevant would
> be "AtomURI" which is the term used in the Atom spec.. but that stinks
> also.  The only consolation I can think of is that, hopefully, folks
> aren't going to be working directly with the element object any way. :-)

Yeah, in that case it really doesn't matter, so I'm +1 on you naming
it whatever you want ;-)

-garrett

Re: IRI

[James M Snell <ja...@gmail.com>]

The only other name option I can think of that would be relevant would
be "AtomURI" which is the term used in the Atom spec.. but that stinks
also.  The only consolation I can think of is that, hopefully, folks
aren't going to be working directly with the element object any way. :-)

- James

Garrett Rooney wrote:
> On 9/25/06, James M Snell <ja...@gmail.com> wrote:
>> Due to an unfortunate naming decision on my part, there is an interface
>> in org.apache.abdera.model called IRI that represents elements with IRI
>> values.  This conflicts, however with the new IRI implementation class I
>> checked in last week.  The solution is to change the name of the model
>> interface to something more appropriate like IRIElement.  However, I
>> didn't want to go changing the name of a core model interface without
>> checking in.
> 
> I don't particularly like the new name, but it seems like some change
> is in order, and I don't have a better name in mind.
> 
> -garrett
> 

Re: IRI

[Garrett Rooney <ro...@electricjellyfish.net>]

On 9/25/06, James M Snell <ja...@gmail.com> wrote:
> Due to an unfortunate naming decision on my part, there is an interface
> in org.apache.abdera.model called IRI that represents elements with IRI
> values.  This conflicts, however with the new IRI implementation class I
> checked in last week.  The solution is to change the name of the model
> interface to something more appropriate like IRIElement.  However, I
> didn't want to go changing the name of a core model interface without
> checking in.

I don't particularly like the new name, but it seems like some change
is in order, and I don't have a better name in mind.

-garrett