Dear Syd,
I think the abstract is fine. In order to shorten it I agree with Raff to drop one or two of the longer examples. In case you don't want to drop "Itsy Bitsy Teeny Weeny Simple Hypertext DTD" you can probably merge the last sentence with the third from last, e.g.:
"This paper will describe (and the talk demonstrate use of) the 'tei_customization' which is not intended to produce a schema that can tell you what is "correct" or "incorrect", but rather an editing assistant to *help* you write a TEI customization."
Best,
Martina
Von meinem iPad gesendet
Am 15.05.2017 um 16:31 schrieb Raffaele Viglianti mailto:raffaeleviglianti@gmail.com>:
Looks great! If you wanted a simpler title I would just leave it at "A TEI
customization for writing TEI customizations". To get to <= 300 words you
could maybe start by cutting a few examples of schemata and customizations,
especially the longer ones.
Did I remember reading there's likely going to be a deadline extension?
Raff
On Sun, May 14, 2017 at 9:36 PM, Elisa Beshero-Bondar mailto:ebb8@pitt.edu> wrote:
Hi Syd-- It's hard to think of a better title than the one you've given it,
unless you call it (as you have in the past) "ODD for ODDs" before the
colon instead of "tei_customization".
Meanwhile I'm cobbling together an abstract on teaching with TEI, building
on the talk I gave at the public day in Prague--in which I propose that a
great way to teach TEI is in the context of repurposing an "old" document.
Elisa
On Sun, May 14, 2017 at 5:41 PM, Syd Bauman mailto:s.bauman@northeastern.edu>
wrote:
Dear Council,
Here is a 1st crack at my submission for the TEI conference, due
tomorrow. I've listed all fields, but am only asking y'all to review
and edit the abstract (which has to be <= 300 words -- it currently
has 329), and to suggest a better title if one jumps to mind.
##################################
Title
-----
tei_customization: A TEI customization for writing TEI customizations
Abstract
--------
The TEI ODD language (and the more modern version thereof, Pure ODD)
can be used for two related, but distinctly different purposes: 1) to
*create* a markup language, including documentation and schemas; and
2) to *customize* a markup language that was already written in ODD.
There are several examples of (1), including the TEI Guidelines, the
Music Encoding Initiative, the ISO Feature Structure encoding system,
the W3C Internationalization Tag Set, and a version of the Itsy Bitsy
Teeny Weeny Simple Hypertext DTD. And there are several well known
examples of (2), including TEI Lite, TEI Tite, TEI Simple Print,
CBML, DALF, DHQ, jTEI, and the TEI in Libraries Best Practice
Guidelines. But the TEI Guidelines are not meant to be used out of
the box -- *every* TEI project is expected to customize the TEI, thus
they are all expected to create a customization in ODD. The
'tei_odds' customization provided by the TEI is, understandably, a
schema intended to check conformance with the rules for using ODD.
Because ODD is used for two different things, and for both TEI and
non-TEI languages, those rules are necessarily much more broad than
those for writing TEI customizations. E.g., the value of the @key
attribute of <moduleRef> can be any XML name. But when used to write
a TEI customization, the only valid values are the actual names of
TEI modules (e.g., "core", "textstructure", "header", "namesdates").
The tei_customization customization is not intended to produce a
schema that can tell you what is "correct" or "incorrect", but rather
to *help* you write a TEI customization. So, e.g., only the names of
TEI modules are allowed as values of moduleRef/@key, and thus your
editor can give you a pop-up box of those values. This paper will
describe (and the talk will demonstrate use of) tei_customization,
and discuss the interesting twist that this is not a schema whose
rules must be obeyed, but rather an editing assistant.
Keywords
--------
TEI, Customization, ODD
Bibliography
------------
2016-08: "The Hard Edges of Soft Hyphens." Presented at Balisage: The
Markup Conference 2016, Washington, DC, August 2-5, 2016.
In Proceedings of Balisage: The Markup Conference 2016.
Balisage Series on Markup Technologies, vol. 17 (2016). DOI:
10.4242/BalisageVol17.Bauman01.
2013-10: "TAPAS and the TEI: An Update and Open Discussion" with
Julia Flanders and Elena Pierazzo. Presented at The Linked
TEI: Text Encoding in the Web: the TEI Conference, 2013,
Rome, Italy, October 2-5, 2013
2013-06: "Encoding Historical Financial Records" with Kathryn
Tomasek. Presented at Digital Humanities 2013, Lincoln, NE,
July 17, 2013.
2012-11: "Encoding Financial Records for Historical Research" with
Kathryn Tomasek. Presented at TEI and the C{rl}O{wu}D: the
Text Encoding Initiative Conference, 2012, College Station,
TX, November 8-10, 2012. In _Journal of the Text Encoding
Initiative_, Issue 6 | December 2013. URL:
http://jtei.revues.org/895; DOI: 10.4000/jtei.895
2011-08: "Interchange vs. Interoperability." Presented at Balisage:
The Markup Conference 2011, Montr?al, Canada, August 2-5,
2011. In Proceedings of Balisage: The Markup Conference
2011. Balisage Series on Markup Technologies, vol. 7 (2011).
doi:10.4242/BalisageVol7.Bauman01.
Remark / Message to the Program Committee and Chairs
------ - ------- -- --- ------- --------- --- ------
Although I am indeed affiliated with Northeastern University (and
that institution must be listed), I am also affiliated with the TEI
Council, who charged me with writing this paper.
--
tei-council mailing list
tei-council@lists.tei-c.orgmailto: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
--
Elisa Beshero-Bondar, PhD
Director, Center for the Digital Text | Associate Professor of English
University of Pittsburgh at Greensburg | Humanities Division
150 Finoli Drive
Greensburg, PA 15601 USA
E-mail: ebb8@pitt.edumailto:ebb8@pitt.edu mailto:ebb8@pitt.edu>
Development site: http://newtfire.org
--
tei-council mailing list
tei-council@lists.tei-c.orgmailto: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.orgmailto: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
