Proposal for personalization semantics as vocabulary

I have put together a hasty proposal for how the personalization 
semantics would look like as a vocabulary:

https://rawgit.com/w3c/personalization-semantics/vocabulary-proposal/semantics.html

You may need to refresh once or twice to get the script to format the 
table of contents etc.

Basically what I've done is:

  * Move all the properties to a section called "List of properties
    <https://rawgit.com/w3c/personalization-semantics/vocabulary-proposal/semantics.html#list-of-properties>";
  * Remove the "coga-" prefix from property names;
  * Renamed the section "Semantic Properties" to "Personalization Use
    Cases", so it focuses on the issues we want to address, and then at
    the end of each sub-section points to the individual properties that
    relate to those use cases - down the road we might even see fit to
    move this section into a separate use cases document;
  * Added an appendix "Vocabulary Implementations
    <https://rawgit.com/w3c/personalization-semantics/vocabulary-proposal/semantics.html#vocabulary-implementations>"
    that describes how items in this vocabulary could be used in RDFa,
    ARIA, and HTML Microdata (very hasty / sketchy for now) - we could
    add more formats as they occur to us.

Most of the work on the spec would still happen in the List of 
properties section, and nothing is really substantively different. The 
value of this is that it more clearly indicates how the properties can 
apply to different technologies, separates the properties from their use 
case rationale, and gets rid of those pesky coga- prefixes in their names.

Michael