#648: Note Taking: New Note URL field
Discussions
2021-06-28
Rossen: started reading through this... First issue was that the explainer that they provided is none.. with the comment that it seems like overkill. Here's discussion, here's the spec. An opportunity to explain why we need explainers.. then start from there.
2021-07-19
Hadley: a link to an explainer - that 404s..
Amy: found it
Hadley: a bunch of user need assumptions based into this.. be nice to spell it out
Rossen: [writes comment]
2021-08-16
Ken: Thanks for the explainer. Looking at the future considerations section, I am wondering whether this is flexible enough. Why does creating a new note have to result in a URL change? I could imagine a canvas app, where I would just add a graphical overlay (post it notes) on top. Could this be a global event instead where you give the options (including future ones) as part of the event details? It doesn't look like you considered this. We would like to hear your thoughts on this.
OpenedJun 15, 2021
Kia Ora TAG!
I'm requesting a TAG review of note_taking: { new_note_url }, fields being added to the web app manifest.
eg. manifest.json
Web apps lack a semantic way of declaring and defining note-taking capabilities. This specification adds a new
note_taking
object member to the web app manifest, where note-taking capabilities can be added. It also adds the first such note-taking capability: anew_note_url
field in thenote_taking
object: a URL within scope that can be used to launch the web app in order to take a new note.Further details:
We'd prefer the TAG provide feedback as: 🐛 open issues in our GitHub repo for each point of feedback and @-notify phoglenix