<scribe> scribe: jeanne

<bruce_bailey> https://www.w3.org/WAI/GL/task-forces/silver/wiki/XR_Subgroup_-_Meeting_Summary

<bruce_bailey> from meeting reminder email: https://github.com/w3c/silver/projects/2

<Zakim> Joshue, you wanted to say the functional user needs group needs to set up meeting time

<bruce_bailey> https://www.w3.org/WAI/GL/task-forces/silver/wiki/XR_and_Emerging_Technologies

<bruce_bailey> https://github.com/w3c/silver/issues

MCr: I have put the user needs from the various XR projects into a Github project page

<bruce_bailey> yes, reminded me of Trello too

+1 to using Github

CH: I like it, but we need agreed usage in the group.

[We are discussing each user need from the XR groups and decidinig whether or not it applies to captioning]

Motion agnostic interactions: This would apply if the captions are not visible or behind the user

Immersive semantics and customization: Applies if the captions include instructions for navigation. Applies if the customization includes symbols inside of captioning.

https://github.com/w3c/silver/projects/2

scribe: will put this into the Under Consideration for Captions in the project

Voice Commands: Not directly relevant because it is more of the input. But when the user gives voice commands, they are reflected on the screen.

scribe: put with Under Consideration pending Jeanne contacting Kim Patch about research on voice commands reflected on screen.

Immersive personalization: Directly relevant

Interaction and target customization: More related to interaction than captions.

Immersive semantics and customization applies because the caption window may need to be moved.

Color Changes: In the UK, color changes are used to signify a change of voice/character. Customizing the color is related, but belongs in a different guideline.

scribe: it is important to XR, but not necessarily directly to the captioning.

Critical Messaging and alerts: Probably not related to captioning.

scribe: Josh: We use Second Screen to be any device.
... recommend the parking for later guidelines

Magnification context and resetting: Needed for people who need captions and have low vision

Gestural interfaces and interactions: Could apply to the settings around the captioning system. Probably doesn't apply to viewing the captioning themselves. Save for later guidelines

Text description transformation: Signing avatars within XR.

Safe Harbor Controls: Important but not directly relevant to captioning

Immersive time limits: Not directly relevant to captioning

Interaction speed: Applies because the speed of captioning is an well-researched issue.

BB: Human captioners do a better job captioning, but automated captioning will take more time for comprehension.

Reset focus and orientation: Need to have the captions move with the orientation, but not directly related.

Routing to second screen: Appropriate for regular captioning routing to a braille device and routing XR captioning to a braille

Avoiding sickness triggers: Applies to pinned captioning window that it can't jiggle as the user moves. Not directly relevant, but does apply. We should probably mention it.

<Joshue108> https://en.wikipedia.org/wiki/Binaural_recording

Binaural audio track alternatives: Binaural is really spatial audio. This is recording with a spacial audio recording.

<CharlesHall> rejoining

Josh: It's more of a need for spatial sound. We proably will remove that need.

Binaural audio will be in a future guideline.

Subtitling customization: It's needed in traditional captioning and XR.

Mcr: We have four left, which we will finish next week.

This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: CharlesHall Mike Bruce Jeanne Josh
Found Scribe: jeanne
Inferring ScribeNick: jeanne

WARNING: No "Topic:" lines found.


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)