[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [wsrp-wsia] [I#165] The Consumer should not strip the namespa ceprefix from f orm parameters
Hi Gil.
I think that you are right, encoding of the parameter names in a form is
not necessary. However we will need to namespace the form name. The
paragraph on stripping the namespace from that name when making a WSRP call
still holds true.
Best regards
Carsten Leue
-------
Dr. Carsten Leue
Dept.8288, IBM Laboratory B�blingen , Germany
Tel.: +49-7031-16-4603, Fax: +49-7031-16-4401
Gil Tayar
<Gil.Tayar@webcol
lage.com> To
"'wsrp-wsia@lists.oasis-open.org'"
12/17/2002 01:55 <wsrp-wsia@lists.oasis-open.org>
PM cc
Subject
RE: [wsrp-wsia] [I#165] The
Consumer should not strip the
namespa ce prefix from f orm
parameters
Another point to note is that HTML/XHTML does not require uniqueness of
form control names across the HTML. This is because the deciding attribute
for form controls is "name", which does not have to be unique, and not
"id", which does (see
http://www.w3.org/TR/html401/interact/forms.html#h-17.2). Thus, Producers
doesn't need to prefix anything to form names, and thus it is pointless for
the Consumer to strip namespaces. We should also stress this fact in the
spec.
Gil
-----Original Message-----
From: Gil Tayar [mailto:Gil.Tayar@webcollage.com]
Sent: Sun, December 01, 2002 13:13
To: wsrp-wsia@lists.oasis-open.org
Subject: [wsrp-wsia] [I#165] The Consumer should not strip the
namespace prefix from f orm parameters
Issue: 165
Status: Active
Topic: interface
Class: Technical
Raised by: Gil Tayar
Title: The Consumer should not strip the namespace prefix from form
parameters
Date Added: 1-Dec-2002
Document Section: v0.85/9.3
Description:
"Quoting from the spec: ""If namespace encoding is used for form
parameters or other data the entity receives as in markupParams, then
the Consumer MUST strip the namespace prefix from the parameter names
before passing them to the Producer"".
believe the Consumer should not do this for two reasons:
1. It now means that the Consumer has to understand the uploadData
and recognize one of the mime types, specifically
application/x-www-form-urlencoded. This is definitely not generic.
2. The Producer will anyway have to understand namespace prefixing,
including using it in JavaScript client code, so its not that big of
a chore for the Producer to do this (for example, by adding another
form parameter which includes the prefix code)."
Resolution:
Gil Tayar
WebCollage
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC