George: in W3C CG epub 3.2 will be developped this year
… and update epub A11Y conformance to 1.1
… question : what could we sublmit to ISO for EPUB and a11Y standard
Makoto: Fast track procedure don’t need editng text
… but in normal procdure rewrting is necessary
Avneesh: IS intead of TW, for 3.0.1
Chage d scenario, A11Y to become is, we need 3.01 and 3.2 need to become IS
Makoto: estimaiton of the amount of work
… like precedence in SC34
… MUST replaced by SHALL
BillK: ediing language : Heather !
Makoto: study first as there may be other thing, Francis can do that
BillM: exploraiton that when 3.2 is done, cg to short lived WG and 3.2 becomes a REC
… W3C REC to ISO with no editing?
Makoto: Francis is now chair of SC34
… Sam Ho key person could help help W3C to push standards
… Yo San Cho agrees with proposal
… If 3.2 become a W3C REC, there a path submissing for it to become ISO
BillM: the idea og CG to become a WK, depends on members, was not the previous plan
Makato: since EPUB has not gone through W3C procedure, it coudl not be a REC
George: starting from a 3.2 CG note, proceed to WG with a charter to go through the REC process
… relatively quickly, a year and a half in W3C
BillM: it is a recent delepment
Cristina: same track for the a11Y ?
Makoto: only Korea did publsih it as an national standard
Avnesh: same path, one of the option
George: REC Track for a11y would be complecated because WCAG 2.1
… silver competing on the REC track?
Avneesh: Not competing
Makoto: a11y depends on schema.org as a registry, then it should be a standard for teh registry
Avneesh: workaround move the schema.org metdata to the techniques
laudrain: these steps should be summarized in a shred docuement
<Makoto> I am afraid that I cannot hear very well.
Makoto: Gho think we should give up the idea of fast track
Avneesh: action item to check with Yo san cho these options
… explore also 3.2 track as REC
Makoto: no editing in this case
George: 3.2 with editorial chanegs compatibel with ISO languge, how much time
Makoto: ballot next year, and start in June, ISO the neaxt year early
… schema.org to techniques, faster?
Cristina: taking in consideration by teh Europan act
Makoto: shadis (?)
<Makoto> XAdES
<Makoto> and eiDAS
<Makoto> in ETSI
George: language in IDPF spec are same as in W3C spec
… take the opportunity that 3.2 in harmony with W3C standards
… and 3.2 as as REC without language changing
<Makoto> eiDAS: https://en.wikipedia.org/wiki/EIDAS
… a11Y in harmony with sliver, and techniques as a module of W3C a11Y
… might help with the european standard
<Makoto> Not in Japan.
Avneesh: If EPUB4 available at that time as REC
<Cristina> I have no idea for Italy but I may check
Goerge: should be adopted as national standard
Avneesh: list of possible otpions
<Makoto> I cannot hear very well.
Luc: have the success and also the failure recorded in the docuement for each item
… so taht we remember in the future why we didn ot take that route
George: module for pub a11y with requirements in Pub but optional for the main web
<Cristina> sorry I have to go
… A11Y metadata otpional
Matt: IDPF follow basically the same language as W3C
Cristina, is it ok for you
<Bill_Kasdorf> s/A11y metadata optional/A11y metadata optional for Web, compulsory for EPUB
<Makoto> Option 1 (PAS): Creating W3C recommendations and then creating ISO/IEC standards via the PAS-submission procedure Option 2 (Normal process): Parallel development between W3C and ISO/IEC: W3C publishes a Community Group Note, and ISO/IEC publishes standards. Option 3 (Fast-track): Creating National Standards first (possibly after W3C publication) and then creating ISO/IEC standards via the fas-track procedure
<Makoto> No such work in SC34
Makoto: NISO to publish EPUB 3.0.1 as TS immediatly (?)
<Makoto> ISO/IEC will publish 3.0.1 as TSs
George to withdraw US objection
good night