ODD - Revision history

Kshawkin: /* Presentations */ added http://tei.it.ox.ac.uk/Talks/2014-10-odds/

2018-08-20T13:51:07Z

‎Presentations: added http://tei.it.ox.ac.uk/Talks/2014-10-odds/

Kshawkin: link to diagram of ODD processing pipeline

2018-08-20T13:49:50Z

link to diagram of ODD processing pipeline

Lou: /* See also */

2017-10-02T19:33:41Z

‎See also

Lou: /* See also */

2017-10-02T19:32:33Z

‎See also

Lou: /* Future plans: "Pure ODD" */

2017-10-02T19:27:39Z

‎Future plans: "Pure ODD"

Piotr Banski: /* Future plans: "Pure ODD" */ + doc

2017-03-15T19:07:53Z

‎Future plans: "Pure ODD": + doc

Piotr Banski: /* Documentation */

2017-01-05T02:03:40Z

‎Documentation

Mholmes: /* See also */

2016-12-31T23:38:11Z

‎See also

Mholmes: /* See also */

2016-12-31T23:37:50Z

‎See also

Mholmes: /* See also */

2016-12-31T23:37:22Z

‎See also

@@ Line 63: / Line 63: @@
 *[http://tei.oucs.ox.ac.uk/Oxford/2006-09-methNet/Talks/RomaJourney.ppt A PowerPoint presentation on TEI/ODD] by Laurent Romary; OUCS, September 2006
 *[http://www.balisage.net/Proceedings/vol7/html/Banski01/BalisageVol7-Banski01.html Literate serialization of linguistic metamodels] by Piotr Bański, Balisage-2011
 === Articles ===

← Older revision		Revision as of 13:49, 20 August 2018
Line 1:		Line 1:
−	'''ODD''' stands for "One Document Does it all". It is a TEI XML-conformant specification format that allows one to customize TEI P5 in a [[Wikipedia:literate programming\|literate programming]] fashion. It uses elements from the new [http://www.tei-c.org/P5/Guidelines/TD.html Documentation Elements] module.	+	'''ODD''' stands for "One Document Does it all". It is a TEI XML-conformant specification format that allows one to customize TEI P5 in a [[Wikipedia:literate programming\|literate programming]] fashion. It uses elements from the new [http://www.tei-c.org/P5/Guidelines/TD.html Documentation Elements] module and is designed for processing in a pipeline as in [http://tei.it.ox.ac.uk/Talks/2014-10-odds/oddity.png this diagram].

	== Description ==		== Description ==

@@ Line 49: / Line 49: @@
 == See also ==
 *[http://en.wikipedia.org/wiki/ODD_%28Text_Encoding_Initiative%29 ODD (Text Encoding Initiative)] in Wikipedia
-*[[ODD-dev]  Not updated since 2012]
+*[[ODD-dev]]   Not updated since 2012
-*[[ODD chaining] Not updated since 2012]
+*[[ODD chaining]]  Not updated since 2012
 === Documentation ===
 * [http://www.tei-c.org/Guidelines/Customization/odds.xml Getting Started with P5 ODDs]

@@ Line 49: / Line 49: @@
 == See also ==
 *[http://en.wikipedia.org/wiki/ODD_%28Text_Encoding_Initiative%29 ODD (Text Encoding Initiative)] in Wikipedia
-*[[ODD-dev]]
+*[[ODD-dev]  Not updated since 2012]
-*[[ODD chaining]]
+*[[ODD chaining] Not updated since 2012]
 === Documentation ===
 * [http://www.tei-c.org/Guidelines/Customization/odds.xml Getting Started with P5 ODDs]

@@ Line 39: / Line 39: @@
 * various standards proposal designed within ISO committee TC 37 have been totally or partially written in TEI/ODD: MLIF, MAF, ISO 16642 rev., ISOTimeML
-== Future plans: "Pure ODD" ==
+==  "Pure ODD" ==
 Over the years ODD has evolved in response to the needs of the TEI community, both as the core specification language for the TEI guidelines, and also as a generic customization language. Since 2004, much
-effort has been put into making it less of a hybrid language, combining its own vocabulary with RelaxNG fragments and Schematron rules. Versions of TEI P5 later than 2.5 contain elements which can be used to express content models directly in the TEI ODD language, rather than in RELAXNG. This work is ongoing in the TEI Technical Council, the goal being to make ODD an entirely self-contained generic specification language, independent
+effort has been put into making it less of a hybrid language, combining its own vocabulary with RelaxNG fragments and Schematron rules. Versions of TEI P5 later than 2.5 contain elements which can be used to express content models directly in the TEI ODD language, rather than in RELAXNG.  ODD is thus an entirely self-contained generic specification language, independent
-of other existing grammars, and hence known as Pure ODD.  See further [https://github.com/TEIC/pureodd "Pure ODD"]. There is a mailing list for discussing Pure ODD called [https://lists.sourceforge.net/lists/listinfo/tei-odds tei-odds].
+of other existing grammars, and hence known as Pure ODD.  The proposals for Pure ODD were included in the Guidelines during January 2016, and are included as part of the 3.0.0 release
-The proposals for Pure ODD were finally included in the Guidelines during January 2016, for inclusion as part of the 3.0.0 release
+If your existing TEI schema was developed prior to this release, you should probably read up on [http://teic.github.io/TCW/purifyDoc.html How to Update your ODD]
 == See also ==

← Older revision		Revision as of 19:07, 15 March 2017
Line 46:		Line 46:

	The proposals for Pure ODD were finally included in the Guidelines during January 2016, for inclusion as part of the 3.0.0 release		The proposals for Pure ODD were finally included in the Guidelines during January 2016, for inclusion as part of the 3.0.0 release
		+
		+	Now that the project has been completed, make sure to go on to read [http://teic.github.io/TCW/purifyDoc.html How to Update your ODD]

	== See also ==		== See also ==

@@ Line 52: / Line 52: @@
 *[[ODD chaining]]
 === Documentation ===
-*[http://www.tei-c.org/Guidelines/Customization/odds.xml Getting Started with P5 ODDs]
+* [http://www.tei-c.org/Guidelines/Customization/odds.xml Getting Started with P5 ODDs]
-*[http://www.w3.org/TR/xml-i18n-bp/#tei-modularization A fragment of W3C's Best Practices for XML Internationalization concerning ODD customization for the Internationalization Tag Set (ITS).]
+* [http://teic.github.io/TCW/howtoGenerate.html How to Make an ODD Automagically]
-*[[Mapping ODD processing]]
+* [http://teic.github.io/TCW/howtoChain.html ODD chaining for Beginners]
 === Presentations ===
 *[http://tei.oucs.ox.ac.uk/Oxford/2007-02-13-oucs/talk-odds.xml A talk about the ODD system], given on 13 Feb 2007 by Lou Burnard and Sebastian Rahtz at the OUCS ''Encoding Digital Texts'' workshop