Issue #66: Clarity needed for actions vs destinations

I am finally taking a look into issue 66, Clarity needed for actions vs destinations, https://github.com/w3c/personalization-semantics/issues/66.

We did remove some of the destinations since Joanie filed this comment but I think there are still some that could use clarification.

We did change comment to feedback but I think we should update the description to, Provides a mechanism to submit feedback.
Suggest we remove email-recipient and phone since we already have contact. If the idea of email-recipient is to actually open an email program, I would argue that we don't need that since the link should already be identified via a mailto attribute.
Update definition of help to, Navigates to instructions or further support. Previous help definition, A help function that navigates to support or instructions. 
Post - remove as I believe this is an action as currently defined. 
Related - remove or redefine. The current definition is an action: Adds a related item(s) to a pre-selected list of items.

With respect to actions we should reconsider these:
end overlaps with destination. The current description describes an destination: Moves to the terminus of a range, list, or sequence. This is typically used in a sequence of steps.
Profile is also defined as an action: Opens the user's profile page. If it is opening a page then it is a destination. If it is opening within the page context (dialog/popup) it could be an action. 
Received is another that us using the term open: Open the received folder. Unless it is opening within the same page it is probably a destination. 
Sent The same logic as received follows for sent: Open the sent folder. 
And also for settings: Open settings and options. I think we may need clearer description for these.
toc uses the term opens as well: Opens a table of contents.

Joanie specifically called out that help exists for both action and destination. We have changed the action name to opens-in-page-help from help. But, the confusion remains about whether something is an action or destination depending upon how it is implemented. If help is part of a dialog then it would be an action and if it is a link to a new page it is a destination. Although, I do think there may be some overlap in action and destination, the definitions need to be made clear. 

The signin and signout actions have the same isses. Sometimes the user remains on the same page to perform that function so that would be an action? If the signin and signout are links then they are destinations. Is this what we want? We don't have signin and signout as actions. 

Joanie had called out that action and destination both had left and right. We have sinced removed left/right/up/down from the list of destinations.

So, I think we need to make clear that some items can be both actions and destinations depending upon how they are invoked. If a button is used to open and provide additional information within the same page context, they it is an action. If a link takes the user to a new location for the additional information or function, it is identified as a destination.  I think we could make our lives easier if we shortened the list for the 1.0 version.




Becky Gibson
https://www.linkedin.com/in/beckygibsona11y/

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa