W3C home > Mailing lists > Public > www-forms@w3.org > February 2004

RE: A note on <bind /> (similar to <group />)

From: Klotz, Leigh <Leigh.Klotz@pahv.xerox.com>
Date: Thu, 5 Feb 2004 14:38:08 -0800
Message-ID: <51B8ABCE456FD111899900805F6FD6EE15EDF663@mercury.ADOC.xerox.com>
To: "'Subramanian Peruvemba (PV)'" <subramanian.peruvemba@oracle.com>, "Klotz, Leigh" <Leigh.Klotz@pahv.xerox.com>
Cc: "'Mark Birbeck'" <mark.birbeck@x-port.net>, "'David Landwehr'" <dlandwehr@novell.com>, "'www-forms@w3c.org'" <www-forms@w3c.org>

Thanks PV, that's a fascinating group construct for discussion.
It's not my issue, but I will be happy to hear what the discussion is that
For now, though, I will feel comfortable in using <group/> and <bind/> as
containers in my XSLT and Xinclude files.

-----Original Message-----
From: Subramanian Peruvemba (PV) [mailto:subramanian.peruvemba@oracle.com] 
Sent: Thursday, February 05, 2004 1:04 PM
To: Klotz, Leigh
Cc: 'Mark Birbeck'; 'David Landwehr'; 'www-forms@w3c.org'
Subject: Re: A note on <bind /> (similar to <group />)

> group has uses other than setting context node, which means that it does
> need to have ref, model, or bind.

Agreed it does not need to have an context node. I never said they must 
have one. All I am saying is having a context node changes the behavior

> You may find it more explicit to say <group ref="." /> and it is a good
> for authors to write in some cases.
> But explicitness is in some cases verbosity, and in this case the
> composition rules already say what to do.

my point has been
   <group> and  <group ref=".'>  is **NOT** the same
(and that is why I like the explicitly)

In the case where group is bound to a instance node (explicitly) the 
model item properties on the node affect the state of the control bound 

Here is an example, hope this clarifies what I am trying to say

Assuming you have the following CSS rules

    group:readonly {color: red}
    group > group:readonly {color: blue}

and a document fragment that is
    <group ref="a">

and another document fragment that is

    <group ref="a">
        <group ref="."/>

Also supposing node "a" is has model item property readonly.

I think the user should see two different behaviors.
In the first case the user should see the entire fragment displayed in 
red, but in second case the inner group should be displayed in blue.

> The issue of <label>, <output>, <message>, <help>, <hint>, <alert> is, I
> think, separate from <group> which is already decided and <bind>, which I
> point out is underspecified.

Bind may be underspecified, but I am just questioning the 
interpretation. (As I said not specifying a nodeset may not be the same 
as specifying nodeset=".")

Received on Thursday, 5 February 2004 17:38:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:11 UTC