Is "section-*****" really a field?

[joanmarie]

All of the items in the field table seem like information which the user would provide via an input control. The exception is section-***** which is defined as "used to group forms together". The user isn't expected to provide that, correct?

In addition, my understanding of the purpose of the field attribute is that it can:

• Facilitate replacement of existing labels with more easily understood/recognizable words and/or symbols so that the user knows what information is expected
• Work with a personalization-specific form population tool

Assuming my understanding is correct, section-***** won't easily be machine parseable because the "*****" (as I understand it) is a wildcard.

With all of the above in mind, is section-***** really a field?

[becka11y]

Edited document to remove section.*****.

[becka11y]

We discussed this in the call and decided that we should discuss further before removing section. The understanding in the group was that this would be applied to a surrounding element and not directly onto a form element. It would help to provide more context for the items within the section. For example, home address, shipping address, or billing address. Another example is using gender surrounding a selection of male or female. John also brought up that we might need a vocabulary for this and wondered if there are any defined. He could also think of institution examples like a university providing a list of grades or a set of courses within a semester. We need input from Lisa to understand if this is how she intended section to be used.

We also discussed removing this for the next editor's draft and addressing in a later draft.

[ghost]

The following may provide some initial ground work for thought, although this may not be a 1:1 model for what we would like to accomplish.

https://schema.org/docs/schemas.html

Best, Thaddeus

---

From: Becky Gibson notifications@github.com Sent: Monday, August 13, 2018 12:09:44 PM To: w3c/personalization-semantics Cc: Subscribed Subject: Re: [w3c/personalization-semantics] Is "section-*****" really a field? (#68)

We discussed this in the call and decided that we should discuss further before removing section. The understanding in the group was that this would be applied to a surrounding element and not directly onto a form element. It would help to provide more context for the items within the section. For example, home address, shipping address, or billing address. Another example is using gender surrounding a selection of male or female. John also brought up that we might need a vocabulary for this and wondered if there are any defined. He could also think of institution examples like a university providing a list of grades or a set of courses within a semester. We need input from Lisa to understand if this is how she intended section to be used.

We also discussed removing this for the next editor's draft and addressing in a later draft.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fpersonalization-semantics%2Fissues%2F68%23issuecomment-412630172&data=02%7C01%7Cjjc6476%40psu.edu%7C0e15225a2b0348545a7d08d6015057e7%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636697841915037175&sdata=GaViOryatNWb05TTSQixz4SfLzaxP7eQSoEf%2FO3ktuU%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAcJxJvh_jkwGbIxp571qr_yW_0HhTojSks5uQc74gaJpZM4TOfoB&data=02%7C01%7Cjjc6476%40psu.edu%7C0e15225a2b0348545a7d08d6015057e7%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636697841915037175&sdata=Vb6QPZH4R6Uj%2F3te9a2sgloX%2BxNICsZ8g8tlDZ08w2s%3D&reserved=0.

[becka11y]

I agree with JoanMarie that section-* does not fulfill a field purpose. I am in favor of removing it from this draft. It is not a field type and is essentially mimicking fieldset. If an author does not understand and use fieldsets properly it is unlikely they would use purpose=section-** correctly. We should encourage symantic HTML first.

[clapierre]

+1 Thanks EOM Charles LaPierre Technical Lead, DIAGRAM and Born Accessible Twitter: @CLaPierreA11Y Skype: charles_lapierre

On Mar 30, 2020, at 6:53 AM, Becky Gibson notifications@github.com<mailto:notifications@github.com> wrote:

I agree with JoanMarie that section-* does not fulfill a field purpose. I am in favor of removing it from this draft. It is not a field type and is essentially mimicking fieldset. If an author does not understand and use fieldsets properly it is unlikely they would use purpose=section-** correctly. We should encourage symantic HTML first.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/w3c/personalization-semantics/issues/68#issuecomment-606013130, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB3A3LIBLHE7243CWGXK2SDRKCP5XANCNFSM4EZZ7IAQ.

[becka11y]

So, on a further investigation - section-**** is part of the available HTML5 autofill values. See example 74 on this page: https://www.w3.org/TR/html52/sec-forms.html#sec-autofill.

It is how you can further distinguish values - "section-item1 shipping postal-code", "section-item2 shipping postal-code", "section-item2 billing postal-code", etc. . The list referenced in WCAG 2.1 (https://www.w3.org/TR/WCAG21/#input-purposes) includes only discrete values. Since we will be referring to the WCAG values, I believe it makes even more sense to remove section-****.

[becka11y]

TF discussion on March 8, 2020 and agreed to remove section-**** based on above comment from March 30, 2020.

[ruoxiran]

Removed in PR #174, we could close this issue, thanks