W3C

– DRAFT –
Immersive Web WG/CG bi-weekly call

07 March 2023

Attendees

Present
ada, alcooper, bajones_, bialpio, cabanier, CharlesL, cwilso, Leonard, yonet
Regrets
-
Chair
-
Scribe
Leonard

Meeting minutes

semantic-labels#1 feedback on semantic label repo (cabanier)

https://github.com/immersive-web/semantic-labels/issues/1

rik: Add support for semantic labels for hit testing and others.
… Did not want to add the specific labels to the spec -- too many updates
… Set up simple Repo (https://github.com/immersive-web/semantic-labels) that lists them
… Also provides horizontal or vertical

Leonard: Who is going to keep order

Rik: No one - general updates

Piotr: Only for labels or is supporting other concepts?

Rik: Just semantic labels

Piotr: No separate feature descriptor.
… #2: Array of semantic lables on a hit test. Will there also be categories such as furnature --> sofa (taxonomy)

Rik: No structure, no taxonomy

Piotr: Perhaps more general labels need to be returned with detailed lables

Ada: Is there an expectation that platforms support at least a major-category subset?

Rik: No requirements - completely optional.

Ada: Android allows hit test on any surface. How do things categorize stuff?

Rik: No restrictions, though best to keep 'floor' for things that are really floors.

Charles: Anticipate use in assisted technologies? I18n? W3C registry?

Rik: Could be used for assisted technologies.
… I18n: these are generic terms. Applications need to handle any translations (similar to ENUMS)
… W3C registry: doesn't know what that is. Suggest filing an issue on registry.

Piotr: Is there any anticipation of guessing labels? Do these confidence value?

Rik: Does not anticipate "guessing".

Piotr: Will file issue

<Zakim> cwilso, you wanted to comment on registry

<cwilso> https://www.w3.org/2021/Process-20211102/#registries defines the Registry track.

ChrisW: See above link for W3C registry info.

Leonard: How do you anticipate this being used?

Rik: Manual step to populate & label the environment

Nick: Relates the capabilities of their current product. Establishes a collection of semantic layers.
… System allows fractional assignments. Allows objects to "fade" into background

Rik: HitTest API not required. Also possible to use PlaneTest API.

layers#298 Add option to skip the clearing of textures requested (cabanier)

https://github.com/immersive-web/layers/issues/298

Rik: Skip clearing of texturtes. Revisiting from a few weeks ago

<bajones_> I have loosened my opinions on this, FWIW

Rik: Request was made to make default value == FALSE. Lots of examples where default == TRUE.

<bajones_> In other words, no objection from me on keeping the value as-is

Rik: ... new attribute does not require textures to be automatically cleared.

Brandon: No voice -- see above comments.

Rik: Will make sure everything is cleaned uo

layers#302 Add support for higher quality filtering requested (cabanier)

https://github.com/immersive-web/layers/pull/302

Rik: Different quality for layers. Allows clearer text, etc.
… Ada had suggested other lables, but Brandon does not necessarily agree

Ada: "Power balance"?

Rik: Would prefer "default" should be do nothing special

Rik&Ada: <discussion on various alternatives>

Ada: suggesting that the labels should be more descriptive.

Brandon: Tends to agree w/Rik on 'default'
… Doesn't want to see anything labeled
… *performant* be slower than 'default'
… May want a layer to be fast over everything else.

Ada: Convinced

Leonard: Might use 'inherit' instead of 'default' to inherit system settings

Charles: Disability user may not care about visual (for example) quality

Rik: Might be a need to increase contrast (user dependent)

Ada: Hint?

Rik: It is a hint

Brandon: Many accessibility cases are better handled by UA rather than this hint

No other discussion, no other topics

Brandel: Place for feedback for how hint is interperted?

Rik: Spec already addresses text clarity and other features

Brandel: More about how this interacts with the user at run-time.

Brandon: Not part of current proposal. Wants to know more about the use case and how developers interact with various responses

Ada: Concern about exposes accessibility info to websites. Info should remain with the UA.

General discussion: About issues and potential solutions. Nothing decided or agreed to

upcoming face-to-face

Ada: Please RSVP to F2F in Apr 24&25 (Apple Infinite Loop). No meetup

<ada> adarose@apple.com

<ada> name, company name, phone number & email

Ada: RSVP to adaRose@applie.com. Need name, company, phone, email.

Ada: That is @apple.com

<EOM>

<ada> Thank you so much Leonard!!

Minutes manually created (not a transcript), formatted by scribe.perl version 197 (Tue Nov 8 15:42:48 2022 UTC).