Applying a visual analytics intent language to generate data visualizations

1. A method, comprising:

at an electronic device having a first device type, the electronic device including one or more processors and memory storing one or more programs for execution by the one or more processors:

receiving a request directed to a data source, the request including (i) one or more intent types and (ii) one or more predefined attributes associated with the one or more intent types, each of the one or more predefined attributes limiting a respective data analysis operation of a respective intent type;

for each of the one or more intent types:

formulating a respective intent specification according to the request, including determining one or more respective properties of the respective intent specification according to the respective one or more predefined attributes and according to data fields, from the data source, specified in the request; and

generating a respective output specification that specifies a respective recommended data visualization type; and

rendering data analysis responsive to the request in accordance with the electronic device having the first device type.

2. The method of claim 1 , wherein:

the first device type comprises a display device; and

rendering the data analysis includes:

generating a respective data visualization according to the respective output specification; and

displaying the respective data visualization.

3. The method of claim 1 , wherein:

the first device type comprises a device without a display; and

rendering the data analysis includes:

converting the respective output specification into a respective verbal response and

outputting the respective verbal response.

4. The method of claim 3 , wherein:

the respective output specification includes inferred information; and

outputting the respective verbal response includes outputting a verbal description of the inferred information.

5. The method of claim 1 , wherein:

the electronic device is running a first application; and

rendering the data analysis includes rendering the data analysis in accordance with configuration parameters of the first application.

6. The method of claim 5 , wherein:

the first application includes a graphical user interface; and

receiving the request includes receiving the request via the graphical user interface.

7. The method of claim 5 , wherein:

the first application is a messaging application; and

rendering the data analysis includes:

converting the respective output specification into a text output; and

displaying the text output in the messaging application.

8. The method of claim 1 , wherein the one or more intent types include one or more of: a focus intent, a trend intent, a correlation intent, a distribution intent, a geographic intent, an encoding intent, and a fields intent.

9. The method of claim 1 , wherein the respective output specification further specifies one or more respective data visualization parameters that specify how to render a data visualization of the respective recommended data visualization type.

10. The method of claim 9 , further comprising:

for each of the one or more intent types:

applying one or more respective rules corresponding to the respective intent type to determine whether the respective intent type is ambiguous and/or underspecified; and

in accordance with a determination that the respective intent type is ambiguous or underspecified, inferring information to resolve the ambiguous and/or underspecified intent according to (i) the one or more respective rules, (ii) metadata for the data source, and (iii) metadata for data fields specified in the request; and

updating the one or more respective data visualization parameters according to the inferred information.

11. The method of claim 10 , wherein applying the one or more respective rules to determine whether the respective intent type is ambiguous and/or underspecified further includes:

in accordance with a determination that the request specifies a measurable adjective and does not specify a quantity:

establishing that the respective intent type is ambiguous; and

inferring a numeric value for the quantity.

12. The method of claim 10 , wherein the metadata for the data source includes metadata for: semantics of data fields, data field types corresponding to the data fields, statistics of the data fields, derivations of the data fields, and/or default bin sizes corresponding to the data fields.

13. The method of claim 10 , further comprising:

inferring information to resolve the ambiguous and/or underspecified intent according to context from previous requests, data fields identified in the previous requests, attributes identified in the previous requests, user-provided interpretations, and/or user-provided definitions.

14. The method of claim 9 , wherein the one or more respective data visualization parameters include: data-shaping information, encoding information, and/or an identifier corresponding to the respective intent specification.

15. An electronic device having a first device type, the electronic device comprising:

one or more processors; and

memory coupled to the one or more processors, the memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for:

receiving a request directed to a data source, the request including (i) one or more intent types and (ii) one or more predefined attributes associated with the one or more intent types, each of the one or more predefined attributes limiting a respective data analysis operation of a respective intent type;

for each of the one or more intent types:

formulating a respective intent specification according to the request, including determining one or more respective properties of the respective intent specification according to the respective one or more predefined attributes and according to data fields, from the data source, specified in the request; and

generating a respective output specification that specifies a respective recommended data visualization type; and

rendering data analysis responsive to the request in accordance with the electronic device having the first device type.

16. The electronic device of claim 15 , further comprising:

a display; and

the instructions for rendering the data analysis includes instructions for:

generating a respective data visualization according to the respective output specification; and

displaying the respective data visualization.

17. The electronic device of claim 15 , wherein:

the electronic device does not have a display; and

the instructions for rendering the data analysis include instructions for:

converting the respective output specification into a respective verbal response and

outputting the respective verbal response.

18. The electronic device of claim 17 , wherein:

the respective output specification includes inferred information; and

the instructions for outputting the respective verbal response include instructions for outputting a verbal description of the inferred information.

19. The electronic device of claim 15 , wherein:

the electronic device is running a first application; and

the instructions for rendering the data analysis include instructions for rendering the data analysis in accordance with configuration parameters of the first application.

20. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by an electronic device, cause the electronic device to perform operations comprising:

receiving a request directed to a data source, the request including (i) one or more intent types and (ii) one or more predefined attributes associated with the one or more intent types, each of the one or more predefined attributes limiting a respective data analysis operation of a respective intent type;

for each of the one or more intent types:

formulating a respective intent specification according to the request, including determining one or more respective properties of the respective intent specification according to the respective one or more predefined attributes and according to data fields, from the data source, specified in the request; and

generating a respective output specification that specifies a respective recommended data visualization type; and

rendering data analysis responsive to the request in accordance with the electronic device having a first device type.