docs: update README with approved explainer content - #2
Conversation
Naming conventions:
Chunking
Syntax
|
reillyeon
left a comment
reillyeon
left a comment
There was a problem hiding this comment.
LGTM with Tom's comments addressed.
michaelwasserman
left a comment
michaelwasserman
left a comment
There was a problem hiding this comment.
lgtm modulo Tom's comments, and a few more that deserve early consideration
|
|
||
| TODO: Fill in the whole explainer template below using https://tag.w3.org/explainers/ as a | ||
| reference. Look for [brackets]. | ||
| This proposal is an early design sketch by the Chrome Built-in AI team to |
There was a problem hiding this comment.
nit: line breaking like this isn't necessary
| rather, we are building the structural plumbing required for that inevitable, | ||
| commoditized future, and all the upsides and ergonomics it entails. | ||
|
|
||
| ## Security Considerations |
There was a problem hiding this comment.
Consider (here or followup) adding internationalization considerations, i.e. how might the API need to support content of various languages, and maybe surface supported input languages? (see other built-in AI APIs for examples)
| ## Use cases | ||
| The **Vector Store API** is a proposed Web Platform API that provides an | ||
| end-to-end semantic retrieval system entirely on the user's device. Instead of | ||
| requiring developers to manually manage vectors, the API automatically handles |
There was a problem hiding this comment.
You should explicitly frame the introduction around the end-user benefits first (e.g., privacy, offline capabilities, and performance), and only then mention the ease of authoring. You should be able to use some of the same info from the semantic embedding API explainer. end-users come before authors in the priority of constituencies https://www.w3.org/TR/html-design-principles/#priority-of-constituencies
|
Thanks for the feedback! Addressed the comments. |
SHA: 7b6ebcd Reason: push, by YinguangZhao Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
4 participants
No description provided.