W3C home > Mailing lists > Public > xml-dist-app@w3.org > April 2001

RE: [soapbuilders] question re: namespace hierarchies

From: Dick Brooks <dick@8760.com>
Date: Fri, 20 Apr 2001 16:17:19 -0500
To: <soapbuilders@yahoogroups.com>
Cc: <xml-dist-app@w3.org>
Message-ID: <NDBBIOBLMLCDOHCHIKMGMEJOFLAA.dick@8760.com>
Henrik,

It appears that "ebXML" qualifies as a "relative-path" URI according
to the following excerpt from section 5, " Relative URI References",
in "Uniform Resource Identifiers (URI): Generic Syntax" [1]:

   A relative reference that does not begin with a scheme name or a
   slash character is termed a relative-path reference.

      rel_path      = rel_segment [ abs_path ]

      rel_segment   = 1*( unreserved | escaped |
                          ";" | "@" | "&" | "=" | "+" | "$" | "," )

   Within a relative-path reference, the complete path segments "." and
   ".." have special meanings: "the current hierarchy level" and "the
   level above this hierarchy level", respectively.  Although this is
   very similar to their use within Unix-based filesystems to indicate
   directory levels, these path components are only considered special
   when resolving a relative-path reference to its absolute form
   (Section 5.2).

   Authors should be aware that a path segment which contains a colon
   character cannot be used as the first segment of a relative URI path
   (e.g., "this:that"), because it would be mistaken for a scheme name.

[1] http://www.ietf.org/rfc/rfc2396.txt


Dick Brooks
Group 8760
110 12th Street North
Birmingham, AL 35203
dick@8760.com
205-250-8053
Fax: 205-250-8057
http://www.8760.com/

InsideAgent - Empowering e-commerce solutions

> -----Original Message-----
> From: Henrik Frystyk Nielsen [mailto:frystyk@microsoft.com]
> Sent: Friday, April 20, 2001 3:51 PM
> To: soapbuilders@yahoogroups.com
> Cc: xml-dist-app@w3.org
> Subject: RE: [soapbuilders] question re: namespace hierarchies
>
>
>
> I think this has been brought up before and so it might already be fixed
> but note that "ebxml" is not a valid value for the SOAPAction header
> field - it has to be in the form of a URI [2]. URI parsers will choke on
> a single token.
>
> Henrik
>
> PS: cc'ed xml-dist-app - full thread is at [1]
>
> [1] http://groups.yahoo.com/group/soapbuilders/message/2046
> [2] http://www.w3.org/TR/SOAP/#_Toc478383528
>
> >Here is what the current (.99) ebXML MS spec says regarding SOAPAction:
> >
> >"The mandatory SOAPAction HTTP header field must also be
> >included in the HTTP header and MAY have a value of ebXML.
> >
> >SOAPAction: ebXML
>
>
> ------------------------ Yahoo! Groups Sponsor ---------------------~-~>
> Do you have 128-bit SSL encryption server security?
> Get VeriSign's FREE Guide, "Securing Your
> Web Site for Business." Get it now!
> http://us.click.yahoo.com/2cW4jC/c.WCAA/bT0EAA/WNqXlB/TM
> ---------------------------------------------------------------------_->
>
> To unsubscribe from this group, send an email to:
> soapbuilders-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
Received on Friday, 20 April 2001 17:19:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:00 GMT