#36 Problem with DSML URN

open
6
2007-10-03
2004-01-07
Anonymous
No

According to the DSML v2 documentation, the base URN
for DSMLv2 is oasis:names:tc:DSML:2:0:core; an example
request should look like

<batchRequest xmlns="oasis:names:tc:DSML:2:0:core">
<searchRequest>...</searchRequest>
</batchRequest>

Now, the presence of colons in the namespace is causing
problems to Lite.pm, in the subroutine 'find_target' at
line

eval 'local $^W; ' . "require $class";

I temporarily modified the Lite.pm module to deal with
the colons in my particular case. However, if
namespaces with colons are valid (and if I am not
doing anything wrong), Lite.pm may have to be modified
to deal with these particular cases

Discussion

  • Byrne Reese

    Byrne Reese - 2004-01-12
    • status: open --> open-wont-fix
     
  • Byrne Reese

    Byrne Reese - 2004-01-12

    Logged In: YES
    user_id=28043

    From the URI Syntax RFC:
    http://www.ietf.org/rfc/rfc2396.txt

    The colon is a reserved character that cannot be used within
    valid URNs and URIs. They must therefore be escaped.

    2.2. Reserved Characters

    Many URI include components consisting of or delimited
    by, certain
    special characters. These characters are called
    "reserved", since
    their usage within the URI component is limited to their
    reserved
    purpose. If the data for a URI component would conflict
    with the
    reserved purpose, then the conflicting data must be
    escaped before
    forming the URI.

    reserved = ";" | "/" | "?" | ":" | "@" | "&" | "="
    | "+" |
    "$" | ","

    The "reserved" syntax class above refers to those
    characters that are
    allowed within a URI, but which may not be allowed within a
    particular component of the generic URI syntax; they are
    used as
    delimiters of the components described in Section 3.

    Characters in the "reserved" set are not reserved in all
    contexts.
    The set of characters actually reserved within any given URI
    component is defined by that component. In general, a
    character is
    reserved if the semantics of the URI changes if the
    character is
    replaced with its escaped US-ASCII encoding.

     
  • Nobody/Anonymous

    Logged In: NO

    the DSML Technical Comittee decided to use this
    URN (as per the spec posted on the oasis web site)

    http://www.oasis-open.org/committees/dsml/docs/DSMLv2.doc

    Oasis actually registered their URN via an RFC (RFC
    3121) and the colon is not a reserved character for
    URNs (RFC 2141).

     
  • Martin Kutter

    Martin Kutter - 2007-10-03

    Logged In: YES
    user_id=884175
    Originator: NO

    From the XML1.0 specs:

    The Namespaces in XML Recommendation [XML Names] assigns a meaning to names containing colon characters. Therefore, authors should not use the colon in XML names except for namespace purposes, but XML processors must accept the colon as a name character.

    Looks like we have to allow this.

     
  • Martin Kutter

    Martin Kutter - 2007-10-03
    • priority: 5 --> 6
    • status: open-wont-fix --> open
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks