URI style and IRI support

This email is the result of the my action item:

  Hugo to continue to look at IRI style/URI style, due 2005-05-26. (LC74a)

I have approached I18N folks with questions about our IRI support. I
believe that we can safely rename the URI style to IRI style, and make
the following change in the specification.

We currently say:

  Note: Element name and element content MUST be URI escaped when
  inserted into the request, as defined in "Serialization as
  application/x-www-form-urlencoded" ([XForms 1.0], Section 11.6).

  In this serialization, the value of the {http location} property is
  used as a template which is combined with the {address} property of
  the endpoint element to form the full URI to be used in an HTTP
  request, as specified in section 5.6.2 Relationship to WSDL
  Component Model.

  -- http://www.w3.org/TR/2005/WD-wsdl20-adjuncts-20050510/#_http_x-www-form-urlencoded

We should change that too:

  In this serialization, the value of the {http location} property is
  used as a template which is combined with the {address} property of
  the endpoint element to form the full IRI to be used in an HTTP
  request, as specified in section 5.6.2 Relationship to WSDL
  Component Model.

  This IRI MUST be mapped to an URI for use in the HTTP Request as per
  section 3.1 "Mapping of IRIs to URIs" of the IRI specification [RFC
  3987].

If people are happy with this change, we will be able to close LC74a
by adding the URI style section to the list of sections that need to
be migrated from URI to IRI.

Cheers,

Hugo

-- 
Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/