Generic Identifier: play
Classes: global structure
Status: REQUIRED
The overall container element.
Contains: head | front | text | back
Rationale: The term play lexically represents the documents the format of the pieces being marked up, thus being an excellent root element.
Occurs In: None, this is the root element
Declaration:
<!ELEMENT play (head, front?, text, back?)>
Example:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE play SYSTEM "play.dtd" >
<?xml-stylesheet type="text/css" href="play.css"?>
<play>
<head></head>
<front></front>
<text>
<act number="5">
<scene number="1">
<stagedirection>The SCENE is the Camp. A Noise of Drums and Trumpets. Enter <name>Aristomenes</name>, <name>Aristor</name>, <name>Demagetus</name>, <name>Alcander</name>, several Officers and Soldiers.
Enter an Officer from the other Door, and speaks to the General.
</stagedirection>
<line>
<speaker>Officer.</speaker>
<speech>My Lord! I'm from <styled how="italics">Alcander</styled> bid to say,
The Battle he has <regularization>marshall'd</regularization> as you <regularization>order'd</regularization>;
And that your Presence now is only wanted.</speech>
</line>
Generic Identifier: head
Classes: global structure
Status: REQUIRED
Large container for metadata concerning the play
Contains: play.metadata
Rationale: It will be helpful to have the general metadata about the dramatic work all be located in a specific place outside of the main text
Occurs In: play
Declaration:
<!ELEMENT head %play.metadata;>
Example:
Head is still a container in process. For this step in the dtd creation process we have not modeled any lower in this part of the hierarchy. These elements will contain DublinCore specific elements.
Generic Identifier: front
Classes: global structure
Status: OPTIONAL
Content that is part of the play, but comes before the play proper and may be thought of as separable from the main text of the play.
Contains: prologue | castList | section
Rationale: Most dramatic works have one or more sections that are distinct from the actual play that precede it.
Occurs In: play
Declaration:
<!ELEMENT front (castList | prologue | section)*>
Example:
<front>
<section>
<title>TO HER
GRACE
THE
DUTCHESS OF BOLTON.</title>
MADAM,
<p>When the Curious hand of Nature draws Perfection, when Beauty like yours appears, all are inspired with Wonder and Delight, every Heart is filled with Pleasure; because every Heart is full of you; Pardon my Ambition, Pardon the daring of a Pen, too weak to Coppy inimitable Graces; but if none may aim at your lovely Picture, unless they have Power to do you Justice, your Praises must be left unsung, and you for ever adored in Silence.
</p>
<p>I own the following Play claims not the least Merrit to such a Glorious Protection, but that is all I have to boast, all the reward my Towring Fancy covets, is centred in my Illustrious Patronesses; this will to after Ages make my Trifle Sacred, when they behold prefix'd such Names, whose Virtues Historians, Poets, and never dying Fame shall join with me to Eternize.</p>
</section>
<section type="dedication">
<title>THE DEDICATION</title>
<p>The Play is partly a Translation from the French; what I added, if it had not the power to please, had no Immodesty to offend, which I hope will be an attonement with your Grace, for other Defects in my Younger Brother; I wou'd have perswaded the World to prize Desert, before the Gifts of Fortune, but the major part are too sordid to like the Example, few are so truly Noble to fix without Intrest, which makes so very few truly happy in their Choice.</p>
<p>I woul'd have deferr'd Addressing to Your Grace, till I had aimed at an Offering more Worthy, but my Charmed Eyes being lately bless'd with the sight of You, have let into my mind such a Beautiful Idea, that I liv'd in pain till I express'd my Admiration.</p>
<p>To be Great and Good, and Exquisitly Fair, are the happiest Epethets Fate bestows on Mortals; that they are justly Your Graces due, will, I am sure, be confirmed by an Universal Voice; and that you may Live long to adorn the Titles, whose Lustre receive addition from that Beauteous Fame, is the Eternal wish off</p>
Generic Identifier: text
Classes: global structure
Status: REQUIRED
Contains the actual marked up text of the dramatic work
Contains: act | scene | section
Rationale: This is the very heart of what we are modeling. There can only be a single text per play. We are not facilitating multiple texts in one XML file.
Occurs In: play
Declaration:
<!ELEMENT text (%play.section;)*>
Example:
<text>
<act number="5">
<scene number="1">
<stagedirection>The SCENE is the Camp. A Noise of Drums and Trumpets. Enter <name>Aristomenes</name>, <name>Aristor</name>, <name>Demagetus</name>, <name>Alcander</name>, several Officers and Soldiers.
Enter an Officer from the other Door, and speaks to the General.
</stagedirection>
<line>
<speaker>Officer.</speaker>
<speech>My Lord! I'm from <styled how="italics">Alcander</styled> bid to say,
The Battle he has <regularization>marshall'd</regularization> as you <regularization>order'd</regularization>;
And that your Presence now is only wanted.</speech>
</line>
Generic Identifier: back
Classes: global structure
Status: OPTIONAL
Content that is part of the play, but generally comes after the play proper and may be thought of as separable from the main text of the play.
Contains: epilogue section
Rationale: Most dramatic works have one or more sections that are distinct from the actual play that follow the text.
Occurs In: play
Declaration:
<!ELEMENT back (epilogue?, section*)>
Example:
<back><epilogue><title>epilogue</title> We regret to announce the death of Lady Westholme, M.P., the result of a tragic accident. Lady Westholme, who was fond of travelling in out-of-the-way countries, always took a small revolver with her. She was cleaning this when it went off accidentally and killed her. Death was instantaneous. The deepest sympathy will be felt for Lord Westholme, etc., etc.</epilogue> </epilogue></back>
Generic Identifier: castList
Classes: Play Sections
Status: OPTIONAL
Listing of the cast in the play
Contains: PCDATA play.content | castMember
Rationale: The cast list is a particularly important subsection to delineate. It is a container for many other elements. As a distinct section of the front matter that occurs in many dramatic works, it enhances comprehension of a play and introduces many of the characters.
Occurs In: front
Declaration:
<!ELEMENT castList (#PCDATA | %play.content; | castMember)*> <!ATTLIST castList %ca;>
Example:
<castList>
<title>Dramatis Person .</title>
<castMember><character>Sir John Roverhead,</character> <description> A Beau</description>, <actor> Mr. Bowman</actor></castMember>
<castMember><character>>Elder Clerimont</character><description> a Country Squire</description>, <actor>Mr. Trout</actor>.</castMember>
<castMember> <character>Younger Clerimont</character><actor>, Mr. Verbruggen</actor>. </castMember>
<castMember><character>Belvoir</character>,<description> his Friend</description>, <actor>Mr. Thurmond</actor>. </castMember>
<castMember><actor>Mr. Rich</actor><actor>,</actor> <character>a Citizen</character>, </castMember>
<castMember><actor>Chris</actor><actor>.</actor> <description>Servant to Sir John</description>. </castMember>
<castMember><character>Toby</character> and <character>Jack</character>. <description>Servants to the two Clerimonts</description>. </castMember>
<title>WOMEN.</title>
<castMember><character>Mrs. Bracegirdle</character>, <actor>Lady Landsworth</actor>, <description>A Rich Widow of the North</description>. </castMember>
<castMember><character>Mrs. Barry</character>, <actor>Mrs. Rich</actor>.<description> a Fantastick City Widow</description>. </castMember>
<castMember><character>Mrs. Bowman</character>, <actor>Mrs. Clerimont</actor>. </castMember>
<castMember><character>Lucinda</character>,<description> Niece to the Widow Rich</description>. </castMember>
<castMember><character>Her Governess</character>. </castMember>
<castMember><character>Prince Lady la Basset</character><character> and</character> <character>Mrs. Trickwell</character>, <description>Gamesters</description>. </castMember>
<castMember><character>Mrs. Fidget</character>, <description>Landlady to Younger Clerimont.</description> </castMember>
<castMember><character>Betty</character>, <description>Mrs. Rich's Maid</description>.</castMember>
</castList>
Generic Identifier: section
Classes: play.section
Status: OPTIONAL
Non-specific section divider.
Contains: PCDATA play.content | play.section
Rationale: Design goal is to help facilitate specific, but allow generic tags for flexibility.
Occurs In: front | text | back | act | scene | section
Declaration:
<!ELEMENT section (#PCDATA | %play.section; | %play.content;)*> <!ATTLIST section %ca; %sectionAttribs; type CDATA #REQUIRED>
Example:
<section type="letter">
<title>TO HER
GRACE
THE
DUTCHESS OF BOLTON.</title>
MADAM,
<p>When the Curious hand of Nature draws Perfection, when Beauty like yours appears, all are inspired with Wonder and Delight, every Heart is filled with Pleasure; because every Heart is full of you; Pardon my Ambition, Pardon the daring of a Pen, too weak to Coppy inimitable Graces; but if none may aim at your lovely Picture, unless they have Power to do you Justice, your Praises must be left unsung, and you for ever adored in Silence.
</p>
<p>I own the following Play claims not the least Merrit to such a Glorious Protection, but that is all I have to boast, all the reward my Towring Fancy covets, is centred in my Illustrious Patronesses; this will to after Ages make my Trifle Sacred, when they behold prefix'd such Names, whose Virtues Historians, Poets, and never dying Fame shall join with me to Eternize.</p>
</section>
<section type="dedication">
<title>THE DEDICATION</title>
<p>The Play is partly a Translation from the French; what I added, if it had not the power to please, had no Immodesty to offend, which I hope will be an attonement with your Grace, for other Defects in my Younger Brother; I wou'd have perswaded the World to prize Desert, before the Gifts of Fortune, but the major part are too sordid to like the Example, few are so truly Noble to fix without Intrest, which makes so very few truly happy in their Choice.</p>
<p>I woul'd have deferr'd Addressing to Your Grace, till I had aimed at an Offering more Worthy, but my Charmed Eyes being lately bless'd with the sight of You, have let into my mind such a Beautiful Idea, that I liv'd in pain till I express'd my Admiration.</p>
<p>To be Great and Good, and Exquisitly Fair, are the happiest Epethets Fate bestows on Mortals; that they are justly Your Graces due, will, I am sure, be confirmed by an Universal Voice; and that you may Live long to adorn the Titles, whose Lustre receive addition from that Beauteous Fame, is the Eternal wish off</p>
<section type="ending">Madam,
Your Graces, most humble,
and most Obedient Servant, Mary Pix.
</section> Generic Identifier: act
Status: OPTIONAL
A single Act of a dramatic work.
Contains: PCDATA scene | section | play.content
Rationale: Acts are an important structural element of dramatic works.
Occurs In: text
Declaration:
<!ELEMENT act (#PCDATA | scene | section | %play.content;)*> <!ATTLIST act %ca; %sectionAttribs;>
Example:
<act n="1"> <scene n="2"> <line> <speaker>Dem</speaker> <speech> Still you're the Best of Men, as they <regularization>declar'd</regularization> you.</speech> </line> <line> <speaker> Aristom</speaker> <speech>Now let me fold <regularization>thee</regularization> thus, my Life's best Treasure! <stagedirection>[He embraces <name>Aristor</name>, but seems<regularization> disorder'd</regularization>, and not to feel him in his Arms, which he often clasps about him.</stagedirection> Thou dost not fill my Arms, 'tis Air I grasp: Nor do my Eyes behold thee- Where is my Son, ha! where is my <name>Aristo</name>? </speech> </line> <line> <speaker>Aristor</speaker> <speech> Here my dear Lord, here pressing to your Bosom.</speech> </line> <stagedirection> [His Voice seems to<name> Aristomenes</name> (still under his disorder) to be low and different to what it was usually. </stagedirection> </scene></act>
Generic Identifier: scene
Classes: play.section
Status: OPTIONAL
Scenes
Contains: section | play.content
Rationale: Scenes are important structural elements of dramatic works.
Declaration:
<!ELEMENT scene (#PCDATA | section | %play.content;)*> <!ATTLIST scene %ca; %sectionAttribs;>
Example:
<scene n="3">
<line>
<speaker> Aristor. </speaker>
<speech> What means my noble Father! </speech>
</line>
<line>
<speaker> Aristom</speaker>
<speech>. Till now, my faithful Senses never <regularization>fail'd</regularization> me.
They talk of Omens, ha! I must not think <regularization>on't</regularization>;
Such chilling Damps <regularization>wou'd</regularization> blast a Day of Battle:
<stagedirection> [ Aside. </stagedirection>
Yet let my evil Genius but be true,
And a <regularization>fam'd</regularization> End is all it can portend me.
</speech> </line>
<line>
<speaker> Aristor</speaker>
<speech> You reason with your self, and turn from us.
May we not know what <regularization>thus</regularization> disturbs your Thoughts?
</speech>
</line>
<line>
<speaker> Aristom</speaker>
<speech><regularization>Nothinga</regularization><regularization>Vapour</regularization> crossed me, but <regularization>'tis</regularization> gone:
And now the Field, the dusty Field, my Sons,
Must be the Scene, where we shall nobly act
What our great Spirits, and our Country urges.
The Trumpet calls, with the impatient Drum;
And He that loves his <regularization>Honour</regularization>, let him come. </speech>
</line>
<stagedirection>
[ He draws his Sword and goes off follow'd by the rest with their Swords drawn, Drums and Shouts of Battle immediately succeed. </stagedirection>
</scene> Generic Identifier: prologue
Status: OPTIONAL
A prologue that is distinct from the main text of the play.
Contains: PCDATA play.content
Rationale: Prologues are important and common enough in a variety of dramatic works to make it helpful to have a non-generic section indicating them.
Occurs In: front
Declaration:
<!ELEMENT prologue (#PCDATA | %play.content;)*> <!ATTLIST prologue %ca; %sectionAttribs;>
Example:
<prologue>
<title>PROLOGUE</title>
<stagedirection>SPOKE BY<name>MR. BOWMAN.</name></stagedirection>
<line>
<speaker>Mr. Bowman</speaker>
<speech>Your Servant Ladies fair---And how I pray,
Like you my Dress and Garniture to Day.
'Faith I've survay'd my self from Top to Toe,
And find I make a most Accomplish'd Beau.
If all these Charms, to win a Fortune fail,
I'le leave Champagne, and drown my shape in Ale;
What care I if I'm bigger than a Whale?
But why should I despair of being Blest.
Can Female Heart withstand a Man thus Drest?
As I was lately Walking in the Mall,
Heav'ns how the Ladies flock'd about me all.
I'le vow they came so Termagently Fierce on,
I fear'd some strange designs upon my Person.
Says one, and faith the Nymph was well enough,
Mind, with what Air and Grace he takes his Snuff,
The second cry'd, and pray observe his Muff.
</speech>
</line>
<line>
<speaker>Mr. Bowman</speaker>
<speech>My Sword-Knot charm'd the fancy of the third,
Poor simple thing she scarce cou'd speak a Word.
And I, replies the fourth, Alass am Slain
With the Celestial motion of his Cane.
The Fifth was strangely smitten with my shape;
Nay hold, I cried, you wont commit a Rape?
For mine, and for your own dear sakes be quiet,
Or Ladies I'le endite you for a Riot.</speech>
</line>
<line>
<speaker>Mr. Bowman</speaker>
<speech>But hold---there's something I was begg'd to say,
In favour of our modest Authors Play.
He hop'd you'd like---but Ha! the Bird is Flown, <stagedirection>[feeling in his Pockets.] </stagedirection>
No matter, I'le say something of my own.
Know then, our Comedy first came from France,
Which here perhaps, its Fortune may advance.
Ladies, be you as kind as you are pretty,
And you Gallants as merciful as Witty:
Then may both Stage and Poet hope to thrive,
Tis by your Bounty both are kept alive.
</speech>
</line>
</prologue> Generic Identifier: epilogue
Status: OPTIONAL
An epilogue that is distinct from the main text of the play and follows it.
Contains: PCDATA play.content
Rationale: Epilogues are important and common enough in a variety of dramatic works to make it helpful to have a non-generic section indicating them.
Occurs In: back
Declaration:
<!ELEMENT epilogue (#PCDATA | %play.content;)*> <!ATTLIST epilogue %ca; %sectionAttribs;>
Example:
epilogue><title>epilogue</title> We regret to announce the death of Lady Westholme, M.P., the result of a tragic accident. Lady Westholme, who was fond of travelling in out-of-the-way countries, always took a small revolver with her. She was cleaning this when it went off accidentally and killed her. Death was instantaneous. The deepest sympathy will be felt for Lord Westholme, etc., etc.</epilogue> </back
Generic Identifier: line
Status: REQUIRED
A single line (prose or metric) in the play
Rationale: Being able to search by line, and by speaker is a probable use scenario. Having a controlled vocabulary of characters and linking to them with IDREFS will help with that.
Occurs In: play.section
Declaration:
<!ELEMENT line (speaker+, speech)>
<!ATTLIST line %ca;
speakers IDREFS #IMPLIED
type CDATA #IMPLIED> Example:
<line> <speaker> Aristom</speaker> <speech>From what far distant Valley comes <regularization>thy</regularization> Voice? It seems so hollow, scarce my Ear receives it. </speech> </line>
Generic Identifier: castMember
Status: OPTIONAL
Container element for a single cast member
Contains: character | description | actor
Rationale: castMember acts as a container for elements of the castlist. These cast member listings can be used to create a controlled vocabulary of namesof people in the play.
Occurs In: castList
Declaration:
<!ELEMENT castMember (#PCDATA | character | description | actor)*>
Example:
<castList> <castMember> <character>Violet</character> <description>Sister to Sebastian</description> <actor>Jane Doe</actor> </castMember> </castlist>
Generic Identifier: character
Status: REQUIRED
Name of the character in the castlist
Contains:
Rationale: As an intricate part of the front matter of a play, indicating the character names not only hierarchically divides different segments of the cast list, but can serve as an identification function within the play. By establishing unique identifiers for each character in the play, searching and linking becomes easier. One of the goals of the project is to help undergraduates understand dramatic works with more ease. One area where undergraduates become most confused is with character names and keeping straight who does what. Marking up individual character names in the cast list will be the central component in organizing these names in a way that will assist in dramatic comprehension.
Occurs In: castMember
Declaration:
<!ELEMENT character (#PCDATA | %play.inline;)*> <!ATTLIST character %ca;>
Example:
<castMember><character>Sir John Roverhead,</character> <description> A Beau</description>, <actor> Mr. Bowman</actor></castMember>
Generic Identifier: description
Status: OPTIONAL
The element that marks a description of a dramatic character. This element is found in the cast list.
Contains: PCDATA | play.inline
Rationale: A description of a character found in the cast list can, but may not be found in a dramatic work. Yet, when a description is present is serves a very different function that other parts of the cast list. Often it is this description that gives the reader and actor a better idea about who the character is, where that character comes from, and how that character relates to other characters in the play.
Occurs In: castMember
Declaration:
<!ELEMENT description (#PCDATA | %play.inline;)*>
Example:
<character>Belvoir</character>,<description> his Friend</description>, <actor>Mr. Thurmond</actor>
Generic Identifier: actor
Status: OPTIONAL
The names an actor who is listed as having played a certain character. This element is found in the cast list.
Contains: PCDATA | play.inline
Rationale: In some texts, especially manuscripts of plays, the name of the performers of a certain performance are listed. For historical purposes this may be interesting for a researcher or student to know.
Occurs In: castMember
Declaration:
<!ELEMENT actor (#PCDATA | %play.inline;)*>
Example:
<character>Hamlet</character>,<description> Prince of Denmark</description>, <actor>Sir Lawrence Olivier</actor>
Generic Identifier: speaker
Status: REQUIRED
Identifies a single speaker of a line
Contains: PCDATA play.inline
Rationale: For presentational issues, we chose to use the "line" tag as a container because it may be easier to pull out the speaker's name and place it in the left margin in a way that imitates printed dramatic works.
Occurs In: line
Declaration:
<!ELEMENT speaker (#PCDATA | %play.inline;)*>
<!ATTLIST speaker %ca;
character IDREF #IMPLIED> Example:
<line> <speaker> Aristom</speaker> <speech>From what far distant Valley comes <regularization>thy</regularization> Voice? It seems so hollow, scarce my Ear receives it. </speech> </line>
Generic Identifier: speech
Status: REQUIRED
The spoken part of a line
Contains: PCDATA play.inline
Rationale: After choosing to wrap the name of speaker of a line in a tag named "speaker", another discussion, probably our biggest argument, was about if spoken part of the line should be wrapped in a tag as well. One argument was that it was unnecessary to wrap the spoken part of the text within the line because it served no function. Another argument was that wrapping the spoken text was not only necessary, but tidy and general good mark-up. In the end it was decided that the spoken text should be wrapped because of the hierarchy. If the spoken text were not marked, then the "speaker" tag would be on an entirely different hierarchical level than the rest of the material in the line. This structure would show the encoder that the spoken part of the text was of less importance and would do injustice to the genre.
Occurs In: line
Declaration:
<!ELEMENT speech (#PCDATA | %play.inline;)*> <!ATTLIST speech %ca; >
Example:
<line> <speaker>Officer.</speaker> <speech>My Lord! I'm from <styled how="italics">Alcander</styled> bid to say, The Battle he has <regularization>marshall'd</regularization> as you <regularization>order'd</regularization>; And that your Presence now is only wanted.</speech> </line>
Generic Identifier: stagedirection
Status: OPTIONAL
This element is used to identify the parts in and outside of lines that are used as stages directions.
Contains: PCDATA play.inline
Rationale: A stage direction occurs in multiple areas of a dramatic text and is used to tell the viewer, reader, or actor what type of physical action is suggested by the playwright for the actor to perform.
Occurs In: play.section
Declaration:
<!ELEMENT stagedirection (#PCDATA | %play.inline;)*> <!ATTLIST stagedirection %ca; type CDATA #IMPLIED>
Example:
<stagedirection>[He embraces <name>Aristor</name>, but seems<regularization> disorder'd</regularization>, and not to feel him in his Arms, which he often clasps about him.</stagedirection>
Generic Identifier: title
Status: OPTIONAL
This is used to indicate the title of the play as well as titles scenes, acts, or sections.
Contains: PCDATA play.inline
Rationale: For metadata and identification purposes, an element identifying the title can be helpful.
Occurs In: head | play.section
Declaration:
<!ELEMENT title (#PCDATA | %play.inline;)*> <!ATTLIST title %ca;>
Example:
<front>
<section>
<title>TO HER
GRACE
THE
DUTCHESS OF BOLTON.</title> Generic Identifier: note
Status: OPTIONAL
An element used to encode a note found within a text.
Contains: PCDATA play.inline
Rationale: When encoding a document, texts may or may not be transcribed from previously printed documents. The note tag is used to identify notes, footnotes, margin notes, or endnotes found in the original text.
Occurs In: play.section | play.content
Declaration:
<!ELEMENT note (#PCDATA | %play.inline;)*> <!ATTLIST note %ca; %noteAttribs;>
Example:
<note>This play was first performed at the Rose theater before it was banned in 1634.</note>
Generic Identifier: comment
Parameter Entity Classes: play.comment
Status: OPTIONAL
A comment is a professor's personal description about how a portion of the text is being interpreted.
Contains: PCDATA play.inline
Rationale: Knowing how a professor interprets certain parts of a play can be helpful to a student taking that professor's class. Also, the distinct between a subjective and objective reading is necessary in a student's development of dramtic interpretation skills.
Occurs In: play.section | play.content
Declaration:
<!ELEMENT comment (#PCDATA | %play.inline;)*> <!ATTLIST comment %ca; %noteAttribs;>
Example:
<comment creator="matthews">In my research, I have found that during the period this play was written the term "earnest" was a colloquial word for homosexuality.</comment>
Generic Identifier: explication
Status: OPTIONAL
An explication is an element that is used to explain different aspects in a particular part of the drama.
Contains: name
Rationale: In many situations, students can be confused by the action of the play compared to the dialog--this may be especially true with Shakespearean English. The explication/explanation element allows professors to explain what exactly is going on in the play. This is not to be confused with opinions found in the comment tag.
Occurs In:
Declaration:
<!ELEMENT explication (#PCDATA | %play.inline;)*> <!ATTLIST explication %ca; %noteAttribs;>
Example:
<explication>Often in Shakespearean plays, higher class characters lines are written in verse and the lines of lower class characters will be written in prose. </explication>
Generic Identifier: regularization
Status: OPTIONAL
A regularization marks a word that is not in current American English.
Contains: PCDATA play.inline
Rationale: In order to help students understand a play better, some antiqued terms or alternative spellings need to be regularized to current American English. For this project the regularization will consist of only the word in the text and the current word the original represents.
Occurs In:
Declaration:
<!ELEMENT regularization (#PCDATA | %play.inline;)*> <!ATTLIST regularization %ca; new CDATA #IMPLIED>
Example:
<regularization new="failed">fail'd</regularization>
Generic Identifier: Name
Status: OPTIONAL
General purpose name element
Contains: PCDATA play.inline
Rationale: To capture and highlight important names
Occurs In: Any inline element content
Declaration:
<!ELEMENT name (#PCDATA | %play.inline;)*> <!ATTLIST name %ca; type CDATA #IMPLIED standard CDATA #IMPLIED>
Example:
<name type="person" standard="Benvolio">Ben.</name>
Generic Identifier: styled
Status: OPTIONAL
This tag identifies certain parts of the text that may not have a structural function, but need to be identified due to how it looks.
Contains:
Rationale: In a text there are often words that differ from the words around them only due to presentation. Presentational elements need to be distinguished when visually presenting a text.
Occurs In:
Declaration:
<!ELEMENT styled (#PCDATA | %play.inline;)*> <!ATTLIST styled %ca; how CDATA #REQUIRED>
Example:
<line>The Trumpet calls, with the <styled how="italics">impatient</styled> Drum; </line>
Entity Name: play.global
Things common to all elements in the play
Contains:
Declaration:
<!ENTITY % ca 'id ID #IMPLIED
name CDATA #IMPLIED '>
Rationale: These are common to all elements, optionally all can be named and identified.
Entity Name: play.content
Content elements
Contains: PCDATA play.inline
Declaration:
<!ENTITY % play.content 'title | p | line | stagedirection | note | comment | explication '>
Rationale: Content are element level items that appear as first level children of sections of plays.
Entity Name: play.commentary
Extra-textual notes, comments, and explications
Contains: PCDATA play.inline
Declaration:
<!ENTITY % play.commentary ' note | comment | explication '>
Rationale: Commentary items are content items, but all share some extra attributes.
Entity Name: play.section
Section-level elements (act, scene, section)
Contains: PCDATA play.content | play.inline
Declaration:
<!ENTITY % play.section 'section | act | scene'>
Rationale: Play sections are the large containing elements of plays that contain and delineate the content.
Entity Name: play.inline
Inline content
Contains: PCDATA play.inline
Declaration:
<!ENTITY % play.inline 'regularized | name | styled | note | comment | explication'>
Rationale: Inline content is content that can be contained within content-level or inline-level elements.