Personalization module renaming discussion

Link to - Work statement

The mission of the Personalization Task Force is to refine the Personalization Semantics specification, in consultation with the APA Working Group. The task force provides a focused forum for this work while the Working Group continues its work on APA development. Personalization Semantics was listed in the APA charter as "User Context" but was renamed as work progressed.

Current titles

• Personalization Semantics Content Module 1.0
• Personalization Help and Support 1.0
• Personalization Tools 1.0

Note: Comments included in this document are from the Personalization Task Force Teleconference 24 January 2022

Overall comments:

• Provisional titles for subsequent modules (after Content Module).
• It is useful to lock in the first and third words.
• COGA's concerns re: metadata and implementation. Limiting the scope and strong consensus is required.
• The word "personalization" doesn't sit well as it can be misinterpreted.
• Whatever is left of the colon in the title will remain consistent.

Suggested names

Personalization: Module

Comments:

Personalization Semantics: [name] Module

Comments:

• Pulling the word "semantics" increases our options for naming.
• Returning to semantics, one of the keys in the attributes is to support other modalities, including highlighting buttons. we are facilitating the ability to point things out and tagging them with metadata.
• We are adding semantics to elements via metadata.
• I like adding semantics to elements that cause them to be machine-readable.

Personalization: Adaptive [name] Module

Comment:

• The inter-webs have this "Adaptive content is a content strategy technique designed to support meaningful, personalized interactions across all channels".
• I like adaptive slightly more than semantics. Adaptation is more ubiquitous. Semantics has been loaded as a term and includes some things and doesn't.

Personalization Adaptation: [name] Module

Comments:

• I strongly like using "adaptation" to the left of the colon. it really does vary strongly and pull it back into the realm of accessibility. whatever the technical means that achieves it, the point is to interact with the content. accessibility working for the minority of users.
• I also think that the scope is so wide that adaptations is more substantive.
• Adaptation is a well-known word and could move personalization into the realm of abilities.

Personalized Adaptation: [name] Module

Comments:

• "Personalized Adaptation" has a better ring to it, and is still conveying what we're doing. (Note: rather than "Personalization Adaptation").
• Personalized Adaptation is what this markup is for.
• Making content adaptable to the market of 'one'.

Personal Adaptation: [name] Module

Comments:

• Likes taking off suffixes, so Personal is more friendly than Personalization.

Adaptation: [name] Module

Comments:

Adaptable Personalization: <title> Module

• Pro: It suggests that the content CAN BE adapted, but that the spec does not prescribe how that could or should happen.
• Con: "Adaptability" for some of our proposed attributes is a bit of a stretch in practice.

Enabling Adaptation

Comments:

Programmatic Personalization: [name] Module

Comments:

Personalization Enabling Adaptation Semantics: [name] Module

Comments:

Transformation Semantics: [name] Module

Comments: other variants:

• Personalized Transformation: [name] Module
• Personalized Transformation Semantics: [name] Module (quite a mouthful!)

Some other words to consider

• Adaptive
• Individualized
• Accommodation(s)
• Alteration(s)