Re: Actions versus destinations

Hi Lisa.

Thank you for your answer. Can you please elaborate on the
implementation problems which resulted from these being two separate
categories?

--joanie

On 04/10/2018 11:55 AM, lisa.seeman wrote:
> Hi Joanie
> It was all in one category but we ran into implementation problems
> because they are handled differently depending what they are.
> Another example of why we need some implementation as we go.
> 
> All the best
> 
> Lisa Seeman
> 
> LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter
> <https://twitter.com/SeemanLisa>
> 
> 
> 
> 
> ---- On Tue, 10 Apr 2018 17:48:23 +0300 *Joanmarie
> Diggs<jdiggs@igalia.com>* wrote ----
> 
>     Hey all.
> 
>     Given recent discussions about how to implement Personalization
>     Semantics, I figured I'd give extension writing a try as a proof of
>     concept. As part of this, I of course had to dive into your spec.
> 
>     Question for your consideration: What are the benefits in making the
>     distinction between an action and a destination?
> 
>     I'm rapidly coming to the conclusion that it doesn't buy you anything,
>     that it may lead to author confusion, and that implementation might be
>     simplified if this distinction were nixed. If you decide to keep the
>     distinction, then I think you might wish to consider prioritizing
>     clarifying actions versus destinations.
> 
>     I already filed a github issue with more details. Just pointing out the
>     issue here in case most of you aren't monitoring github issues.
>     https://github.com/w3c/personalization-semantics/issues/66
> 
>     Looking forward to your answers. Thanks!
>     --joanie
> 
> 
> 
>

Received on Tuesday, 10 April 2018 16:07:10 UTC