Yes - the ARIA specs use it to have a common set of terms, as well as some external tables / sections that get pulled into the final doc. The RDFa docs use it to pull in external DTD / Schema files. On Mon, Dec 22, 2014 at 11:50 AM, Ivan Herman <ivan@w3.org> wrote: > > > On 22 Dec 2014, at 18:29 , Robin Berjon <robin@w3.org> wrote: > > > > On 22/12/2014 18:07 , Tobie Langel wrote: > >> On Mon, Dec 22, 2014 at 6:05 PM, Robin Berjon <robin@w3.org > >> <mailto:robin@w3.org>> wrote: > >> > >> Yes, that could very easily be the cause of the problem. In fact, > >> I'm pretty sure it was: I just made a change that ought to fix that. > >> > >> I was actually wondering why that changed had been made and thought > >> there was a valid reason to move it back. > >> > >> Should have asked on the PR. > >> > >> Mea culpa. > > > > I read through the same code and thought that it might make sense to > have dfn processing happen earlier. So that's that. > > > > Inclusion is a brittle, rarely used, and undertested feature. > > And damn useful! Not only it helped, in this case, share a glossary among > two files, but it also helped me to edit an ugly table in a separate files; > I hate editing huge files. So it is very useful! > > Thanks > > Ivan > > > > Unless we get a lot more tests for it it's likely not the last time we > break it a bit... > > > > -- > > Robin Berjon - http://berjon.com/ - @robinberjon > > > ---- > Ivan Herman, W3C > Digital Publishing Activity Lead > Home: http://www.w3.org/People/Ivan/ > mobile: +31-641044153 > ORCID ID: http://orcid.org/0000-0003-0782-2704 > > > > > -- Shane McCarron Managing Director, Applied Testing and Technology, Inc.
Received on Monday, 22 December 2014 17:59:01 UTC