This line was removed.
This word was removed. This word was added.
This line was added.
Changes (17)View Page History
This is a draft - please comment....
Version:1.0 StartHTML:0000000257 EndHTML:0000098256 StartFragment:0000053332 EndFragment:0000098220 SourceURL:file://localhost/Users/liddynevile/Documents/ISOwork/ISO-IECJTC1-SC36-WG7_N0248_ISO_IEC_24751_v2_Information_tech%202/sc36_wg7_N0248-LN.docx
ISO/IEC 24751 is intended to facilitate the matching of individual user needs and preferences with resources \[note:interfaces are used to access resources\] that meet those needs and preferences to enable appropriate perception of the resources. This matching might involve finding a suitable resource or interface, or format of a resource, or it might involve adaptation of the resource or its interface. It is intended to address mismatches between personal needs and preferences caused by any number of circumstances, including requirements related to client devices, environments, language proficiency or abilities. The terms and definitions within ISO/IEC 24751 are not judgmental or based on disability classifications, diagnosis or assumptions regarding disability, rather they are descriptions of functions that can be applied by all users; the purpose is not to point out flaws in resources or interfaces with respect to accessibility and adaptability, but to facilitate the discovery and use of the most appropriate resource, configuration or interface for each user.
h3. 2.1.2 The creation of accessible content
ISO/IEC N24751 does not describe how to create accessible content. Other work exists and standards are under development that describe how content and interfaces can be made more accessible.[|#_ftn1]\\ accessible.\[\|#_ftn1\]
h3. 2.1.3 Person: organization and public administration
ISO/IEC24751 does not define how to deal with types and roles of Persons, (and two sub-types of Person namely organization and public administration). Other standards exist and are under development that address these and related issues.[|#_ftn2]\\ issues.\[\|#_ftn2\]
h2. 2.2 Aspects not currently addressed
A registry of terms to be used in creating PNP statements, resource descriptions, pull statements[|#_ftn3] statements\[\|#_ftn3\] and other functions in support of personalization on demand enabled by ICT and networked systems
Personal Needs and preferences (PNP) context set
A (named) *dataset* (4.8) of conditions to determine if a PNP statement (4.16) applies[|#_ftn4] applies\[\|#_ftn4\]
W3C World Wide Web Consortium
W3C/WAI WCAG World Wide Web Consortium/Web Accessibility Initiative Web Content Accessibility Guidelines\\
h1. 6 Basic Principles
The registry will establish a lightweight, minimally formalized process for sanctioning new terms.
[|#_ftnref1] \[\|#_ftnref1\] See for example W3C/WAI Web Content Accessibility Guidelines \[W3C/WAI, WCAG\], ISO 15836, ISO 15706, other standards of ISO/TC 46 and ISO/IEC JTC 1/SC 29, as well as standards being developed by ISO/IEC JTC 1/SC 36.\\
[|#_ftnref2] See further ISO/IEC 14662:2004, _Information technology --- Open-edi reference model_ and the ISO/IEC15944 multi-part e-business standard.\\
\[\|#_ftnref2\] See further ISO/IEC 14662:2004, \_Information technology --- Open-edi reference model_ and the ISO/IEC15944 multi-part e-business standard.
[|#_ftnref3] \[\|#_ftnref3\] Pull statements are requests to fill gaps in meeting a PNP statement.
[|#_ftnref4] \[\|#_ftnref4\] The stress is on the individual’s perspective. A condition should be clear: for example, an objectively determined condition such as ‘if it is raining’ does not indicate if the user is affected by the rain, as they may be sheltered or have an umbrella.