W3C home > Mailing lists > Public > public-personalization-tf@w3.org > August 2021

Re: ISO, Coga and module two

From: John Foliot <john@foliot.ca>
Date: Thu, 26 Aug 2021 07:33:42 -0400
Message-ID: <CAFmg2sWM8xO9CGRxH-NX9jU+aDZYK4fk3kXTCmmbwPwBn=YTzQ@mail.gmail.com>
To: Lisa Seeman <lisa1seeman@gmail.com>
Cc: public-personalization-tf <public-personalization-tf@w3.org>
Hi Lisa,

I think there is an important 'third' component that you may be missing
here, and that is where and how the metadata is rendered and used.

Our Personalization work is focused on applying metadata at the *element
level*, which has been attempted before (Microdata, microformats, RDFa,
etc), but ours is a newer, (and I believe simpler) approach. But our work
seeks to leverage the metadata for 'transformative' purposes (i.e. the more
I know about 'foo', the more I can manipulate 'foo' - mechanically or
manually - to meet my personal needs).

However there is also the more traditional, document-level metadata, which
for me is more about discovery - finding the web documents [sic] that
addresses my needs. In that area, the excellent work that Benetch has done
with Schema.org <https://schema.org/> is the shining example (as it
integrates seamlessly with ePub), although Dublin Core
<https://www.dublincore.org/groups/access/standards/> has done some
critical work in this area as well (also works in ePub), and there are
other efforts that I am peripherally aware of such as the IMS Global
Learning Consortium's Access For All specification (
http://www.imsglobal.org/accessibility/), and the work of the Accessibility
Metadata Project (http://www.a11ymetadata.org/

(I'll note that multiple schemas has both a positive and negative impact -
I personally waffle back and forth on that).

Not sure if or how much of this would be important in the current
discussion with ISO - I'm curious to better understand their ultimate goal


On Thu, Aug 26, 2021 at 5:47 AM Lisa Seeman <lisa1seeman@gmail.com> wrote:

> Hi Folks
> ISO approached me about metadata support for COGA. This is really
> supported by module 2  (see
> https://w3c.github.io/personalization-semantics/help/ ). However as this
> is a very early draft I though some more clarity, review of cogas later
> works etc, would be a good idea.
> To help this along I have made a draft at docs.google.com
> <https://docs.google.com/document/d/1TDPA3R1Y4hVn4Eq9NlRTZ_hg4cpd_8ZtpWoFiVuF_lk/edit?usp=sharing>
> of items that could be supported in content or alternative versions.
> Other collections:
> https://github.com/w3c/personalization-semantics/wiki/User-needs-collections
> such as https://www.w3.org/wiki/WebSchemas/Accessibility
> All the best
> lisa

*John Foliot* |
Senior Industry Specialist, Digital Accessibility |
W3C Accessibility Standards Contributor |

"I made this so long because I did not have time to make it shorter." -
Pascal "links go places, buttons do things"
Received on Thursday, 26 August 2021 11:34:12 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 26 August 2021 11:34:13 UTC