- From: Markus Gylling <markus.gylling@gmail.com>
- Date: Wed, 04 Feb 2015 12:48:58 +0100
- To: "public-dpub-aria@w3.org" <public-dpub-aria@w3.org>
- Message-ID: <54D2072A.4080306@gmail.com>
Hi all, FYI, I just synced up some stuff [1] for the 4 skeleton terms that reflects the input we got on the call last week. We are still pending on the JS autogeneration of some (+to know which) fields based on inheritance from the mother spec -- that's one reason why they still look a tad, shall we say, bleak. Using inlined .ednotes to capture all questions/open issues we've got so far. To remind ourselves, where Tzviya and I would like to get asap is to a point where these four terms look generally ok in terms of the actual layout, so that we can fill in the rest of the terms, publish a first ed draft, and then get going on the real discussions re inheritance, differentiation, superfluousness, behaviors etc. [1] https://github.com/w3c/aria/commits/master/aria/dpub.html /markus > Markus Gylling <mailto:markus.gylling@gmail.com> > 26 Jan 2015 14:22 > Hi all, > I just pushed 4 skeleton role defs to aria/dpub.html in master. In > hopes that they will be good to serve for the initial exercise of the > approach, I chose the four terms relating to glossaries (this gives us > a xhv vocab dupe, parent/child relationships, region and atomic types, > and a link type). Shane, I looked in the wiki for parent roles, but > didnt see any (or did I look at the wrong page? [1]); made up three of > my own in the meanwhile. And, needless to say, many placeholders left > to fill in. > > For now, /markus > > [1] https://www.w3.org/dpub/IG/wiki/DPUBVocabulary >
Received on Wednesday, 4 February 2015 11:49:33 UTC