Personalization Tools 1.0

W3C Editor's Draft

This version:
https://w3c.github.io/personalization-semantics/tools/
Latest published version:
https://www.w3.org/TR/personalization-semantics-tools-1.0/
Latest editor's draft:
https://w3c.github.io/personalization-semantics/tools/
Editors:
(Benetech)
(W3C)
(W3C)
Richard Schwerdtfeger (Knowbility) (Editor until October 2017)

Abstract

This document list examples of the tools defined values, this is an extension of Personalization Explainer 1.0.

1. Introduction

This section is non-normative.

This document list examples of the tools defined values. This is an extension of Personalization Explainer 1.0.

Editor's note

Personalization semantics defines a set of properties and values to annotate content. The specific mechanism to apply these properties to content has not been decided. Several approaches are under consideration and future drafts will show progress. To help with understanding of the properties, this document provides many examples of personalization semantics applied to content, which show attributes beginning with the prefix "data-". This has not been decided as the chosen approach, but the simplicity supports understanding of the examples.

Status of This Document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.

This document was published by the Accessible Platform Architectures Working Group as an Editor's Draft.

Comments regarding this document are welcome. Please send them to public-personalization-tf@w3.org (archives).

Publication as an Editor's Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the W3C Patent Policy. The group does not expect this document to become a W3C Recommendation. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

This document is governed by the 1 March 2019 W3C Process Document.

2. Use Cases and Requirements

The Requirements for Personalization Semantics describes use cases and requirements. This module provides properties to fulfill requirements related to user support tools.

3. Tools

3.1 All the Step Indicator Properties

3.1.1 Step Indicator Usage

3.1.1.1 Description

The stepindicator defined values should be used whenever there is a sequence of tasks that the user is required to complete, so that users who have memory issues can keep track of the steps previously completed.



Note that there is no default value.

3.1.1.2 Example

Note, the specific mechanism to apply these defined values has not been decided:

Example 1: stepindicator using data-
      <div data-stepindicator="book trip">
        <div data-status="complete" aria-label="select flight" data-step="1" data-steplocation="uri" />
        <div data-status="current" aria-label="book hotel" data-step="2" data-steplocation="uri" />
        <div data-status="" aria-label="book car" data-step="3" data-steplocation="uri" />
        <div data-status="" aria-label="purchase trip" data-step="4" steplocation="uri" />
      </div>

      

or the step number can be implied by the DOM



        <div data-stepindicator="book trip">
          <div data-status="complete" aria-labelledby="select flight">
            <a href="uri">Select flight</a>
          </div>
          <div data-status="current" aria-labelledby="book hotel">
            <a href="uri">Book Hotel</a>
          </div>
          <div data-status="" aria-labelledby="book car">
            <a href="uri">Book car</a>
          </div>
          <div data-status="" aria-labelledby="purchase trip">
            <a href="uri">Purchase trip</a>
          </div>
        </div>    
     

3.2 All the message properties

3.2.1 messageimportance

3.2.1.1 Description

The messageimportance attribute is used to indicate the priority level of a message . This can be helpful for a person who gets overwhelmed with messages and filter out low messages and concentrate on critical priority messages.

Supported values: low, medium(Default), critical

3.2.1.2 Example

The specific mechanism to apply these defined values has not been decided

Example 2: messageimportance using data-
        <div role="alert" data-messageimportance="medium">
            It is your daughter's birthday tomorrow
        </div>
    
3.2.1.3 Characteristics
Characteristic Value
Related Concepts:
Used in Roles: All elements of the base markup
Inherits into Roles: Placeholder
Value: token
3.2.1.4 Values
Value Description
critical To be critical a message needs to be both urgent and content that the user is very likely to consider important. For example, a system may send a message that it is going to reboot in one minute to install updates.
medium (default) Important messages that needs the user's attention at their convenience. For example, a relatively important chat message.
low A message that does not need time sensitive attention. For example, a typical chat message.

3.2.2 messagefrom

3.2.2.1 Description

The messagefrom attribute can be used to help identify who a message a user receives is from.

