explainer review

Hi



As I am going though the explainer, I am finding quite a few editorial issues.

If it is ok I will try and make a branch and edit it before the weekend.



Issues so far



1.add "for example" is the short list of four items of types of extra support for users 



change

2."To achieve this, we need standardized terms and supportive syntax. These can be linked to associated symbols, terms, translations and explanations. This allows modifications based on an individual's personal preferences."
to
"To achieve this, we need standardized terms and supportive syntax that enables adaptable interfaces based on an individual's personal preferences. The terms and syntax can be linked to associated symbols, terms, translations and explanations."



3.remove: Requirements for Personalization Semantics elaborates many use cases that further contextualize the above summary of user needs. These example use cases form the basis of requirements for this technology. 



4. Example: You want to get the latest weather report for your city and go to the http://www.weather.com 

issues - we reference a real website.

sudden change of tense etc





To achieve this, we need standardized terms and supportive syntax. These can be linked to associated symbols, terms, translations and explanations. This allows modifications based on an individual's personal preferences.



should be

To achieve this, we need standardized terms and supportive syntax that enables addaptble interveces based on an individual's personal preferences. The terms and syntax can be linked to associated symbols, terms, translations and explanations.



remove: Requirements for Personalization Semantics elaborates many use cases that further contextualize the above summary of user needs. These example use cases form the basis of requirements for this technology.




All the best

Lisa Seeman

http://il.linkedin.com/in/lisaseeman/, https://twitter.com/SeemanLisa