On 4/27/06, Nestor Urquiza <[EMAIL PROTECTED]> wrote:
Cool, I vote for modifying the schema then.
Thanks!
<snip/>
If you hear back about the schema URL at the W3C, let us know (I'm on
the matching W3C list, no need to ping if its posted there).
-Rahul
--- Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> On 4/27/06, Nestor Urquiza <[EMAIL PROTECTED]>
> wrote:
> > So guys,
> > either we change the @name by @location or we do
> not
> > use the schema to validate ... thoughts?
> >
> <snip/>
>
> There is another option since you host the schema
> yourself, if you'd
> like. And thanks for following up on this promptly.
>
> Anyway, from an implementation perspective, having
> an attribute mean
> multiple things means we have to figure out
> beforehand if the
> expression is a "degenerate path", and in one form
> or the other, this
> will boil down to:
>
> <pseudo>
> if (means one thing) {
> do the thing one thing does;
> } else (means another thing) {
> do the thing another thing does;
> } else {
> throw up in the log file;
> }
> </pseudo>
>
> You get none of that with the @name and @location
> distinction (for
> "scratch space variable" and "XML data tree node"
> respectively). Also,
> as Jim mentions, the WD is subject to change WRT the
> data model, so I
> don't know if we should urgently move to a
> sub-optimal impl for
> assign, especially since the @name usage does appear
> in the var
> section of the draft.
>
> -Rahul
>
<snap/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
