UXC Dictionary: Difference between revisions
Jump to navigation
Jump to search
Mary Hodder (talk | contribs) (updated to reflect UXC meeting 7/30/15) |
Mary Hodder (talk | contribs) (Added additional words for dictionary, etc) |
||
(One intermediate revision by the same user not shown) | |||
Line 3: | Line 3: | ||
! Term !! Definition !! Notes !! Citations | ! Term !! Definition !! Notes !! Citations | ||
|- | |- | ||
| '''User''' || Human. This does not include machines, algorithms, or other non-human agents or actors. || Our perspective is that this definition applies this way in any context in the IDESG framework. We suggest changing the use of USER for other meanings to another word. Note that the NSTIC document (see citation) names "user" as separate from devices and processes here on page 8: "Technology and processes for identification (establishing unique digital identities) and authentication (verifying the identity of a | | '''User''' || Draft: Individual Human-Being. This does not include machines, algorithms, or other non-human agents or actors. Rough Equivalents: Terms in the Common Semantic Domain found in the NSTIC Strategy include: | ||
* user | |||
* user centric | |||
* user centered | |||
* user-centered | |||
* human-centered | |||
* human centered | |||
* end-user | |||
* end user | |||
* individual user | |||
* user-friendly || Our perspective is that this definition applies this way in any context in the IDESG framework. We suggest changing the use of USER for other meanings to another word. Note that the NSTIC document (see citation) names "user" as separate from devices and processes here on page 8: "Technology and processes for identification (establishing unique digital identities) and authentication (verifying the identity of a | |||
user, process, or device) are at the forefront of this Strategy " NSTIC Document: https://www.idecosystem.org/idesgwiki/images/b/bc/Full_NSTIC_Strategy_Document_-_04152012_ARR_Annotated_for_user_centric.pdf | user, process, or device) are at the forefront of this Strategy " NSTIC Document: https://www.idecosystem.org/idesgwiki/images/b/bc/Full_NSTIC_Strategy_Document_-_04152012_ARR_Annotated_for_user_centric.pdf | ||
|| | || | ||
|- | |- | ||
| '''User-centric''' || | | '''User-centric''' || DRAFT Systems, design and / or program processes that put the individual human being at the center of the activity. Rough Equivalents: user centric, user centered, user-centered, human-centered, human centered, end-user, end user, individual user, user-friendly. || Sample usage from NSTIC: | ||
*"The realization of this vision is the user-centric “Identity Ecosystem” described in this Strategy."P8 | *"The realization of this vision is the user-centric “Identity Ecosystem” described in this Strategy."P8 | ||
Line 29: | Line 39: | ||
|- | |- | ||
| '''Third Parties''' || Example || re: supplemental on Usable 3: research systems that display entities on a page or system. consider burden on user vs. accessibility of entities list) || Example | | '''Third Parties''' || Example || re: supplemental on Usable 3: research systems that display entities on a page or system. consider burden on user vs. accessibility of entities list) || Example | ||
|- | |||
| '''Third Party Tracking''' || Example || NOTE: revisit as necessary per Privacy and other groups def.s || Example | |||
|- | |- | ||
| '''Pseudonymous''' || An interaction designed such that the data collected is not sufficient to allow the entity to infer the user involved but which does permit an entity to associate multiple interactions with the user’s claimed identity. || Example || Example | | '''Pseudonymous''' || An interaction designed such that the data collected is not sufficient to allow the entity to infer the user involved but which does permit an entity to associate multiple interactions with the user’s claimed identity. || Example || Example | ||
Line 42: | Line 54: | ||
| Feasible (per Req 5) || Example || Example || Example | | Feasible (per Req 5) || Example || Example || Example | ||
|- | |- | ||
| | | Interaction || TBD: define what an interaction is in context to UXC reqs || Example || Example | ||
|- | |- | ||
| | | Transparency || Example || Example || Example | ||
|- | |- | ||
| Example || Example || Example || Example | | Example || Example || Example || Example | ||
|} | |} |
Revision as of 19:26, 3 August 2015
Term | Definition | Notes | Citations |
---|---|---|---|
User | Draft: Individual Human-Being. This does not include machines, algorithms, or other non-human agents or actors. Rough Equivalents: Terms in the Common Semantic Domain found in the NSTIC Strategy include:
user, process, or device) are at the forefront of this Strategy " NSTIC Document: https://www.idecosystem.org/idesgwiki/images/b/bc/Full_NSTIC_Strategy_Document_-_04152012_ARR_Annotated_for_user_centric.pdf |
||
User-centric | DRAFT Systems, design and / or program processes that put the individual human being at the center of the activity. Rough Equivalents: user centric, user centered, user-centered, human-centered, human centered, end-user, end user, individual user, user-friendly. | Sample usage from NSTIC:
|
The common semantic domain is roughly referred to hereas:https://en.wikipedia.org/wiki/User-centered_design |
Entity / Entities | Any organization providing identity services. | Example | Example |
System | An entity's system a user is interacting with at a particular time. | Example | Example |
Anonymous | An interaction designed such that the data collected is not sufficient to infer the identity of the user involved nor is such data sufficient to permit an entity to associate multiple interactions with a user or to determine patterns of behavior with a user. | Example | Example |
Third Parties | Example | re: supplemental on Usable 3: research systems that display entities on a page or system. consider burden on user vs. accessibility of entities list) | Example |
Third Party Tracking | Example | NOTE: revisit as necessary per Privacy and other groups def.s | Example |
Pseudonymous | An interaction designed such that the data collected is not sufficient to allow the entity to infer the user involved but which does permit an entity to associate multiple interactions with the user’s claimed identity. | Example | Example |
Verified identity | Example | Example | Example |
Action | Might include providing information or a digital signature. | Example | Example |
Pathway | Example | Example | Example |
Reasonable Accommodation | Example | Example | Example |
Feasible (per Req 5) | Example | Example | Example |
Interaction | TBD: define what an interaction is in context to UXC reqs | Example | Example |
Transparency | Example | Example | Example |
Example | Example | Example | Example |