RE: SWAP Example

Looks good to me, except you didn't use the current namespace syntax.  Now
the namespace is declared the first time it is used.  Also don't forget to
close your xml tag.  Here is the first example fixed up:

<?xml version="1.0" ?> 
<d:swap xmlns:D="SWAP:"> 
  <d:observer>http://www.ics.uci.edu/pub/ietf/swap/chair.html</d:observer>
  <d:name>equipment-purchase-process</d:name> 
  <d:subject>procurement</d:subject> 
  <d:description>New equipment purchase</d:description> 
  <d:contextData> 
    <z:processor
xmlns:Z="http://conf.pcmanufact.com/">pentiumII</z:processor> 
    <z:memory> 
      <z:size>256 Meg</z:size> 
      <z:speed>60 ns</z:speed> 
      <z:type>DRAM</z:type> 
    </z:memory> 
  <!-- "name, billing address, etc." --> 
  </d:contextData> 
  <d:startImmediately>no</d:startImmediately><!-- "available?"-->
</d:swap> 
</xml>


Lisa

-----Original Message-----
From: Gregory Alan Bolcer [mailto:gbolcer@endeavors.org]
Sent: Wednesday, December 02, 1998 10:49 AM
To: SWAP Working Group
Subject: SWAP Example


Looking for feedback on the short SWAP/XML example, particularly 
from the XML/EDI folks.  

Greg


EXCERPT:

All parameters are put into an XML encoding including scoping and
namespaces to be sent with the
appropriate calls.  In the example of Figure 1, the root node has a list
of attributes including interfaces,
process instance key, valid states, actual state, and data.  From this
XML snippet, we can determine
the values and state of that process instance as well as the others
possible.  This example shows a
potential purchase order made by the SWAP working group chair using the
configuration information
provided by an online PC manufacturer.  The SWAP protocol creates a
trackable process instance
upon the request, but doesn't begin the execution of the process.  The
method call returns a value of
"207" Multi-Status indicating several different values are appropriate. 
It turns out that the size of the
memory conflicts with the order configuration.  The customer can then
choose to TERMINATE the
purchase order or amend it using the appropriate PROPFIND and PROPPATCH
methods for
assigning particular values. 
  
           >>Request 
           CREATEPROCESSINSTANCE /submit/order?proc=10 HTTP/1.1 
           Host: www.widget-makers.com 
           Content-Type: text/xml 
           Content-Length: xxxx 
           Authorization: Digest username="skreddy" 
             realm="skreddy@oracle.com", ... 

           <?xml version="1.0" ?> 
           <?xml:namespace ns="SWAP:" prefix="d" ?> 
           <?xml:namespace ns="http://conf.pcmanufact.com/" prefix="z"
?>

           <d:swap> 
          
<d:observer>http://www.ics.uci.edu/pub/ietf/swap/chair.html</d:observer>

           <d:name>equipment-purchase-process</d:name> 
           <d:subject>procurement</d:subject> 
           <d:description>New equipment purchase</d:description> 
           <d:contextData> 
                <z:processor>pentiumII</z:processor> 
                <z:memory> 
                     <z:size>256 Meg</z:size> 
                     <z:speed>60 ns</z:speed> 
                     <z:type>DRAM</z:type> 
                </z:memory> 
                <!-- "name, billing address, etc." --> 
           </d:contextData> 
           <d:startImmediately>no</d:startImmediately><!-- "available?"
-->

           </d:swap> 

           >>Response 
           HTTP/1.1 207 Multi-Status 
           Content-Type: text/xml 
           Content-Length: xxxxx 

           <?xml version="1.0" ?> 
           <?xml:namespace ns="SWAP:" prefix="d" ?> 
           <?xml:namespace ns="http://conf.pcmanufact.com/" prefix="z"
?>

           <d:multistatus> 
                <d:response> 
                     <d:processInstance> 
                         
<d:href>http://www.widget-makers.com/status?proc=10.1 
                          </d:href> 
                          <?-- "other items as defined by process" --> 
                     </d:processInstance> 
                     <d:propstat> 
                          <d:prop><z:size/></d:prop> 
                          <d:status>HTTP/1.1 409 Conflict</d:status> 
                          <d:comment>part unavailable</d:comment> 
                     </d:propstat> 
                     <d: propstat> 
                          <?-- "other resource properties" --> 
                     </d:propstat> 
                </d:response> 
           </d:multistatus>

Received on Wednesday, 2 December 1998 17:39:42 UTC