wbs responses to 'WoT Use Case Prioritization' as delegated

Janina Sajka via WBS Mailer writes:
> The following answers have been successfully submitted to 'WoT Use Case
> Prioritization' (public) for Janina Sajka.
> 
> > 
> > ---------------------------------
> > UC Category 1: Retail
> > 
> > ----
> > 
> > Integrating and interconnecting multiple devices into the common retail
> > workflow.
> > 
> > 
> > 
> > Please see the Retail use case for the detail.
> > 
> > 
> > Also please add your comments to the following "Comments" field if you
> > have any ideas on additional use cases for this category and/or
> > additional categories related to this category.
> > 
> > 
> 
>  * ( ) not interested
>  * ( ) useful, but not business relevant
>  * (x) business relevant
>  * ( ) business critical
> Comments: 
> While a11y implications of this use case have not yet been discussed by
> APA/RQTF, it's clear that
> persons with disabilities will be retail customers. Some pwd may also be
> retail employees. Thus 
> the accessibility of user facing interfaces is critical and will determine
> whether pwd are included or excluded from participation.
> 
> > 
> > 
> > ---------------------------------
> > UC Category 2: Audio/Video
> > 
> > ----
> > 
> > Synchronizing media across different devices:
> > 
> >  * People in different homes watch the same content at the same time.
> > Conversation about content.
> >  * Multi-room sync playback
> >  * Multi-camera angles
> >  * Voice control of a media playback device (integration of smart
> > speakers from multiple vendors) Describe proprietary (vendor specific)
> > device control interfaces to control media playback on TV set.
> > (proprietary implementations exist, open protocol is proposed?)
> > 
> > Please see the following use cases for the detail:
> > 
> > 
> >  * Media Use Case Information Bucket
> >  * Home WoT devices work according to TV programs
> > Also please add your comments to the following "Comments" field if you
> > have any ideas on additional use cases for this category and/or
> > additional categories related to this category.
> > 
> > 
> 
>  * ( ) not interested
>  * (x) useful, but not business relevant
>  * ( ) business relevant
>  * ( ) business critical
> Comments: 
> Not yet discussed by APA/RQTF.
> 
> > 
> > 
> > ---------------------------------
> > UC Category 3: Agriculture
> > 
> > ----
> > 
> > Smart Agriculture (Greenhouse Horticulture) to create an optimal
> > environment for growing plants.
> > 
> > 
> > 
> > Please see the Smart Agriculture use case for the detail.
> > 
> > 
> > Also please add your comments to the following "Comments" field if you
> > have any ideas on additional use cases for this category and/or
> > additional categories related to this category.
> > 
> > 
> 
>  * ( ) not interested
>  * ( ) useful, but not business relevant
>  * (x) business relevant
>  * ( ) business critical
> Comments: 
> While not yet discussed by APA/RQTF, pwds may be among the employees who
> would
> access and manage such systems. This again points to the importance
> of accessibility UX.
> 
> > 
> > 
> > ---------------------------------
> > UC Category 4: Smart City
> > 
> > ----
> > 
> > Integrating multi-vendor IoT services for Smart City purposes.
> > 
> > 
> > 
> > Please see the following use cases for the detail:
> > 
> > 
> >  * Smart City Geolocation
> >  * Interactive Public Spaces
> >  * Meeting Room Event Assistance
> > 
> > Also please add your comments to the following "Comments" field if you
> > have any ideas on additional use cases for this category and/or
> > additional categories related to this category.
> > 
> > 
> 
>  * ( ) not interested
>  * ( ) useful, but not business relevant
>  * ( ) business relevant
>  * (x) business critical
> Comments: 
> While not yet discussed by APA/RQTF, it can be expected an accessibility UX
> sill
> be seen as both critical to pwd, and also as a vector to provide
> a level of access not otherwise available to pwds.
> 
> > 
> > 
> > ---------------------------------
> > UC Category 5: Health
> > 
> > ----
> > 
> > Integrating multi-vendor IoT services for public/private Healthcare
> > purposes.
> > 
> > 
> > 
> > Please see the following use cases for the detail:
> > 
> > 
> >  * Public Health Monitoring
> > 
> >  * Health Notifiers
> > Also please add your comments to the following "Comments" field if you
> > have any ideas on additional use cases for this category and/or
> > additional categories related to this category.
> > 
> > 
> 
>  * ( ) not interested
>  * ( ) useful, but not business relevant
>  * (x) business relevant
>  * ( ) business critical
> Comments: 
> While not yet discussed by APA/RQTF, pwds no less than anyone else
> need to participate in their health management. Additionally, some pwds
> will be
> professionals (at all levels) in health delivery.
> 
> > 
> > 
> > ---------------------------------
> > UC Category 6: Manufacturing
> > 
> > ----
> > 
> > Monitoring production lines and plants and predicting and preventing
> > fault conditions.
> > 
> > 
> > 
> > Please see the Big Data for Manufacturing use case for the detail.
> > 
> > 
> > Also please add your comments to the following "Comments" field if you
> > have any ideas on additional use cases for this category and/or
> > additional categories related to this category.
> > 
> > 
> 
>  * ( ) not interested
>  * (x) useful, but not business relevant
>  * ( ) business relevant
>  * ( ) business critical
> Comments: 
> Not yet discussed in APA/RQTF. Accessibility issues likely only arise when
> 
> data gathered is presented by some kind of informational or management UX.
> 
> > 
> > 
> > ---------------------------------
> > UC Category 7: Multi-vendor System Integration
> > 
> > ----
> > 
> > Integrating multi-vendor systems for IoT purposes in general.
> > 
> > 
> > 
> > Please see the following use cases for the detail:
> > 
> > 
> >  * Out of the box interoperability
> >  * Digital Twin
> >  * Cross Protocol Interworking
> > 
> > Also please add your comments to the following "Comments" field if you
> > have any ideas on additional use cases for this category and/or
> > additional categories related to this category.
> > 
> > 
> 
>  * ( ) not interested
>  * ( ) useful, but not business relevant
>  * ( ) business relevant
>  * (x) business critical
> Comments: 
> While not yet discussed by APA/RQTF, it is likely this use case will be
> seen as a11y critical because
> interoperability tends to contribute strongly to accessible UX. In part
> this could be
> because interoperability frees developers to focus on subject specific
> content management, while leaving the UX to others.
> 
> > 
> > 
> > ---------------------------------
> > UC Category 8: Multimodal System Integration
> > 
> > ----
> > 
> > Integrating multi-vendor IoT services for Multimodal system ingegration
> > purposes.
> > 
> > 
> > 
> > Please see the following use cases for the detail:
> > 
> > 
> >  * Multimodal Recognition Support
> >  * Enhancement of Synergistic Interactions
> > Also please add your comments to the following "Comments" field if you
> > have any ideas on additional use cases for this category and/or
> > additional categories related to this category.
> > 
> > 
> 
>  * ( ) not interested
>  * ( ) useful, but not business relevant
>  * ( ) business relevant
>  * (x) business critical
> Comments: 
> While not yet discussed by APA/RQTF, it is likely this use case will be
> seen as a11y critical because
> it describes auto-adapting the UX to a user's particular interface needs.
> 
> > 
> > 
> > ---------------------------------
> > UC Category 9: Accessibility
> > 
> > ----
> > 
> > Integrating multi-vendor IoT services for Accessibility purposes in Smart
> > Homes.
> > 
> > 
> > 
> > Please see the following use cases for the detail:
> > 
> > 
> >  * Audiovisual Devices Acting as Smartphone Extensions
> >  * Unified Smart Home Control and Status Interface
> > Also please add your comments to the following "Comments" field if you
> > have any ideas on additional use cases for this category and/or
> > additional categories related to this category.
> > 
> > 
> 
>  * ( ) not interested
>  * ( ) useful, but not business relevant
>  * ( ) business relevant
>  * (x) business critical
> Comments: 
> Discussed and provisionally supported as a11y critical by APA and our
> RQTF-TF. APA process requires a formal consensus call
> which is now in progress here:
> https://lists.w3.org/Archives/Public/public-apa-admin/2020Jun/0004.html
> 
> > 
> > 
> > ---------------------------------
> > UC Category 10: Automotive
> > 
> > ----
> > 
> > Integrating multi-vendor IoT services for Connected Car purposes.
> > 
> > 
> > 
> > Please see the Smart Car Configuration Management use case for the
> > detail.
> > 
> > 
> > Also please add your comments to the following "Comments" field if you
> > have any ideas on additional use cases for this category and/or
> > additional categories related to this category.
> > 
> > 
> 
>  * ( ) not interested
>  * ( ) useful, but not business relevant
>  * (x) business relevant
>  * ( ) business critical
> Comments: 
> While not yet discussed by APA/RQTF, this use case is likely to be seen as
> critically relevant to apa. The more
> autonomous the vehicle, the more critical the a11y.
> 
> > 
> > 
> > ---------------------------------
> > UC Category 11: Energy / Smart Grid
> > 
> > ----
> > 
> > Integrating multi-vendor IoT services for Energy / Smart Grid purposes.
> > 
> > 
> > 
> > Please see the Smart Grids use case for the detail.
> > 
> > 
> > In addition, please add your comments to the following "Comments" field
> > if you have any ideas on additional use cases for this category and/or
> > additional categories related to this category.
> > 
> > 
> 
>  * ( ) not interested
>  * ( ) useful, but not business relevant
>  * ( ) business relevant
>  * (x) business critical
> Comments: 
> While not yet discussed by APA/RQTF, it is highly likely this use case will
> be seen as a11y critical.
> In fact there are some pwd for whom an accessible interface to power
> management may be life critical.
> 
> > 
> > 
> > ---------------------------------
> > UC Category 12: Transportation
> > 
> > ----
> > 
> > Integrating multi-vendor IoT services for fleet management, public
> > transport, managing shipping, air cargo, train cargo, last mile
> > transportation.
> > 
> > 
> > 
> > Please see the Transportation use case for the detail.
> > 
> > 
> > Also please add your comments to the following "Comments" field if you
> > have any ideas on additional use cases for this category and/or
> > additional categories related to this category.
> > 
> > 
> 
>  * ( ) not interested
>  * ( ) useful, but not business relevant
>  * ( ) business relevant
>  * (x) business critical
> Comments: 
> While not yet directly discussed by APA/RQTF, similar use cases discussed
> in the past suggest the critical accessibility classification.
> We all go places regardless of ability/disability. An accessible UX is
> therefore critical, e.g. how
> do I know which for hire vehicle approaching the airport pick up point is
> mine vs for the person standing next to me?
> 
> > 
> > 
> > ---------------------------------
> > UC Category 13: Smart Building
> > 
> > ----
> > 
> > Integrating multi-vendor IoT services for managing Smart Buildings.
> > 
> > 
> > 
> > Please see the following use cases for the details:
> > 
> > 
> >  * Smart Building
> >  * Connected Building Energy Efficiency
> > Also please add your comments to the following "Comments" field if you
> > have any ideas on additional use cases for this category and/or
> > additional categories related to this category.
> > 
> > 
> 
>  * ( ) not interested
>  * ( ) useful, but not business relevant
>  * (x) business relevant
>  * ( ) business critical
> Comments: 
> Not yet discussed by APA/RQTF. However, pwds may indeed also be system
> engineers/administrators
> indicating the requirement for a11y UX.
> 
> > 
> > 
> > ---------------------------------
> > UC Category 14: Shared Devices and Resources
> > 
> > ----
> > 
> > Integrating multi-vendor IoT services with shared devices/resources.
> > 
> > 
> > 
> > 
> > Please see the Education use case for the detail.
> > 
> > 
> > Also please add your comments to the following "Comments" field if you
> > have any ideas on additional use cases for this category and/or
> > additional categories related to this category.
> > 
> > 
> 
>  * ( ) not interested
>  * ( ) useful, but not business relevant
>  * (x) business relevant
>  * ( ) business critical
> Comments: 
> Not yet discussed by APA/RQTF. However, it should be noted that pwds are
> also included amongst both students and teachers/administrators.
> An a11y UX is thus required, and may be further required by local mandates
> on educating pwd.
> 
> > 
> > 
> > ---------------------------------
> > UC Category 15: OAuth2 Flows
> > 
> > ----
> > 
> > Authentication using OAuth2 for multi-vendor IoT services.
> > 
> > 
> > 
> > 
> > Please see the OAuth2 Flow use case for the detail.
> > 
> > 
> > Also please add your comments to the following "Comments" field if you
> > have any ideas on additional use cases for this category and/or
> > additional categories related to this category.
> > 
> > 
> 
>  * ( ) not interested
>  * ( ) useful, but not business relevant
>  * ( ) business relevant
>  * (x) business critical
> Comments: 
> While not yet directly discussed by APA/RQTF, accessible authentication has
> been a concern over time, and particularlyh so
> most recently in our Cognitive and learning Disabilities (COGA) Task Force.
> The more adaptive to individual user abilities such
> systems can be, the more a11y successful they will be.
> 
> > 
> > 
> > ---------------------------------
> > UC Category 16: Device lifecycle
> > 
> > ----
> > 
> > Handling the entire device lifecycle for multi-vendor IoT services.
> > 
> > 
> > 
> > 
> > Please see the Device lifecycle use case for the detail.
> > 
> > 
> > Also please add your comments to the following "Comments" field if you
> > have any ideas on additional use cases for this category and/or
> > additional categories related to this category.
> > 
> > 
> 
>  * ( ) not interested
>  * ( ) useful, but not business relevant
>  * (x) business relevant
>  * ( ) business critical
> Comments: 
> Not yet discussed by APA/RQTF. However, as humans are listed in the use
> case, we are again in need of a11y UX.
> 
> > 
> > 
> > ---------------------------------
> > UC Category 17: New Category
> > 
> > ----
> > If you have any ideas on a completely new use case category, please add
> > your comments to the following "Comments" field. It would be appreciated
> > if you could generate some concrete use case description based on the Use
> > Case Template.
> > 
> > 
> 
>  * (x) not interested
>  * ( ) useful, but not business relevant
>  * ( ) business relevant
>  * ( ) business critical
> Comments: 
> APA/RQTF intends to continue a focus on WoT and looks forward to working
> with this WG on building
> standards to support a more accessible (and useful) world.
> I should also note my responses are on behalf of APA & RQTF in my role as
> APA Chair.
> 
> > 
> > These answers were last modified on 26 June 2020 at 14:59:55 U.T.C.
> > by Janina Sajka
> > 
> Answers to this questionnaire can be set and changed at
> https://www.w3.org/2002/09/wbs/1/wot-uc-priority-202005/ until 2020-06-26.
> 
>  Regards,
> 
>  The Automatic WBS Mailer

-- 

Janina Sajka
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Received on Friday, 26 June 2020 15:03:33 UTC