[
Lists Home |
Date Index |
Thread Index
]
PASWA and XForms appear to be compatible.
In XForms 1.0 we allow binary data submission in one of three ways:
1. As RFC 2388 multipart/form-data, strictly compatible with existing
RFC 2388 servers (no XML submitted, just name/value pairs and
attachments),
which is backward compatible with XHTML and HTML form submission.
2. With xsd:base64binary or xsd:hexbinary data in the submitted instance,
with the structure surrounding the data supplied by the initial
instance and the encoding chosen by the XML Schema for the instance.
3. As in PASWA and SWA, using RFC 2387 multipart/related, with the
references to
the binary data declared as xsd:anyURI by the Schema, and structure
surrounding the data supplied by the initial instance and content
type available in the instance as well.
Given that there is no normative server-side processing model for XForms,
construction of an XML document compatible with PASWA is a matter of
starting with an initial document containing an empty xmime:MediaType
attribute and a empty xbinc:Include@href declared as xsd:anyURI,
both populated by an XForms upload form control, as illustrated below:
<html xmlns="http://www.w3.org/2002/06/xhtml2";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xforms="http://www.w3.org/2003/xforms/cr";
xmlns:xmime='http://schemas.xmlsoap.org/2003/04/xmime'
xmlns:xbinc='http://schemas.xmlsoap.org/2003/04/xbinc'
xmlns:soap='http://www.w3.org/2002/12/soap-envelope'
xmlns:m='http://example.org/stuff'
>
<head>
...
<model xmlns="http://www.w3.org/2003/xforms/cr";>
<instance>
<soap:Envelope>
<soap:Header>
<xbinc:DoInclude
soap:role='http://www.w3.org/2002/12/soap-envelope/role/next'
soap:mustUnderstand='false'
soap:relay='true' />
</soap:Header>
<soap:Body>
<m:data>
<m:photo xmime:MediaType='' >
<xbinc:Include href='' />
</m:photo>
<m:sound xmime:MediaType='' >
<xbinc:Include href='' />
</m:sound>
</m:data>
</soap:Body>
</soap:Envelope>
</instance>
<bind nodeset="//xbinc:Include@href" type="xsd:anyURI" />
<submission action="..." method="multipart-post" ... />
</model>
</head>
<body>
<group xmlns="http://www.w3.org/2003/xforms/cr";>
<upload ref="/m:data/m:photo/xbinc:Include@href" mediatype="image/png">
<label>Photo</label>
<mediatype ref="/m:data/m:photo@xmime:MediaType"/>
</upload>
<upload ref="/m:data/m:sound/xbinc:Include@href" mediatype="audio/mpeg">
<label>Sound</label>
<mediatype ref="/m:data/m:sound@xmime:MediaType"/>
</upload>
</group>
</body>
</html>
-----Original Message-----
From: Dare Obasanjo [mailto:dareo@microsoft.com]
Sent: Wednesday, May 07, 2003 2:46 PM
To: Chiusano Joseph; xml-dev@lists.xml.org
Subject: RE: [xml-dev] DIME - Status?
This may help
http://www.gotdotnet.com/team/dbox/default.aspx?key=2003-04-22T06:50:29Z
--
PITHY WORDS OF WISDOM
If at first you don't succeed, imitate.
This posting is provided "AS IS" with no warranties, and confers no
rights.
> -----Original Message-----
> From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
> Sent: Wednesday, May 07, 2003 2:05 PM
> To: xml-dev@lists.xml.org
>
> Does anyone have any information on the status of DIME? The
> IETF draft [1] expired in December 2002.
>
> Kind Regards,
> Joe Chiusano
> Booz | Allen | Hamilton
>
> [1]
> http://msdn.microsoft.com/library/en-us/dnglobspec/html/draft-
nielsen-dime-02.txt
-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>
|
