wendy wrote down additional thoughts
wendy looked at metadata that might not be in the content space
wendy way to classify thousands of devices
wendy a rough notion of how look on diff devices
wendy what would it mean to have content-side metadata that said
"what was the author thinking about this class of devices when built this..."
wendy debated that probably not just devices, may need to cover
something to do with user modeling
wendy what is the user likely to do with this stuff
wendy a topic for diwg to discuss
wendy what you like if you like large text, here's for bigger text
wendy work across devices and user profiles
wendy role seemed to be key thing
wendy clearly a need to say, "it has a role that i can't express
alone in xhtml"
wendy also talked about tasks. concluded that task, an
achievement th euser makes on the site, could also be a role
wendy roles could span multiple pages, not just defined in one page
wendy adaptation rules - what need to say?
wendy image degredation - scaling down? clipping? diff kind of
wendy this at principles level: general ways to do transformation
wendy also general principels for metadata itself
wendy scalable, maintain it further downstream than you think
(perhaps not metadata itself, but references to it), standards-based, if extend - do in a findable way
wendy took some of the things we came up with yesterday,
identified some as key
wendy debate about which things are separable or the same thing
wendy no conclusions on some of that
wendy icra - did not talk about privacy and client profiles.
wendy rhys when talking about info that would flow upstream for
adaptation, if you decide to make available, do in a trusted environment.
wendy .. some info may be really senstive...all of it could be
sensitive, thus all should be subject to policy