Difference between revisions of "Mondrian: Decisions during eDITem project"

From XML
Jump to: navigation, search
 
(19 intermediate revisions by the same user not shown)
Line 6: Line 6:
  
 
We will not be using sic and corr, but orig and reg.  
 
We will not be using sic and corr, but orig and reg.  
We only keep the changed (added, deleted) string within the element and keep the unchanged part out of these elements. We maintain the @type for the orig.
+
We move the @type from the sic to the reg (not to the orig: not allowed).
  
  
Line 22: Line 22:
 
         settlement
 
         settlement
 
         desc
 
         desc
 +
----
 +
  
 
'''Layout:'''
 
'''Layout:'''
  
 
For now we regularise layout of postcards the way we do letters.
 
For now we regularise layout of postcards the way we do letters.
 
  
 
We display date/place always full left, on a single line, followed by one white line. We change the current encoding for address and date in dateline (to be added by a stylesheet):
 
We display date/place always full left, on a single line, followed by one white line. We change the current encoding for address and date in dateline (to be added by a stylesheet):
Line 34: Line 35:
 
   <salute> … </salute>
 
   <salute> … </salute>
 
</opener>
 
</opener>
 
  
 
We display salutation always full left, beneath the date/place after a white line and the first line of the letter immediately below the salutation, set full left.
 
We display salutation always full left, beneath the date/place after a white line and the first line of the letter immediately below the salutation, set full left.
 +
 +
----
  
 
'''Paragraphs''' are indented except for the first line of the letter text and after a white line.
 
'''Paragraphs''' are indented except for the first line of the letter text and after a white line.
 +
 +
encoded as <p> with @xml:id and @n added via a stylesheet (<p xml:id="p.nl.2" n="2"> and <p xml:id="p.en.2" n="2">)
 +
 +
<opener> and <closer> encoded as paragraphs: <opener xml:id="p.nl.1" n="1"> and <opener xml:id="p.en.1" n="1">
 +
 +
----
  
 
'''Postscripts''' are shown after the signature and after one white line.
 
'''Postscripts''' are shown after the signature and after one white line.
  
'''Superscript''' (and general rule for unusual abbreviations): keep encoding exactly what’s on the manuscripts and then the editors will decide how to regularize it.  
+
----
 +
 
 +
'''Superscript''' encoded as @rend='super'. @underline, when combined with superscript, removed in the site, but kept in the xml.
  
Es:
 
<choice><orig>N<hi rend="super underline2">o</hi></orig><reg>No.</reg></choice>
 
  
 
Unusual abbreviations: to be coded as <choice><abbr><expan>. The usual abbreviations will be described in a list.
 
Unusual abbreviations: to be coded as <choice><abbr><expan>. The usual abbreviations will be described in a list.
  
'''White lines:''' keep them in xml as they are encoded (vertical spaces) and display them as one white line when they occurs within the body of the letters. Only after <salute> use the @rend=“norend” encoding, since we don’t want to display the white line/lines here. (The @rend=“norend” will be added through a stylesheet)
+
----
 +
 
 +
'''White lines:''' keep them in xml as they are encoded (vertical spaces) and display them as one white line when they occur within the body of the letters. After <opener> use the @rend=“norend” encoding. (The @rend=“norend” will be added through a stylesheet)
 +
 
 +
----
  
 
'''Quotation marks:''' still under discussion.
 
'''Quotation marks:''' still under discussion.
 +
 +
----
  
 
'''Comma and full stop:''' to be encoded with <orig> and <reg>  
 
'''Comma and full stop:''' to be encoded with <orig> and <reg>  
 +
 +
----
  
 
'''Single underlining:''' encode as underlined and display in italics  
 
'''Single underlining:''' encode as underlined and display in italics  
 +
 +
----
  
 
'''Multiple underlining:''' encode as multiple underlined and display in italics. Annotation when the underlining have a specific meaning.
 
'''Multiple underlining:''' encode as multiple underlined and display in italics. Annotation when the underlining have a specific meaning.
 +
 +
