- From: Joshue O'Connor <joconnor@w3.org>
- Date: Tue, 28 Sep 2021 12:57:42 +0100
- To: "public-apa@w3.org" <public-apa@w3.org>
Hi all, I have reviewed the Web of Things (WoT) Profile FPWD as per my action item. [1] Overview The WoT Profile Specification defines profiles that enable out of the box interoperability among things and devices (without deep level adaptations). Usually just minor configurations such as entering a network key, or IP address. The profile is a subset of a thing description. It also has a ' Profiling Mechanism' which can be used to add to, or extend, profiles. Here is my draft response regarding this spec: The Accessible Platform Architectures (APA) working group has reviewed the first public working draft of the 'Web of Things (WoT) Profile' https://www.w3.org/TR/wot-profile/. We have the following questions: * Does the ' Profiling Mechanism' have any accessibility related potential? For example, does it impact or relate to middle-ware, that needs to support accessibility related use cases? [3] * With the degree of variability in current Thing Descriptions and no interoperability guarantee; how does the WoT group intent to support accessibility related user needs/requirements, if needed at this level? Should a reliable data structure for accessibility be defined in WoT Profiles to insure interoperability and support, if needed? We acknowledge some use cases are yet to be determined, but the discussion now of an architecture that may be required for accessibility, seems needed/sensible at this point. It may be determined that the generic profile requirements are sufficient to describe accessibility related supports, but it also may not. [1] https://lists.w3.org/Archives/Public/public-apa/2020Dec/0002.html [2] https://www.w3.org/TR/wot-profile/#dfn-wot-core-profile [3] https://www.w3.org/WAI/APA/wiki/Wot_usecases Thanks Josh -- Emerging Web Technology Specialist/Accessibility (WAI/W3C)
Received on Tuesday, 28 September 2021 11:57:50 UTC