Re: essential use case of personlization missed out

> there was a browser that changed the symbol set based on the concept code used, and the users preferred symbol set, it is opensource on github. But there was not the content to support it.

So there is no user-agent for this at the moment?

> What we need to do is have a requirement that content made for this audience

If it is content specific to certain audiences, how would that be scoped? Without a specific scope that is derived from the content, that puts it at AAA at best.

> the scope really needs to be written in terms of audience not content - and that is the challenge

Indeed, that isn’t how “content guidelines” work.

Is there an agreed & published concept set, the “Linked Open Data” referenced?

The links to don’t appear to work.


Received on Wednesday, 26 July 2017 14:05:41 UTC