Task list for semantics
can we have an attribute such as "coga-context" and allow a URI OR a fixed value such as "action-send"
should we mark section at risk such as reminders, logs, langwage related stuff Or remove for now Or adress. (LS- change to at rist with ed notes)
Also more notes and implementation information is at the survey https://www.w3.org/2002/09/wbs/101569/2017-10-12_priorities/results
Harmonize with definitions from WCAG 2.1 - the conventional name of conventional form fields, conventional buttons or controls, or conventional links can be programmatically determined. see: https://www.w3.org/TR/WCAG21/#dfn-conventional-form-fields https://www.w3.org/TR/WCAG21/#dfn-conventional-buttons https://www.w3.org/TR/WCAG21/#dfn-conventional-links
Add short line definitions for each value from wcag 2.1
Make single lines definitions for each attribute name. Make them consistent
Adding non-coga usecases int he requirements
Attributes should be handeled consistently across the speck restructure document
make the requirement and user experience for each attribute name as well as per "topic" or high level category
Comments from MichaelC values list is long, and contains whitespace values
Comments from MichaelC : needs fleshing out values
Comments from MichaelC : needs fleshing out value descriptions
Comments from MichaelC : needs refinement and fleshing out of values
Comments from MichaelC : needs fleshing out value descriptions
Comments from MichaelC : needs complete value type restructuring
Comments from MichaelC : needs refinement / clarification of values
Comments from MichaelC : needs complete value type restructuring (LS: why?) Charles: down to three items and change terms (maybe essential - yes, med, no)
Ls: topic should be in an appendix
LS: merge with coga-concept and give two examples
coordinate with digital publishing - on charles