[tei-council] Fwd: extra artefacts

[Sebastian Rahtz]

my message below didn't get any yay or nay responses.

can I get some feeling from folks over whether we should be
providing these beasts?

Sebastian

Begin forwarded message:

> From: Sebastian Rahtz <sebastian.rahtz at it.ox.ac.uk>
> Subject: Re: [tei-council] extra artefacts
> Date: 7 August 2012 23:14:01 BST
> To: <James.Cummings at it.ox.ac.uk>
> Cc: <tei-council at lists.village.Virginia.EDU>
> 
> How about this:
> 
> Source and data support files for TEI Guidelines
> 
> In addition to the schema modules and example customizations generated for each
> release of the Guidelines, a set of files are provided in the xml/tei/odd/ directory
> which are for use by those writing TEI tools such as editors or visualizations.
> 
> 	p5attlist.txt
> This is a text file with a comma-separated cataligue of all the attributes available on TEI elements,
> list the element or class name, the attribute name, the datatype, and  an indication ("multiple"
> or "single") as to whether it can contain multiple values. eg
> 	att.ascribed,who,data.pointer,multiple
> 
> 
> 	p5subset.json
> This is a representation of all TEI modules, classes, elements and attributes (with their
> descriptions) in JSON format for consumption by Javascript tools in web applications. For
> example, this fragment provides summary information about the <gi>ab</gi> element:
> 
> 	p5subset.xml
> This is copy of the reference component of the TEI source, extracting all
> the <gi>elementSpec</gi>, <gi>classSpec</gi>, <gi>macroSpec</gi>
> and <gi>moduleSpec</gi> elements, with descriptions. It does not include
> the text of the chapters of the Guidelines, and is intended for use by ODD processors
> which need to access all of the TEI components in a convenient single file.
> 
> 	stripspace.xsl.model
> This is a fragmeht of XSL which can be added to any transformation which 
> is being applied to a TEI document. It consists of a <xsl:strip-space> element
> which lists all the elements which can <emph>not</emph> contain character
> data. This tells the processor it can ignore white space around child components
> of these elements.

--
Sebastian Rahtz      
Director (Research Support) of Academic IT Services 
University of Oxford IT Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431