SpeakQL: Towards Speech-driven Multimodal Querying

SpeakQL: Towards Speech-driven Multimodal Querying
复制标题

SpeakQL:迈向语音驱动的多模式查询

DOI:
10.1145/3299869.3300093
复制
发表时间:
2019
期刊:
Proceedings of the 2019 International Conference on Management of Data
影响因子:
--
通讯作者:
Vraj Shah
Vraj Shah
中科院分区:
--
文献类型:
--
作者:
Vraj Shah

文献摘要

被引文献

相似文献

基于语音的输入已经在受限设备环境(诸如智能手机和平板电脑,甚至个人会话助理(诸如Siri、Alexa和Cortana))上的许多应用中变得流行。受语音驱动界面最近成功的启发,在这项工作中,我们考虑一个重要的基本问题:应该如何设计一个语音驱动的系统来查询结构化数据?最近的工作已经研究了新的查询模式,如视觉[4,8],基于触摸的[3,7]和自然语言界面(NLI)[5,6],特别是对于受限的查询环境,如平板电脑,智能手机和会话助理。然后,用户给出的命令被转换为结构化查询语言(SQL)。但它的缺席是一个语音驱动的接口,用于常规SQL或其他结构化查询。有人可能会问:为什么要规定结构化查询,而不只是使用NLI或可视化界面?从实践的角度来看,许多用户,包括C套件、企业、Web和其他领域的用户,已经熟悉SQL(即使只是它的一个子集),并经常使用它。一个口语SQL接口可以帮助他们加快查询规范,特别是在智能手机和平板电脑等受限环境中,输入SQL将是痛苦的。更基本的是,任何查询接口都有一个内在的权衡,如图1(A)所示。
Speech-based inputs have become popular in many applications on constrained device environments such as smartphones and tablets, and even personal conversational assistants such as Siri, Alexa, and Cortana. Inspired by this recent success of speech-driven interfaces, in this work, we consider an important fundamental question: How should one design a speech-driven system to query structured data? Recent works have studied new querying modalities like visual [4, 8], touch-based [3, 7], and natural language interfaces (NLIs) [5, 6], especially for constrained querying environments such as tablets, smartphones, and conversational assistants. The commands given by the user are then translated to the Structured Query Language (SQL). But conspicuous by its absence is a speech-driven interface for regular SQL or other structured querying. One might wonder: Why dictate structured queries and not just use NLIs or visual interfaces? From a practical standpoint, many users, including in the C-suite, enterprise, Web, and other domains are already familiar with SQL (even if only a subset of it) and use it routinely. A spoken SQL interface could help them speed up query specification, especially in constrained settings such as smartphones and tablets, where typing SQL would be painful. More fundamentally, there is a trade-off inherent in any query interface, as illustrated in Figure 1(A).