----
  
 
'''Atypical writing, combinations, repeated quotes, quotations, lines and dots:''' not relevant or not present
 
'''Atypical writing, combinations, repeated quotes, quotations, lines and dots:''' not relevant or not present
  
'''Parentheses:''' all parentheses are rendered as ( )
+
----
And also transcribed as ()?
+
  
If not, eg:  
+
'''Parentheses:''' all parentheses are typed as written
<choice><orig>[</orig><reg>(</reg></choice>
+
 
 +
----
  
 
'''Uncertainties:''' encode with <choice><unclear><unclear>.  
 
'''Uncertainties:''' encode with <choice><unclear><unclear>.  
Display content of first unclear element. Always add note?
+
Display content of first unclear element. (Perhaps visualise with mouse-over).
  
'''Additions in margins:''' encode with <metamark> with @function and @place and show (and encode) them where they are supposed to be insert by Mondrian.
+
----
It is also necessary to keep into account the direction of writing?
+
Not sure whether we really need @function on metamark. @place on <add>
+
  
'''Appendices:''' encode as a separated division (<div type="appendix">) and a new <pb>:
+
'''Additions in margins:''' encode with <add> and @place with values: “left margin” “right margin” “bottom margin” “top margin”
<div type="appendix">
+
<pb/>
+
  
When the facsimile is available: the distinction between what is written in Mondrian’s hand and what is preprint or written in another hand is omitted.
+
----
When the facsimile is not available: we will send some proposals to make the distinction clear.
+
 
 +
'''Metamark''' coded as <metamark/>
 +
 
 +
----
 +
 
 +
'''Appendices:''' encode as a separated division with @type="appendix", and a new <pb/>
 +
 
 +
We make explicit what is preprinted or pre-written by using the @rend with "preprinted" or "prewritten" values.  
 +
We do that only when Mondrian fill in preprinted/prewritten address or forms and not for fixed parts of the letters (as letterheads).
 +
 
 +
----
  
 
'''Table:''' encode as such when they occur (with <table>, <row> and <cell>).
 
'''Table:''' encode as such when they occur (with <table>, <row> and <cell>).
 +
 +
----
  
 
'''Introductions:''' not provided at this stage: most of the letters don’t require introduction and when pieces of information are needed, they are provided within annotation. This point could be discuss again in the future.
 
'''Introductions:''' not provided at this stage: most of the letters don’t require introduction and when pieces of information are needed, they are provided within annotation. This point could be discuss again in the future.
+
 
 +
 
 +
----
 +
 
 
We will make the '''XML freely available''' for users If Steering Committee agrees.
 
We will make the '''XML freely available''' for users If Steering Committee agrees.
 +
 +
----
 +
 +
'''lb and hyphens''': removed
 +
 +
----
 +
 +
'''Nationality''': we decided to add (one or more) <nationality> for each person in the bio.xml file, before the date of birth:
 +
 +
 
 +
                    <persName><forename>xxx</forename> <surname>xxx</surname></persName>
 +
                    <nationality from="xxxx" to="yyyy"></nationality>
 +
                    <nationality from="xxxx" to="yyyy"></nationality>
 +
                    <birth when="xxxx">
 +
 +
----
 +
 +
'''References'''
 +
 +
[https://docs.google.com/document/d/1YySFR7RR79O8PHkw7JMFuKhZqUhFFq8zqlag1fB-W-4/edit?usp=sharing]
 +
 +
'''Note: rs type=person'''' used (with type and ref attribute) also for names that occur in the opener, also with abbreviation: ex. when we have D.A. we encode D.<rs type="person" ref="#bio.xml#xxxx">A.</rs>
 +
 +
----
 +
'''Multiple authors'''
 +
 +
In case of letters with multiple authors (co-signed by Mondrian), use multiple <rs> element (with @ref and @type=person) in <correspAction type=’sent’>
 +
 +
----
 +
 +
'''References to images'''
 +
 +
[https://docs.google.com/document/d/1OFuGibtZ9DS4PXXz3JXf-XjAneUu9y5zR3J6ZGOaGWk/edit?usp=sharing]
 +
 +
 +
----
 +
 +
'''Writings''' (work in progress)
 +
 +
[https://docs.google.com/document/d/14fYrdCs-csrZFmiLYM1QGX9BNXeVmU9UdNvJalIi5ek/edit?usp=sharing]

Latest revision as of 10:32, 29 August 2023


These are decisions taken during the eDITem project that have to be worked into the rest of the documentation. For the moment, we document them here.


We will not be using sic and corr, but orig and reg. We move the @type from the sic to the reg (not to the orig: not allowed).


Organizations:

We create a separated .xml file for organizations. In the text we use the following encoding: <rs type="org" ref="org.xml#xxx">

Sample of the Organizations file:

  -listOrg
       org
         @ana (value: museum, gallery, artistassoc, firm, org) and @xml:id 
        orgName
        place
        country 
        settlement
        desc


Layout:

For now we regularise layout of postcards the way we do letters.

We display date/place always full left, on a single line, followed by one white line. We change the current encoding for address and date in dateline (to be added by a stylesheet):

<opener>

  <dateline> … </dateline>
  <salute> … </salute>

</opener>

We display salutation always full left, beneath the date/place after a white line and the first line of the letter immediately below the salutation, set full left.


Paragraphs are indented except for the first line of the letter text and after a white line.

encoded as

with @xml:id and @n added via a stylesheet (<p xml:id="p.nl.2" n="2"> and <p xml:id="p.en.2" n="2">) <opener> and <closer> encoded as paragraphs: <opener xml:id="p.nl.1" n="1"> and <opener xml:id="p.en.1" n="1">


Postscripts are shown after the signature and after one white line.


Superscript encoded as @rend='super'. @underline, when combined with superscript, removed in the site, but kept in the xml.


Unusual abbreviations: to be coded as <choice><expan>. The usual abbreviations will be described in a list.


White lines: keep them in xml as they are encoded (vertical spaces) and display them as one white line when they occur within the body of the letters. After <opener> use the @rend=“norend” encoding. (The @rend=“norend” will be added through a stylesheet)


Quotation marks: still under discussion.


Comma and full stop: to be encoded with <orig> and <reg>


Single underlining: encode as underlined and display in italics


Multiple underlining: encode as multiple underlined and display in italics. Annotation when the underlining have a specific meaning.


Atypical writing, combinations, repeated quotes, quotations, lines and dots: not relevant or not present


Parentheses: all parentheses are typed as written


Uncertainties: encode with <choice><unclear><unclear>. Display content of first unclear element. (Perhaps visualise with mouse-over).


Additions in margins: encode with <add> and @place with values: “left margin” “right margin” “bottom margin” “top margin”


Metamark coded as <metamark/>


Appendices: encode as a separated division with @type="appendix", and a new <pb/>

We make explicit what is preprinted or pre-written by using the @rend with "preprinted" or "prewritten" values. We do that only when Mondrian fill in preprinted/prewritten address or forms and not for fixed parts of the letters (as letterheads).


Table: encode as such when they occur (with , <row> and <cell>).

Introductions: not provided at this stage: most of the letters don’t require introduction and when pieces of information are needed, they are provided within annotation. This point could be discuss again in the future.



We will make the XML freely available for users If Steering Committee agrees.


lb and hyphens: removed


Nationality: we decided to add (one or more) <nationality> for each person in the bio.xml file, before the date of birth:


                   <persName><forename>xxx</forename> <surname>xxx</surname></persName>
                   <nationality from="xxxx" to="yyyy"></nationality>
                   <nationality from="xxxx" to="yyyy"></nationality>
                   <birth when="xxxx">

References

[1]

Note: rs type=person' used (with type and ref attribute) also for names that occur in the opener, also with abbreviation: ex. when we have D.A. we encode D.<rs type="person" ref="#bio.xml#xxxx">A.</rs>


Multiple authors

In case of letters with multiple authors (co-signed by Mondrian), use multiple <rs> element (with @ref and @type=person) in <correspAction type=’sent’>


References to images

[2]



Writings (work in progress)

[3]