Protocols for XML delivery

bullet1 User requirements (applications, use cases)

bullet2 IETF WGs and BOFs

  • CNRP - name resolution
    http://www.ietf.org/html.charters/cnrp-charter.html

    http://www.ietf.org/rfc/rfc2972.txt

    http://www.ietf.org/internet-drafts/draft-ietf-cnrp-12.txt

    http://www.ietf.org/internet-drafts/draft-ietf-cnrp-uri-07.txt



    » See document: http://www.ietf.org/html.charters/cnrp-charter.html
     
  • IOTP - trade
    http://www.ietf.org/html.charters/trade-charter.html

    http://www.ietf.org/rfc/rfc2801.txt

    http://www.ietf.org/rfc/rfc2935.txt



    » See document: http://www.ietf.org/html.charters/trade-charter.html
     
  • WebDav
    http://www.ietf.org/html.charters/webdav-charter.html

    http://www.ietf.org/rfc/rfc2518.txt



    » See document: http://www.ietf.org/html.charters/webdav-charter.html
     
  • IMPP
    http://www.ietf.org/html.charters/impp-charter.html

    http://www.ietf.org/rfc/rfc2779.txt

    http://www.ietf.org/rfc/rfc2778.txt

    http://www.ietf.org/internet-drafts/draft-ietf-impp-cpim-msgfmt-06.txt

    http://www.ietf.org/internet-drafts/draft-ietf-impp-cpim-pidf-05.txt



    See also:

    http://xml.coverpages.org/cpim.html



    » See document: http://www.ietf.org/html.charters/impp-charter.html
    » See also: CPIM
     
  • OPES
    http://www.ietf.org/html.charters/opes-charter.html

    http://www.ietf.org/internet-drafts/draft-ietf-opes-architecture-03.txt

    http://www.ietf-opes.org/documents/draft-beck-opes-irml-02.txt

    The OPES ruleset is proposed to be XML;  the OPES callout protocol will need to be able to deliver this together with arbitrary requests.


    » See document: http://www.ietf.org/html.charters/opes-charter.html
     
  • Calendaring
    http://www.ietf.org/html.charters/calsch-charter.html

    (Currently does not use XML, but this is an application area with a lot of XML interest.)


    » See document: http://www.ietf.org/html.charters/calsch-charter.html
     
  • XMLconf BOF
    BOF at 54th IETF, Yokohama

    http://www.ietf.org/ietf/02jul/xmlconf.txt


    » See document: http://www.ietf.org/ietf/02jul/xmlconf.txt
     
  • INCH - incident handling BOF
    http://www.ietf.org/ietf/02jul/inch.txt

    http://www.ietf.org/internet-drafts/draft-meijer-inch-iodef-00.txt



    » See document: http://www.ietf.org/ietf/02jul/inch.txt
     

bullet2 Others

  • Web services
    http://www.w3.org/2002/ws/



    » See document: http://www.w3.org/2002/ws/
     
  • Metadata and distribution
    XMLs flexibility makes it particularly attractive for constructing metadata and annotations

    http://www.w3.org/Metadata/

    http://dublincore.org/

    http://www.ietf.org/html.charters/webdav-charter.html

    http://www.ifla.org/II/metadata.htm

    http://www.ukoln.ac.uk/metadata/


    Also consider:

    calendaring

    vCard

    RFC2822 and MIME



     
  • Workflow
    http://www.wfmc.org/

    http://www.wfmc.org/standards/docs.htm



    » See document: http://www.wfmc.org/
     
  • Telecoms?
    ftp://ftp.t1.org/T1M1/NEW-T1M1.0/2m100022.doc

    ftp://ftp.t1.org/T1M1/NEW-T1M1.0/2M100910.txt



    » See document: http://www.itu.int/home/index.html
     
  • SW agents
    http://www.daml.org/

    http://www-2.cs.cmu.edu/~softagents/

    http://agents.umbc.edu/



     
  • Anana
    http://www.ietf.org/internet-drafts/draft-anana-datastore-01.txt


    » See document: http://search.ietf.org/internet-drafts/draft-anana-datastore-01.txt
     
  • Policies
    Hmmm... "policy" is one of those much-abused terms; it's wide open.

    A working definition I saw once was "rules of behaviour".

    OASIS:

    http://www.oasis-open.org/committees/xacml/sc-model.shtml


    Possibly related:

    P3P

    Loads of commercial developments (google for XML policy rules)


     
  • Grid computing
    http://www.gridforum.org/

    http://www.gridforum.org/ogsi-wg/

    http://www.gridforum.org/ogsi-wg/drafts/GS_Spec_draft03_2002-07-17.pdf

    http://www.fawcette.com/xmlmag/2002_08/magazine/columns/signal/apatrizio/


    » See document: http://www.gridforum.org/
     
  • RPC
    My requirements for an RPC technology include both long-lived connections and the ability to pass arbitrary XML fragments in requests and receive arbitrary XML fragments in reply. I've no idea how common these needs and concerns are, given the traditional RPC use cases SOAP is aiming at.