| ... | ... | @@ -6,15 +6,15 @@ Our encoding usually starts with the dramatis personae, as we do not use a `titl |
|
|
|
|
|
|
|
## Dedications
|
|
|
|
|
|
|
|
If any, using a `<div type="dedication">`. Dedication-like information is also encoded with the same attribute (e.g. a notice that the play was written to commemorate the 50th anniversary of something, even if there is no explicit dedication of the play). We don't respect case value in the source unless required by orthography, but we record line breaks as in the source, see an [[example]](https://git.unistra.fr/methal/methal-sources/-/blob/master/bastian-hofnarr-heidideldum.xml#L172).
|
|
|
|
If any, they are encoding using a `<div type="dedication">`. Dedication-like information is also encoded with the same attribute (e.g. a notice that the play was written to commemorate the 50th anniversary of something, even if there is no explicit dedication of the play). We don't respect case value in the source unless required by orthography, but we record line breaks as in the source, see an [[example]](https://git.unistra.fr/methal/methal-sources/-/blob/master/bastian-hofnarr-heidideldum.xml#L172).
|
|
|
|
|
|
|
|
## Dramatis personae
|
|
|
|
|
|
|
|
Using a `<castList>`.
|
|
|
|
Encoding within a `<castList>`.
|
|
|
|
|
|
|
|
## Additional character descriptions
|
|
|
|
|
|
|
|
If any, using `<div type="character-description">`.
|
|
|
|
If any, encoded using `<div type="character-description">`.
|
|
|
|
|
|
|
|
Some plays provide a more detailed character description after the character list, giving additional information about clothes and appearance. If formatted as a list in the source, we encode this in a `<list>` element. For numbered lists, use a `<list>` and specify `@rend="numbered"` rather than reproducing the numbering. See an [[example]](https://git.unistra.fr/methal/methal-sources/-/blob/master/clemens-chrischtowe.xml#L191).
|
|
|
|
|
| ... | ... | @@ -24,7 +24,7 @@ Using one or more `<set>` elements. |
|
|
|
|
|
|
|
Plays in this corpus most often have a small description regarding the time and place where the action takes place, sometimes itemized by act and/or scene.
|
|
|
|
|
|
|
|
These descriptions are generally simple, and our encoding is very simple so far. We keep the text but not its format (bold etc. is not kept) We do not tag place or time expressions, although this would be very useful future work. See some examples below.
|
|
|
|
These descriptions are generally simple, and our encoding is very simple so far. We keep the text but not its formatting. We do not tag place or time expressions, although this would be very useful future work. See some examples below.
|
|
|
|
|
|
|
|
|
|
|
|
|
| ... | ... | @@ -35,7 +35,7 @@ These descriptions are generally simple, and our encoding is very simple so far. |
|
|
|
</set>
|
|
|
|
```
|
|
|
|
|
|
|
|
Some authors use more complex conventions (e.g. Camille Jost, who breaks up the setting information in a more detailed way). For these cases, so far we have used `<p>` elements and indeed kept the bold format used for headings (_ORT_, _ZYTT_ and so on, see example below). (This was used instead of a `<head>` since we were using a single `<set>` element, and each `<set>` only allows one `<head>`. We will improve this in the future; the whole encoding of setting information may be made more semantic in the future).
|
|
|
|
Some authors use more complex conventions (e.g. Camille Jost, who breaks up the setting information in a more detailed way). For these cases, so far we have used `<p>` elements and indeed kept the bold format used for headings (_ORT_, _ZYTT_ and so on, see example below). Keeping the format was used instead of a `<head>` element, since we were using a single `<set>` element, and each `<set>` only allows one `<head>`. We will improve this in the future; the whole encoding of setting information may be made more semantic in the future.
|
|
|
|
|
|
|
|
|
|
|
|
|
| ... | ... | @@ -48,11 +48,11 @@ Some authors use more complex conventions (e.g. Camille Jost, who breaks up the |
|
|
|
</set>
|
|
|
|
```
|
|
|
|
|
|
|
|
The way we encode sets may be revised in the future, and be made more semantic (e.g. with several `<set>` elements with a relevant `@type` value like _time_, _place_ and so on) instead of `<p>` elements.
|
|
|
|
The way we encode sets may be revised in the future, and be made more semantic (e.g. with several `<set>` elements with a relevant `@type` value like _time_, _place_ and so on) instead of `<p>` elements, and with named-entity tagging.
|
|
|
|
|
|
|
|
## Play summary
|
|
|
|
|
|
|
|
If any, e.g. an _Inhaltsangabe_ paragraph: Using `<div type="front">`. See [[example]](https://git.unistra.fr/methal/methal-sources/-/blob/master/hart-dr-poetisch-oscar.xml#L110).
|
|
|
|
If any, e.g. an _Inhaltsangabe_ paragraph. Encoded using `<div type="front">`. See [[example]](https://git.unistra.fr/methal/methal-sources/-/blob/master/hart-dr-poetisch-oscar.xml#L110).
|
|
|
|
|
|
|
|
## General guidelines
|
|
|
|
|
| ... | ... | |
