Skip to content
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

@role and @rel vs @epub:type #73

Closed
GoogleCodeExporter opened this issue Mar 24, 2015 · 1 comment
Closed

@role and @rel vs @epub:type #73

GoogleCodeExporter opened this issue Mar 24, 2015 · 1 comment
Labels
Priority-Medium Topic-ContentDocs The issue affects EPUB content documents

Comments

@GoogleCodeExporter
Copy link

HTML5s role and rel attributes could be used instead of the epub:type attribute 
in XHTML Content Documents and Media Overlays for the purposes of 
attribute-axis semantic inflection. 

Here's a rundown of the situation:

* HTML5 expresses strict conformance rules of which values @role might take 
depending on element context. We would have to "willfully violate that" - with 
potentially unpredictable UA behavior as a result.
* WAI ARIA contains prose that says that any @role value that isn't in the ARIA 
vocabulary should not be passed on to AT.

In discussions with HTML5 WG chairs during TPAC 2010, they advised against 
doing such willfull violations of @role. WAI PF however, is suggesting it might 
be the best thing to do afterall, and welcome future collaboration on 
vocabulary development. 

It should also be noted that there are two versions of the role attribute in 
W3C territory at this time; the role attribute in HTML5 (and it remains unclear 
where that attribute is defined, in HTML5 or in ARIA?) and 
http://www.w3.org/TR/role-attribute/, which is a PF product. The main 
difference between these two is that the PF version defines an explicit model 
for value extensibility (which we need for domain-specific semantic inflection 
outside the direct scope of the EPUB spec) and is compatible with RDFa 1.1. 

The epub:type attribute was originally created to circumvent the (potential or 
real) issues above and let us move on with our lives. It is however worthwhile 
revisiting this choice, and continue discussions with PF, as we have a chance 
here of reusing native (HTML5 or HTML5+RDFa) constructs rather than rolling our 
own.

The concerned spec sections are here:
http://epub-revision.googlecode.com/svn/trunk/build/spec/epub30-contentdocs.html
#sec-xhtml-semantic-inflection

and here: 

http://epub-revision.googlecode.com/svn/trunk/build/spec/epub30-mediaoverlays.ht
ml#sec-semantic-inflection

Original issue reported on code.google.com by markus.g...@gmail.com on 30 Jan 2011 at 5:25

@GoogleCodeExporter
Copy link
Author

This is deferred to a later epub revision. @role as defined in html5 today does 
not satisfy our use cases (@role is AT centric, and per HTML5 and ARIA1, its 
extensibility properties are unfit).

Original comment by markus.g...@gmail.com on 2 May 2011 at 6:22

  • Changed state: Deferred

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority-Medium Topic-ContentDocs The issue affects EPUB content documents
Projects
None yet
Development

No branches or pull requests

1 participant