FWIW, "a printed domain name can be up to 254 characters." From http://www.ietf.org/rfc/rfc0882.txt?number=882
gg
> -----Original Message-----
> From: Hollenbeck, Scott [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 15, 2003 10:47
> To: '[EMAIL PROTECTED]'
> Subject: RE: Treatment of anyURI in release 2.5.0
>
> > I guess the best way to summarize the behavior is by way of a
> > pattern. I
> > tested using values of the form:
> >
> > telnet://[a-z]{n}.com
> >
> > and found that, for values of n <= 62, the values was
> > accepted, but when
> > n >= 64, the value is rejected as being outside the value space for
> > anyURI. It looks as if Xerces is imposing a length
> > restriction on anyURI
> > which has not been imposed in previous releases I have used
> > (specifically, release 2.4.0 does not exhibit this behavior).
> >
> > I note that the values I am using, as can be seen from the pattern,
> > contain only two components in the hostname, the first of
> > which can be
> > very long (and not necessarily very sensible :-) ). Here's an example:
> >
> >
> > telnet://effortstandardsbesenseorganizationsecfordevelopedtoac
> cessibleb.com
>
> I've checked the Schema REC and errata, as well as the relevant RFCs and
> sections of XLink and XML Core, and can find no mention of a constraint
> on the length of the anyURI datatype, on URIs in general, or on the
> components of URIs.
>
> Have I missed something? Any feedback gratefully appreciated.
>
> RFC 1034 (sections 3.1 and 3.5) limits the length of domain name labels
> (the
> strings between the dots) to a maximum of 63 characters. Perhaps that has
> something to do with the behavior you're seeing.
>
> Scott Hollenbeck
> VeriSign Naming and Directory Services
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
