W3C home > Mailing lists > Public > www-voice@w3.org > April to June 2006

Re: <data> tag under <menu>?

From: Shane Smith <safarishane@gmail.com>
Date: Mon, 8 May 2006 18:50:37 -0500
Message-ID: <8fc15e140605081650u1bfb4fa5ge0e8fd496f93ee0a@mail.gmail.com>
To: raxit@phonologies.com
Cc: "Mangesh Deshmukh" <mangeshd@genesyslab.com>, www-voice@w3.org

Raxit,

I'm not against using data in a menu, I just think the spec needs
clarification on this.  Right now it clearly wants data and var to
have the same scoping rules, and possibly either the dtd or schema
needs to be updated to reflect this.  While I personally would like to
see the menu tag just disappear, since all the functionality is
already handled by regular form/fields, if data should be available
inside menu than we need an argument for it.

Menu is really used by folks who are writing a "vxml" application, one
driven by the vxml client browser.  With products like Audium and
Nuance OSDM's taking the industry by storm, vxml is quickly becoming
just the defacto protocol to drive IVR.  As such, anything that
simplifies this protocol is a good thing, as long as functionality
isn't sacrified.  The vendors who create these vxml generation tools
would be helped by reducing the complexity of the "connectors" for
each individual platform.  (I'm guessing, but I would bet that Audium
spends as much time making their software compatible for different
implementations of vxml, as they do just making it just comply to the
spec. Either that or they charge for it.)

By reducing the scope and complexity of vxml (by removing redundant
functionality) will make vendor implementation easier, which should
cause greater compliance to the actual spec. That would make the code
more portable, and make it easier for audium, nuance, or anyone to
code connectors to individual implementations of vxml.

Does menu need to use data?  Sure, I can see it.  But do we really
even need menu?  Not so sure.

-Shane Smith-


On 5/8/06, Sheth Raxit <raxit@phonologies.com> wrote:
> Mangesh Deshmukh wrote:
>
> >There are no differences for <var> in schema and DTD. (But <var> doesn't
> >appear under <menu> in both schema and DTD). So is it safe to assume
> >that <data> is not a child of <menu>?
> >
> No.
>
> >If so, will the DTD be updated?
> >
> >
> >
> I do think dtd need to be updated, please see below,
>
> >-----Original Message-----
> >From: Shane Smith [mailto:safarishane@gmail.com]
> >Sent: Thursday, May 04, 2006 4:52 PM
> >To: Mangesh Deshmukh
> >Subject: Re: <data> tag under <menu>?
> >
> ><Data/> should be usable all the same places that <var/> is.  From the
> >2.1 spec:
> >
> >
> >
> But the Reverse may not be true,
>
> >"Like the <var> element, the <data> element can occur in executable
> >content or as a child of <form> or <vxml>. In addition, it shares the
> >same scoping rules as the <var> element."
> >
> >
> >
> Here, Element X follows Same rule as all rule followed by Y,
> But  All the rule apply to Y may NOT (correctly) apply to X.
>
> something like relation is not Symmetric.
>
> Logically if one do want to generate Menu based on some dynamic data
> then one way is of using <data> in <menu> , but at that time <var> may
> not usable( dynamic nature)
>
>
> >Are there any differences for <var> between the scheme and dtd?
> >
> >-Shane
> >
> >
> >
>
> Comment plz on this ?
>
> --
> Raxit Sheth
>
> --
>
> Raxit Sheth
> Systems Software Engineer
> Raxit@Phonologies.com
>
> ***********************
> Please note our new Address.
> ***********************
> Phonologies (India) Private Limited
> 17/18 Metro House, Colaba Causeway,
> Mumbai 400001. INDIA.
> Ph:+91-22-22029732 / 36   Fax:+91-22-22029728
>
> Info@Phonologies.COM
> http://www.phonologies.com
>
> ****The information in this email is confidential and may be legally
> privileged. It is intended solely for the addressee. Access to this email by
> anyone else is unauthorized. If you are not the intended recipient, any
> disclosure, copying, distribution or any action taken or omitted to be taken
> in reliance on it, is prohibited and may be unlawful****
>
>
Received on Monday, 8 May 2006 23:50:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 October 2006 12:49:02 GMT