- From: Norman Walsh <ndw@nwalsh.com>
- Date: Thu, 12 Jul 2007 07:53:39 -0400
- To: public-xml-processing-model-wg@w3.org
- Message-ID: <87lkdlzvlo.fsf@nwalsh.com>
/ Alex Milowski <alex@milowski.org> was heard to say:
| Here's what I've updated:
|
| * Added authentication support to p:http-request
Where? The "attributes" username, password, and friends are mentioned
in the prose but they aren't options on p:http-request or attributes
on c:http-request, so I'm confused.
| * Added encoding and charset options to p:unescape-markup to work
| better with p:http-request results that are encoded.
The unescape-markup step says:
Further, if the namespace option is specified, the default namespace
is declared on that wrapper element.
But in the example:
<description>
<p xmlns="http://www.w3.org/1999/xhtml">This is a chunk.</p>
<p xmlns="http://www.w3.org/1999/xhtml">This is a another chunk.</p>
</description>
The namespace is not specified on the wrapper element. On balance, I
think the example is a better idea than the prose since adding a
default namespace to the wrapper would usually change its name.
| * Added text describing how xsl:output is ignored in p:xslt as we
| don't serialize
|
| * Added text describing how p:xslt must produce a well-formed document.
Good.
| * Added serialization options to p:store and p:http-request
I thought we were going to have a simple "store" component that didn't
require implementing the full richness of the XSLT 2.0 serialization
story and an optional "serialize" step that would.
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | Time is a great teacher, but
http://nwalsh.com/ | unfortunately it kills all its
| pupils.-- Berlioz
Received on Thursday, 12 July 2007 11:53:48 UTC