Supported values: a string value that identifies the sender of the message. If multiple names are used they can be separated by a comma.

Note that there is no default value.

3.2.2.2 Example

The specific mechanism to apply these defined values has not been decided

Example 3: messagefrom using data-
        <div role="alert" data-messageimportance="low"
            data-messagefrom="lisa seeman, lseeman">
            I posted a new version on GitHub for you to review
        </div>
        
3.2.2.3 Characteristics

The specific mechanism to apply these defined values has not been decided

Characteristic Value
Related Concepts:
Used in Roles: All elements of the base markup
Inherits into Roles: Placeholder
Value: string text

3.2.3 messagecontext

3.2.3.1 Description

The messagecontext attribute can help clarify where a message is coming from. Knowing who the message is from as well as in which context the message was written are both importent in understanding the meaning of the message received.

Supported values: a string value that identifies the location that makes this message relevant. Typical values are "home" and "work". If multiple locations are relevant they can be separated by a coma.

Note that there is no default value.

3.2.3.2 Example

The specific mechanism to apply these defined values has not been decided

Example 4: messagecontext using data-
    <div role="alert"
        data-messageimportance="low"
        data-messagefrom="lisa seeman, lseeman"
        data-messagecontext="work">
        I posted a new version on GitHub for you to review
    </div>
    
3.2.3.3 Characteristics
Characteristic Value
Related Concepts:
Used in Roles: All elements of the base markup
Inherits into Roles: Placeholder
Value: string text

3.2.4 messagetime

3.2.4.1 Description

The messagetime attribute helps clarify when the message was sent.

Supported values: 24 hour date time format. DD.MM.YEAR.HOUR.MM - DD.MM.YEAR.HOUR.MM where the second date is an optional exclusive expiry date.

Note that there is no default value.

3.2.4.2 messagetime

The specific mechanism to apply these defined values has not been decided

@@1-line description

Example 5: messagetime using data-
    <div role="alert"
        data-messageimportance="medium"
        data-messagefrom="my calender"
        data-messagecontext="work"
        data-messagetime="10.02.2017.00.00-16.02.2017.00.00">
        Renew your driving license this week
    </div>



    <div role="alert"
        data-messageimportance="critical"
        data-messagefrom="my calender"
        data-messagecontext="work"
        data-messagetime="16.02.2017.00.00">
        Renew your driving license ASAP
    </div>
    
3.2.4.3 Characteristics

The specific mechanism to apply these defined values has not been decided

Characteristic Value
Related Concepts:
Used in Roles: All elements of the base markup
Inherits into Roles: Placeholder
Value: string text

A. Vocabulary Implementations

The vocabulary implementations of this document is available at Personalization Explainer 1.0 Vocabulary Implementations section.

B. Acknowledgments

This section is non-normative.

The following people contributed to the development of this document.

B.1 Participants active in the Personalization TF at the time of publication

B.2 Other Personalization TF contributors, commenters, and previously active participants

B.3 Enabling funders

This publication has been funded in part with U.S. Federal funds from the Health and Human Services, National Institute on Disability, Independent Living, and Rehabilitation Research (NIDILRR) under contract number HHSP23301500054C. The content of this publication does not necessarily reflect the views or policies of the U.S. Department of Health and Human Services, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government. Some of the work on this project has also received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No.780529 and 643399.

C. References

C.1 Informative references

[DOM4]
DOM Standard. Anne van Kesteren. WHATWG. Living Standard. URL: https://dom.spec.whatwg.org/
[SVG2]
Scalable Vector Graphics (SVG) 2. Nikos Andronikos; Rossen Atanassov; Tavmjong Bah; Amelia Bellamy-Royds; Brian Birtles; Cyril Concolato; Erik Dahlström; Chris Lilley; Cameron McCormack; Doug Schepers; Dirk Schulze; Richard Schwerdtfeger; Satoru Takagi; Jonathan Watt et al. W3C. W3C Working Draft. URL: http://www.w3.org/TR/2015/WD-SVG2-20150915/