-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ARIA 1.1. should define a formal modularization scheme for role values (via prefixes or some other means) #52
Comments
Note: This syntax is valid ARIA 1.0 and allows clearer list distinction for both authors and implementors. |
+1 Regards SteveF On 28 April 2015 at 20:03, James Craig notifications@github.com wrote:
|
I am really only in favor of this if these well defined prefixes are mapped to stable URIs so that the combination of the prefix and term equal a URI that can be deferenced by data processing engines. I know that I have an RDF bias here, but there is no reason that we can't have tight relationships between our terms and the core underpinnings of the semantic web. See http://www.w3.org/TR/role-attribute and http://www.w3.org/TR/rdfa-core/ for information about how we envisioned having additional vocabularies be defined. |
Moving to ARIA 2.0 as we did not define formal modularization in ARIA 1.1 and it is not in scope for ARIA 1.2. |
It seems this was effectively adopted ( Closing this -- please re-open if you think additional action is needed. |
My preference is for hyphenated reserved role prefixes:
pub-* or dpub-* for the DPUB roles
g-* or graphic-* (?) for the graphics/SVG roles
vendor prefixes -webkit-, -ie-, for experimental UA proposals.
etc.
The text was updated successfully, but these errors were encountered: