- From: Sheth Raxit <raxit@phonologies.com>
- Date: Fri, 18 Nov 2005 3:05:52 -0500
- To: <paolo.baggia@loquendo.com>, <bkdelong@pobox.com>
- CC: <www-voice@w3.org>
Paolo,B.K.Delong and Other Members, Baggia Paolo Wrote: ==================== > > Yes, that is the interesting point, but I do not think the technology is mature today for allowing that standard or almost-standard. > > Even for Speaker Verification/Identification there is not a standard for voice prints, > but I'm not 100% sure there is not a standardization effort on this simpler task. Raxit : ======== Yes, the same stuff applies to Speaker Verification stuff also. ( and speaker verification may be the STRONG example) The Common-Format/Protocols may be one of the solutions. Other solution may be Some standard API for Migrations So that Vendor can have their own formats but with Set of Migration API to convert to standard format and Migration of ASR are not to frequently so API may be the good option. No two vendors of Speaker Verification have similar Voice Prints ( stored in file /database etc); but migration can be done if some standard set of Interface (API) is available without compromising RUN-TIME Performance and FORCE to follow standard format... (here i am assuming that Migration would not happen frequently) Technology may be one of the constraints. (can we remove the effect of constraint ?) ( Differnt Vendors of Speaker Verification may using different combinations of 'voice print' (or some voice properties ) ). But I think Technology should not be the constraint. Is there any other constraint also ? (Like Runtime performance, Securtity or any...) Waiting for reply, Thanking you, Regards 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 Friday, 18 November 2005 08:08:26 UTC