-
Notifications
You must be signed in to change notification settings - Fork 0
/
RI.Prov.BU.Class.G.Sq.IG_I3_1380.xml
327 lines (269 loc) · 19.1 KB
/
RI.Prov.BU.Class.G.Sq.IG_I3_1380.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
<?xml version="1.0" encoding="UTF-8"?>
<?oxygen RNGSchema="http://dev.stg.brown.edu/projects/usepigraphy/schema/exp-epidoc.rng" type="xml"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xmlns:xi="http://www.w3.org/2001/XInclude">
<teiHeader>
<fileDesc>
<!-- ************************************* <titleStmt> *********************************
Used to group information about the title of a work and its creator.
<title> stores the US Epigraphy number as it will appear when it is displayed. It is the "real" US Epigraphy number
that is based on the collection's accession number and can contain characters such as ? * # + / and [space].
-->
<titleStmt>
<title>RI.Prov.BU.Class.G.Sq.IG I3 1380</title>
</titleStmt>
<!-- ************************************* <publicationStmt> *********************************
Used to group information about the publication and permissions of a work. All files will have a US Ep. copyright
statement, which is stored in an external file called include_publicationStmt.xml. In the future, if a collection has
special copyright or permissions, we can add more information after the included file.
<idno>: Repeat the value that is in <title>.
@xml:id is the machine readable US Epigraphy number. This is the US Epigraphy number in the title
element above, with any illegal characters such as ? * # & + [space] replaced with a set of predeterimined
characters that are legal in XML names and viable URLs. See the wiki for the list of substitutions.
-->
<publicationStmt>
<xi:include
href="http://dev.stg.brown.edu/projects/usepigraphy/xml/include_publicationStmt.xml">
<xi:fallback>
<p>The Publications Statement should appear in this space.</p>
</xi:fallback>
</xi:include>
<idno type="USEpigraphy" xml:id="RI.Prov.BU.Class.G.Sq.IG_I3_1380">RI.Prov.BU.Class.G.Sq.IG I3 1380</idno>
</publicationStmt>
<!-- ************************************* <sourceDesc> ********************************* -->
<sourceDesc>
<!-- ************************************* <msDesc> *********************************
<msIdentifier>** breaks out the information that is packed into the US Epigraphy number into its component parts,
and spells each part out.
<region> corresponds to the first part of the number = state
<settlement> corresponds to the second part = city
<institution> is optional, but is used if there is a university or other entity to which the collection belongs
<repository> is the third or fourth part of the number = museum or collection where the inscription is housed
<idno> is the last part of the number, and generally represents the accession number the inscription has been given by the collection that houses it.
It should correspond to the last component of <title>.
If there is more repository information, or if the inscription is known by another name, this information can
be encoded using <altIdentifer>, which has the same elements as <msIdentifier>, or by <msName>, which contains text.
-->
<msDesc>
<msIdentifier>
<region>RI</region>
<settlement>Prov</settlement>
<institution>BU</institution>
<repository>Class</repository> <!-- optional -->
<idno>Sq.IG I3 1380</idno>
</msIdentifier>
<!-- ************************************* <msContents> *********************************
<msContents>** is normally used to describe the contents of an inscription.
<textLang> has two attributes: @mainLang which is used for the language in which the inscription is written
and @otherLangs which can have as its values one or more other languages found in the inscription. The
values of both attributes must use the proper codes, so if you need a language for which there is no
code listed, please ask. This element can have content if it is necessary to explain something.
<msItem> contains a short summary of the content of the inscription. It can have other markup within
such as <persname>, <foreign> or <emph>. If there is more than one inscription or face, there
can be more than one <msItem>. The genre of the inscription is encoded in @class
using one or more values from the genre taxonomy. The first character of the attribute value should be a #.
-->
<msContents>
<textLang mainLang="grc"/> <!-- la, grc, ett ?? -->
<msItem class="#funerary.epitaph">
<p>Base of the funerary stele of Lampito.</p>
</msItem>
</msContents>
<!-- ************************************* <physDesc> ********************************* -->
<physDesc>
<!-- ************************************* <objectDesc> *********************************
<objectDesc> contains information about the physical properties of the object and the inscribed text.
@ana contains one or more controlled values for the type of support, from the form section
of the taxonomy. You may use more than one value, separating values with a
space. ex: ana="#ash_urn #base"
<supportDesc> contains a range of information about the support.
@ana contains one or more controlled value for the inscribed material from the material section
of the taxonomy.
<support> contains a <p> with free text about the material and the form of the support, and a structured
component that records the dimensions of the support.
<p> should have one or two short sentences that describe the form and material of the support. The <seg>s
may optionally be used to demarcate detailed information about each within the sentence.
<dimensions>
@type indicates what the dimensions are measuring, for example, "surface"
@unit indicates the unit of measurement.
Note that instead of <height>, <width> and <depth> it is possible to use <dim type="xx">.
This may be useful for round objects. There can be more than one dimensions element.
<condition> can contain free text that describes the condition of the inscription. [optional]
@ana contains a controlled value from the preservation category of the taxonomy.
-->
<objectDesc ana="#">
<supportDesc ana="#xx">
<support>
<p></p>
<dimensions type="surface" unit="cm">
<height/>
<width/>
<depth/>
</dimensions>
<p/>
</support>
<condition ana="#fragment.single">
<p />
</condition>
</supportDesc>
<!-- ************************************* <layoutDesc> *********************************
This is where information about the format of the text is encoded.
Use <locus> to narrow down part of inscription being discussed if necessary.
<layout> can have free text content inside the <p> that provides more detailed information. [optional]
@columns and @writtenLines record the number of columns and number of lines.
-->
<layoutDesc>
<layout columns="1" writtenLines="3">
<p/>
</layout>
</layoutDesc>
</objectDesc>
<!-- ************************************* <handDesc> *********************************
Contains information about types of writing and means of inscription.
<handNote> is a repeatable element, so that it can handle more than one type of writing.
@ana has one or more values from the writing taxonomy.
Any more specific information is contained inside <handNote>. If there is more than one type of writing,
add @hands (<handDesc hands="2">).
-->
<handDesc>
<handNote ana="#xx">
</handNote>
</handDesc>
<!-- ************************************* <decoDesc> *********************************
US Epigraphy doesn't use this much yet, but this is where information about any decorations will go.
<decoNote> is a repeatable element, so that it can handle more than one decoration.
@type has one or more values from the decoration taxonomy, and any more specific information
is contained inside <decoNote>
-->
<decoDesc>
<decoNote ana="#xx">
<p/>
</decoNote>
</decoDesc>
</physDesc>
<!-- ************************************* <history> *********************************
This section is for the history of the inscription.
<summary> currently used only if it is necessary to indicate if an inscription is genuine or fake.
If fake, put the text "fake" inside <rs>. Ex: <rs>fake</s>
[This is a USEp. convention for now, to indicate if an inscription is fake.]
<origin> encodes the origin of inscription including place and date.
<provenance> can appear multiple times, and encodes any additional events in the history of the inscription.
Not currently in use.
<date> use 4 digit years, with leading zeros. BCE has a - sign in front of the number. Both @notBefore
and @notAfter are required. There is no 0000 date; there are only -0001 and 0001.
<placeName> contains a detailed place name as content.
@ref has a USEp controlled vocabulary. In the future we plan to use Pleiades information.
-->
<history>
<summary>
<rs/>
</summary>
<origin>
<date notBefore="-0510" notAfter="-0490">c.500 BCE</date>
<placeName ref="http://pleiades.stoa.org/places/579885" type="pleiades">Plaka, Athens, Greece</placeName>
</origin>
<provenance>
<date notBefore="0001" notAfter="0002">xx</date>
<placeName ref="xx">xx</placeName>
</provenance>
</history>
<additional>
<surrogates>
<msDesc n="estampage-uninked">
<msIdentifier>
<repository>Class</repository>
<idno type="USEpigraphy" xml:id="Sq.IG_I3_1380">Sq.IG I3 1380</idno>
</msIdentifier>
<physDesc>
<p>Two sheets held together with a nail. Top of inscription damaged, though the squeeze preserves the entirety of the stone. Marked CIA I 477.</p>
</physDesc>
</msDesc>
</surrogates>
</additional>
</msDesc>
<!-- ************************************* <listBibl> *********************************
Encodes bibliographic entries.
<bibl> used to encode each reference. There can be multiple <bibl>s.
@target points to the id of the publication, which is found in the title.xml file.
<biblScope> contains the reference in the publication, either page or item numbers.
@type[item] contains the item number in a corpus or other publication
@type[pp] contains page numbers.
Either or both of these can be part of a reference.
External links, for example to digital corpora. Encode this as a <ref> inside a <bibl>.
Ex: <ref type="external" target="(the url)">EDH nr. HD0000000</ref>
-->
<listBibl>
<bibl>
<ptr type="rest-of-bibl" target="#IG_I3"/>
<biblScope type="item">1380</biblScope>
</bibl>
</listBibl>
</sourceDesc>
</fileDesc>
<!-- ************************************* <encodingDesc> *********************************
This section of the header contains the controlled vocabularies for the genre, form and material of
an inscription. The taxonomies are in external files, but as you work, Oxygen is reading them, and can
validate ids so that you can be assured that you are using correct values.
If you don't find the value you need, you should talk to the project manager or John Bodel, in order to see
what value to use, or (rarely) whether the taxonomies need to be modified.
Encoders do not edit the <encodingDesc>.
-->
<encodingDesc>
<!-- Taxonomies with lists of controlled values go here. Each controlled vocabulary is a single file stored at
the URL given below. This allows all encoded inscriptions to use the same set of controlled vocabularies.
The taxonomy files can be updated by US Epigraphy staff, but changes should be made only if approved.
-->
<xi:include
href="http://dev.stg.brown.edu/projects/usepigraphy/xml/include_taxonomies.xml">
<xi:fallback>
<p>Taxonomies for US Epigraphy controlled values</p>
</xi:fallback>
</xi:include>
</encodingDesc>
<!-- Ignore profileDesc for now -->
<profileDesc> </profileDesc>
<!-- ************************************* <revisionDesc> *********************************
<change> Any change to the file should be recorded here, with most recent revisions listed at the top of the list.
@when Dates should be in the format YYYYY-MM-DD.
@who Type in your name.
The content of <change> can be a short description of what changes were made, for example:
initial encoding; update original US Ep. values to P5 values; corrected xx; etc.
-->
<revisionDesc>
<change when="2012-06-06" who="SJD">Initial Encoding</change>
</revisionDesc>
</teiHeader>
<!-- ************************************* <facsimile> *********************************
Used to point to images of an inscription.
<graphic> (directly within <facsimile>) Use this if there is only a single "main" image without a special caption.
<surface> Use <desc> and <graphic> within <surface> if there are mutiple images or if they have captions. <surface>
pairs one or more images with a single caption. Usually, in US Ep. captions are only indicated when the image is of a detail.
@url contains the name of the image file (no path or directory information, for now).
<facsimile> can have more than one <graphic> or <surface>.
-->
<facsimile>
<graphic url=""/>
<surface>
<desc/>
<graphic url=""/>
</surface>
</facsimile>
<text>
<body>
<div type="edition">
<ab>
<lb n="1"/><gap reason="lost" extent="unknown" unit="line"/>
<lb n="2"/><supplied reason="lost">ἐνθά</supplied><unclear>δε</unclear> Φ<unclear>ι</unclear><gap reason="lost" quantity="12" unit="character"/> κατέθε
<lb n="3" type="inWord"/>κε θανσαν ⋮Λ<supplied reason="lost">αμπι</supplied><unclear>τ</unclear>ὸ αἰδοίεν γς ἀπ
<lb n="4" type="inWord"/>ὸ πατροΐες. ⋮ Ἐνδοιο<unclear>ς</unclear> ἐποίεσεν.
</ab>
</div>
<div type="bibliography">
<xi:include href="http://dev.stg.brown.edu/projects/usepigraphy/xml/titles.xml">
<xi:fallback>
<p>US Ep bibliography</p>
</xi:fallback>
</xi:include>
</div>
</body>
</text>
</TEI>