W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > April 2007

More defaulting

From: Norman Walsh <ndw@nwalsh.com>
Date: Tue, 24 Apr 2007 12:38:59 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <87647lohgc.fsf@nwalsh.com>
Consider:

<p:serialize>
  <p:option name="href" value="/tmp/out.xml"/>
  <p:option name="method" value="html"/>
</p:serialize>

I wonder if we should allow that to be written as:

<p:serialize href="/tmp/out.xml" method="html"/>

I wonder if we should also allow

  <p:option name="href" value="/tmp/out.xml"/>

to be expressed as

  <p:option href="/tmp/out.xml"/>

I have mixed feelings about both of these, but I find myself doing the
latter by accident sometimes and wishing for the former. Now that we
have options and parameters clearly distinct, it doesn't seem totally
unreasonable to do this.

In both cases, I would expect the attribute values to be taken literally.
If you want a select, you have to do it the long way:

  <p:option name="href" select="concat($basedir,'foo.html')"/>

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | The great man is he who has not lost
http://nwalsh.com/            | the heart of a child.-- Mencius

Received on Tuesday, 24 April 2007 16:39:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:50 GMT