<scribe> Agenda:

1. Discuss next steps for proposed vocabulary [1]

2. Discuss members and logistics of proposed joint TF

3. Plan time line

[1] http://www.w3.org/dpub/IG/wiki/DPUBVocabulary

<scribe> scribe: mgylling

Rick: you need to look at the current tazxonomy, for example your “title”, how does that map?

Tzviya: we have two columns, usage and definitions, which brings about a second question: are we defining this just in terms of HTML or mulitple languages?

Rich: its not just HTML, we are expanding ARIA for graphics and STEM.

… parts of it may exist in the ARIA spec today, or it may be a subclass of whats in the ARIA taxonomy today

Rich: we have in ARIA semantics aside for the abstract classes are targeted at: structural elements of web pages, interactive widgets, and some additional things that we find in forms today, that were gaps in HTML

… landmarks for example would be a structural element. In SVG, we’re gonna have a whole different set of semantics

… in SVG: what are the main concepts we’re gonna have in graphics, taking a look at the primitives, and what the interaction model has to be. We need to do the same with books

… a lot of these look like document structural elements is that correct?

Tzviya: some yes, and some of the come from testing as well

… wouldnt be structural per se

<tzviya> rich: it is important that a user will be interested in jumping to one of these elements. For example, will a user be interested in jumping to "assessment"

<janina> BRB -- Someone's at my door ...

<janina> I'm back ...

<tzviya> mgylling: what kind of document should we provide?

<richardschwerdtfeger> http://www.w3.org/TR/wai-aria-1.1/

<richardschwerdtfeger> http://www.w3.org/TR/wai-aria-1.1/#roles

Rich: you can reference the basic roles, talking about removing the RDF but the concepts remain

<richardschwerdtfeger> http://www.w3.org/TR/wai-aria-1.1/#roles

<tzviya> rich: refer to aria spec roles heavily, determine if there is a need to include calculation http://www.w3.org/TR/wai-aria-1.1/#namecalculation

<richardschwerdtfeger> http://www.w3.org/TR/wai-aria-1.1/#roles_categorization

<tzviya> rich: follow template of abstract roles in aria spec (section 5.3)

<richardschwerdtfeger> http://www.w3.org/TR/wai-aria-1.1/#heading

<tzviya> ...see Document structure roles

<tzviya> ...fairly straightforward to follow model, avoid duplication, is there something in the taxonomy already?

<tzviya> ...can any of ARIA landmarks solve issues?

<tzviya> ...can refer to ARIA spec for implementation and host languages

Rich: and then once you have the set of roles that you need

… map them to platform a11y APIs

… each platform has the ability to pass the role string along, I think, that may be your vehicle

as long as AT vendors

… know what these are it should work

Janina: regular editors meeting: 1st and 3d wednesday of every month 1800 UTC

<richardschwerdtfeger> http://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html

http://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html#mapping_role

<richardschwerdtfeger> http://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html#mapping_role

Rich: the host language restricts usage

<tzviya> rich: reach out to Shane McCarron to help with authoring and ReSpec

<tzviya> mgylling: concerns about restrictions on host language and implied elements (e.g. toc can be on nav only or children of bibliography are bibentry)

<tzviya> rich: these restrictions are on host language, talk to Steve Faulkner about HTML 5

"WAI ARIA Digital Publishing role module"

or something like that

decision to write the document in PF git space

<tzviya> Michael Cooper will set up GitHub repo for Joint TF

<richardschwerdtfeger> https://github.com/w3c/aria/

<scribe> ACTION: Janina to contect Michael Copper to set up Git repo for joint TF [recorded in http://www.w3.org/2014/12/17-dpub-minutes.html#action01]

<trackbot> Error finding 'Janina'. You can review and register nicknames at <http://www.w3.org/dpub/IG/track/users>.

<richardschwerdtfeger> Shane McCarron

Rich: here btw are current draft comics terms in the epub type vocabulary: http://www.idpf.org/epub/vocab/structure/#h_comics

Janina: ARIA 1.1 CR by end of next year

… modularization means all things dont have to get finished at the same time

… your module should depend on ARIA 1.1

This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/Rick/Rich/
Succeeded: s/semantis/semantics/
Succeeded: s/:/"/
Found Scribe: mgylling
Inferring ScribeNick: mgylling

WARNING: No "Topic:" lines found.

Default Present: Tzviya, Susann_Keohane, Markus, George_Kerscher, Rich_Schwerdtfeger, Janina
Present: Tzviya Susann_Keohane Markus George_Kerscher Rich_Schwerdtfeger Janina

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 17 Dec 2014
Guessing minutes URL: http://www.w3.org/2014/12/17-dpub-minutes.html
People with action items: janina

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report