Introduction
For discussion, expanding upon questions raised in #6, presented here is that websites or webpages could use HTML metadata to provide settings, e.g., adaptation parameters.
Examples
In XHTML, using a Boolean attribute, one could express these ideas in a manner resembling:
<html prefix="wd: https://www.wikidata.org/entity/">
<head>
<meta name="wd:Q441" content="0.75" setting="true" />
<meta name="wd:Q11351" content="0.75" setting="true" />
</head>
<body>
...
</body>
</html>In HTML, using a Boolean attribute, one could express these ideas in a manner resembling:
<html prefix="wd: https://www.wikidata.org/entity/">
<head>
<meta setting name="wd:Q441" content="0.75">
<meta setting name="wd:Q11351" content="0.75">
</head>
<body>
...
</body>
</html>If a webpage doesn't want to provide default values for one or more of its settings, and desires, instead, for end-users to be able to opt to populate these settings' values from some sort of a "settings store", then a webpage could express:
<html prefix="wd: https://www.wikidata.org/entity/">
<head>
<meta name="wd:Q441" setting="true" />
<meta name="wd:Q11351" setting="true" />
</head>
<body>
...
</body>
</html><html prefix="wd: https://www.wikidata.org/entity/">
<head>
<meta setting name="wd:Q441">
<meta setting name="wd:Q11351">
</head>
<body>
...
</body>
</html>JavaScript
Perhaps one could add some new methods on the DOM document interface for interacting with webpages' settings.
var value = document.getSettingNS(namespace, name);
document.hasSettingNS(namespace, name);
document.setSettingNS(namespace, name, value);
document.addEventListener('settingschange', function() { ... });URIs and URLs
If settings' URIs can be interpreted as being URLs, then, at settings' locations, one could provide sufficient semantics, sufficient descriptive content (e.g., text/turtle or application/json content), for the visual presentation and configuration of settings in browser panels. These settings-related semantics might include settings' titles, descriptions, indications of whether their values were Boolean values, discrete enumerated values, or continuous numerical values, and much more (see also: #3).
Envisioned User Experiences
As broached in #7, Web browsers could provide side panels for end-users to be able to use to view and adjust websites' or webpages' settings, these settings including adaptation parameters.
Web Storage API
How might these document-metadata-related features best interoperate with the Web Storage API?
Introduction
For discussion, expanding upon questions raised in #6, presented here is that websites or webpages could use HTML metadata to provide settings, e.g., adaptation parameters.
Examples
In XHTML, using a Boolean attribute, one could express these ideas in a manner resembling:
In HTML, using a Boolean attribute, one could express these ideas in a manner resembling:
If a webpage doesn't want to provide default values for one or more of its settings, and desires, instead, for end-users to be able to opt to populate these settings' values from some sort of a "settings store", then a webpage could express:
JavaScript
Perhaps one could add some new methods on the DOM
documentinterface for interacting with webpages' settings.URIs and URLs
If settings' URIs can be interpreted as being URLs, then, at settings' locations, one could provide sufficient semantics, sufficient descriptive content (e.g.,
text/turtleorapplication/jsoncontent), for the visual presentation and configuration of settings in browser panels. These settings-related semantics might include settings' titles, descriptions, indications of whether their values were Boolean values, discrete enumerated values, or continuous numerical values, and much more (see also: #3).Envisioned User Experiences
As broached in #7, Web browsers could provide side panels for end-users to be able to use to view and adjust websites' or webpages' settings, these settings including adaptation parameters.
Web Storage API
How might these document-metadata-related features best interoperate with the Web Storage API?