Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #61 from w3c/sharon_log_section
Updates to Log section
- Loading branch information
Showing
2 changed files
with
77 additions
and
110 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,54 +1,43 @@ | ||
| <section id="use_case_log"> | ||
| <h3 id="logs">Logs</h3> | ||
| <p>This proposal is to track the tasks that a user has done, so that they can be reminded of them, and return to or fix a task. The suggested syntax should allow the author to transform some of the information into breadcrumbs via CSS, and the user system can read and present more or less information to the user as per their preferences.</p> | ||
| <p>Preferably this should be in the header so that the user agent can build a cross application log of user tasks.</p> | ||
| <p>Note that there is no default value.</p> | ||
| <p>Relevant properties: <a href="#x3-1-all-the-log-properties">log</a>, <a href="#step">step</a>, <a href="#actiontaken">actiontaken</a>, <a href="#steplocation">steplocation</a>, <a href="#status">status</a></p> | ||
| <section id="use_case_log_usage"> | ||
| <h4>Log Usage Examples</h4> | ||
| <pre><div aui-log="booking trip" aui-step="1" aria-label="buy ticket" aria-hidden="true" | ||
| aui-actiontaken="bought ticket to NY return" steplocation ="uri" /></pre> | ||
| <p>or</p> | ||
| <pre><div aui-log="booking trip" aui-step="1" aui-actiontaken="bought ticket to NY return"> | ||
| buy ticket | ||
| <a href="uri">change</a> | ||
| </div></pre> | ||
| <p>or the step number can be implied by the DOM</p> | ||
| <pre><div aui-log="booking trip"> | ||
| <div aui-actiontaken="bought ticket to NY return"> | ||
| buy ticket | ||
| <a href="uri">change</a> | ||
| </div> | ||
| </div></pre> | ||
| </section> | ||
| <section id="use_case_alternative_syntax"> | ||
| <h4>Alternative Syntax for Log</h4> | ||
| <p>Note we are considering supporting an alternative syntax such as:</p> | ||
| <pre><log name="booking trip"> | ||
| <step status ="done"> | ||
| <name>buy ticket</name> | ||
| <actiontaken>bought ticket to NY return</actiontaken> | ||
| <view changepossible="yes">url </view> | ||
| </step> | ||
| <step status ="done"> | ||
| <name>hotel</name> | ||
| <actiontaken>booked Sheraton single room</actiontaken> | ||
| <view changepossible="yes">url </view> | ||
| </step> | ||
| <step status ="current"> | ||
| <name>car rental</name> | ||
| <view current changepossible="yes"/> | ||
| </step> | ||
| </log> | ||
| </pre> | ||
| </section> | ||
| </section> | ||
| <section id="use_case_reminder"> | ||
| <h3>Reminders and Messages</h3> | ||
| <p><strong>Requirement: </strong>We require an attribute that enables different users to experience different amount of reminders and messages based on personal preferences. Reminders are a wonderful tool for many people with cognitive disabilities. However too many reminders will be annoying or distracting for some other users. Currently people can turn off distractions such as Skype, and Facebook, across different devices, and then may forget to turn them back on.</p> | ||
| <p>These semantics allow for different solutions so that users are able to focus without missing important messages. Users need to manage all distractions by forming a cross application and cross device distraction matrix that manages all distractions in one setting. It is based on a matrix for distractions at the operating system , browser or cloud level. People and users can be clustered in terms of importance or groups. For example, the CEO and your child's care giver could both be considered critical contacts. So even if they do not feel the message is urgent they can sometimes disrupt the user anyway. Some family members and important colleagues can be in another group, friends and extended family in a third group, system messages from the compliance system can be a different group again. </p> | ||
| <p>Relevant properties: <a href="#x3-2-1-messageimportance">messageimportance</a>, <a href="#x3-2-2-messagefrom">messagefrom</a>, <a href="#x3-2-3-messagecontext">messagecontext</a>, <a href="#x3-2-4-messagetime">messagetime</a></p> | ||
| </section> | ||
| <section id="use_case_general_tool"> | ||
| <h3>General Tools</h3> | ||
| </section> | ||
| <section id="use_case_stepindicator"> | ||
| <h3 id="stepindicator">Step Indicator</h3> | ||
| <p> | ||
| <b>Requirement:</b> The user must be able to track all completed tasks in a sequence of tasks so they know where they are | ||
| in the process and can be reminded of the tasks that are complete. In addition, the user must be able to navigate to | ||
| any completed task and make corrections. The suggested syntax allows the author to transform some of the information | ||
| into breadcrumbs that identify the completed tasks using CSS so that the user's system can present more or less information | ||
| to the user based on the user's preferences.</p> | ||
| <p><b>Example User Experience:</b> A breadcrumb displays in the header so that the user agent can build a | ||
| cross application step-by-step indicator that displays each task in the order it was completed | ||
| by the user. | ||
| </p> | ||
| <p>Relevant properties: | ||
| <a href="#x3-1-all-the-stepindicator-properties">stepindicator</a>, | ||
| <a href="#step">step</a>, | ||
| <a href="#steplocation">steplocation</a>, | ||
| <a href="#status">status</a> | ||
| </p> | ||
| </section> | ||
| <section id="use_case_reminder"> | ||
| <h3>Reminders and Messages</h3> | ||
| <p> | ||
| <strong>Requirement: </strong>We require an attribute that enables different users to experience different amount of reminders | ||
| and messages based on personal preferences. Reminders are a wonderful tool for many people with cognitive disabilities. | ||
| However too many reminders will be annoying or distracting for some other users. Currently people can turn off distractions | ||
| such as Skype, and Facebook, across different devices, and then may forget to turn them back on.</p> | ||
| <p>These semantics allow for different solutions so that users are able to focus without missing important messages. Users | ||
| need to manage all distractions by forming a cross application and cross device distraction matrix that manages all distractions | ||
| in one setting. It is based on a matrix for distractions at the operating system , browser or cloud level. People and | ||
| users can be clustered in terms of importance or groups. For example, the CEO and your child's care giver could both | ||
| be considered critical contacts. So even if they do not feel the message is urgent they can sometimes disrupt the user | ||
| anyway. Some family members and important colleagues can be in another group, friends and extended family in a third | ||
| group, system messages from the compliance system can be a different group again. </p> | ||
| <p>Relevant properties: | ||
| <a href="#x3-2-1-messageimportance">messageimportance</a>, | ||
| <a href="#x3-2-2-messagefrom">messagefrom</a>, | ||
| <a href="#x3-2-3-messagecontext">messagecontext</a>, | ||
| <a href="#x3-2-4-messagetime">messagetime</a> | ||
| </p> | ||
| </section> | ||
| <section id="use_case_general_tool"> | ||
| <h3>General Tools</h3> | ||
| </section> |