Re: Review of approaches matrix is ready for review :-)

Hi Charles, all,

Thanks for looking at this.

1. Good point. We do have an action "opens-in-page-help" which I suppose could be used in this case (which I had been thinking had been removed/renamed) but there were two reasons for picking this example, which will need to be revisited: (a) to show a situation where both an action and a destination are needed in order to convey something useful (IIRC we've discussed that, whilst unusual, we wouldn't want to say this is invalid); and (b) To show that "opens-in-page-help" isn't very generic. Will have a think about it.

2. I agree there's nothing to stop us putting a "purpose" attribute on static content, though the current spec doesn't mention that, and when it does talk about the attribute, it does so in the context of input controls, so I left it out of the "current" column. (I know we discussed being very light on validation, but I thought it best to consider anything the current spec either ignores or discourages as out of scope for it.)

Thanks again; hope that helps clarify some things at least.

Best regards,


Matthew
-- 
Matthew Tylee Atkinson
--
Senior Accessibility Engineer
TPG Interactive
https://www.tpgi.com

A Vispero Company
https://www.vispero.com

--
This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately.
Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.

On 14/07/2021, 14:13, "Charles LaPierre" <charlesl@benetech.org> wrote:

    CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender.

    In this table under: Column "Current Spec" / Row "Help Button" The example is:

    <button action="opens-in-page-dialog" destination="help">Help</button>

    I don't see this in the current list of values in our Spec.

    https://raw.githack.com/w3c/personalization-semantics/master/content/index.html#values


    Closest we have is
    openOpen an item. (Implied simplification <https://raw.githack.com/w3c/personalization-semantics/master/content/index.html#simplification-explanation> = "critical".)


    Also why wouldn't 
    Contact telephone number (content)  / "Current Spec"

    Currently
    (out of scope)

    Instead be 
    <p purpose="tel">


    Thanks
    EOM
    Charles LaPierre
    Technical Lead, DIAGRAM and Born Accessible
    Imageshare Product Manager
    Twitter: @CLaPierreA11Y
    Skype: charles_lapierre







    On Jul 14, 2021, at 5:37 AM, Matthew Atkinson <matkinson@tpgi.com> wrote:

    Hi all,

    Just to let you know that the PR adding the standalone matrix of approaches was approved. The wiki page has been updated to link to it. You can find the standalone matrix at the URL below. Please help out when you're able by checking that the code samples accurately reflect their respective approaches.

    https://w3c.github.io/personalization-semantics/review-of-approaches-for-action-destination-purpose.html


    best regards,


    Matthew

    P.S. Thanks Roy for the info on how to link my GitHub account.
    -- 
    Matthew Tylee Atkinson
    --
    Senior Accessibility Engineer
    TPG Interactive
    https://www.tpgi.com

    A Vispero Company
    https://www.vispero.com

    --
    This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately.
    Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.

Received on Monday, 19 July 2021 11:55:38 UTC