Printer Services Mail Archive: PS> XML Updates

PS> XML Updates

From: HALL,DAVID (HP-Vancouver,ex1) (dhall@hp.com)
Date: Tue Apr 02 2002 - 11:08:59 EST

  • Next message: BERKEMA,ALAN C (HP-Roseville,ex1): "PS> [PSI]: next 4/9 8:00:am Pacific"

    Hi guys - I snipped the XML updates out of the doc. Dave
    1.1 OffRampIdentifier
    The OffRampIdentifier is an XML document. Example OffRampIdentifiers
    follow:
    See bluetooth definitions for additional identifier attributes... The idea
    is to not only define the identifier for the offramp, but also everything
    you need to know in order to establish a connection with the identifier.
    Have a separate XML DTD for each OffRampIdentifier Type.
    UNC
    <XML>
            <offramp type="unc">
                    <identifier>
                            <\\server\share>
                    </identifier>
            </offramp>
    </XML>

    Port 9100
    <XML>
            <offramp type="rawport">
                    <identifier>
                            <IPAddress>IP</IPAddress>
                            <PORT>PORT</PORT>
                            <USER>user</USER>
                            <PASSWORD>password</PASSWORD>
                    </identifier>
            </offramp>
    </XML>

    FAX
    <XML>
            <offramp type="fax">
                    <identifier>
                            phone <\\server\share> number and other stuff
                    </identifier>
            </offramp>
    </XML>

    Offramp JobControl Soap Endpoint
    <XML>
            <offramp type="offrampjobcontrolsoapendpoint">
                    <identifier>
                            http://a/b/c
                    </identifier>
            </offramp>
    </XML>

    1.2 Reference
    The reference passed into AddContentReference is an XML document. Example
    References follow:
    Also defined in bluetooth URL definition...
    Document URL
    <XML>
            <reference type="documentURL">
                    <identifier>
                            http://a/b/c
                    </identifier>
            </offramp>
    </XML>

    Secure Document URL
    <XML>
            <reference type="securedocumentURL">
                    <identifier>
                            https://a/b/c
                    </identifier>
            </offramp>
    </XML>

    Document via FTP
    <XML>
            <reference type="FTP">
                    <server>
                            hostname or ip
                    </server>
                    <user>
                            username
                    </user>
                    <password>
                            password
                    </password>
                    <identifier>
                            \a\b\c\d\e.doc
                    </identifier>
            </offramp>
    </XML>

    Another possibility is to simply pass these parameters on the URL. We would
    need to be sure and define the schemas with a DTD...



    This archive was generated by hypermail 2b29 : Tue Apr 02 2002 - 11:09:18 EST