Separate query-related and product-related response fields

openculinary / knowledge-graph

The RecipeRadar knowledge graph stores and provides access to recipe and ingredient relationship information.

GNU Affero General Public License v3.0

10 stars 0 forks source link

Separate query-related and product-related response fields #34

Closed jayaddison closed 4 years ago

jayaddison commented 4 years ago

Is your feature request related to a problem? Please describe. Currently the responses from the knowledge-graph contain some fields that refer to a product -- for example, is_plural and category -- and some fields that relate to the way that the query has been handled -- for example, markup.

To improve the clarity of client code, it would be useful to distinguish these underneath separate response field keys.

Describe the solution you'd like TBD

Edit 1: typo fixup

jayaddison commented 4 years ago

It may make sense to consider future support for different entity types in the knowledge-graph when making these changes.

For example, moving the direction-parser's appliances, utensils and vessels into the graph may make sense (especially for consistency regarding price and availability tracking).