andyheath at axelrod.plus.com
Thu Aug 2 07:35:14 UTC 2012
Thankyou. A combination of your reply and Christophe's did.
The reason behind my question is I'd seen no mention of services
and there may be architectural implications of including both
content transformation services and people-delivered support
services (whole organisations are devoted to delivering those in the UK,
particularly in H.E.) along with matching to devices and preferences -
its an order of magnitude harder having that extra dimension (and its
hard enough just having prefs, content-and-interface and delivery
contexts to juggle).
I have seen approaches to this that work - I'll raise them at the
> I think it is part covered and part not covered.
> Cloud4all covers user interfaces. so if content contains them - then it
> would cover them. but we are only testing this with web apps (a type of
> GPII also covers documents -- but that is not really targeted in Cloud4all.
> Does this answer the question you asked?
> Gregg Vanderheiden Ph.D.
> Director Trace R&D Center
> Professor Industrial & Systems Engineering
> and Biomedical Engineering
> University of Wisconsin-Madison
> Co-Director, Raising the Floor - International
> and the Global Public Inclusive Infrastructure Project
> http://Raisingthefloor.org --- http://GPII.net
> On Jul 31, 2012, at 3:00 AM, Andy Heath <andyheath at axelrod.plus.com
> <mailto:andyheath at axelrod.plus.com>> wrote:
>> Can someone explain to me where services (e.g. that transform content
>> or that are delivered alongside content) and their discovery fit into
>> the cloud4all architecture ?
>> Andy Heath
>> Accessforall mailing list
>> Accessforall at fluidproject.org
More information about the Accessforall