Yes. Personally I think it's a good idea to suppress them in this case, since the surrounding prose already comments on what the namespace prefixes mean, and (as you rightly say) in the real world you wouldn't declare them at this level anyway. On 08/10/15 14:05, Hugh Cayless wrote:
In fact they are. This seems to be a Stylesheets thing. The PDF version prints the namespace nodes, but the web version elides them. I'm pretty sure I could print them properly, but I'd rather not be mucking around right before a release in case there are unexpected side effects.
On Thu, Oct 8, 2015 at 8:53 AM, James Cummings
wrote: Maybe I'm missing earlier discussion but with the examples on the ref page why not declare the namespace prefixes on xenodata? (Yes, in reality you'd do it on root TEI.)
James
-- Dr James Cummings, Academic IT, University of Oxford
-----Original Message----- From: Hugh Cayless [philomousos@gmail.com] Received: Thursday, 08 Oct 2015, 8:08 To: TEI Council [tei-council@lists.tei-c.org] Subject: [tei-council] Release?
The modified xenoData sections are viewable at
http://teijenkins.hcmc.uvic.ca/job/TEIP5/lastSuccessfulBuild/artifact/P5/rel... and
http://teijenkins.hcmc.uvic.ca/job/TEIP5/lastSuccessfulBuild/artifact/P5/rel...
Can at least some of you look them over and either approve or suggest/make corrections?
Once that's done, we need to decide whether we're proceeding with the release today. tomorrow, or at some later date. I don't have an opinion yet in the absence of feedback on the latest changes, except to say that I'd like to get this over with. -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived