Actually, there seems to a spec-to-spec inconsistency. In XML Namespaces 1.0, the start characters for NcName are limited to '_' and Letter, so '.' is not allowed. In XML Namespaces 1.1 (with Candidate Recommendation status), they apparently are going to say that the start character for an NcName is any NameStartCharacter except ':', so Anne's chapter and verse below, allowing '.', will apply.
But nobody is confused, right? Jeff ----- Original Message ----- From: "Anne Thomas Manes" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, August 14, 2003 6:45 AM Subject: RE: question regarding axis in tomcat > A service name is an NCname -- so the question is, are blanks allowed in > an NCname. From the XML spec, here are the requirements for an NCname > (anyone here know how to interpret Unicode?): > > > The character classes defined here can be derived from the Unicode 2.0 > character database as follows: > > * Name start characters must have one of the categories Ll, Lu, Lo, Lt, Nl. > * Name characters other than Name-start characters must have one of the > categories Mc, Me, Mn, Lm, or Nd. > * Characters in the compatibility area (i.e. with character code > greater than #xF900 and less than #xFFFE) are not allowed in XML names. > * Characters which have a font or compatibility decomposition (i.e. > those with a "compatibility formatting tag" in field 5 of the database -- > marked by field 5 beginning with a "<") are not allowed. > * The following characters are treated as name-start characters rather > than name characters, because the property file classifies them as > Alphabetic: [#x02BB-#x02C1], #x0559, #x06E5, #x06E6. > * Characters #x20DD-#x20E0 are excluded (in accordance with Unicode > 2.0, section 5.14). > * Character #x00B7 is classified as an extender, because the property > list so identifies it. > * Character #x0387 is added as a name character, because #x00B7 is its > canonical equivalent. > * Characters ':' and '_' are allowed as name-start characters. > * Characters '-' and '.' are allowed as name characters. > > > At 10:26 AM 8/14/2003 +0100, you wrote: > >Guys, > > > >Is this not an argument about web service namimg conventions? I have never > >seen a web service name with spaces (although I am fairly new to this game) > >so could someone on the list advise whether spaces in service names are > >advisable at all? > > > >Jim > > > > > -----Original Message----- > > > From: Shantanu Sen [mailto:[EMAIL PROTECTED] > > > Sent: 14 August 2003 00:23 > > > To: [EMAIL PROTECTED] > > > Subject: Re: question regarding axis in tomcat > > > > > > > > > Chris, > > > > > > I agree that this will be easier. But customers may > > > want spaces in their service names for whatever > > > reason. > > > > > > Also, this brings out a problem with the > > > MessageContext properties initialization in > > > AxisServlet. It forces me to override the get/post > > > methods where I could just override the > > > createMessageContext method if it was protected. > > > > > > Probably I should post this axis-dev. > > > > > > Shantanu > > > > > > --- chaddad <[EMAIL PROTECTED]> wrote: > > > > Shantanu - > > > > > > > > If you have control over the service, it would be > > > > easier to just remove the space from the service > > > > name. > > > > > > > > > > > > /Chris > > > > > > > > > > > > ---------- Original Message > > > > ---------------------------------- > > > > From: Shantanu Sen <[EMAIL PROTECTED]> > > > > Reply-To: [EMAIL PROTECTED] > > > > Date: Wed, 13 Aug 2003 14:05:55 -0700 (PDT) > > > > > > > > >Now if the service name has spaces e.g. "My > > > > Service", > > > > >I see a problem > > > > > >
