Meeting minutes
Selectors in Annotations - w3c/epub-specs#2892
Laurent: Providing overview of selectors
… page being explained is https://
duga: model syntax is referring to a spine item not a manifest item. A manifest item is not necessarily in the spine.
… referring to an item in the Spine is easier than referring to an item in the manifest.
Laurent: Showing examples of selectors.
ivan: The text selector was designed for a URL not HTML
… before this will go to the recommendation it will be looked at by other groups.
… I would prefer to use the work done by the web development group, rather than define the definition of the selector in the Working Group
duga: What is our fallback position if we propose solution that has not been defined by another group?
Laurent: There is a different fallback solution.
ivan: The Text Fragment selector is the preferred solution. but if it is not specified, then there is another solution already proposed.
Laurent: The Spatial selector will solve problems.
Hadrien: I would rather reference solutions from other groups, than have to define something so technical in this group.
<sueneu> +1 Hadrien
ivan: We will be in contact with that group before this proposal goes for recommendation. So we will be able to adjust the proposal before hand.
Laurent: The CSS selector is an alternate solution to the Text Fragment selector
sueneu: Do I need to identify an element in HTML in order to find it a CSS selector?
Laurent: No, CSS selectors will find content even if it is not specifically identified with an attribute.
Hadrien: Do we want this to be general enough that it will work in different applications than EPUB? What is the scope?
wendyreid: EPUBs are rendered on different types of devices. Our solutions need to be aware of the limitation is processing capability of older reading systems.
… it depends on the inner structure on how data is loaded in an older reading system. The backwards compatibility is an issue.
Hadrien: Reading systems will optimize their approach.
duga: Do we focus on resiliency over performance? +1 for CSS.
ivan: We have run into this technical hurdle before. CFI?
… let's use the technology CSS provides rather than trying to define something ourselves.
<ivan> +1 wendy
wendyreid: Having run into problems with bookmarks in the past, we need a robust solution.
duga: We need to keep the number of selectors small: Text, spatial, audio. We need a solution that will be actually implemented. Don't provide too many options for solving the same problem.
sueneu: Would the solutions work with older EPUBS?
Hadrien: It depends.
ivan: Based on today's discussion. Laurent will come up with different wording.
JXL in EPUB
<wendyreid> w3c/
duga: We need to fix the table that references media types regarding FXL
sueneu: I recommend we merge the PR and make a note to fix the table.
<wendyreid> Proposed: Merge PR 2899, adding JXL support and information on EPUB version for core media types.
<ivan> +1
<wendyreid> +1
<shiestyle> +1
<Dale> +1
<duga> 0
<gautierchomel_> +1
<CharlesL> +1
<sueneu> +1
<gman> +1
<Hadrien> +1
<MasakazuKitahara> +1
RESOLUTION: Merge PR 2899, adding JXL support and information on EPUB version for core media types.