W3C home > Mailing lists > Public > www-voice@w3.org > January to March 2007

Re: Question about tag-format in SISR specification

From: Dave Burke <david.burke@voxpilot.com>
Date: Sat, 24 Mar 2007 16:08:03 +0000
To: "Shyam K. Madhusudhana" <ShyamMadhusudhana@LumenVox.com>
Cc: www-voice@w3.org
Message-id: <46054CE3.6050107@voxpilot.com>

Hi Shyam,

Early implementations of specifications - such as the implementation of 
SISR provided by your company - greatly helps the ultimate quality of 
the specification. The downside of early implementations is that the 
specification is subject to change. I appreciate this can be annoying 
for developers on both the platform and application side.

The only official specifications are W3C  Recommendations however, and 
other maturity levels (e.g.  Last Call Working Draft, etc)  should be 
considered "works in progress". The good news is that SISR is very close 
to the Recommendation stage (watch this space!) and any future official 
version of the specification will certainly carry a different tag-format 
as you suggest.

Thanks,

Dave


Shyam K. Madhusudhana wrote:
> Hi,
>     We, at LumenVox, have been supporting the 2004 specification of 
> SISR. Now we're trying to move on with the latest specification. There 
> have been quite a few major changes in the latest specification. 
> However, the /tag-format/ can still only assume either /semantics/1.0/ 
> or /semantics/1.0-literals/. A change in the tag version number is 
> something that is really needed. Something like /semantics/1.1/ or 
> /semantics/2.0/.
>  
>     Most of our clients use grammars that follow the older 
> specification, so we would definitely want to be backward compatible 
> for some time. People that test and rate our products go with the 
> latest available standards, so we need to to be compatible with the 
> new specification too. But, with same version numbers for two 
> drastically different specifications, it wouldn't be easy to 
> distinguish one from the other. The specification documents do not 
> address this issue.
>  
>     Why is the version number not being changed with every 
> specification? Will the next specification have a change in the tag 
> version number, or do you suggest any ways of handling the issue?
>  
>     Thank you.
>  
> Regards,
> Shyam
>  
> ------------------------------------------------------------------------
> Shyam Kumar Madhusudhana
>  
> P: 858-707-0707 Just say "Shyam" (or ext 176)
> F: 858-707-7072
> shyam@LumenVox.com
>  
> <http://www.lumenvox.com/>
>  
> Internet Telephony Product of the Year
> IP Contact Center Technology Pioneer Award
> Speech Technology Excellence Award
>  
Received on Saturday, 24 March 2007 16:09:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 24 March 2007 16:09:50 GMT