OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   URI Design

[ Lists Home | Date Index | Thread Index ]

    I'm working on my XML pipeline engine, Relay. I'm using special
    URIs to view information as documents. I'm creating a servlet,
    for example, that explodes the HttpServletRequest into a
    document, so I can bite into it with XSLT.


    The above document is available from the URI:


    As you can see, I get the input as a stream using:


    I parse the content of the post in a Relay, and it makes each
    form field avaialable as a stream, in case one of the fields is
    really a hidden field with an JavaScript generated XML document in it.

    Or, else, I can run a textarea through HTML Tidy, to permit mild
    markup in a comments box.

    That URI looks like:


    Which will return the first field named e-mail-address as a

    What do you all think? Am I designing these URIs correctly?

    Should I bother making them heirarcical? Or should I simply
    create my own interpreation of the scheme specific part?



Alan Gutierrez - alan@engrm.com
    - http://engrm.com/blogometer/index.html
    - http://engrm.com/blogometer/rss.2.0.xml


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS