<filiation>
<filiation> contains information concerning the manuscript's filiation, i.e. its relationship to other surviving manuscripts of the same text, its protographs, antigraphs and apographs. [10.6.1 The msItem and msItemStruct Elements] | |
Module | msdescription — Manuscript Description |
Attributes | att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) |
Member of | |
Contained by | msdescription: msItem msItemStruct |
May contain | core: abbr add address bibl biblStruct binaryObject cb choice cit corr date del desc distinct email emph expan foreign gap gb gloss graphic hi index l label lb lg list listBibl measure measureGrp media mentioned milestone name note num orig p pb ptr q quote ref reg rs said sic soCalled sp stage term time title unclear figures: figure formula notatedMusic table gaiji: g msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName affiliation bloc climate country district forename genName geo geogFeat geogName listEvent listNym listOrg listPerson listPlace location nameLink offset orgName persName placeName population region roleName settlement state surname terrain trait nets: eTree forest graph listForest tree tagdocs: att classSpec code constraintSpec dataSpec eg egXML elementSpec gi ident listRef macroSpec moduleSpec outputRendition schemaSpec specDesc specGrp specGrpRef specList tag val textstructure: floatingText transcr: addSpan am damage damageSpan delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space subst substJoin supplied surplus undo character data |
Example | <msContents> <msItem> <title>Beljakovski sbornik</title> <filiation type="protograph">Bulgarian</filiation> <filiation type="antigraph">Middle Bulgarian</filiation> <filiation type="apograph"> <ref target="#DN17">Dujchev N 17</ref> </filiation> </msItem> </msContents> <!-- ... --> <msDesc xml:id="DN17"> <msIdentifier> <settlement>Faraway</settlement> </msIdentifier> <!-- ... --> </msDesc> In this example, the reference to ‘Dujchev N17’ includes a link to some other manuscript description which has the identifier |
Example | <msItem> <title>Guan-ben</title> <filiation> <p>The "Guan-ben" was widely current among mathematicians in the Qing dynasty, and "Zhao Qimei version" was also read. It is therefore difficult to know the correct filiation path to follow. The study of this era is much indebted to Li Di. We explain the outline of his conclusion here. Kong Guangsen (1752-1786)(17) was from the same town as Dai Zhen, so he obtained "Guan-ben" from him and studied it(18). Li Huang (d. 1811) (19) took part in editing Si Ku Quan Shu, so he must have had "Guan-ben". Then Zhang Dunren (1754-1834) obtained this version, and studied "Da Yan Zong Shu Shu" (The General Dayan Computation). He wrote Jiu Yi Suan Shu (Mathematics Searching for One, 1803) based on this version of Shu Xue Jiu Zhang (20).</p> <p>One of the most important persons in restoring our knowledge concerning the filiation of these books was Li Rui (1768(21) -1817)(see his biography). ... only two volumes remain of this manuscript, as far as chapter 6 (chapter 3 part 2) p.13, that is, question 2 of "Huan Tian San Ji" (square of three loops), which later has been lost.</p> </filiation> </msItem> <!--http://www2.nkfust.edu.tw/~jochi/ed1.htm--> |
Content model | <content> |
Schema Declaration | <rng:element name="filiation"> element filiation { att.global.attributes, att.global.rendition.attributes, att.global.linking.attributes, att.global.analytic.attributes, att.global.facs.attributes, att.global.change.attributes, att.global.responsibility.attributes, att.global.source.attributes, att.typed.attributes, macro.specialPara } |