From b8d8ec96c603e5b83bb80aa95d2a5324fd7b2372 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 15 Dec 2023 09:15:27 -0500 Subject: [PATCH] Using XML utility, change header comments in every Source XML file. --- P5/Source/Guidelines/en/AB-About.xml | 466 +- .../Guidelines/en/AI-AnalyticMechanisms.xml | 772 +--- P5/Source/Guidelines/en/BIB-Bibliography.xml | 1022 ++--- .../Guidelines/en/CC-LanguageCorpora.xml | 795 +--- .../en/CE-CertaintyResponsibility.xml | 362 +- .../en/CH-LanguagesCharacterSets.xml | 285 +- P5/Source/Guidelines/en/CO-CoreElements.xml | 3944 +++++------------ P5/Source/Guidelines/en/COL-Colophon.xml | 16 +- P5/Source/Guidelines/en/DEPRECATIONS.xml | 11 +- .../Guidelines/en/DI-PrintDictionaries.xml | 2427 +++------- .../Guidelines/en/DR-PerformanceTexts.xml | 1170 ++--- .../Guidelines/en/DS-DefaultTextStructure.xml | 1397 ++---- P5/Source/Guidelines/en/Dedication.xml | 8 +- .../Guidelines/en/FM1-IntroductoryNote.xml | 230 +- .../Guidelines/en/FS-FeatureStructures.xml | 1454 ++---- .../en/FT-TablesFormulaeGraphics.xml | 397 +- .../Guidelines/en/GD-GraphsNetworksTrees.xml | 1791 +++----- P5/Source/Guidelines/en/HD-Header.xml | 2309 +++------- .../en/MS-ManuscriptDescription.xml | 2358 ++++------ P5/Source/Guidelines/en/ND-NamesDates.xml | 2136 ++------- .../Guidelines/en/NH-Non-hierarchical.xml | 585 +-- P5/Source/Guidelines/en/PARTIND.xml | 16 +- P5/Source/Guidelines/en/PH-PrimarySources.xml | 2171 +++------ P5/Source/Guidelines/en/PrefatoryNote.xml | 482 +- P5/Source/Guidelines/en/REF-ATTRIBUTES.xml | 25 +- P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml | 26 +- P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml | 25 +- P5/Source/Guidelines/en/REF-ELEMENTS.xml | 26 +- P5/Source/Guidelines/en/REF-MACROS.xml | 25 +- .../en/SA-LinkingSegmentationAlignment.xml | 2142 +++------ .../Guidelines/en/SG-GentleIntroduction.xml | 618 +-- P5/Source/Guidelines/en/ST-Infrastructure.xml | 529 +-- .../Guidelines/en/TC-CriticalApparatus.xml | 682 +-- .../en/TD-DocumentationElements.xml | 1066 +---- .../en/TS-TranscriptionsofSpeech.xml | 978 ++-- P5/Source/Guidelines/en/TitlePageVerso.xml | 39 +- P5/Source/Guidelines/en/USE.xml | 1186 +---- P5/Source/Guidelines/en/VE-Verse.xml | 711 +-- .../en/WD-NonStandardCharacters.xml | 914 ++-- P5/Source/Specs/TEI.xml | 23 +- P5/Source/Specs/ab.xml | 14 +- P5/Source/Specs/abbr.xml | 32 +- P5/Source/Specs/abstract.xml | 18 +- P5/Source/Specs/accMat.xml | 10 +- P5/Source/Specs/acquisition.xml | 49 +- P5/Source/Specs/activity.xml | 17 +- P5/Source/Specs/actor.xml | 26 +- P5/Source/Specs/add.xml | 14 +- P5/Source/Specs/addName.xml | 10 +- P5/Source/Specs/addSpan.xml | 18 +- P5/Source/Specs/additional.xml | 14 +- P5/Source/Specs/additions.xml | 8 +- P5/Source/Specs/addrLine.xml | 14 +- P5/Source/Specs/address.xml | 36 +- P5/Source/Specs/adminInfo.xml | 28 +- P5/Source/Specs/affiliation.xml | 65 +- P5/Source/Specs/age.xml | 97 +- P5/Source/Specs/alt.xml | 18 +- P5/Source/Specs/altGrp.xml | 18 +- P5/Source/Specs/altIdent.xml | 11 +- P5/Source/Specs/altIdentifier.xml | 52 +- P5/Source/Specs/alternate.xml | 23 +- P5/Source/Specs/am.xml | 33 +- P5/Source/Specs/analytic.xml | 38 +- P5/Source/Specs/anchor.xml | 8 +- P5/Source/Specs/annotation.xml | 11 +- P5/Source/Specs/annotationBlock.xml | 8 +- P5/Source/Specs/anyElement.xml | 38 +- P5/Source/Specs/app.xml | 42 +- P5/Source/Specs/appInfo.xml | 14 +- P5/Source/Specs/application.xml | 75 +- P5/Source/Specs/arc.xml | 22 +- P5/Source/Specs/argument.xml | 28 +- P5/Source/Specs/att.anchoring.xml | 30 +- P5/Source/Specs/att.ascribed.directed.xml | 95 +- P5/Source/Specs/att.ascribed.xml | 30 +- P5/Source/Specs/att.breaking.xml | 14 +- P5/Source/Specs/att.cReferencing.xml | 29 +- P5/Source/Specs/att.calendarSystem.xml | 26 +- P5/Source/Specs/att.canonical.xml | 51 +- P5/Source/Specs/att.citeStructurePart.xml | 8 +- P5/Source/Specs/att.citing.xml | 150 +- P5/Source/Specs/att.combinable.xml | 78 +- P5/Source/Specs/att.coordinated.xml | 34 +- P5/Source/Specs/att.damaged.xml | 20 +- P5/Source/Specs/att.datable.custom.xml | 50 +- P5/Source/Specs/att.datable.iso.xml | 32 +- P5/Source/Specs/att.datable.w3c.xml | 67 +- P5/Source/Specs/att.datable.xml | 8 +- P5/Source/Specs/att.datcat.xml | 157 +- P5/Source/Specs/att.declarable.xml | 12 +- P5/Source/Specs/att.declaring.xml | 14 +- P5/Source/Specs/att.deprecated.xml | 19 +- P5/Source/Specs/att.dimensions.xml | 30 +- P5/Source/Specs/att.divLike.xml | 16 +- P5/Source/Specs/att.docStatus.xml | 14 +- P5/Source/Specs/att.duration.iso.xml | 14 +- P5/Source/Specs/att.duration.w3c.xml | 12 +- P5/Source/Specs/att.duration.xml | 10 +- P5/Source/Specs/att.editLike.xml | 30 +- P5/Source/Specs/att.edition.xml | 18 +- P5/Source/Specs/att.enjamb.xml | 16 +- P5/Source/Specs/att.entryLike.xml | 14 +- P5/Source/Specs/att.formula.xml | 40 +- P5/Source/Specs/att.fragmentable.xml | 18 +- P5/Source/Specs/att.gaijiProp.xml | 139 +- P5/Source/Specs/att.global.analytic.xml | 16 +- P5/Source/Specs/att.global.change.xml | 14 +- P5/Source/Specs/att.global.facs.xml | 10 +- P5/Source/Specs/att.global.linking.xml | 93 +- P5/Source/Specs/att.global.rendition.xml | 39 +- P5/Source/Specs/att.global.responsibility.xml | 26 +- P5/Source/Specs/att.global.source.xml | 28 +- P5/Source/Specs/att.global.xml | 61 +- P5/Source/Specs/att.handFeatures.xml | 32 +- P5/Source/Specs/att.identified.xml | 22 +- P5/Source/Specs/att.internetMedia.xml | 14 +- P5/Source/Specs/att.interpLike.xml | 22 +- .../Specs/att.lexicographic.normalized.xml | 73 +- P5/Source/Specs/att.lexicographic.xml | 37 +- P5/Source/Specs/att.linguistic.xml | 34 +- P5/Source/Specs/att.locatable.xml | 15 +- P5/Source/Specs/att.measurement.xml | 45 +- P5/Source/Specs/att.media.xml | 24 +- P5/Source/Specs/att.metrical.xml | 31 +- P5/Source/Specs/att.milestoneUnit.xml | 13 +- P5/Source/Specs/att.msClass.xml | 46 +- P5/Source/Specs/att.msExcerpt.xml | 14 +- P5/Source/Specs/att.namespaceable.xml | 12 +- P5/Source/Specs/att.naming.xml | 18 +- P5/Source/Specs/att.notated.xml | 12 +- P5/Source/Specs/att.partials.xml | 99 +- P5/Source/Specs/att.patternReplacement.xml | 16 +- P5/Source/Specs/att.personal.xml | 16 +- P5/Source/Specs/att.placement.xml | 30 +- P5/Source/Specs/att.pointing.group.xml | 18 +- P5/Source/Specs/att.pointing.xml | 54 +- P5/Source/Specs/att.predicate.xml | 76 +- P5/Source/Specs/att.ranging.xml | 31 +- P5/Source/Specs/att.rdgPart.xml | 14 +- P5/Source/Specs/att.repeatable.xml | 14 +- P5/Source/Specs/att.resourced.xml | 14 +- P5/Source/Specs/att.scoping.xml | 24 +- P5/Source/Specs/att.segLike.xml | 28 +- P5/Source/Specs/att.sortable.xml | 15 +- P5/Source/Specs/att.spanning.xml | 14 +- P5/Source/Specs/att.styleDef.xml | 16 +- P5/Source/Specs/att.tableDecoration.xml | 22 +- P5/Source/Specs/att.textCritical.xml | 26 +- P5/Source/Specs/att.timed.xml | 18 +- P5/Source/Specs/att.transcriptional.xml | 27 +- P5/Source/Specs/att.translatable.xml | 14 +- P5/Source/Specs/att.typed.xml | 18 +- P5/Source/Specs/att.witnessed.xml | 14 +- P5/Source/Specs/att.written.xml | 44 +- P5/Source/Specs/att.xml | 21 +- P5/Source/Specs/attDef.xml | 42 +- P5/Source/Specs/attList.xml | 34 +- P5/Source/Specs/attRef.xml | 20 +- P5/Source/Specs/author.xml | 53 +- P5/Source/Specs/authority.xml | 10 +- P5/Source/Specs/availability.xml | 14 +- P5/Source/Specs/back.xml | 8 +- P5/Source/Specs/bibl.xml | 34 +- P5/Source/Specs/biblFull.xml | 8 +- P5/Source/Specs/biblScope.xml | 12 +- P5/Source/Specs/biblStruct.xml | 10 +- P5/Source/Specs/bicond.xml | 8 +- P5/Source/Specs/binary.xml | 26 +- P5/Source/Specs/binaryObject.xml | 14 +- P5/Source/Specs/binding.xml | 71 +- P5/Source/Specs/bindingDesc.xml | 26 +- P5/Source/Specs/birth.xml | 87 +- P5/Source/Specs/bloc.xml | 49 +- P5/Source/Specs/body.xml | 22 +- P5/Source/Specs/broadcast.xml | 14 +- P5/Source/Specs/byline.xml | 26 +- P5/Source/Specs/c.xml | 10 +- P5/Source/Specs/cRefPattern.xml | 14 +- P5/Source/Specs/caesura.xml | 14 +- P5/Source/Specs/calendar.xml | 14 +- P5/Source/Specs/calendarDesc.xml | 21 +- P5/Source/Specs/camera.xml | 14 +- P5/Source/Specs/caption.xml | 13 +- P5/Source/Specs/case.xml | 8 +- P5/Source/Specs/castGroup.xml | 29 +- P5/Source/Specs/castItem.xml | 28 +- P5/Source/Specs/castList.xml | 10 +- P5/Source/Specs/catDesc.xml | 22 +- P5/Source/Specs/catRef.xml | 22 +- P5/Source/Specs/catchwords.xml | 12 +- P5/Source/Specs/category.xml | 8 +- P5/Source/Specs/cb.xml | 14 +- P5/Source/Specs/cell.xml | 10 +- P5/Source/Specs/certainty.xml | 37 +- P5/Source/Specs/change.xml | 59 +- P5/Source/Specs/channel.xml | 14 +- P5/Source/Specs/char.xml | 28 +- P5/Source/Specs/charDecl.xml | 20 +- P5/Source/Specs/choice.xml | 30 +- P5/Source/Specs/cit.xml | 36 +- P5/Source/Specs/citeData.xml | 14 +- P5/Source/Specs/citeStructure.xml | 8 +- P5/Source/Specs/citedRange.xml | 13 +- P5/Source/Specs/cl.xml | 20 +- P5/Source/Specs/classCode.xml | 18 +- P5/Source/Specs/classDecl.xml | 18 +- P5/Source/Specs/classRef.xml | 34 +- P5/Source/Specs/classSpec.xml | 36 +- P5/Source/Specs/classes.xml | 18 +- P5/Source/Specs/climate.xml | 83 +- P5/Source/Specs/closer.xml | 30 +- P5/Source/Specs/code.xml | 14 +- P5/Source/Specs/collation.xml | 26 +- P5/Source/Specs/collection.xml | 8 +- P5/Source/Specs/colloc.xml | 10 +- P5/Source/Specs/colophon.xml | 10 +- P5/Source/Specs/cond.xml | 10 +- P5/Source/Specs/condition.xml | 10 +- P5/Source/Specs/constitution.xml | 14 +- P5/Source/Specs/constraint.xml | 10 +- P5/Source/Specs/constraintSpec.xml | 18 +- P5/Source/Specs/content.xml | 72 +- P5/Source/Specs/conversion.xml | 59 +- P5/Source/Specs/corr.xml | 12 +- P5/Source/Specs/correction.xml | 22 +- P5/Source/Specs/correspAction.xml | 28 +- P5/Source/Specs/correspContext.xml | 74 +- P5/Source/Specs/correspDesc.xml | 18 +- P5/Source/Specs/country.xml | 49 +- P5/Source/Specs/creation.xml | 67 +- P5/Source/Specs/custEvent.xml | 49 +- P5/Source/Specs/custodialHist.xml | 18 +- P5/Source/Specs/damage.xml | 24 +- P5/Source/Specs/damageSpan.xml | 14 +- P5/Source/Specs/dataFacet.xml | 66 +- P5/Source/Specs/dataRef.xml | 48 +- P5/Source/Specs/dataSpec.xml | 14 +- P5/Source/Specs/datatype.xml | 10 +- P5/Source/Specs/date.xml | 10 +- P5/Source/Specs/dateline.xml | 26 +- P5/Source/Specs/death.xml | 77 +- P5/Source/Specs/decoDesc.xml | 22 +- P5/Source/Specs/decoNote.xml | 10 +- P5/Source/Specs/def.xml | 10 +- P5/Source/Specs/default.xml | 14 +- P5/Source/Specs/defaultVal.xml | 10 +- P5/Source/Specs/del.xml | 10 +- P5/Source/Specs/delSpan.xml | 14 +- P5/Source/Specs/depth.xml | 10 +- P5/Source/Specs/derivation.xml | 17 +- P5/Source/Specs/desc.xml | 34 +- P5/Source/Specs/dictScrap.xml | 30 +- P5/Source/Specs/dim.xml | 10 +- P5/Source/Specs/dimensions.xml | 12 +- P5/Source/Specs/distinct.xml | 26 +- P5/Source/Specs/distributor.xml | 12 +- P5/Source/Specs/district.xml | 49 +- P5/Source/Specs/div.xml | 10 +- P5/Source/Specs/div1.xml | 10 +- P5/Source/Specs/div2.xml | 10 +- P5/Source/Specs/div3.xml | 10 +- P5/Source/Specs/div4.xml | 8 +- P5/Source/Specs/div5.xml | 8 +- P5/Source/Specs/div6.xml | 8 +- P5/Source/Specs/div7.xml | 178 +- P5/Source/Specs/divGen.xml | 14 +- P5/Source/Specs/docAuthor.xml | 10 +- P5/Source/Specs/docDate.xml | 8 +- P5/Source/Specs/docEdition.xml | 10 +- P5/Source/Specs/docImprint.xml | 30 +- P5/Source/Specs/docTitle.xml | 18 +- P5/Source/Specs/domain.xml | 14 +- P5/Source/Specs/eLeaf.xml | 25 +- P5/Source/Specs/eTree.xml | 14 +- P5/Source/Specs/edition.xml | 12 +- P5/Source/Specs/editionStmt.xml | 20 +- P5/Source/Specs/editor.xml | 50 +- P5/Source/Specs/editorialDecl.xml | 24 +- P5/Source/Specs/education.xml | 71 +- P5/Source/Specs/eg.xml | 10 +- P5/Source/Specs/egXML.xml | 79 +- P5/Source/Specs/elementRef.xml | 18 +- P5/Source/Specs/elementSpec.xml | 12 +- P5/Source/Specs/ellipsis.xml | 12 +- P5/Source/Specs/email.xml | 10 +- P5/Source/Specs/emph.xml | 10 +- P5/Source/Specs/empty.xml | 14 +- P5/Source/Specs/encodingDesc.xml | 24 +- P5/Source/Specs/entry.xml | 10 +- P5/Source/Specs/entryFree.xml | 30 +- P5/Source/Specs/epigraph.xml | 20 +- P5/Source/Specs/epilogue.xml | 36 +- P5/Source/Specs/equipment.xml | 14 +- P5/Source/Specs/equiv.xml | 24 +- P5/Source/Specs/etym.xml | 42 +- P5/Source/Specs/event.xml | 63 +- P5/Source/Specs/eventName.xml | 21 +- P5/Source/Specs/ex.xml | 10 +- P5/Source/Specs/exemplum.xml | 18 +- P5/Source/Specs/expan.xml | 31 +- P5/Source/Specs/explicit.xml | 10 +- P5/Source/Specs/extent.xml | 8 +- P5/Source/Specs/f.xml | 20 +- P5/Source/Specs/fDecl.xml | 26 +- P5/Source/Specs/fDescr.xml | 10 +- P5/Source/Specs/fLib.xml | 14 +- P5/Source/Specs/facsimile.xml | 10 +- P5/Source/Specs/factuality.xml | 14 +- P5/Source/Specs/faith.xml | 67 +- P5/Source/Specs/figDesc.xml | 10 +- P5/Source/Specs/figure.xml | 28 +- P5/Source/Specs/fileDesc.xml | 34 +- P5/Source/Specs/filiation.xml | 10 +- P5/Source/Specs/finalRubric.xml | 8 +- P5/Source/Specs/floatingText.xml | 26 +- P5/Source/Specs/floruit.xml | 49 +- P5/Source/Specs/foliation.xml | 10 +- P5/Source/Specs/foreign.xml | 10 +- P5/Source/Specs/forename.xml | 10 +- P5/Source/Specs/forest.xml | 10 +- P5/Source/Specs/form.xml | 32 +- P5/Source/Specs/formula.xml | 22 +- P5/Source/Specs/front.xml | 12 +- P5/Source/Specs/fs.xml | 22 +- P5/Source/Specs/fsConstraints.xml | 20 +- P5/Source/Specs/fsDecl.xml | 30 +- P5/Source/Specs/fsDescr.xml | 10 +- P5/Source/Specs/fsdDecl.xml | 10 +- P5/Source/Specs/fsdLink.xml | 22 +- P5/Source/Specs/funder.xml | 53 +- P5/Source/Specs/fvLib.xml | 16 +- P5/Source/Specs/fw.xml | 14 +- P5/Source/Specs/g.xml | 14 +- P5/Source/Specs/gap.xml | 114 +- P5/Source/Specs/gb.xml | 14 +- P5/Source/Specs/gen.xml | 10 +- P5/Source/Specs/genName.xml | 10 +- P5/Source/Specs/gender.xml | 59 +- P5/Source/Specs/geo.xml | 10 +- P5/Source/Specs/geoDecl.xml | 12 +- P5/Source/Specs/geogFeat.xml | 51 +- P5/Source/Specs/geogName.xml | 49 +- P5/Source/Specs/gi.xml | 14 +- P5/Source/Specs/gloss.xml | 8 +- P5/Source/Specs/glyph.xml | 10 +- P5/Source/Specs/gram.xml | 33 +- P5/Source/Specs/gramGrp.xml | 28 +- P5/Source/Specs/graph.xml | 24 +- P5/Source/Specs/graphic.xml | 16 +- P5/Source/Specs/group.xml | 36 +- P5/Source/Specs/handDesc.xml | 26 +- P5/Source/Specs/handNote.xml | 10 +- P5/Source/Specs/handNotes.xml | 14 +- P5/Source/Specs/handShift.xml | 18 +- P5/Source/Specs/head.xml | 34 +- P5/Source/Specs/headItem.xml | 10 +- P5/Source/Specs/headLabel.xml | 10 +- P5/Source/Specs/height.xml | 10 +- P5/Source/Specs/heraldry.xml | 10 +- P5/Source/Specs/hi.xml | 13 +- P5/Source/Specs/history.xml | 30 +- P5/Source/Specs/hom.xml | 24 +- P5/Source/Specs/hyph.xml | 10 +- P5/Source/Specs/hyphenation.xml | 18 +- P5/Source/Specs/iNode.xml | 38 +- P5/Source/Specs/iType.xml | 14 +- P5/Source/Specs/ident.xml | 10 +- P5/Source/Specs/idno.xml | 60 +- P5/Source/Specs/if.xml | 14 +- P5/Source/Specs/iff.xml | 14 +- P5/Source/Specs/imprimatur.xml | 10 +- P5/Source/Specs/imprint.xml | 40 +- P5/Source/Specs/incident.xml | 14 +- P5/Source/Specs/incipit.xml | 10 +- P5/Source/Specs/index.xml | 26 +- P5/Source/Specs/institution.xml | 8 +- P5/Source/Specs/interaction.xml | 22 +- P5/Source/Specs/interp.xml | 10 +- P5/Source/Specs/interpGrp.xml | 10 +- P5/Source/Specs/interpretation.xml | 14 +- P5/Source/Specs/item.xml | 11 +- P5/Source/Specs/join.xml | 22 +- P5/Source/Specs/joinGrp.xml | 8 +- P5/Source/Specs/keywords.xml | 24 +- P5/Source/Specs/kinesic.xml | 18 +- P5/Source/Specs/l.xml | 10 +- P5/Source/Specs/label.xml | 10 +- P5/Source/Specs/lacunaEnd.xml | 14 +- P5/Source/Specs/lacunaStart.xml | 14 +- P5/Source/Specs/lang.xml | 8 +- P5/Source/Specs/langKnowledge.xml | 83 +- P5/Source/Specs/langKnown.xml | 65 +- P5/Source/Specs/langUsage.xml | 22 +- P5/Source/Specs/language.xml | 30 +- P5/Source/Specs/layout.xml | 66 +- P5/Source/Specs/layoutDesc.xml | 24 +- P5/Source/Specs/lb.xml | 16 +- P5/Source/Specs/lbl.xml | 16 +- P5/Source/Specs/leaf.xml | 26 +- P5/Source/Specs/lem.xml | 15 +- P5/Source/Specs/lg.xml | 14 +- P5/Source/Specs/licence.xml | 53 +- P5/Source/Specs/line.xml | 24 +- P5/Source/Specs/link.xml | 8 +- P5/Source/Specs/linkGrp.xml | 4 +- P5/Source/Specs/list.xml | 87 +- P5/Source/Specs/listAnnotation.xml | 14 +- P5/Source/Specs/listApp.xml | 25 +- P5/Source/Specs/listBibl.xml | 10 +- P5/Source/Specs/listChange.xml | 18 +- P5/Source/Specs/listEvent.xml | 24 +- P5/Source/Specs/listForest.xml | 14 +- P5/Source/Specs/listNym.xml | 50 +- P5/Source/Specs/listObject.xml | 11 +- P5/Source/Specs/listOrg.xml | 10 +- P5/Source/Specs/listPerson.xml | 12 +- P5/Source/Specs/listPlace.xml | 10 +- P5/Source/Specs/listPrefixDef.xml | 20 +- P5/Source/Specs/listRef.xml | 21 +- P5/Source/Specs/listRelation.xml | 26 +- P5/Source/Specs/listTranspose.xml | 10 +- P5/Source/Specs/listWit.xml | 26 +- P5/Source/Specs/localProp.xml | 68 +- P5/Source/Specs/locale.xml | 10 +- P5/Source/Specs/location.xml | 71 +- P5/Source/Specs/locus.xml | 32 +- P5/Source/Specs/locusGrp.xml | 12 +- P5/Source/Specs/m.xml | 34 +- P5/Source/Specs/macro.abContent.xml | 10 +- P5/Source/Specs/macro.limitedContent.xml | 22 +- P5/Source/Specs/macro.paraContent.xml | 12 +- P5/Source/Specs/macro.phraseSeq.limited.xml | 22 +- P5/Source/Specs/macro.phraseSeq.xml | 26 +- P5/Source/Specs/macro.specialPara.xml | 28 +- P5/Source/Specs/macro.xtext.xml | 20 +- P5/Source/Specs/macroRef.xml | 18 +- P5/Source/Specs/macroSpec.xml | 16 +- P5/Source/Specs/mapping.xml | 8 +- P5/Source/Specs/material.xml | 12 +- P5/Source/Specs/measure.xml | 8 +- P5/Source/Specs/measureGrp.xml | 22 +- P5/Source/Specs/media.xml | 14 +- P5/Source/Specs/meeting.xml | 49 +- P5/Source/Specs/memberOf.xml | 26 +- P5/Source/Specs/mentioned.xml | 10 +- P5/Source/Specs/metDecl.xml | 50 +- P5/Source/Specs/metSym.xml | 18 +- P5/Source/Specs/metamark.xml | 48 +- P5/Source/Specs/milestone.xml | 14 +- P5/Source/Specs/mod.xml | 10 +- P5/Source/Specs/model.addrPart.xml | 10 +- P5/Source/Specs/model.addressLike.xml | 10 +- P5/Source/Specs/model.annotationLike.xml | 8 +- P5/Source/Specs/model.annotationPart.body.xml | 8 +- P5/Source/Specs/model.applicationLike.xml | 10 +- P5/Source/Specs/model.attributable.xml | 13 +- P5/Source/Specs/model.availabilityPart.xml | 10 +- P5/Source/Specs/model.biblLike.xml | 10 +- P5/Source/Specs/model.biblPart.xml | 10 +- P5/Source/Specs/model.castItemPart.xml | 10 +- P5/Source/Specs/model.catDescPart.xml | 10 +- P5/Source/Specs/model.certLike.xml | 8 +- P5/Source/Specs/model.choicePart.xml | 10 +- P5/Source/Specs/model.common.xml | 10 +- P5/Source/Specs/model.contentPart.xml | 12 +- P5/Source/Specs/model.correspActionPart.xml | 12 +- P5/Source/Specs/model.correspContextPart.xml | 12 +- P5/Source/Specs/model.correspDescPart.xml | 12 +- P5/Source/Specs/model.dateLike.xml | 10 +- P5/Source/Specs/model.descLike.xml | 10 +- P5/Source/Specs/model.describedResource.xml | 8 +- P5/Source/Specs/model.dimLike.xml | 10 +- P5/Source/Specs/model.div1Like.xml | 10 +- P5/Source/Specs/model.div2Like.xml | 10 +- P5/Source/Specs/model.div3Like.xml | 10 +- P5/Source/Specs/model.div4Like.xml | 10 +- P5/Source/Specs/model.div5Like.xml | 10 +- P5/Source/Specs/model.div6Like.xml | 10 +- P5/Source/Specs/model.div7Like.xml | 10 +- P5/Source/Specs/model.divBottom.xml | 10 +- P5/Source/Specs/model.divBottomPart.xml | 10 +- P5/Source/Specs/model.divGenLike.xml | 10 +- P5/Source/Specs/model.divLike.xml | 10 +- P5/Source/Specs/model.divPart.spoken.xml | 20 +- P5/Source/Specs/model.divPart.xml | 10 +- P5/Source/Specs/model.divTop.xml | 12 +- P5/Source/Specs/model.divTopPart.xml | 14 +- P5/Source/Specs/model.divWrapper.xml | 16 +- P5/Source/Specs/model.editorialDeclPart.xml | 13 +- P5/Source/Specs/model.egLike.xml | 16 +- P5/Source/Specs/model.emphLike.xml | 16 +- P5/Source/Specs/model.encodingDescPart.xml | 13 +- P5/Source/Specs/model.entryLike.xml | 10 +- P5/Source/Specs/model.entryPart.top.xml | 10 +- P5/Source/Specs/model.entryPart.xml | 12 +- P5/Source/Specs/model.eventLike.xml | 10 +- P5/Source/Specs/model.featureVal.complex.xml | 12 +- P5/Source/Specs/model.featureVal.single.xml | 12 +- P5/Source/Specs/model.featureVal.xml | 10 +- P5/Source/Specs/model.formPart.xml | 13 +- P5/Source/Specs/model.frontPart.drama.xml | 14 +- P5/Source/Specs/model.frontPart.xml | 12 +- P5/Source/Specs/model.fsdDeclPart.xml | 6 +- P5/Source/Specs/model.gLike.xml | 8 +- P5/Source/Specs/model.global.edit.xml | 14 +- P5/Source/Specs/model.global.meta.xml | 10 +- P5/Source/Specs/model.global.spoken.xml | 10 +- P5/Source/Specs/model.global.xml | 12 +- P5/Source/Specs/model.gramPart.xml | 14 +- P5/Source/Specs/model.graphicLike.xml | 14 +- P5/Source/Specs/model.headLike.xml | 12 +- P5/Source/Specs/model.hiLike.xml | 18 +- P5/Source/Specs/model.highlighted.xml | 14 +- P5/Source/Specs/model.identEquiv.xml | 8 +- P5/Source/Specs/model.identSynonyms.xml | 8 +- P5/Source/Specs/model.imprintPart.xml | 14 +- P5/Source/Specs/model.inter.xml | 8 +- P5/Source/Specs/model.lLike.xml | 10 +- P5/Source/Specs/model.lPart.xml | 10 +- P5/Source/Specs/model.labelLike.xml | 10 +- P5/Source/Specs/model.lexicalRefinement.xml | 10 +- P5/Source/Specs/model.limitedPhrase.xml | 10 +- P5/Source/Specs/model.linePart.xml | 10 +- P5/Source/Specs/model.listLike.xml | 10 +- P5/Source/Specs/model.measureLike.xml | 10 +- P5/Source/Specs/model.milestoneLike.xml | 10 +- P5/Source/Specs/model.morphLike.xml | 10 +- P5/Source/Specs/model.msItemPart.xml | 10 +- P5/Source/Specs/model.msQuoteLike.xml | 10 +- P5/Source/Specs/model.nameLike.agent.xml | 10 +- P5/Source/Specs/model.nameLike.xml | 10 +- P5/Source/Specs/model.noteLike.xml | 10 +- P5/Source/Specs/model.objectLike.xml | 10 +- P5/Source/Specs/model.oddDecl.xml | 10 +- P5/Source/Specs/model.oddRef.xml | 10 +- P5/Source/Specs/model.offsetLike.xml | 10 +- P5/Source/Specs/model.orgPart.xml | 10 +- P5/Source/Specs/model.orgStateLike.xml | 10 +- P5/Source/Specs/model.pLike.front.xml | 10 +- P5/Source/Specs/model.pLike.xml | 10 +- P5/Source/Specs/model.pPart.data.xml | 10 +- P5/Source/Specs/model.pPart.edit.xml | 10 +- P5/Source/Specs/model.pPart.editorial.xml | 10 +- P5/Source/Specs/model.pPart.msdesc.xml | 10 +- .../Specs/model.pPart.transcriptional.xml | 15 +- P5/Source/Specs/model.paraPart.xml | 8 +- P5/Source/Specs/model.persNamePart.xml | 10 +- P5/Source/Specs/model.persStateLike.xml | 10 +- P5/Source/Specs/model.personLike.xml | 10 +- P5/Source/Specs/model.personPart.xml | 10 +- P5/Source/Specs/model.phrase.xml | 10 +- P5/Source/Specs/model.phrase.xml.xml | 10 +- P5/Source/Specs/model.physDescPart.xml | 10 +- P5/Source/Specs/model.placeLike.xml | 10 +- P5/Source/Specs/model.placeNamePart.xml | 10 +- P5/Source/Specs/model.placeStateLike.xml | 10 +- P5/Source/Specs/model.profileDescPart.xml | 10 +- P5/Source/Specs/model.ptrLike.form.xml | 10 +- P5/Source/Specs/model.ptrLike.xml | 10 +- .../model.publicationStmtPart.agency.xml | 10 +- .../model.publicationStmtPart.detail.xml | 10 +- P5/Source/Specs/model.quoteLike.xml | 10 +- P5/Source/Specs/model.rdgLike.xml | 10 +- P5/Source/Specs/model.rdgPart.xml | 10 +- P5/Source/Specs/model.recordingPart.xml | 10 +- P5/Source/Specs/model.resource.xml | 8 +- P5/Source/Specs/model.respLike.xml | 10 +- P5/Source/Specs/model.segLike.xml | 10 +- P5/Source/Specs/model.settingPart.xml | 10 +- P5/Source/Specs/model.sourceDescPart.xml | 10 +- P5/Source/Specs/model.specDescLike.xml | 10 +- P5/Source/Specs/model.stageLike.xml | 10 +- P5/Source/Specs/model.standOffPart.xml | 8 +- P5/Source/Specs/model.teiHeaderPart.xml | 10 +- P5/Source/Specs/model.textDescPart.xml | 10 +- P5/Source/Specs/model.titlepagePart.xml | 10 +- P5/Source/Specs/model.xml | 8 +- P5/Source/Specs/modelGrp.xml | 8 +- P5/Source/Specs/modelSequence.xml | 8 +- P5/Source/Specs/moduleRef.xml | 38 +- P5/Source/Specs/moduleSpec.xml | 26 +- P5/Source/Specs/monogr.xml | 138 +- P5/Source/Specs/mood.xml | 10 +- P5/Source/Specs/move.xml | 26 +- P5/Source/Specs/msContents.xml | 36 +- P5/Source/Specs/msDesc.xml | 14 +- P5/Source/Specs/msFrag.xml | 34 +- P5/Source/Specs/msIdentifier.xml | 10 +- P5/Source/Specs/msItem.xml | 36 +- P5/Source/Specs/msItemStruct.xml | 86 +- P5/Source/Specs/msName.xml | 10 +- P5/Source/Specs/msPart.xml | 17 +- P5/Source/Specs/musicNotation.xml | 10 +- P5/Source/Specs/name.xml | 55 +- P5/Source/Specs/nameLink.xml | 10 +- P5/Source/Specs/namespace.xml | 12 +- P5/Source/Specs/nationality.xml | 63 +- P5/Source/Specs/node.xml | 42 +- P5/Source/Specs/normalization.xml | 13 +- P5/Source/Specs/notatedMusic.xml | 24 +- P5/Source/Specs/note.xml | 28 +- P5/Source/Specs/noteGrp.xml | 30 +- P5/Source/Specs/notesStmt.xml | 26 +- P5/Source/Specs/num.xml | 24 +- P5/Source/Specs/number.xml | 8 +- P5/Source/Specs/numeric.xml | 26 +- P5/Source/Specs/nym.xml | 33 +- P5/Source/Specs/oRef.xml | 16 +- P5/Source/Specs/object.xml | 44 +- P5/Source/Specs/objectDesc.xml | 32 +- P5/Source/Specs/objectIdentifier.xml | 17 +- P5/Source/Specs/objectName.xml | 51 +- P5/Source/Specs/objectType.xml | 10 +- P5/Source/Specs/occupation.xml | 63 +- P5/Source/Specs/offset.xml | 51 +- P5/Source/Specs/opener.xml | 38 +- P5/Source/Specs/org.xml | 10 +- P5/Source/Specs/orgName.xml | 49 +- P5/Source/Specs/orig.xml | 12 +- P5/Source/Specs/origDate.xml | 8 +- P5/Source/Specs/origPlace.xml | 47 +- P5/Source/Specs/origin.xml | 49 +- P5/Source/Specs/orth.xml | 14 +- P5/Source/Specs/outputRendition.xml | 13 +- P5/Source/Specs/p.xml | 10 +- P5/Source/Specs/pRef.xml | 64 +- P5/Source/Specs/param.xml | 14 +- P5/Source/Specs/paramList.xml | 45 +- P5/Source/Specs/paramSpec.xml | 8 +- P5/Source/Specs/particDesc.xml | 206 +- P5/Source/Specs/path.xml | 24 +- P5/Source/Specs/pause.xml | 14 +- P5/Source/Specs/pb.xml | 14 +- P5/Source/Specs/pc.xml | 39 +- P5/Source/Specs/per.xml | 10 +- P5/Source/Specs/performance.xml | 36 +- P5/Source/Specs/persName.xml | 68 +- P5/Source/Specs/persPronouns.xml | 153 +- P5/Source/Specs/person.xml | 52 +- P5/Source/Specs/personGrp.xml | 55 +- P5/Source/Specs/persona.xml | 59 +- P5/Source/Specs/phr.xml | 10 +- P5/Source/Specs/physDesc.xml | 20 +- P5/Source/Specs/place.xml | 60 +- P5/Source/Specs/placeName.xml | 49 +- P5/Source/Specs/population.xml | 51 +- P5/Source/Specs/pos.xml | 11 +- P5/Source/Specs/postBox.xml | 10 +- P5/Source/Specs/postCode.xml | 10 +- P5/Source/Specs/postscript.xml | 40 +- P5/Source/Specs/precision.xml | 73 +- P5/Source/Specs/prefixDef.xml | 24 +- P5/Source/Specs/preparedness.xml | 14 +- P5/Source/Specs/principal.xml | 51 +- P5/Source/Specs/profileDesc.xml | 18 +- P5/Source/Specs/projectDesc.xml | 14 +- P5/Source/Specs/prologue.xml | 36 +- P5/Source/Specs/pron.xml | 19 +- P5/Source/Specs/provenance.xml | 49 +- P5/Source/Specs/ptr.xml | 14 +- P5/Source/Specs/pubPlace.xml | 10 +- P5/Source/Specs/publicationStmt.xml | 32 +- P5/Source/Specs/publisher.xml | 13 +- P5/Source/Specs/punctuation.xml | 20 +- P5/Source/Specs/purpose.xml | 18 +- P5/Source/Specs/q.xml | 14 +- P5/Source/Specs/quotation.xml | 20 +- P5/Source/Specs/quote.xml | 10 +- P5/Source/Specs/rb.xml | 41 +- P5/Source/Specs/rdg.xml | 10 +- P5/Source/Specs/rdgGrp.xml | 24 +- P5/Source/Specs/re.xml | 28 +- P5/Source/Specs/recordHist.xml | 18 +- P5/Source/Specs/recording.xml | 24 +- P5/Source/Specs/recordingStmt.xml | 18 +- P5/Source/Specs/redo.xml | 18 +- P5/Source/Specs/ref.xml | 16 +- P5/Source/Specs/refState.xml | 20 +- P5/Source/Specs/refsDecl.xml | 14 +- P5/Source/Specs/reg.xml | 14 +- P5/Source/Specs/region.xml | 49 +- P5/Source/Specs/relatedItem.xml | 24 +- P5/Source/Specs/relation.xml | 71 +- P5/Source/Specs/remarks.xml | 18 +- P5/Source/Specs/rendition.xml | 18 +- P5/Source/Specs/repository.xml | 8 +- P5/Source/Specs/residence.xml | 55 +- P5/Source/Specs/resp.xml | 49 +- P5/Source/Specs/respStmt.xml | 20 +- P5/Source/Specs/respons.xml | 12 +- P5/Source/Specs/restore.xml | 10 +- P5/Source/Specs/retrace.xml | 10 +- P5/Source/Specs/revisionDesc.xml | 10 +- P5/Source/Specs/rhyme.xml | 61 +- P5/Source/Specs/role.xml | 14 +- P5/Source/Specs/roleDesc.xml | 10 +- P5/Source/Specs/roleName.xml | 10 +- P5/Source/Specs/root.xml | 30 +- P5/Source/Specs/row.xml | 22 +- P5/Source/Specs/rs.xml | 10 +- P5/Source/Specs/rt.xml | 37 +- P5/Source/Specs/rubric.xml | 10 +- P5/Source/Specs/ruby.xml | 28 +- P5/Source/Specs/s.xml | 27 +- P5/Source/Specs/said.xml | 18 +- P5/Source/Specs/salute.xml | 10 +- P5/Source/Specs/samplingDecl.xml | 22 +- P5/Source/Specs/schemaRef.xml | 24 +- P5/Source/Specs/schemaSpec.xml | 24 +- P5/Source/Specs/scriptDesc.xml | 22 +- P5/Source/Specs/scriptNote.xml | 10 +- P5/Source/Specs/scriptStmt.xml | 14 +- P5/Source/Specs/seal.xml | 69 +- P5/Source/Specs/sealDesc.xml | 30 +- P5/Source/Specs/secFol.xml | 10 +- P5/Source/Specs/secl.xml | 29 +- P5/Source/Specs/seg.xml | 4 +- P5/Source/Specs/segmentation.xml | 14 +- P5/Source/Specs/sense.xml | 32 +- P5/Source/Specs/sequence.xml | 14 +- P5/Source/Specs/series.xml | 38 +- P5/Source/Specs/seriesStmt.xml | 42 +- P5/Source/Specs/set.xml | 32 +- P5/Source/Specs/setting.xml | 10 +- P5/Source/Specs/settingDesc.xml | 130 +- P5/Source/Specs/settlement.xml | 49 +- P5/Source/Specs/sex.xml | 55 +- P5/Source/Specs/shift.xml | 25 +- P5/Source/Specs/sic.xml | 10 +- P5/Source/Specs/signatures.xml | 8 +- P5/Source/Specs/signed.xml | 10 +- P5/Source/Specs/soCalled.xml | 10 +- P5/Source/Specs/socecStatus.xml | 63 +- P5/Source/Specs/sound.xml | 18 +- P5/Source/Specs/source.xml | 10 +- P5/Source/Specs/sourceDesc.xml | 28 +- P5/Source/Specs/sourceDoc.xml | 11 +- P5/Source/Specs/sp.xml | 8 +- P5/Source/Specs/spGrp.xml | 26 +- P5/Source/Specs/space.xml | 14 +- P5/Source/Specs/span.xml | 18 +- P5/Source/Specs/spanGrp.xml | 12 +- P5/Source/Specs/speaker.xml | 10 +- P5/Source/Specs/specDesc.xml | 30 +- P5/Source/Specs/specGrp.xml | 10 +- P5/Source/Specs/specGrpRef.xml | 20 +- P5/Source/Specs/specList.xml | 14 +- P5/Source/Specs/sponsor.xml | 53 +- P5/Source/Specs/stage.xml | 41 +- P5/Source/Specs/stamp.xml | 47 +- P5/Source/Specs/standOff.xml | 135 +- P5/Source/Specs/state.xml | 61 +- P5/Source/Specs/stdVals.xml | 14 +- P5/Source/Specs/street.xml | 10 +- P5/Source/Specs/stress.xml | 10 +- P5/Source/Specs/string.xml | 10 +- P5/Source/Specs/styleDefDecl.xml | 14 +- P5/Source/Specs/subc.xml | 11 +- P5/Source/Specs/subst.xml | 12 +- P5/Source/Specs/substJoin.xml | 6 +- P5/Source/Specs/summary.xml | 10 +- P5/Source/Specs/superEntry.xml | 18 +- P5/Source/Specs/supplied.xml | 16 +- P5/Source/Specs/support.xml | 10 +- P5/Source/Specs/supportDesc.xml | 12 +- P5/Source/Specs/surface.xml | 50 +- P5/Source/Specs/surfaceGrp.xml | 24 +- P5/Source/Specs/surname.xml | 10 +- P5/Source/Specs/surplus.xml | 14 +- P5/Source/Specs/surrogates.xml | 10 +- P5/Source/Specs/syll.xml | 10 +- P5/Source/Specs/symbol.xml | 18 +- P5/Source/Specs/table.xml | 57 +- P5/Source/Specs/tag.xml | 16 +- P5/Source/Specs/tagUsage.xml | 22 +- P5/Source/Specs/tagsDecl.xml | 16 +- P5/Source/Specs/taxonomy.xml | 10 +- P5/Source/Specs/tech.xml | 19 +- P5/Source/Specs/teiCorpus.xml | 14 +- P5/Source/Specs/teiHeader.xml | 14 +- P5/Source/Specs/teidata.authority.xml | 12 +- P5/Source/Specs/teidata.certainty.xml | 6 +- P5/Source/Specs/teidata.count.xml | 18 +- P5/Source/Specs/teidata.duration.iso.xml | 66 +- P5/Source/Specs/teidata.duration.w3c.xml | 66 +- P5/Source/Specs/teidata.enumerated.xml | 22 +- P5/Source/Specs/teidata.gender.xml | 10 +- P5/Source/Specs/teidata.interval.xml | 28 +- P5/Source/Specs/teidata.key.xml | 77 +- P5/Source/Specs/teidata.language.xml | 227 +- P5/Source/Specs/teidata.name.xml | 18 +- P5/Source/Specs/teidata.namespace.xml | 18 +- P5/Source/Specs/teidata.namespaceOrName.xml | 15 +- P5/Source/Specs/teidata.nullOrName.xml | 31 +- P5/Source/Specs/teidata.numeric.xml | 51 +- P5/Source/Specs/teidata.outputMeasurement.xml | 44 +- P5/Source/Specs/teidata.pattern.xml | 8 +- P5/Source/Specs/teidata.point.xml | 18 +- P5/Source/Specs/teidata.pointer.xml | 18 +- P5/Source/Specs/teidata.prefix.xml | 21 +- P5/Source/Specs/teidata.probCert.xml | 26 +- P5/Source/Specs/teidata.probability.xml | 18 +- P5/Source/Specs/teidata.replacement.xml | 14 +- P5/Source/Specs/teidata.sex.xml | 26 +- P5/Source/Specs/teidata.temporal.iso.xml | 46 +- P5/Source/Specs/teidata.temporal.w3c.xml | 36 +- P5/Source/Specs/teidata.temporal.working.xml | 13 +- P5/Source/Specs/teidata.text.xml | 14 +- P5/Source/Specs/teidata.truthValue.xml | 20 +- P5/Source/Specs/teidata.unboundedCount.xml | 10 +- P5/Source/Specs/teidata.version.xml | 16 +- P5/Source/Specs/teidata.versionNumber.xml | 14 +- P5/Source/Specs/teidata.word.xml | 18 +- P5/Source/Specs/teidata.xTruthValue.xml | 30 +- P5/Source/Specs/teidata.xmlName.xml | 14 +- P5/Source/Specs/teidata.xpath.xml | 24 +- P5/Source/Specs/term.xml | 21 +- P5/Source/Specs/terrain.xml | 83 +- P5/Source/Specs/text.xml | 14 +- P5/Source/Specs/textClass.xml | 22 +- P5/Source/Specs/textDesc.xml | 14 +- P5/Source/Specs/textLang.xml | 20 +- P5/Source/Specs/textNode.xml | 28 +- P5/Source/Specs/then.xml | 14 +- P5/Source/Specs/time.xml | 8 +- P5/Source/Specs/timeline.xml | 20 +- P5/Source/Specs/title.xml | 67 +- P5/Source/Specs/titlePage.xml | 18 +- P5/Source/Specs/titlePart.xml | 14 +- P5/Source/Specs/titleStmt.xml | 8 +- P5/Source/Specs/tns.xml | 10 +- P5/Source/Specs/trailer.xml | 38 +- P5/Source/Specs/trait.xml | 49 +- P5/Source/Specs/transcriptionDesc.xml | 72 +- P5/Source/Specs/transpose.xml | 10 +- P5/Source/Specs/tree.xml | 22 +- P5/Source/Specs/triangle.xml | 30 +- P5/Source/Specs/typeDesc.xml | 22 +- P5/Source/Specs/typeNote.xml | 10 +- P5/Source/Specs/u.xml | 14 +- P5/Source/Specs/unclear.xml | 49 +- P5/Source/Specs/undo.xml | 18 +- P5/Source/Specs/unicodeProp.xml | 545 +-- P5/Source/Specs/unihanProp.xml | 275 +- P5/Source/Specs/unit.xml | 35 +- P5/Source/Specs/unitDecl.xml | 91 +- P5/Source/Specs/unitDef.xml | 87 +- P5/Source/Specs/usg.xml | 13 +- P5/Source/Specs/vAlt.xml | 18 +- P5/Source/Specs/vColl.xml | 28 +- P5/Source/Specs/vDefault.xml | 18 +- P5/Source/Specs/vLabel.xml | 18 +- P5/Source/Specs/vMerge.xml | 18 +- P5/Source/Specs/vNot.xml | 14 +- P5/Source/Specs/vRange.xml | 10 +- P5/Source/Specs/val.xml | 10 +- P5/Source/Specs/valDesc.xml | 10 +- P5/Source/Specs/valItem.xml | 24 +- P5/Source/Specs/valList.xml | 14 +- P5/Source/Specs/variantEncoding.xml | 22 +- P5/Source/Specs/view.xml | 10 +- P5/Source/Specs/vocal.xml | 18 +- P5/Source/Specs/w.xml | 12 +- P5/Source/Specs/watermark.xml | 8 +- P5/Source/Specs/when.xml | 24 +- P5/Source/Specs/width.xml | 10 +- P5/Source/Specs/wit.xml | 10 +- P5/Source/Specs/witDetail.xml | 18 +- P5/Source/Specs/witEnd.xml | 14 +- P5/Source/Specs/witStart.xml | 14 +- P5/Source/Specs/witness.xml | 12 +- P5/Source/Specs/writing.xml | 14 +- P5/Source/Specs/xenoData.xml | 225 +- P5/Source/Specs/xr.xml | 34 +- P5/Source/Specs/zone.xml | 14 +- 876 files changed, 17978 insertions(+), 38841 deletions(-) diff --git a/P5/Source/Guidelines/en/AB-About.xml b/P5/Source/Guidelines/en/AB-About.xml index 9ca1077c08..3691ce820b 100644 --- a/P5/Source/Guidelines/en/AB-About.xml +++ b/P5/Source/Guidelines/en/AB-About.xml @@ -1,24 +1,13 @@ - - - + -
-About These Guidelines - -

These Guidelines have been developed and are maintained by the Text + About These Guidelines +

These Guidelines have been developed and are maintained by the Text Encoding Initiative Consortium (TEI); see . They are addressed to anyone who works with any kind of textual resource in digital form.

- -

They make recommendations about suitable ways of representing those +

They make recommendations about suitable ways of representing those features of textual resources which need to be identified explicitly in order to facilitate processing by computer programs. In particular, they specify a set of markers (or tags) which @@ -40,8 +29,7 @@ context; we use the term markup vocabulary for the specific set of markers or named distinctions employed by a given encoding scheme. Thus, this work both describes the TEI encoding scheme, and documents the TEI markup vocabulary.

- -

The TEI encoding scheme is of particular usefulness in facilitating +

The TEI encoding scheme is of particular usefulness in facilitating the loss-free interchange of data amongst individuals and research groups using different programs, computer systems, or application software. Since they contain an inventory of the features most often @@ -49,8 +37,7 @@ deployed for computer-based text processing, these Guidelines are also useful as a starting point for those designing new systems and creating new materials, even where interchange of information is not a primary objective.

- -

These Guidelines apply to texts in any natural language, of any +

These Guidelines apply to texts in any natural language, of any date, in any literary genre or text type, without restriction on form or content. They treat both continuous materials (running text) and discontinuous materials such as dictionaries and @@ -65,8 +52,7 @@ applicable to textual material which is born digital. We believe them to be adequate to the widest variety of currently existing practices in using digital textual data, but by no means limited to them.

- -

The rules and recommendations made in these Guidelines are +

The rules and recommendations made in these Guidelines are expressed in terms of what is currently the most widely-used markup language for digital resources of all kinds: the Extensible Markup Language (XML), as defined by the World Wide Web Consortium's XML @@ -80,24 +66,21 @@ languages see chapter ; for more information on the associated character encoding issues see chapter .

- -

This document provides the authoritative and complete statement of +

This document provides the authoritative and complete statement of the requirements and usage of the TEI encoding scheme. As such, although it includes numerous small examples, it must be stressed that this work is intended to be a reference manual rather than a tutorial guide.

- -

The remainder of this chapter comprises three sections. The first +

The remainder of this chapter comprises three sections. The first gives an overview of the structure and notational conventions used throughout these Guidelines. The second enumerates the design principles underlying the TEI scheme and the application environments in which it may be found useful. Finally, the third section gives a brief account of the origins and development of the Text Encoding Initiative itself.

- -
Structure and Notational +
+ Structure and Notational Conventions of this Document - -

The remaining two sections of the front matter to these Guidelines +

The remaining two sections of the front matter to these Guidelines provide background tutorial material for those unfamiliar with basic markup technologies. Following the present introductory section, we present a detailed introduction to XML itself, intended to cover in a @@ -109,8 +92,7 @@ languages and writing systems in digital form. This chapter is largely intended for the user unfamiliar with the Unicode encoding systems, though the expert may also find its historical overview of interest.

- -

The body of this edition of these Guidelines proper contains 23 +

The body of this edition of these Guidelines proper contains 23 chapters arranged in increasing order of specialist interest. The first five chapters discuss in depth matters likely to be of importance to anyone intending to apply the TEI scheme to virtually @@ -123,16 +105,14 @@ encoding used to represent the TEI scheme itself, and provide technical information about its implementation. The last chapter also defines the notion of TEI conformance and its implications for interchange of materials produced according to these Guidelines.

- -

As noted above, this is a reference work, and is not intended to be +

As noted above, this is a reference work, and is not intended to be read through from beginning to end. However, the reader wishing to understand the full potential of the TEI scheme will need a thorough grasp of the material covered by the first four chapters and the last two. Beyond that, the reader is recommended to select according to their specific interests: one of the strengths of the TEI architecture is its modular nature.

- -

As far as possible, extensive cross referencing is provided +

As far as possible, extensive cross referencing is provided wherever related topics are dealt with; these are particularly effective in the online version of these Guidelines. In addition, a series of technical appendixes provide detailed formal definitions for @@ -141,9 +121,7 @@ the work; these are also cross linked as appropriate. Finally, a detailed bibliography is provided, which identifies the source of many examples cited in the text as well as documenting works referred to, and listing other relevant publications.

- - -

As an aid to the reader, most chapters of these Guidelines follow +

As an aid to the reader, most chapters of these Guidelines follow the same basic organization. The chapter begins with an overview of the subjects treated within it, linked to the following subsections. Within each section where new elements are described, a @@ -157,8 +135,7 @@ usefully be applied. Where appropriate, a link to a statement of the source for most examples is provided in the online version. Within the examples, use of whitespace such as newlines or indentation is simply intended to aid legibility, and is not prescriptive or normative.

- -

Wherever TEI elements or classes are mentioned in the text, they +

Wherever TEI elements or classes are mentioned in the text, they are linked in the online version to the relevant reference specification for the element or class concerned. Element names are always given in the form name, where name is the @@ -170,45 +147,32 @@ attribute. References to classes are also presented as links, for example model.divLike for a model class, and att.global for an attribute class.

- -
- The use of modal verbs -

In general the TEI guidelines try to be careful when using modal verbs and phrases such as 'must', 'must not, +

+ The use of modal verbs +

In general the TEI guidelines try to be careful when using modal verbs and phrases such as 'must', 'must not, 'should', 'should not' and 'may'. In terms of the meanings, these generally follow in the different meanings of these words. In particular: - - - This word, or the terms "REQUIRED" or "SHALL", means that this is an absolute requirement of the TEI Guidelines - for production of a TEI conformant file. - - This phrase, or the phrase "SHALL NOT", means that this is an absolute prohibition of the - TEI Guidelines for production of a TEI conformant file. - - This word, or the adjective "RECOMMENDED", means that there may exist valid reasons in + This word, or the terms "REQUIRED" or "SHALL", means that this is an absolute requirement of the TEI Guidelines + for production of a TEI conformant file.This phrase, or the phrase "SHALL NOT", means that this is an absolute prohibition of the + TEI Guidelines for production of a TEI conformant file.This word, or the adjective "RECOMMENDED", means that there may exist valid reasons in particular circumstances to ignore a particular recommendation, but the full implications - must be understood and carefully weighed before choosing a different course. - - This phrase, or the phrase "NOT RECOMMENDED" means that there may exist valid reasons in + must be understood and carefully weighed before choosing a different course.This phrase, or the phrase "NOT RECOMMENDED" means that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications - should be understood and the case carefully weighed before implementing any behavior so described. - - This word, or the adjective "OPTIONAL", means that a recommendation is truly optional. One user may + should be understood and the case carefully weighed before implementing any behavior so described.This word, or the adjective "OPTIONAL", means that a recommendation is truly optional. One user may choose to follow the recommendation because a particular project requires it or feels that - it enhances their work while another project may choose to not follow this recommendation. - + it enhances their work while another project may choose to not follow this recommendation. However, the prose of the TEI Guidelines continually undergoes revision and all uses may not reflect this. Please report any errors or unclear use of these words.

-
- -
-TEI Naming Conventions -

These Guidelines use a more or less consistent set of conventions +

+
+ TEI Naming Conventions +

These Guidelines use a more or less consistent set of conventions in the naming of XML elements and classes. This section summarizes those conventions.

-
-Element and Attribute Names -

An unadorned name such as blort is the +

+ Element and Attribute Names +

An unadorned name such as blort is the name of a TEI element or attribute. During generation of TEI RELAX NG schema fragments, the patterns corresponding with these TEI names are given a prefix tei to allow them @@ -216,88 +180,44 @@ to co-exist with names from other XML namespace. This prefix is not visible to the end user, and is not used in TEI documentation. When generating multi-namespace schemas, however, the user needs to be aware of them. .

-

The following conventions apply to the choice of names: - -Elements are given generic identifiers as far as possible +

The following conventions apply to the choice of names: +Elements are given generic identifiers as far as possible consisting of one or more tokens, by which we mean whole words or recognisable abbreviations of them, taken from the English -language. -Where an element name contains more than one token, the first +language. Where an element name contains more than one token, the first letter of the second token, and of any subsequent ones, is capitalized, as in for example biblStruct, listPerson. This camelCasing is used also for attribute names and -symbolic values. -Module names also use whole words, for the most part, but are -always all lower case. -The specification for an element or attribute whose name +symbolic values. Module names also use whole words, for the most part, but are +always all lower case. The specification for an element or attribute whose name contains abbreviations generally also includes a gloss -element providing the expanded sense of the name. -An element specification may also contain approved translations +element providing the expanded sense of the name.An element specification may also contain approved translations for element or attribute names in one or more other languages using the altIdent element; this is not however generally done in -TEI P5. - +TEI P5.

- -

Whole words are generally preferred for clarity. The following +

Whole words are generally preferred for clarity. The following abbreviations are however commonly used within generic identifiers: - - - -attribute - -bibliographic description or reference in a bibliography - -category, especially as used in text classification - -character, typically a Unicode character - -document: this usually refers to the original source document -which is being encoded, - -declaration: has a specific sense in the TEI -header, as discussed in - -description: has a specific sense in the TEI header, as -discussed in - -group. In TEI usage, a group is distinguished from a list in that +attributebibliographic description or reference in a bibliographycategory, especially as used in text classification character, typically a Unicode characterdocument: this usually refers to the original source document +which is being encoded,declaration: has a specific sense in the TEI +header, as discussed in description: has a specific sense in the TEI header, as +discussed in group. In TEI usage, a group is distinguished from a list in that the former associates several objects which act as a single entity, while the latter does not. For example, a linkGrp combines several link elements which have certain properties in common, whereas a listBibl simply lists a number of otherwise -unrelated bibl elements. - -interpretation or analysis -(natural) language -manuscript - -organization, that is, a named group of people or legal entity - -reading or version found in a specific witness -reference or link - -technical specification or definition - -statement: used in a specific sense in the TEI header, -as discussed in - -structured: that is, containing a specific set of -named elements rather than mixed content - -value, for example of a variable or an attribute - -witness: that is, a specific document which attests specific -readings in a textual tradition or apparatus - +unrelated bibl elements.interpretation or analysis(natural) languagemanuscriptorganization, that is, a named group of people or legal entityreading or version found in a specific witnessreference or linktechnical specification or definitionstatement: used in a specific sense in the TEI header, +as discussed in structured: that is, containing a specific set of +named elements rather than mixed contentvalue, for example of a variable or an attributewitness: that is, a specific document which attests specific +readings in a textual tradition or apparatus

-

Some abbreviations are used inconsistently: for example, +

Some abbreviations are used inconsistently: for example, add is an addition, and addSpan is a spanning addition, but addName is an additional name, not the name of an addition. Such inconsistencies are relatively few in number, and it is hoped to remove them in subsequent revisions of these Guidelines.

-

Some elements have very short abbreviated names: these are for the +

Some elements have very short abbreviated names: these are for the most part elements which are likely to be used very frequently in a marked up text, for example p (paragraph), s (segment) hi (highlighted phrase), ptr (pointer), @@ -305,100 +225,63 @@ marked up text, for example p (paragraph), s here: as noted above, an expansion of each such abbreviated name is provided within the documentation using the gloss element .

-
-
-
-Class, Macro, and Datatype Names - -

All named objects other than elements and attributes have one of +

+
+
+ Class, Macro, and Datatype Names +

All named objects other than elements and attributes have one of the following prefixes, which indicate whether the object is a module, -an attribute class, a model class, a datatype, or a macro: - -Component -Name -Example - -Attribute -Classesatt.*att.global -Model -Classesmodel.*model.biblPart -Macrosmacro.*macro.paraContent -Datatypesteidata.*teidata.pointer -
+an attribute class, a model class, a datatype, or a macro: ComponentNameExampleAttribute +Classesatt.*att.globalModel +Classesmodel.*model.biblPartMacrosmacro.*macro.paraContentDatatypesteidata.*teidata.pointer

-

The concepts of model class, attribute class, etc. are defined in +

The concepts of model class, attribute class, etc. are defined in . Here we simply note some conventions about their naming.

- -

The following rules apply to attribute class names: -Attribute class names take the form att.xxx, where +

The following rules apply to attribute class names: Attribute class names take the form att.xxx, where xxx is typically an adjective, or a series of adjectives separated by dots, describing a property common to the attributes -which make up the class. -Attributes with the same name are considered to have the same +which make up the class.Attributes with the same name are considered to have the same semantics, whether the attribute is inherited from a class, or locally -defined. - +defined.

- -

The following rules apply to model class names: -Model classes have names beginning model. followed +

The following rules apply to model class names: Model classes have names beginning model. followed by a root name, and zero or more suffixes as described -below. -A root name may be the name of an element, generally the +below.A root name may be the name of an element, generally the prototypical parent or sibling for elements which are members of the -class. -The first suffix should be Part, if the class +class.The first suffix should be Part, if the class members are all children of the element named rootname; or Like, if the class members are all siblings of the -element named rootname. -The rootname global is used to indicate that class -members are permitted anywhere in a TEI document. -Additional suffixes may be added, prefixed by a dot, to -distinguish subclasses, semantic or structural. - +element named rootname. The rootname global is used to indicate that class +members are permitted anywhere in a TEI document.Additional suffixes may be added, prefixed by a dot, to +distinguish subclasses, semantic or structural.

-

For example, the class of elements which can form part of a +

For example, the class of elements which can form part of a div is called model.divPart. This class includes as a subclass the elements which can form part of a div in a spoken text, which is named model.divPart.spoken

- - -
- - - -
Design Principles - -

Because of its roots in the humanities research community, the TEI +

+
+ Design Principles +

Because of its roots in the humanities research community, the TEI scheme is driven by its original goal of serving the needs of research, and is therefore committed to providing a maximum of comprehensibility, flexibility, and extensibility. More specific design goals of the TEI have been that these Guidelines should: - -provide a standard format for data interchange -provide guidance for the encoding of texts in this format -support the encoding of all kinds of features of all -kinds of texts studied by researchers -be application independent +provide a standard format for data interchangeprovide guidance for the encoding of texts in this formatsupport the encoding of all kinds of features of all +kinds of texts studied by researchersbe application independent This has led to a number of important design decisions, such as: - -the choice of XML and Unicode -the provision of a large predefined tag set -encodings for different views of text -alternative encodings for the same textual features -mechanisms for user-defined modification of the scheme +the choice of XML and Unicodethe provision of a large predefined tag setencodings for different views of textalternative encodings for the same textual featuresmechanisms for user-defined modification of the scheme We discuss some of these goals in more detail below.

- -

The goal of creating a common interchange format which is +

The goal of creating a common interchange format which is application independent requires the definition of a specific markup syntax as well as the definition of a large set of elements or concepts. The syntax of the recommendations made in this document conforms to the World Wide Web Consortium's XML Recommendation () but their definition is as far as possible independent of any particular schema language.

-

The goal of providing guidance for text encoding suggests that +

The goal of providing guidance for text encoding suggests that recommendations be made as to what textual features should be recorded in various situations. However, when selecting certain features for encoding in preference to others, these Guidelines have tended to @@ -413,7 +296,7 @@ very rarely require you to encode any particular feature, they do require you to be honest about which features you have encoded, that is, to respect the meanings and usage rules they recommend for specific elements and attributes proposed.

-

The requirement to support all kinds of materials likely to be of +

The requirement to support all kinds of materials likely to be of interest in research has largely conditioned the development of the TEI into a very flexible and modular system. The development of other XML vocabularies or standards is typically motivated by the desire to @@ -424,14 +307,14 @@ domains. It achieves its generality by means of the modular architecture described in which enables each user to create a schema appropriate to their needs without compromising the interoperability of their data.

-

The Guidelines have been written largely with a focus on text capture +

The Guidelines have been written largely with a focus on text capture (i.e. the representation in electronic form of an already existing copy text in another medium) rather than text creation (where no such copy text exists). Hence the frequent use of terms like transcription, original, copy text, etc. However, these Guidelines are equally applicable to text creation, although certain elements, such as sourceDesc, and certain attributes, such as the rendition indicators, will not be relevant in this case.

-

Concerning text capture the TEI Guidelines do not specify a +

Concerning text capture the TEI Guidelines do not specify a particular approach to the problem of fidelity to the source text and recoverability of the original; such a choice is the responsibility of the text encoder. The current version of these Guidelines, however, @@ -443,7 +326,7 @@ version of these Guidelines, it is no longer necessarily the case that an unmediated version of the source text can be recovered from an encoded text simply by removing the markup.

-

In these Guidelines, no hard and fast distinction is drawn between +

In these Guidelines, no hard and fast distinction is drawn between objective and subjective information or between representation and interpretation. These distinctions, though @@ -458,7 +341,7 @@ types of encoding in these Guidelines is not intended to support any particular view on these theoretical issues. Historically, it reflects a purely practical division of responsibility amongst the original working committees (see further ).

-

In general, the accuracy and the reliability of the encoding and the +

In general, the accuracy and the reliability of the encoding and the appropriateness of the interpretation is for the individual user of the text to determine. The Guidelines provide a means of documenting the encoding in such a way that a user of the text can know the reasoning @@ -467,8 +350,7 @@ is based. The TEI header should be used to document and justify many such aspects of the encoding, but the choice of TEI elements for a particular feature is in itself a statement about the interpretation reached by the encoder.

- -

In many situations more than one view of a text is needed since no +

In many situations more than one view of a text is needed since no absolute recommendation to embody one specific view of text can apply to all texts and all approaches to them. Within limits, the syntax of XML ensures that some encodings can be ignored for some purposes. To @@ -483,8 +365,7 @@ syntax of XML (which requires a single hierarchical view of text structure) poses some problems; recommendations concerning ways of overcoming or circumventing that restriction are discussed in chapter .

- -

In brief, the TEI Guidelines define a general-purpose encoding +

In brief, the TEI Guidelines define a general-purpose encoding scheme which makes it possible to encode different views of text, possibly intended for different applications, serving the majority of scholarly purposes of text studies in the humanities. Because no @@ -496,34 +377,33 @@ the TEI recommendations, the TEI makes it simple for such user-identified modifications to be incorporated into future releases of these Guidelines as they evolve. The underlying mechanisms which support these aspects of the scheme are introduced in chapter , and detailed discussions of their use provided in -chapter .

- -
Intended Use -

We envisage three primary functions for these Guidelines: - -guidance for individual or local practice in text -creation and data capture; -support of data interchange; -support of application-independent local processing. +chapter .

+
+
+ Intended Use +

We envisage three primary functions for these Guidelines: +guidance for individual or local practice in text +creation and data capture;support of data interchange;support of application-independent local processing. These three functions are so thoroughly interwoven in practice that it is hardly possible to address any one without addressing the others. However, the distinction provides a useful framework for discussing the possible role of these Guidelines in work with electronic texts.

-
Use in Text Capture and Text Creation -

The description of textual features found in the chapters which +

+ Use in Text Capture and Text Creation +

The description of textual features found in the chapters which follow should provide a useful checklist from which scholars planning to create electronic texts should select the subset of features suitable for their project.

-

Problems specific to text creation or text +

Problems specific to text creation or text capture have not been considered explicitly in this document. These Guidelines are not concerned with the process by which a digital text comes into being: it can be typed by hand, scanned from a printed book or typescript, read from a typesetter's tape, or acquired from another researcher who may have used another markup scheme (or no explicit markup at all).

-

We include here only some general points which are often raised about +

We include here only some general points which are often raised about markup and the process of data capture.

-

XML can appear distressingly verbose, particularly when (as in these +

XML can appear distressingly verbose, particularly when (as in these Guidelines) the names of tags and attributes are chosen for clarity and not for brevity. Editor macros and keyboard shortcuts can allow a typist to enter frequently used tags with single keystrokes. @@ -531,16 +411,16 @@ It is often possible to transform word-processed or scanned text automatically. Markup-aware software can help with maintaining the hierarchical structure of the document, and display the document with visual formatting rather than raw tags.

-

The techniques described in chapter +

The techniques described in chapter may be used to develop simpler data capture TEI-conformant schemas, for example with limited numbers of elements, or with shorter names for the tags being used most often. Documents created with such schemas may then be automatically converted to a more elaborated TEI form.

-
-
Use for Interchange - -

The TEI format may simply be used as an interchange format, +

+
+ Use for Interchange +

The TEI format may simply be used as an interchange format, permitting projects to share resources even when their local encoding schemes differ. If there are n different encoding formats, to provide mappings between each possible pair of formats @@ -551,91 +431,67 @@ loss of information, the interchange format chosen must be as expressive (in a formal sense) as any of the target formats; this is a further reason for the TEI's provision of both highly abstract or generic encodings and highly specific ones.

-

To translate between any pair of encoding schemes implies: - -identifying the sets of textual features distinguished -by the two schemes; -determining where the two sets of features correspond; -creating a suitable set of mappings.

-

For example, to translate from encoding scheme X into the TEI +

To translate between any pair of encoding schemes implies: +identifying the sets of textual features distinguished +by the two schemes;determining where the two sets of features correspond;creating a suitable set of mappings.

+

For example, to translate from encoding scheme X into the TEI scheme: - -Make a list of all the textual features distinguished in -X. -Identify the corresponding feature in the TEI scheme. +Make a list of all the textual features distinguished in +X. Identify the corresponding feature in the TEI scheme. There are three possibilities for each feature: - -the feature exists in both X and the TEI scheme; -X has a feature which is absent from the TEI scheme; -X has a feature which corresponds with more than one +the feature exists in both X and the TEI scheme;X has a feature which is absent from the TEI scheme;X has a feature which corresponds with more than one feature in the TEI scheme. The first case is a trivial renaming. The second will require an extension to the TEI scheme, as described in chapter . The third is more problematic, but not impossible, provided that a consistent -choice can be made (and documented) amongst the alternatives. -

-

The ease with which this translation can be defined will of +choice can be made (and documented) amongst the alternatives.

+

The ease with which this translation can be defined will of course depend on the clarity with which scheme X represents the features it encodes.

-

Translating from the TEI into scheme X follows the same pattern, +

Translating from the TEI into scheme X follows the same pattern, except that if a TEI feature has no equivalent in X, and X cannot be extended, information must be lost in translation.

-

The rules defining conformance to these Guidelines are +

The rules defining conformance to these Guidelines are given in some detail in chapter . The basic principles informing those rules may be summarized as follows: - -The TEI abstract model (that is, the set of +The TEI abstract model (that is, the set of categorical distinctions which it defines in the prose of the Guidelines) must be respected. The correspondence between a tag X and the semantic function assigned to it by these Guidelines may not be changed; such changes are known -as tag abuse and strongly discouraged. -A TEI document must be expressed as a valid XML-conformant +as tag abuse and strongly discouraged.A TEI document must be expressed as a valid XML-conformant document which uses the TEI namespace appropriately. If, for example, the document encodes features not provided by these Guidelines, such -extensions should not be associated with the TEI namespace. -It must be possible to validate a TEI document against a schema +extensions should not be associated with the TEI namespace. It must be possible to validate a TEI document against a schema derived from these Guidelines, possibly with extensions provided in -the recommended manner. - +the recommended manner. -

- - -
Use for Local Processing -

Machine-readable text can be manipulated in many ways; some users: - -edit texts (e.g. word processors, syntax-directed -editors) -edit, display, and link texts in hypertext systems -format and print texts using desktop publishing systems, -or batch-oriented formatting programs -load texts into free-text retrieval databases or -conventional databases -unload texts from databases as search results or for -export to other software -search texts for words or phrases -perform content analysis on texts -collate texts for critical editions -scan texts for automatic indexing or similar purposes -parse texts linguistically -analyze texts stylistically -scan verse texts metrically -link text and images

-

These applications cover a wide range of likely uses but are by no +

+
+
+ Use for Local Processing +

Machine-readable text can be manipulated in many ways; some users: +edit texts (e.g. word processors, syntax-directed +editors) edit, display, and link texts in hypertext systemsformat and print texts using desktop publishing systems, +or batch-oriented formatting programs load texts into free-text retrieval databases or +conventional databases unload texts from databases as search results or for +export to other software search texts for words or phrases perform content analysis on texts collate texts for critical editions scan texts for automatic indexing or similar purposesparse texts linguistically analyze texts stylistically scan verse texts metrically link text and images

+

These applications cover a wide range of likely uses but are by no means exhaustive. The aim has been to make the TEI Guidelines useful for encoding the same texts for different purposes. We have avoided anything which would restrict the use of the text for other applications. We have also tried not to omit anything essential to any single application.

-

Because the TEI format is expressed using XML, +

Because the TEI format is expressed using XML, almost any modern text processing system is able to process it, and new TEI-aware software systems are able to build on a solid base -of existing software libraries.

- -
Historical Background - -

The Text Encoding Initiative grew out of a planning conference +of existing software libraries.

+
+
+
+
+ Historical Background +

The Text Encoding Initiative grew out of a planning conference sponsored by the Association for Computers and the Humanities (ACH) and funded by the U.S. National Endowment for the Humanities (NEH), which was held at Vassar College in November 1987. At this conference some @@ -648,7 +504,7 @@ agreed to join ACH as sponsors of a project to develop these Guidelines. The outcome of the conference was a set of principles (the Poughkeepsie Principles, ), which determined the further course of the project.

- - -

The Text Encoding Initiative project began in June 1988 with funding + +

The Text Encoding Initiative project began in June 1988 with funding from the NEH, soon followed by further funding from the Commission of the European Communities, the Andrew W. Mellon Foundation, and the Social Science and Humanities Research Council of Canada. Four working @@ -715,7 +571,7 @@ metalanguage and syntax issues. Each committee was charged with the task of identifying significant particularities in a range of texts, and two editors appointed to harmonize the resulting recommendations.

-

A first draft version (P1, with the P here and subsequently +

A first draft version (P1, with the P here and subsequently standing for Proposal) of the Guidelines was distributed in July 1990 under the title Guidelines for the Encoding and Interchange of Machine-Readable Texts. + -

Simple Analytic Mechanisms - -

This chapter describes a module for associating simple analyses and +

+ Simple Analytic Mechanisms +

This chapter describes a module for associating simple analyses and interpretations with text elements. We use the term analysis here to refer to any kind of semantic or syntactic interpretation which an encoder wishes to attach to all or @@ -20,14 +14,14 @@ structure (such as theme, reconciliation etc.). The mechanisms presented in this chapter are simpler but less powerful than those described in chapter .

-

Section introduces elements which can be used +

Section introduces elements which can be used to characterize text segments according to the familiar linguistic categories of sentence or s-unit, clause, phrase, word, morpheme, character, and punctuation mark. These elements represent special cases of the generic seg element described in section .

-

Section introduces an additional global +

Section introduces an additional global attribute which allows passages of text to be associated with specialized elements representing their interpretation. These interpretative elements (span and @@ -39,42 +33,41 @@ however, with XML attributes and their values, which are similar in concept but distinct in their formal definitions. each such pair being linked to one or more stretches of text, either directly, in the case of spans, or indirectly, in the case of interpretations.

-

Finally section revisits the topic of linguistic +

Finally section revisits the topic of linguistic analysis, and illustrates how these interpretative mechanisms may be used to associate simple linguistic analysis with text segments.

- -
Linguistic Segment Categories -

In this section we introduce specialized linguistic segment +

+ Linguistic Segment Categories +

In this section we introduce specialized linguistic segment category elements which may be used to represent the segmentation of a text into the traditional linguistic categories of sentence, clause, phrase, word, morpheme, characters, and punctuation marks.

-
Words and Above -

Although different languages have very different rules about what +

+ Words and Above +

Although different languages have very different rules about what constitutes a word or a sentence, these remain generally useful concepts. In this section we discuss elements provided for marking up linguistic units down to the word level, however defined. - - +

-

As members of the att.segLike class, these +

As members of the att.segLike class, these elements all share the following attribute: They also share attributes from att.typed:

-

These elements are also all members of the model.segLike class, which is a subclass of +

These elements are also all members of the model.segLike class, which is a subclass of model.phrase. They may thus appear anywhere that text is permitted within a document, when the module defined by this chapter is included in a schema.

- -

The w and pc elements belong to the att.linguistic class, which supplies +

The w and pc elements belong to the att.linguistic class, which supplies attributes that may be used for lightweight linguistic annotation (see section below):

-

Additionally, these elements also have access to the att.lexicographic.normalized class, +

Additionally, these elements also have access to the att.lexicographic.normalized class, which supplies the attributes norm and orig: the former for handling normalization/regularization at the word level, the latter providing the original form if the element content is modernized or regularized. Note that these attributes are a local (word-level) alternative @@ -85,20 +78,16 @@ handle a subset of normalizations in linguistic contexts where a single sequence in historical corpora subject to linguistic analysis. It needs to be stressed that the simplified attribute-based mechanism is not meant to be used for editorial interventions. The att.lexicographic.normalized class is also used in dictionary -entries, as discussed in chapter .

- -

The s element may be used simply to segment a text +entries, as discussed in chapter .

+

The s element may be used simply to segment a text end-to-end into a series of non-overlapping segments, referred to here and elsewhere as s-units, or sentences. -

- Nineteen fifty-four, when I was eighteen years old, +

Nineteen fifty-four, when I was eighteen years old, is held to be a crucial turning point in the history of the Afro-American — for the U.S.A. as a whole — the - year segregation was outlawed by the U.S. Supreme Court. - It was also a crucial year for me because on June 18, + year segregation was outlawed by the U.S. Supreme Court.It was also a crucial year for me because on June 18, 1954, I began serving a sentence in state prison for - possession of marijuana. -

+ possession of marijuana.

The s element is more restricted both in its content and its usage than the generic seg element. The seg unit may @@ -119,58 +108,36 @@ type="s-unit", seg type="clause" and seg type="phrase", respectively, but with the above-mentioned restrictions.

-

The s element may be further subdivided into +

The s element may be further subdivided into clauses, marked with the cl element, as in the following example: -

- - It was about the beginning of September, 1664, +

It was about the beginning of September, 1664, that I, among the rest of my neighbours, heard in ordinary discourse - that the plague was returned again to Holland; - for it had been very violent there, and particularly at - Amsterdam and Rotterdam, in the year 1663, - whither, they say, it was brought, + that the plague was returned again to Holland; for it had been very violent there, and particularly at + Amsterdam and Rotterdam, in the year 1663, whither, they say, it was brought, some said from Italy, others from the Levant, among some goods - which were brought home by their Turkey fleet; - others said it was brought from Candia; - others from Cyprus. - - - It mattered not from whence it came; - but all agreed it was come into Holland again. - -

+ which were brought home by their Turkey fleet; others said it was brought from Candia; + others from Cyprus. It mattered not from whence it came; but all agreed it was come into Holland again.

-

Clauses may be further divided into phr elements in the same +

Clauses may be further divided into phr elements in the same way. A text may be segmented directly into clauses, or into phrases, with no need to include segmentation at a higher level as well.

-

For verse texts, the overlapping of metrical and syntactic structure +

For verse texts, the overlapping of metrical and syntactic structure requires that special care be given to representing both using an element hierarchy. One simple approach is to split the syntactic phrases into fragments when they cross verse boundaries, reuniting them with the part attribute: -

- Tweedledum and Tweedledee - Agreed to have a battle; - For Tweedledum said Tweedledee - Had spoiled his nice new rattle.
-
- Just then flew down a monstrous crow, - As black as a tar barrel; - Which frightened both the heroes so, - They quite forgot their quarrel.
+
Tweedledum and TweedledeeAgreed to have a battle;For Tweedledum said TweedledeeHad spoiled his nice new rattle.
Just then flew down a monstrous crow,As black as a tar barrel;Which frightened both the heroes so,They quite forgot their quarrel.
 Another approach is to use the next and prev attributes defined in the additional module for linking (chapter ): For Tweedledum said - Tweedledee - - Had spoiled his nice new rattle. + TweedledeeHad spoiled his nice new rattle. Other methods are also possible; for discussion, see chapter .

-

The type attribute on linguistic segment categories can +

The type attribute on linguistic segment categories can be used to provide additional interpretative information about the category. The function attribute on the cl and phr elements can be used to provide additional information @@ -181,7 +148,7 @@ documented in the segmentation element of the A general approach to the encoding of linguistic categories for parts of a text is discussed in section below.

-

Using traditional terminology, these attributes provide a convenient +

Using traditional terminology, these attributes provide a convenient way of specifying, for example, that the clause from whence it came is a relative clause modifying another, or that the phrase by the U.S. Supreme Court is a prepositional @@ -189,27 +156,17 @@ post-modifier: It mattered not from whence it came; -the year segregation -was outlawed -by the U.S. Supreme Court. +the year segregationwas outlawedby the U.S. Supreme Court.

-

Segmentation into clauses and phrases can, of course, be combined. +

Segmentation into clauses and phrases can, of course, be combined. Such detailed encodings as the following may require careful formatting if they are to be easily readable however. -

- - - Nineteen fifty-four, +

Nineteen fifty-four, when I was eighteen years old , - - is held - - - to be - a crucial turning point + is heldto bea crucial turning point in the history of the Afro-American @@ -224,35 +181,22 @@ formatting if they are to be easily readable however. — the year - - segregation - - was outlawed - by the U.S. Supreme Court - . - - - It - - was + segregationwas outlawedby the U.S. Supreme Court.Itwas also a crucial year for me - - because + because on June 18, 1954, I - - began serving - a sentence in state prison + began servinga sentence in state prison for possession of marijuana .

-

This style of markup may introduce spurious new lines and blanks +

This style of markup may introduce spurious new lines and blanks into the text. If the original layout is important, it should be explicitly encoded, using such facilities as the lb element, the global rend or rendition attributes, etc.

- -

The w, m, and c elements are identical + +

The w, m, and c elements are identical in meaning to the seg element with a type attribute of w, m, or c respectively, and may occur wherever seg is permitted to occur. However, their @@ -267,7 +211,7 @@ character. Consequently, while these more specific elements can be translated directly into typed seg elements, the reverse is not necessarily the case.

-

The restriction on the content of the w element in +

The restriction on the content of the w element in particular requires that a certain care must be exercised when using it, especially in relation to the use of other tags that one may think of as word level, but which are in fact defined as phrase @@ -277,35 +221,24 @@ level. Consider the problem of segmenting an occurrence of the The first of the following two encodings is legitimate; the second is not, since the mentioned element is not part of the content model of the w element: - -grandiloquent +grandiloquent grandiloquent

-

On the other hand, both of the following encodings are +

On the other hand, both of the following encodings are legitimate: - - grandiloquent speech - - - grandiloquent speech - +grandiloquent speech +grandiloquent speech The first encoding describes the citing of a phrase. The second describes a phrase which consists of something mentioned.

-

The w element carries additional attributes +

The w element carries additional attributes which may be of use in many indexing or analytic applications. The lemma attribute may be used to specify the lemma, that is the head- or uninflected form of an inflected verb or noun, for example: - - timeo - Danaos - et - dona - ferentes - +timeoDanaosetdonaferentes

-

In some situations it may be more convenient to use the +

In some situations it may be more convenient to use the lemmaRef pointer attribute than to supply an explicit uninflected form. This attribute assumes the existence of a list of uninflected forms, for example in an online lexicon, with which @@ -314,53 +247,34 @@ pointer mechanisms. Assuming that a standardized lexicon for Latin is available at the location http://lexicon.org/latin.xml, we might for example revise the above example as: - - timeo - Danaos - -

-
- -
Below the Word Level -

It is sometimes helpful to markup explicitly sub-word components +timeoDanaos

+
+
+ Below the Word Level +

It is sometimes helpful to markup explicitly sub-word components such as morphemes, characters, or punctuation. - - +

- -

The m element is used to mark up morphologically +

The m element is used to mark up morphologically identified segmentation below the word level. Analogous to the lemma attribute for w, there is a baseForm attribute for the m element, which may be used to indicate the base form of an inflected morpheme; where appropriate, m elements may also be organized hierarchically: - - - com - fort - - able - +comfortable

-

The distinction between m and w is provided as a +

The distinction between m and w is provided as a convenience only; it may not be appropriate for all linguistic theories, nor is it meaningful in all languages. The intention is to provide a means for those cases where it is considered helpful to distinguish lexical from sub-lexical tokens, to complement the more general mechanism already provided by the seg element, using which the above example could alternatively be marked up as follows: - - - com - fort - - able - +comfortable See section for an alternative to using type in such contexts.

- -

There is a substantial +

There is a substantial linguistic difference between characters like letters or diacritics and punctuation marks. The former are used to construct meaningful units like morphemes or words. The latter are @@ -368,36 +282,18 @@ functionally independent units acting at the level of syntactic units. A word may consist of a single letter (for example I in English), but this does not mean that we should use c instead of w to mark it up.

- -

The c (character) element should be used to mark up any non-lexical +

The c (character) element should be used to mark up any non-lexical character, whether this appears within a word, or outside it. In the following example, the encoder wishes to indicate that the letters are not to be regarded as words: - - - M - O - A - I - doth - sway - my - life - - + MOAIdothswaymylife

-

The c element may be used for +

The c element may be used for individual characters occurring within a w or m element which it is desired to distinguish for some reason, as in the following examples: - - - n - ' - t - - + n't This encoding represents the constituents of a common abbreviation, but does not indicate that it is in fact an abbreviation; the am element () may be preferred for the @@ -405,8 +301,7 @@ latter purpose. Generally speaking, the use of c use to mark non-lexical punctuation marks is deprecated, since the pc element is provided specifically to distinguish these.

- -

The pc (punctuation character) element should be used to mark up +

The pc (punctuation character) element should be used to mark up characters which are specifically regarded as providing punctuation, rather than constituting parts of a word. It may be particularly useful when transcribing older written materials, in which an encoding @@ -414,9 +309,7 @@ of the original punctuation may be useful for interpretive or analytic purposes, in much the same way as an encoding of the original orthography may be. For example, in the following extract from a Bodleian Library musical manuscript -

- -
+
two different punctuation marks are used to distinguish kinds of pause in the text. The punctus elevatus (which resembles an inverted semicolon) is not a Unicode character, but may still be encoded using @@ -426,12 +319,10 @@ character which may be stored either locally or elsewhere. ; natus est in bethlehem .o . mira gratia... - - - +

-

The pc element carries special attributes to record +

The pc element carries special attributes to record analyses of the functional behaviour or classification of the punctuation mark it contains. The unit attribute may be used, as on the milestone element to name the kind of unit @@ -440,15 +331,12 @@ section. The pre attribute may be used to indicate whether the punctuation precedes or follows the unit it delimits. The force attribute indicates the strength of the association between the punctuation mark and its adjacent word.

-

In the following example, the paragraph marker (¶) has been tagged +

In the following example, the paragraph marker (¶) has been tagged as a strong punctuation mark, preceding the unit it marks, which is named para: - -

Incipit...

- +

Incipit...

- -

A similar encoding can be used for hyphenation: +

A similar encoding can be used for hyphenation: A fire-proof vest is recom- mended. @@ -456,23 +344,14 @@ mended. Refer to for a discussion of the motivations for explicitely recording the presence of hyphens.

- - -

The w, m, c, and pc elements can be used +

The w, m, c, and pc elements can be used together to give a fairly detailed low-level grammatical analysis of text. For example, consider the following segmentation of the English S-unit I didn't do it. -I - - did - n't - -do -it -. +Ididn'tdoit.

-

This segmentation, crude as it is, succeeds in representing the idea +

This segmentation, crude as it is, succeeds in representing the idea that did occurring as a morphological component of the word didn't has something in common with the word do. A further advantage of segmenting the text down @@ -481,25 +360,24 @@ such segment with a more detailed formal analysis, for example by providing a baseform, or morphological analysis at whichever level is appropriate. This matter is taken up in detail in section .

- - - - - - - - - - - - - - - -
-
-
Global Attributes for Simple Analyses -

When the module described by this chapter is selected, an + + + + + + + + + + + + + +

+
+
+ Global Attributes for Simple Analyses +

When the module described by this chapter is selected, an additional attribute is defined for all elements: The ana attribute may be specified for any element. @@ -511,17 +389,18 @@ see section or fs, on which see chapter . If a hierarchical form of classification is desired then it may point to category element at a suitable level in a taxonomy see .

- - + + -
-
Spans and Interpretations -

The simplest mechanisms for attaching analytic notes in some +

+
+ Spans and Interpretations +

The simplest mechanisms for attaching analytic notes in some structured vocabulary to particular passages of text are provided by the span and interp elements, and their associated grouping elements spanGrp and interpGrp.

- -

These elements are all members of the class att.interpLike, and thus share the following attribute: +

These elements are all members of the class att.interpLike, and thus share the following attribute: They also inherit the following attributes from att.global.responsibility: - - +

-

The type attribute of the +

The type attribute of the span and interp elements may be used to indicate that the annotations are of specific types, for example thematic or structural. The annotation itself is supplied as the content of the @@ -560,74 +438,53 @@ In the case of interp (see below), the span is indicated by a pointer from a link element or some similar mechanism. The resp attribute indicates the annotator responsible for this annotation.

-

The span element provides a simple way of indicating such +

The span element provides a simple way of indicating such features as phrasal verbs in a linguistic analysis, as in this example: - -Whatdidyoumakeup -phrasal verb "make up" - +Whatdidyoumakeupphrasal verb "make up" Here the two components of the span follow each other, so the to and from attributes may be used. The same effect could however be achieved by using the target attribute: - -Whatdidyoumakeup -phrasal verb "make up" - +Whatdidyoumakeupphrasal verb "make up" This second approach might be cumbersome if the number of components to be combined is very large. It is however essential if the components do not follow each other, as in this example: - -Didyoumakeitup -phrasal verb "make up" - +Didyoumakeitupphrasal verb "make up"

-

The span element can be used for any kind of +

The span element can be used for any kind of annotation. In this example it is used in a narratological analysis: -

-There was certainly a definite point at which the - thing began. -It was not; then it was suddenly inescapable, - and nothing could have frightened it away. -There was a slow integration, during which she, +

There was certainly a definite point at which the + thing began.It was not; then it was suddenly inescapable, + and nothing could have frightened it away.There was a slow integration, during which she, and the little animals, and the moving grasses, and the sun-warmed trees, and the slopes of shivering silvery mealies, and the great dome of blue light overhead, and the stones of earth under her feet, became one, shuddering together in a dissolution of dancing - atoms. -She felt the rivers under the ground forcing + atoms.She felt the rivers under the ground forcing themselves painfully along her veins, swelling them out in an unbearable pressure; her flesh was the earth, and suffered growth like a ferment; and her eyes stared, fixed like the eye of the - sun. -Not for one second longer (if the terms for time + sun.Not for one second longer (if the terms for time apply) could she have borne it; but then, with a sudden movement forwards and out, the whole process stopped; and that was the moment which it was impossible to remember - afterwards. -the moment -For during that space of time (which was + afterwards.the momentFor during that space of time (which was timeless) she understood quite finally her smallness, the - unimportance of humanity. -

+ unimportance of humanity.

-

The span element may, as in this example, be placed in the +

The span element may, as in this example, be placed in the text near the textual span it is associated with. Alternatively, it may be placed elsewhere in the same or a different document. Where several span or interp elements share the same attributes, for example having the same responsibility or type, it may be convenient to group them within a spanGrp or interpGrp element as follows: - - the moment - - +the moment

-

Spans may also be used to represent structural divisions within +

Spans may also be used to represent structural divisions within a narrative, particularly when these do not coincide with the structure implied by the element structure. Consider the following narrative: - -

Sigmund, the son of Volsung, was a king in Frankish country. +

Sigmund, the son of Volsung, was a king in Frankish country. Sinfiotli was the eldest of his sons, the second was Helgi, the third Hamund. Borghild, Sigmund's wife, had a brother named — @@ -647,64 +504,39 @@ everything happened as before. And a third time she brought him a horn, and reproachful words as well, if he didn't drink from it. He spoke again to Sigmund as before. He said Filter it through your mustache, son! Sinfiotli drank it off and at once fell dead. -

-

Sigmund carried him a long way in his arms and came to a long, +

Sigmund carried him a long way in his arms and came to a long, narrow fjord, and there was a small boat there and a man in it. He offered to ferry Sigmund over the fjord. But when Sigmund carried the body out to the boat, it was fully laden. The man said Sigmund should go around the fjord inland. The man pushed the boat out and then suddenly vanished. -

-

King Sigmund lived a long time in Denmark in the kingdom of +

King Sigmund lived a long time in Denmark in the kingdom of Borghild, after he married her. Then he went south to Frankish lands, to the kingdom he had there. Then he married Hiordis, the daughter of King Eylimi. Their son was Sigurd. King Sigmund fell in a battle with the sons of Hunding. And then Hiordis married Alf, the son of King Hialprec. Sigurd grew up there as a boy. -

-

Sigmund and all his sons were tall and outstanding in their +

Sigmund and all his sons were tall and outstanding in their strength, their growth, their intelligence, and their accomplishments. But Sigurd was the most outstanding of all, and everyone who knows about the old days says he was the most outstanding of men and the noblest of all the warrior kings.

-

A structural analysis of this text, dividing it into narrative units +

A structural analysis of this text, dividing it into narrative units in a pattern shared with other texts from the same literature, might look like this: -

-Sigmund ... was a king in Frankish country. -Sinfiotli was the eldest of his sons. -Borghild, Sigmund's wife, had a brother ... -But Sinfiotli ... wooed the same woman -and Sinfiotli killed him over it. -And when he came home, ... she was obliged to accept it. -At the funeral feast Borghild was serving beer. -She took poison ... and brought it to Sinfiotli. -Sinfiotli drank it off and at once fell dead. - +

Sigmund ... was a king in Frankish country.Sinfiotli was the eldest of his sons.Borghild, Sigmund's wife, had a brother ...But Sinfiotli ... wooed the same womanand Sinfiotli killed him over it.And when he came home, ... she was obliged to accept it.At the funeral feast Borghild was serving beer.She took poison ... and brought it to Sinfiotli.Sinfiotli drank it off and at once fell dead.

Sigmund carried him a long way in his arms ...

King Sigmund lived a long time in Denmark ...

Sigmund and all his sons were tall ...

introductionconflictclimaxrevengereconciliationaftermath

-

Sigmund carried him a long way in his arms ...

-

King Sigmund lived a long time in Denmark ...

-

Sigmund and all his sons were tall ...

- - introduction - conflict - climax - revenge - reconciliation - aftermath - -

-

Note the use of an empty anchor element to provide a target for +

Note the use of an empty anchor element to provide a target for the reconciliation unit which is normally part of the narrative pattern but which is not realized in the text shown.

- -

The same analysis may be expressed with the interp element +

The same analysis may be expressed with the interp element instead of the span element; this element provides attributes for recording an interpretive category and its value, as well as the identity of the interpreter, but does not itself indicate which passage @@ -717,77 +549,36 @@ pointing at both text and interpretation from a link element, as described in chapter .

-

To encode the first example above using interp, it is +

To encode the first example above using interp, it is necessary to create a text element which contains—or corresponds to—the third, fourth, and fifth orthographic sentences (S-units) in the paragraph. This can be done either with the seg element, described in , or the join element, described in . The resulting element can then be associated with the interp element using the ana attribute described in section . We illustrate using the seg element. -

-There was certainly a definite point ... -It was not; then it was suddenly inescapable ... - -There was a slow integration ... -She felt the rivers under the ground ... -Not for one second longer ... - -For during that space of time ... -

-the moment +

There was certainly a definite point ... It was not; then it was suddenly inescapable ... There was a slow integration ... She felt the rivers under the ground ... Not for one second longer ... For during that space of time ...

the moment

-

The second example above can be recoded using interp and +

The second example above can be recoded using interp and interpGrp tags in a similar manner. The interpretation itself can be expressed in an interpGrp element, which would replace the spanGrp in the example shown above: - - introduction - conflict - climax - revenge - reconciliation - aftermath - +introductionconflictclimaxrevengereconciliationaftermath

-

Any of these interp elements may be linked to the text either +

Any of these interp elements may be linked to the text either by means of the ana attribute, or by means of link elements. Using the ana attribute (on seg elements introduced specifically for this purpose), the text would be encoded as follows: -

- -Sigmund ... was a king in Frankish country. -Sinfiotli was the eldest of his sons. -Borghild, Sigmund's wife, had a brother ... - -But Sinfiotli ... wooed the same woman -and Sinfiotli killed him over it. - -And when he came home, ... she was obliged to accept it. -At the funeral feast Borghild was serving beer. -Sinfiotli drank it off and at once fell dead. -

- -

Sigmund carried him a long way in his arms ...

-

King Sigmund lived a long time in Denmark ...

-

Sigmund and all his sons were tall ...

- +

Sigmund ... was a king in Frankish country.Sinfiotli was the eldest of his sons.Borghild, Sigmund's wife, had a brother ... But Sinfiotli ... wooed the same womanand Sinfiotli killed him over it.And when he came home, ... she was obliged to accept it.At the funeral feast Borghild was serving beer.Sinfiotli drank it off and at once fell dead.

Sigmund carried him a long way in his arms ...

King Sigmund lived a long time in Denmark ...

Sigmund and all his sons were tall ...

-

The linkage may also be accomplished using a linkGrp element, +

The linkage may also be accomplished using a linkGrp element, whose content is a set of link elements which point to each interpretive element and its corresponding text unit. This method does not require the use of the ana attribute on the text units. - - - - - - - - +

-

One obvious advantage of using interp rather than +

One obvious advantage of using interp rather than span elements for the Sigmund text is that the interp elements can be reused for marking up other texts in the same document, whereas the span elements cannot. - - +

-

Each linguistic segment so far discussed has been well-behaved with +

Each linguistic segment so far discussed has been well-behaved with respect to the basic document hierarchy, having only a single parent. Moreover, the segmentation has been complete, in that each part of the text is accounted for by some segment at each level of analysis, without @@ -1015,9 +721,10 @@ chapter ; also see . These mechanisms all depend to a greater or lesser degree on the use of pointing elements of various kinds.

-
-
Lightweight Linguistic Annotation -

While these Guidelines offer a variety of means to add linguistic information to textual +

+
+ Lightweight Linguistic Annotation +

While these Guidelines offer a variety of means to add linguistic information to textual units and much of that has been presented above, two kinds of use cases and two groups of users call for a dedicated set of specialized attributes to carry linguistic information. One relevant use case is where basic linguistic information gets added to an @@ -1029,13 +736,9 @@ devoted to careful literary analysis and hand-encoding of the relevant phenomena to the analysis of the completed resources, and therefore the phase of resource-building must be quick and relatively effortless, requiring minimal structural markup, well-established containers for grammatical information, and a standardized way of filling them in.

- -

The aims defined above can be realized by means of lightweight linguistic annotation using -attributes that belong to the att.linguistic class: - -

- -

The essence of lightweight linguistic annotation is that the basic grammatical information +

The aims defined above can be realized by means of lightweight linguistic annotation using +attributes that belong to the att.linguistic class:

+

The essence of lightweight linguistic annotation is that the basic grammatical information is encapsulated at the word level, together with the orthographic shape of the word. This has clear advantages for automatic processing but, on the other hand, this form of data encapsulation also imposes restrictions on the extent of information that can be encoded, @@ -1054,9 +757,8 @@ word forms, various repair strategies can be used (e.g., recursing w to multi-token compounds or using att.fragmentable to point at disjoint tokens). Beyond that, more robust TEI mechanisms, based on standoff principles and feature structures, should replace lightweight annotation.

- - -

The basic grammatical information encoded by means of + +

The basic grammatical information encoded by means of att.linguistic is sufficient for the purpose of enhancing queries or improving the analysis of search results by, for example, making it possible to distinguish between the noun cut and the identically spelled verb @@ -1071,8 +773,7 @@ base form (also called bare infinitive), so the value of lemma the verbal forms write, writes, wrote, written, and writing is typically write.

- -

Together with the span-delimiting elements mentioned in this section, such as s, +

Together with the span-delimiting elements mentioned in this section, such as s, cl, or phr, lightweight grammatical annotation may be used to build basic syntactic constituency structures, where hierarchical information is expressed through span containment rather than by relations among tree nodes. This is however the limit of @@ -1081,15 +782,13 @@ syntactic structures, one needs to turn to more robust mechanisms offered by the may involve graph description (see chapter ) or standoff techniques (see section ), and where grammatical labels may need to be annotated by means of feature structures (see chapter ).

- -

Some of the above-mentioned robust methods will also prove handy in cases where more than one tagset +

Some of the above-mentioned robust methods will also prove handy in cases where more than one tagset (label inventory) is used to label the words, or where automatic morphological analysis yields multiple possibilities (for example, the form cutting is morphologically ambiguous between verbal, adjectival, and nominal) and needs to be followed by (often also automatic) disambiguation in morphosyntactic contexts, with varying probabilities that may also need to be recorded together with their corresponding part-of-speech and morphosyntactic values.

- -

It should be borne in mind that tokenization, lemmatization, part-of-speech identification, and +

It should be borne in mind that tokenization, lemmatization, part-of-speech identification, and morphosyntactic labelling, especially when performed automatically, should in most cases be seen as involving pragmatic decisions, dictated by concrete practical goals, economy of description, or the demands of particular analytic and/or visualization tools. It comes therefore as no surprise that @@ -1108,17 +807,15 @@ Guidelines, but it has to be stressed that all the strategies adopted for lingui even at the lightweight level of complexity, must be documented in the header of the given electronic resource, not only for the purpose of guaranteeing successful data interpretation and exchange, but also for the sake of sustainability of the results of the given project.

- -

The last of the att.linguistic attributes, join, has the most text-technological +

The last of the att.linguistic attributes, join, has the most text-technological flavour. It can be used to amend the loss of whitespace-related information in non-inline -markup.

-

Compare the following two listings. The first difference between them is in the +markup.

+

Compare the following two listings. The first difference between them is in the tagset used (CLAWS-5 vs. CLAWS-7) and only serves to exemplify the need to document the choice of descriptive vocabulary in the header, lest the encoded information is unreadable or confusing. The second difference is the difference in the treatment of inter-token whitespace, and it is here that the join attribute proves indispensable.

- -

The first example listing uses CLAWS-5 and inline annotation, where whitespace serves as +

The first example listing uses CLAWS-5 and inline annotation, where whitespace serves as part of the markup: The victim's friends @@ -1126,115 +823,62 @@ part of the markup: drove into the quarry and never surfaced.

- -

In the second example, the attribute join is the only way to encode whether two +

In the second example, the attribute join is the only way to encode whether two tokens are adjacent or not: - -The -victim -'s -friends -told -police -that -Kruger -drove -into -the -quarry -and -never -surfaced -.

-

Note that projects will need to decide whether they want to redundantly encode full +Thevictim'sfriendstoldpolicethatKrugerdroveintothequarryandneversurfaced.

+

Note that projects will need to decide whether they want to redundantly encode full information on the adjacency of each token (in which case, the above listing should also have join with the value right on the tokens victim and surfaced, or whether information on a single direction of adjacency is enough. Strategies vary, and it is important to document them in the TEI header.

-

The following example shows a German sentence Wir fahren in den +

The following example shows a German sentence Wir fahren in den Urlaub (We're going on vacation) annotated with all the attributes discussed -above.The annotation values have been adapted from the CLARIN Weblicht service, +above.The annotation values have been adapted from the CLARIN Weblicht service, where e.g. the full morphosyntactic description of the first item reads: [cat pronoun, personal true, substituting true, person 1, case nominative, number plural], and has been mapped from a sequence of attribute-value pairs suitable for feature structure notation, into a compressed form that fits inside a single attribute value. - -Wir -fahren -in -den -Urlaub -. - - +WirfahrenindenUrlaub.

-

The final examples lay out a strategy for dealing with e.g. historical corpora where it is on +

The final examples lay out a strategy for dealing with e.g. historical corpora where it is on the one hand important to maintain a steady stream of token-level elements (w and pc) for efficient processing, but, on the other hand, it is also important to either record the original spelling (when the corpus text is normalized) or to record the normalized variants (when the element content of the corpus preserves the original spelling). The attribute class att.lexicographic.normalized can be used for that purpose:

-

The first fragment below comes from "Gottfried, Newe Welt Vnd Americanische Historien. Frankfurt/M., 1631" +

The first fragment below comes from "Gottfried, Newe Welt Vnd Americanische Historien. Frankfurt/M., 1631" encoded in the Deutsches Textarchiv and records normalized forms in the norm attribute. - - vnuermuthete - Freundſchafft - angebotten -

-

The following example comes from the EarlyPrint project and uses the attribute orig to + vnuermutheteFreundſchafftangebotten

+

The following example comes from the EarlyPrint project and uses the attribute orig to record the original spelling (note that the xml:id attributes have been removed for the sake of readability). - - he - hath - brought - forth -

-
-
Spoken Text -

The mechanisms proposed in this chapter may also be used to encode + hehathbroughtforth

+
+
+ Spoken Text +

The mechanisms proposed in this chapter may also be used to encode analyses of an entirely different kind, for example discourse function. Here is an application of the span technique to record details of a sales transaction in a spoken text. -Can I have ten oranges and a kilo of bananas please? -Yes, anything else? -No thanks. -That'll be dollar forty. -Two dollars -Sixty, eighty, two dollars. Thank you. - - sale request - sale compliance - sale - purchase - purchase closure - +Can I have ten oranges and a kilo of bananas please?Yes, anything else?No thanks.That'll be dollar forty.Two dollarsSixty, eighty, two dollars. Thank you.sale requestsale compliancesalepurchasepurchase closure For further discussion of the u (utterance) element and other elements recommended for transcriptions of spoken language, see chapter . -

-
-
- Module for Analysis and Interpretation -

The module described in this chapter makes available the +

+
+
+
+ Module for Analysis and Interpretation +

The module described in this chapter makes available the following components: - - Analysis and Interpretation - Simple analytic mechanisms - Mécanismes analytiques simples - 簡易分析機制 - Semplici meccanismi di analisi - Mecanismos simples de análise - 分析モジュール - + Analysis and InterpretationSimple analytic mechanismsMécanismes analytiques simples簡易分析機制Semplici meccanismi di analisiMecanismos simples de análise分析モジュール The selection and combination of modules to form a TEI schema is described in .

-
+
diff --git a/P5/Source/Guidelines/en/BIB-Bibliography.xml b/P5/Source/Guidelines/en/BIB-Bibliography.xml index 14d10b349b..0283d2c559 100644 --- a/P5/Source/Guidelines/en/BIB-Bibliography.xml +++ b/P5/Source/Guidelines/en/BIB-Bibliography.xml @@ -1,88 +1,61 @@ - + + +
Bibliography
Works Cited in Examples in these Guidelines - 阿城，《棋王》。 Académie française, - Rectifications de l'orthographe - J.O. du 06-12-1990, En ligne, + Rectifications de l'orthographe - J.O. du 06-12-1990, En ligne, consulté le 05-03-2010. - - Adams, Douglas. The Hitchhiker's Guide to the + <bibl xml:id="DROTH-eg-57"><author>Adams, Douglas</author>. <title level="m">The Hitchhiker's Guide to the Galaxy, New York: Pocket Books, 1979, chapter 31. Agence bibliographique de l'enseignement - supérieur, ABES:Site internet + supérieur, ABES:Site internet par l'ABES,consulté le 05-03-2010. 阿拉伯短劍，國史館：嚴家淦總統文物。 Alighieri, Dante. Doglia mi - reca ne lo core ardire, Rime, XLIX. + reca ne lo core ardire, Rime, XLIX. Allinson, E.P. and B. Penrose. - Philadelphia 1681-1887 (1887), p. 138. + Philadelphia 1681-1887 (1887), p. 138. American National Standard for Bibliographic References, ANSI Z39.29-1977, New York: American National Standards Institute (1977). - - - - Andersson, Theodore M.. A Preface to the Nibelungenlied, + Andersson, Theodore M.. A Preface to the Nibelungenlied, Stanford University Press (1987). - - Andrews, Mr.. Song, Chambers's - Edinburgh Journal Series 1 - 9:463 (12 - December 1840), 376. + Andrews, Mr.. Song, Chambers's + Edinburgh Journal Series 19:463 (12 + December 1840), 376. Anouilh, Jean, Antigone, 1842. - - [As in Visions of] Single leaf of Notes for a poem about night "visions," + [As in Visions of] Single leaf of Notes for a poem about night "visions," possibly related to the untitled 1855 poem that Whitman eventually titled "The Sleepers." Fragments of an unidentified newspaper clipping about the Puget Sound area have been pasted to the leaf. The Trent Collection of Walt Whitman Manuscripts, Duke University Rare Book, - Manuscript, and Special Collections Library. + Manuscript, and Special Collections Library. - - Atkins et al. - Collins Robert French-English English-French Dictionary. + Atkins et al. Collins Robert French-English English-French Dictionary. London: Collins (1978). - - Atkinson, J. Maxwell and John Heritage. Structures of social action: Studies in conversation analysis, + Atkinson, J. Maxwell and John Heritage. Structures of social action: Studies in conversation analysis, Cambridge and Paris: Cambridge University Press, Editions de la Maison des Sciences de l'Homme (1984), ix-xvi. Austen, Jane. Pride and Prejudice. (1813), chapter 1. - - 白先勇，〈金大班的最後一夜〉，《台北人》。 白先勇，《孽子》。 白居易，《憶江南》。 - - Amheida I: Ostraka from Trimithis Volume 1: Texts from the 2004–2007 Seasons, + Amheida I: Ostraka from Trimithis Volume 1: Texts from the 2004–2007 Seasons, Bagnall, R. S. and G. R. Ruffini, with contributions by R. Cribiore and G. Vittmann (2012). - - Baker, James K.. Night in Tarras. In Hilltop: A Literary Paper, vol 1 no 2. Wellington: Victoria University College + Baker, James K.. Night in Tarras. In Hilltop: A Literary Paper, vol 1 no 2. Wellington: Victoria University College Literary Society. (1949). Balzac, Honoré de, Les Chouans, 1845. @@ -92,22 +65,17 @@ $Id$ vie conjugale, 1850. Barbauld, Lucy Aikin. The Works of Anna Laetitia Barbauld (1826). - - Barker, Jane. The Lining to the Patch-Work Screen + Barker, Jane. The Lining to the Patch-Work Screen (1726). - - Base de datos paleográfica da lírica galego-portuguesa (PalMed). Versión 1.2. + Base de datos paleográfica da lírica galego-portuguesa (PalMed). Versión 1.2. Santiago de Compostela: Centro Ramón Piñeiro para a Investigación en Humanidades. . f. B126r, column a, l. 21-32. Bataille, Michel , L'Arbre de Noël, 1967. - - Les Chats, in : Baudelaire, Charles, Les Fleurs du mal, 1861. - - La Vie antérieure, in : Baudelaire, Charles, + Les Chats, in : Baudelaire, Charles, Les Fleurs du mal, 1861. + La Vie antérieure, in : Baudelaire, Charles, Les Fleurs du mal, 1861. 電影《霸王別姬》，1993年。 Beck, Béatrice, Léon @@ -125,83 +93,59 @@ $Id$ <author>Bowers, Jack</author> <title>Mixtepec-Mixtec Project Personography - + - - Beerbohm, Max. Autograph manuscript of The Golden Drugget, + Beerbohm, Max. Autograph manuscript of The Golden Drugget, Pierpont Morgan MA 3391. in 123. Behn, Aphra. The Rover, (1697). - - Beeton, Isabella. The book of Household Management, + Beeton, Isabella. The book of Household Management, London: S.O. Beeton (1861). Belloc, Denis , Képas, 1989. - - Belloc, Denis , Néons, 1987. + Belloc, Denis , Néons, 1987. Bentham, Jeremy. The Book of Fallacies. (1824). - - Beowulf and The fight at Finnsburg; edited, with introduction, bibliography, + Beowulf and The fight at Finnsburg; edited, with introduction, bibliography, notes, glossary, and appendices, by Fr. Klaeber. Boston, New York - [etc.] - D.C. Heath & Co. (1922). - - Bibliographie dans le cadre de la semaine italienne du 11 au 18 mars 2006, , - document électronique. + [etc.] D.C. Heath & Co. (1922). + Bibliographie dans le cadre de la semaine italienne du 11 au 18 mars 2006, , + document électronique. Bibliothèque nationale de France, Projet de description des reliures remarquables de la Réserve des livres rares selon le modèle de la TEI manuscrits. Billetdoux, Marie, Un peu de désir sinon je meurs, 2006. - - Blake, William. London, in Songs + <bibl xml:id="VE-eg-04"><author>Blake, William</author>. <title level="a">London, in Songs of Experience (1791). - - Blake, William. The Sick Rose, in Songs of Experience (1794). - - Blake, William. The Tyger, in Songs of Experience (1794). + Blake, William. The Sick Rose, in Songs of Experience (1794). + Blake, William. The Tyger, in Songs of Experience (1794). Bloomfield, Leonard. Literate and - Illiterate Speech, American Speech, 2, (1927), pp. + Illiterate Speech, American Speech, 2, (1927), pp. 432-441. Borges, Jorge Luis, tr. R. Simms. The Analytical Language of John Wilkins. In - Emir Rodriguez Monegal and Alistair Reid, eds. Borges: A reader, Dutton Adult + Emir Rodriguez Monegal and Alistair Reid, eds. Borges: A reader, Dutton Adult (1981), p.141. Borges, Jorge Luis. Avatars of - the Tortoise In James E. Irby tr. Labyrinths: Selected Stories and Other Writings, New York: - New Directions, (1962), pp.202-203. + the Tortoise In James E. Irby tr. Labyrinths: Selected Stories and Other Writings, New York: + New Directions, (1962), pp.202-203. Bouillier, Grégoire, Rapport sur moi, 2002. - Bresson, Robert, Mouchette : script, l'Avant-scène cinéma, + Bresson, Robert, Mouchette : script, l'Avant-scène cinéma, n° 80, avril 1968. - Extract from British National Corpus () Text KB7, sentence 13730. - - Brontë, Charlotte. Jane Eyre: An Autobiography, - Third edition; reprintLondon - Service & Paton, 1897; + Extract from British National Corpus () Text KB7, sentence 13730. + Brontë, Charlotte. Jane Eyre: An Autobiography, + Third edition; reprintLondonService & Paton, 1897; Project Gutenberg, 1 December 2020. chapter XII. - - - - Browning, Robert. Letter to George Moulton-Barrett, Pierpont + + Browning, Robert. Letter to George Moulton-Barrett, Pierpont Morgan MA 310, ( 23). Buirette de Belloy, Pierre Laurent, Gabrielle de Vergy, 1777. - - Bunyan, John. The Pilgrim's Progress from this world to that which + <bibl xml:id="DS-eg-06"><author>Bunyan, John</author>. <title>The Pilgrim's Progress from this world to that which is to come..., London (1678). Burgess, Anthony. A Clockwork Orange. (1962), opening. @@ -211,15 +155,11 @@ $Id$ Horwood Ltd, Ellis Horwood Series in Computers and Their Applications, (1987), p. 54. Burnard, Lou, - Sperberg-McQueen, C. M., - <ref target="http://www.gutenberg.eu.org/publications/autres/TEILITE/">La TEI simplifiée, + <author>Sperberg-McQueen, C. M.</author>, <title><ref target="http://www.gutenberg.eu.org/publications/autres/TEILITE/">La TEI simplifiée, une introduction au codage des textes électroniques en vue de leur échange -- version de - travail </ref> - , 1996. - - Burton, Robert. Anatomy of Melancholy - (1621), 16th ed. reprinted 1846, p. 743. + travail , 1996. + Burton, Robert. Anatomy of Melancholy + (1621), 16th ed. reprinted 1846, p. 743. Butler, Samuel. The Way of All Flesh (1903), chapter 37. Byron, George Gordon. Don Juan @@ -227,39 +167,32 @@ $Id$ Byron, George Gordon. Vision of Judgment In E.H. Coleridge ed. The Poetical Works of Lord Byron, viii, 1922. - - C 60/16 Fine Roll 6 HENRY III (28 October 1221-27 October 1222), membrane 5, entry 154. CBETA Cædmon's Hymn in Bede's Historia Ecclesiastica (MS Kk. 5. 16, Cambridge, University Library). - - Cabaret. A musical play, with book by Joe Masteroff, lyrics by Fred Ebb, and + Cabaret. A musical play, with book by Joe Masteroff, lyrics by Fred Ebb, and music by John Kaner. Based on the play by John van Druten and stories by Christopher Isherwood. 1966 Edward Barkley, describing how Essex drove the Irish from the plains into the woods to freeze or famish in winter; quoted by Canny, Nicholas P. The Ideology of English Colonization: From Ireland to America. In - Stanley N. Katz and John M. Murrin eds. Colonial America: Essays in Politics and Social Development, 3d + Stanley N. Katz and John M. Murrin eds. Colonial America: Essays in Politics and Social Development, 3d ed - New York: Knopf, (1983), p.53. - - Carroll, Lewis. Through the Looking Glass, and what Alice + <bibl xml:id="AI-BIBL-3"><author>Carroll, Lewis</author>. <title level="m">Through the Looking Glass, and what Alice found there. (1871). Catéchisme de l'Eglise catholique, 1968. - - Cavendish, Margaret. Nature's Pictures. + Cavendish, Margaret. Nature's Pictures. London, 1656. Women Writers Online. Women Writers Project, Northeastern University. 29 Mar. 2015 - - Chaucer, Geoffrey. Canterbury Tales, f52r, in Holkham MS. - - Chaucer, Geoffrey. The Tale of Sir Topas, The Canterbury Tales, In F. N. Robinson ed. The Works of Geoffrey Chaucer, 2nd edition + Chaucer, Geoffrey. Canterbury Tales, f52r, in Holkham MS. + Chaucer, Geoffrey. The Tale of Sir Topas, The Canterbury Tales, In F. N. Robinson ed. The Works of Geoffrey Chaucer, 2nd edition Boston: Houghton Mifflin Co., 1957. 陳政彥，〈戰後臺灣現代詩論戰史研究〉，2007。 - - Cholières, Nicolas de, La Forest Nuptiale + Cholières, Nicolas de, La Forest Nuptiale (1600). - - Chomsky, Noam and Morris Halle. The Sound Pattern - of English. New York: Harper & Row (1968), p. 415. - Claude Simon - Le jardin des plantes, 1997, p 284 - - Cleaver, Eldridge. Soul on Ice. New + Chomsky, Noam and Morris Halle. The Sound Pattern + of English. New York: Harper & Row (1968), p. 415. + Claude SimonLe jardin des plantes, 1997, p 284 + Cleaver, Eldridge. Soul on Ice. New York (1968). - - Cloud of Unknowing In Hodgson, Phyllis ed. The Cloud of Unknowing and The Book of Privy Counselling, + Cloud of Unknowing In Hodgson, Phyllis ed. The Cloud of Unknowing and The Book of Privy Counselling, London: Oxford University Press, Early English Text Society, 218, (1944). Clover, Carol J.The Medieval Saga, Ithaca: Cornell University Press (1982). - - Cocteau, Jean. La Machine Infernale. + Cocteau, Jean. La Machine Infernale. Coleridge, Samuel Taylor. The Rime of the Ancient Mariner. In Wordsworth, William and Samuel Taylor Coleridge. Lyrical Ballads @@ -330,22 +248,14 @@ $Id$ Press, (1967), p.240. Colette, Colette à l'école, 1900. - - Collins English Dictionary, 12th edition - Glasgow: Collins + Collins English Dictionary, 12th editionGlasgow: Collins (2014). - - Collins Pocket Dictionary of the English language. + Collins Pocket Dictionary of the English language. London: Collins. - - Collins, Wilkie. The Moonstone, + Collins, Wilkie. The Moonstone, Penguin, 6th narrative. - - Comenius, John Amos. Orbis Pictus: a facsimile of the - first English edition of 1659 (ed. John - E. - Sadler - ) Oxford University Press (1968). + Comenius, John Amos. Orbis Pictus: a facsimile of the + first English edition of 1659 (ed. JohnE.Sadler) Oxford University Press (1968). Cope, Thomas Pym. Philadelphia merchant: the diary of Thomas P. Cope, 1800-1851, Eliza Cope Harrison ed. @@ -354,62 +264,44 @@ $Id$ Corneille, Pierre, Théodore, vierge et martyre : tragédie chrétienne, 1646. - - Cowley, Hannah. The Runaway (1813). - - Crashaw, Richard, ed. J.R. Tutin. The + <bibl xml:id="RESPONS-eg-02"><author>Cowley, Hannah</author>. <title level="m">The Runaway (1813). + Crashaw, Richard, ed. J.R. Tutin. The Poems of Richard Crashaw. Muses Library Edition: (1900). - - Creeley, Robert - A counterpoint in For Love: Poems 1950-1960 + Creeley, RobertA counterpoint in For Love: Poems 1950-1960 (1962). 崔西．雪佛蘭。《戴珍珠耳環的少女》。台北：皇冠，2003。 - - Dallas, George Mifflin. Unpublished letter cited in Russell F. Weigley, Nicholas B. Wainwright, Edwin Wolf eds. Philadelphia: A 300 Year History, New York and London: - W. W. Norton & Company, 1982, p. 349. + W. W. Norton & Company, 1982, p. 349. Danhauser, Adolphe-Leopold, Théorie de la musique, 1872. - - Darwin, Charles. Narrative of the Surveying Voyages of His Majesty's + <bibl xml:id="beagle"><author>Darwin, Charles</author>. <title>Narrative of the Surveying Voyages of His Majesty's ships Adventure and Beagle... volume 3 : Journal and Remarks (The Voyage of the Beagle), chap 3. 1839. Daudet, Alphonse, Les contes du lundi, 1873. - - Davenant, William. The vvitts. A comedie, presented at the + <bibl xml:id="WD-TWac"><author>Davenant, William</author>. <title level="m">The vvitts. A comedie, presented at the private house in Blacke Fryers, by his Majesties servants. The author VVilliam D'avenant, - servant to Her Majestie. - London, 1636. [STC S109311] - - De Nutrimento et Nutribili, Tractatus 1, fol 217r col b of Merton College + servant to Her Majestie.London, 1636. [STC S109311] + De Nutrimento et Nutribili, Tractatus 1, fol 217r col b of Merton College Oxford MS O.2.1; in pl. 16. - - Dean of Sarum Churchwardens' presentments, 1731, Hurst; Wiltshire Record + Dean of Sarum Churchwardens' presentments, 1731, Hurst; Wiltshire Record Office; transcribed by Donald A. Spaeth. Defoe, Daniel. The Fortunes and Misfortunes of the Famous Moll Flanders (1722). Defoe, Daniel. Robinson Crusoe (1719). - - Defoe, Daniel. Journal of the Plague Year. + Defoe, Daniel. Journal of the Plague Year. London (1722). - - Dekker, Thomas and Thomas Middleton. The Honest + <bibl xml:id="DR-eg-04"><author>Dekker, Thomas</author> and <author>Thomas Middleton</author>. <title>The Honest Whore, Part One (1604). Deloney, Thomas. Thomas of Reading or the Sixe Worthie Yeomen of the West (1612). - Dennery, Annie. Du mélos à la note : Les notations musicales au Moyen Age, Médiévales, n° 3 - 1983. + Dennery, Annie. Du mélos à la note : Les notations musicales au Moyen Age, Médiévales, n° 31983. Dickens, Charles. A Christmas Carol in Prose, Being a Ghost Story of Christmas, Chapman and Hall, (1843), p. 5, p. @@ -423,34 +315,27 @@ $Id$ Diderot, Denis, Lettres à Sophie Volland, 26 sept. 1762. 〈第三屆第一次大會第一次會議記錄〉，臺灣省諮議會。 - Disraeli, Benjamin. Coningsby (1844), preface. + Disraeli, Benjamin. Coningsby (1844), preface. Doyle, Arthur Conan. The Red-headed league. In The Adventures of Sherlock Holmes (1892). - - Doyle, Arthur Conan. The Original Illustrated Sherlock + <bibl xml:id="DSGRP-eg-57"><author>Doyle, Arthur Conan</author>. <title level="m">The Original Illustrated Sherlock Holmes, Castle Books, 1989. Drawing of a leaden plaque bearing an inquiry by Hermon from the - oracular precinct at Dodona. Catalogue no 725; LSAG 230.13. Image from + oracular precinct at Dodona. Catalogue no 725; LSAG 230.13. Image from Dubois, Jacques, Nyssen, Hubert (dir. de collection), Babel, Actes sud,1989-.... Dubois, Jean, Dictionnaire de linguistique, 1974. - - Dudo of St Quentin. De moribus et actis primorum Normannie + <bibl xml:id="PH-eg-04"><author>Dudo of St Quentin</author>. <title>De moribus et actis primorum Normannie ducum, fol 4v of British Library MS Harley 3742; in pl 6(i). Dufournaud, Nicole, - Numérisation des Titres de famille, édition électronique, 2002. + Numérisation des Titres de famille, édition électronique, 2002. Duhamel, Georges, Chronique des Pasquier, 1933-1945. - - Dutt, Toru. Lakshman In Ancient + <bibl xml:id="eg-rhyme-dutt"><author>Dutt, Toru</author>. <title level="a">Lakshman In Ancient Ballads and Legends of Hindustan, Kegan Paul, Trench & Co., (1882) Dylan, Bob. All Along the @@ -459,101 +344,67 @@ $Id$ <bibl xml:id="pos4st"><author>Dylan, Bob</author>. <title level="a">Positively 4th Street In Highway 61 Revisited (1965). - - - - Eddic poems, in Reykjavík, Landsbókasafn Íslands, Lbs 1562 4to. + Eddic poems, in Reykjavík, Landsbókasafn Íslands, Lbs 1562 4to. Editorial, .EXE magazine, 6.11 (1992), p. 2. - Eliot, George. Middlemarch (1871), I.1. - - Eliot, George. Middlemarch (1871), + Eliot, George. Middlemarch (1871), I.1. + Eliot, George. Middlemarch (1871), I.XXI. - - Eliot, George. Daniel Deronda (1876), + Eliot, George. Daniel Deronda (1876), III.1. Eliot, Thomas Stearns. The waste land: a facsimile and transcript of the original drafts including the annotations of Ezra Pound, Eliot, Valerie ed. Faber and Faber Ltd. (1971), p. 37. - - Scalable Vector Graphics (SVG) 1.1 (Second Edition). Editors - Erik Dahlström, Jon Ferraiolo, 藤沢 淳, Anthony Grasso, Dean - Jackson, Chris Lilley, Cameron McCormack - Doug Schepers, Jonathan Watt and Patrick + Scalable Vector Graphics (SVG) 1.1 (Second Edition). Editors + Erik Dahlström, Jon Ferraiolo, 藤沢 淳, Anthony Grasso, Dean + Jackson, Chris Lilley, Cameron McCormackDoug Schepers, Jonathan Watt and Patrick Dengler. World Wide Web Consortium (W3C) (22 June 2010). Available from . Ernaux, Annie, Se perdre, 1988. Ernaux, Annie, L'usage de la photo, 2005. - - - <ref target="http://www.etudes-litteraires.com/figures-de-style/deictique.php">Études - littéraires</ref> - , consulté le 07-05-2010. - + <ref target="http://www.etudes-litteraires.com/figures-de-style/deictique.php">Études + littéraires</ref>, consulté le 07-05-2010. - Fallet , René, Le Triporteur, 1951. - Field, Syd - Screenplay: the Foundations of Screenwriting (1998). + Field, SydScreenplay: the Foundations of Screenwriting (1998). Fielding, Henry. The History of the Adventures of Joseph Andrews and his Friend, Mr. Abraham Abrams (1742). - - Fielding, Henry. Tragedy of Tragedies, + Fielding, Henry. Tragedy of Tragedies, (1737). - - Fish, Stanley. Is there a text in this class? The authority of + <bibl xml:id="DS-eg-05"><author>Fish, Stanley</author>. <title>Is there a text in this class? The authority of interpretive communities. Harvard University Press (1980). Fisher, M. F. K. I Was Really Very Hungry In As They Were, Knopf (1982), p. 43. - - - FitzGerald, Edward. The Rubáiyát of Omar Khayyám, translated into + <bibl xml:id="fitrub"><!-- tip o the hat to John Lavignino --><author>FitzGerald, Edward</author>. <title>The Rubáiyát of Omar Khayyám, translated into English Verse (1859), stanza 25. Flaubert, Gustave, Salammbô, 1862. Flaubert, Gustave, La Tentation de saint Antoine, 1874. Foley James D., Andries van Dam, - Steven K. Feiner and John F. Hughes. Computer Graphics: Principles and Practice, 2nd edition - Reading: Addison-Wesley, p.259. + Steven K. Feiner and John F. Hughes. Computer Graphics: Principles and Practice, 2nd edition + Reading: Addison-Wesley, p.259. Forster, E.M., Howards End. Edward Arnold. (1910). - - - <ref target="http://sites.radiofrance.fr/franceinter/em/labassijysuis">France inter, - Là-bas si j'y suis</ref> - , consulté le 07-05-2010. - - - <ref target="http://sites.radiofrance.fr/franceinter/em/letelephonesonne/contact.php" - >France inter, Le téléphone sonne</ref> - , consulté le 07-05-2010. - - - <ref target="http://franglais.ini.hu/">Franglais et franricain</ref> - , consulté le 07-05-2010. + <ref target="http://sites.radiofrance.fr/franceinter/em/labassijysuis">France inter, + Là-bas si j'y suis</ref>, consulté le 07-05-2010. + <ref target="http://sites.radiofrance.fr/franceinter/em/letelephonesonne/contact.php">France inter, Le téléphone sonne</ref>, consulté le 07-05-2010. + <ref target="http://franglais.ini.hu/">Franglais et franricain</ref>, consulté le 07-05-2010. Fry, Christopher, The firstborn (1948). 福春嫁女 - - Fussell, Paul. The Norton Book of Travel. W. W. + Fussell, Paul. The Norton Book of Travel. W. W. Norton (1987). - - Galilei, Galileo, Sidereus Nuncius, Venetiis: Apud Thomam Baglionum, 1610, quoted by Tufte, Edward R., @@ -564,39 +415,29 @@ $Id$ Mille et une nuits, 1704. Galsworthy, John, Strife. In Plays, vol 1. (1909). - Gaskell, Elizabeth Cleghorn. The Grey Woman, MS. + Gaskell, Elizabeth Cleghorn. The Grey Woman, MS. Gavioli, Laura and Gillian Mansfield. The PIXI corpora: bookshop encounters in English and Italian, Bologna: Cooperativa Libraria - Universitaria Editrice (1990), p.74. + Universitaria Editrice (1990), p.74. Gay, John. The Beggar's Opera (1728). Gazdar, Gerald and Mellish, Christopher. Natural language processing in Prolog. - Addison-Wesley (1989), p.5. - - Gazdar, Gerald, Ewan Klein, Geoffrey Pullum, and Ivan Sag: + Addison-Wesley (1989), p.5. + Gazdar, Gerald, Ewan Klein, Geoffrey Pullum, and Ivan Sag: Generalized Phrase Structure Grammar, Harvard University Press (1985). - - Gershwin, Ira - By Strauss (from An American in Paris, 1953). + Gershwin, IraBy Strauss (from An American in Paris, 1953). Gianfraco Contini, Poeti del Duecento, Milano-Napoli:Ricciardi I, (1960). pp 155-64. Gibbon, Edward, The History of the - Decline and Fall of the Roman Empire, (1789), chapter 58. + Decline and Fall of the Roman Empire, (1789), chapter 58. Gide, André, Le Journal des Faux-Monnayeurs, 1927. Gide, André, Journal : 1889-1939, 1939. - - Gilbert, William Schwenck and Sullivan, Arthur. HMS Pinafore (1878), I. + Gilbert, William Schwenck and Sullivan, Arthur. HMS Pinafore (1878), I. Gilbert, William Schwenck and Sullivan, Arthur. The Mikado (1885). Ginsberg, Allen. My alba, @@ -606,34 +447,25 @@ $Id$ Regain, 1930. Giraudoux, Jean, La guerre de Troie n'aura pas lieu, 1935. - - Godefroy, Frédéric, Dictionnaire de l'ancienne langue française et + <bibl xml:id="fr-ex-Godefroy" xml:lang="fr"><author>Godefroy, Frédéric</author>, <title>Dictionnaire de l'ancienne langue française et de tous ses dialectes du IXe au XVe siècle, 1881. - Goethe, Johann Wolfgang von, tr. Philip Wayne. Faust, Part + Goethe, Johann Wolfgang von, tr. Philip Wayne. Faust, Part 1, London: Penguin. (1949). - - Goethe, Johann Wolfgang von. Auf dem See + Goethe, Johann Wolfgang von. Auf dem See (1775). - - [Goldsmith, Oliver], The History of Little GOODY TWO-SHOES; + <bibl xml:id="G2S"><author>[Goldsmith, Oliver]</author>, <title>The History of Little GOODY TWO-SHOES; Otherwise called, Mrs. MARGERY TWO-SHOES... (Printed for J. Newbery, 1766). - - Grallert, Till, Tools for the Computational Normalisation and + <bibl xml:id="HDUDECL-TG"><author>Grallert, Till</author>, <title>Tools for the Computational Normalisation and Analysis of Food Prices and Food Riots in the Eastern Mediterranean (Bilād al-Shām) in the - 19th and 20th Centuries. Zenodo, 2021. . - - Graves, Robert. Rough draft of letter to Desmond Flower. + 19th and 20th Centuries. Zenodo, 2021. . + Graves, Robert. Rough draft of letter to Desmond Flower. 17 Dec 1938. (from Diary of Robert Graves 1935-39 and ancillary materials, compiled by Beryl Graves, C.G. Petter, L.R. Roberts, University of Victoria Libraries). - - Greene, Robert. Groatsworth of Wit Bought with a Million + <bibl xml:id="DSBACK-eg-86"><author>Greene, Robert</author>. <title level="m">Groatsworth of Wit Bought with a Million of Repentance (1592). - - Gregory of Tours. Ecclesiastical History of the + <bibl xml:id="DS-eg-01"><author>Gregory of Tours</author>. <title level="m">Ecclesiastical History of the Franks (translated by Lewis Thorpe). Greimas, Algirdas Julien et Courtés, Joseph, Sémiotique : dictionnaire raisonné de la théorie @@ -642,13 +474,9 @@ $Id$ Jacobs</author>. <title level="m">Parsing Techniques: A Practical Guide, New York and London: Ellis Horwood, 1990, p. 24. - - Guerard, Françoise. Le Dictionnaire de Notre Temps, ed. - Paris: Hachette, 1990 - - + Guerard, Françoise. Le Dictionnaire de Notre Temps, ed. + Paris: Hachette, 1990 - Hall, Radclyffe. The well of loneliness. (1928). Halliday, M.A.K. and R. @@ -663,8 +491,7 @@ $Id$ Hannam's last farewell to the world:: being a full and true relation of the notorious life and shamfull death of Mr. Richard Hannam... (1656). - - Hansberry, Lorraine. A raisin in the sun. + Hansberry, Lorraine. A raisin in the sun. (1959). Harvey, Gabriel. Four letters and certain sonnets specially touching Robert Greene... (1592). @@ -677,90 +504,66 @@ $Id$ BertheFleurs, fruits et feuillages choisis de l'île de Java peints d'après nature, troisième édition par C. Muquardt, Bruxelles, 1880. - - Hornby, A.S. et al. Oxford Advanced Learner's Dictionary of Current + <bibl xml:id="DIC-OALD"><editor>Hornby, A.S. et al</editor>. <title>Oxford Advanced Learner's Dictionary of Current English. Oxford University Press (1974). 黃晨淳編著，《希臘羅馬神話故事》，p76。 Hugo, Victor, Notre-Dame de Paris, 1845. - - Souvenir de la nuit du 4, in : Hugo, Victor, + Souvenir de la nuit du 4, in : Hugo, Victor, Les Contemplations, 1853. Hugo, Victor, Les Misérables, 1862. - - A la fenêtre pendant la nuit, in : Hugo, Victor , + A la fenêtre pendant la nuit, in : Hugo, Victor , Les Contemplations, 1856. Huizinga, Johan, L'Automne du Moyen-Âge, 1919. - - ISO 690:1987: Information and documentation – - Bibliographic references – Content, form and structure - clause 4.1, p.2. + Bibliographic references – Content, form and structure clause 4.1, p.2. ISO 24611:2012 Language resource management — Morpho-syntactic annotation framework (MAF). International Organization for Standardization. 2012. - - Ibsen, Henrik, tr. William and Charles Archer. + Ibsen, Henrik, tr. William and Charles Archer. Peer Gynt (1875). - - Ibsen, Henrik - Den episke Brand KBK Collin 2869, 4º I, fol. 11v. - - Ibsen, Henrik - Digte NBO Ms.4º 1110a, p. 36. - - Ibsen, Henrik - Brand, The Royal Library, Denmark. KBK Collin 262, 4°, I.1.1, fol. + Ibsen, HenrikDen episke Brand KBK Collin 2869, 4º I, fol. 11v. + Ibsen, HenrikDigte NBO Ms.4º 1110a, p. 36. + Ibsen, HenrikBrand, The Royal Library, Denmark. KBK Collin 262, 4°, I.1.1, fol. [4]v Ibsen, Henrik, tr. R. Farquharson Sharp and Eleanor Marx-Aveling. A Doll's House In A Doll's House; and Two Other - Plays by Henrik Ibsen, Everyman's library: the drama 494 + Plays by Henrik Ibsen, Everyman's library: the drama 494 , London: J. M. Dent & Sons, 1910. Idle, Eric, Michael Palin, Graham Chapman, John Cleese, Terry Gilliam. The Complete Monty Python's Flying Circus: All the - Words, Pantheon Books, (1989), 2, p.230. + Words, Pantheon Books, (1989), 2, p.230. Imbs, Paul, Martin, Robert, Straka, Georges, Mélanges de linguistique française et de philologie et littérature médiévales offerts à Monsieur Paul Imbs, 1973 . Institut de Littérature Française Moderne de - l’Université de Neuchâtel, Présentation du projet Cyrus, En ligne, consulté le - 05-03-2010. + l’Université de Neuchâtel, Présentation du projet Cyrus, En ligne, consulté le + 05-03-2010. Ionesco, Eugène, La cantatrice chauve, 1950. 羅貫中，《三國演義》。 - - - - Jakacki, Diane. Schema question: further constraining + <bibl xml:id="TEI-L_b092ac32.2101"><author>Jakacki, Diane</author>. <title level="a">Schema question: further constraining @subtype based on @type. January 18, 2021. TEI (Text Encoding Initiative) public discussion - list, . + list, . Jarry, Alfred, tr. Simon Watson Taylor and Cyril Connolly. The Ubu plays, London: Methuen, 1968. - Jean-Jacques Rousseau - Les confessions vol 6 - Jerome, Jerome K. - Three men in a boat (1889), chapter 6. + Jean-Jacques RousseauLes confessions vol 6 + Jerome, Jerome K. Three men in a boat (1889), chapter 6. Joachim Heinrich CampeWörterbuch der Deutschen Sprache. Erster Theil. A - bis - E., 1807. John, Lord Sheffield, The - Auto-biography of Edward Gibbon esq., (1846), 222. + Auto-biography of Edward Gibbon esq., (1846), 222. Jonson, Ben. Bartholomew Fair. Jonson, Ben. Volpone, @@ -773,29 +576,21 @@ $Id$ Joyce, James. Ulysses: The Bodley Head, 1960. p. 933. - - Judith Patt, Michiko Warkentyne and Barry + Judith Patt, Michiko Warkentyne and Barry Till. Haiku: Japanese Art and Poetry. 2010. - Pomegranate Communications, Inc. San Francisco. . + Pomegranate Communications, Inc. San Francisco. . - - Karlstadt, Andreas Bodenstein. Distinctiones Thomistarum. - Wittenberg - 1507. In Harald Bollbuck ed. Kritische Gesamtausgabe + Wittenberg1507. In Harald Bollbuck ed. Kritische Gesamtausgabe Karlstadt - I, available: + I, available: Kersey, John. Dictionarium Anglo-Brittannicum: Or, a General English Dictionary. London: J. Wilde, 1715. 2nd ed. - Kilian, Wilfrid, <ref - target="http://jubil.upmc.fr/sdx/pl/toc.xsp?id=GH_000484_001&fmt=upmc&idtoc=GH_000484_001-pleadetoc&base=fa" - >Neige et glaciers ; notes prises au cours de géologie de la Faculté des Sciences de + <bibl xml:id="fr-ex-Kilian-Neige" xml:lang="fr"><author>Kilian, Wilfrid</author>, <title><ref target="http://jubil.upmc.fr/sdx/pl/toc.xsp?id=GH_000484_001&fmt=upmc&idtoc=GH_000484_001-pleadetoc&base=fa">Neige et glaciers ; notes prises au cours de géologie de la Faculté des Sciences de Grenoble par M. Alamelle</ref>, 1891-1895. King, Martin Luther. Letter from Birmingham City Jail. Philadelphia, PA: American Friends Service @@ -803,25 +598,20 @@ $Id$ Kipling, Rudyard. The mother hive. In Actions and Reactions, London: Macmillan, (1909). - - Kipling, Rudyard. Stalky & Co., + Kipling, Rudyard. Stalky & Co., London: Macmillan (1899). Kipling, Rudyard. Kim, Macmillan, (1901), p. 9. Knuth, Donald Ervin. The Potrzebie - System of Weights and Measures, Mad Magazine33June 1957. + System of Weights and Measures, Mad Magazine33June 1957. Koltès, Bernard-Marie, Quai ouest, 1985. - Krummrey, Hans, Panciera, Silvio - Criteri di edizione e segni diacritici, Tituli 2 (1980), + Krummrey, Hans, Panciera, SilvioCriteri di edizione e segni diacritici, Tituli 2 (1980), 205-215. Kyd, Thomas. Spanish Tragedy (1592). - - La Fayette, Marie-Madeleine Pioche de La Vergne, comtesse de, La Princesse de Clèves, 1678. @@ -833,84 +623,63 @@ $Id$ et le renard In Fables Choisies, Classiques Larousse, Paris: Librairie Larousse, 1, 1940. - Laboratoire ATILF - - <ref target="http://www.atilf.fr/">Analyse et traitement informatique de la langue - française (ATILF)</ref> - , consulté le 07-05-2010. - - Laclos, Pierre Choderlos de. Les Liaisons + <bibl xml:id="fr-ex-ATILF" xml:lang="fr"><author>Laboratoire ATILF</author><title><ref target="http://www.atilf.fr/">Analyse et traitement informatique de la langue + française (ATILF)</ref>, consulté le 07-05-2010. + Laclos, Pierre Choderlos de. Les Liaisons dangereuses (1772), 1963, p. 13. - Ladurie, Emmanuel Le Roy. Montaillou, Middlesex: Penguin Books, + Ladurie, Emmanuel Le Roy. Montaillou, Middlesex: Penguin Books, 1980, p. 3. Lamartine, Alphonse de, Méditations poétiques, 1820. Lamothe, Alexandre - de - Principaux manuscrits latins et français conservés dans la Bibliothèque - impériale et dans celle de l'Ermitage à Saint-Pétersbourg, édition numérique, Bibliothèque de l'école nationale des + de</author><title level="a">Principaux manuscrits latins et français conservés dans la Bibliothèque + impériale et dans celle de l'Ermitage à Saint-Pétersbourg, édition numérique, Bibliothèque de l'école nationale des chartes, 1864. Langendoen, D. Terence and Paul M. Postal. Vastness of Natural Languages, Oxford: Basil Blackwell, 1984, p. 24, note 12. Langendoen, D. Terence and Paul Postal. The - vastness of natural languages, Blackwell, , 1, 1984. - - Langland, William. The Vision of Piers Plowman. In + vastness of natural languages, Blackwell, , 1, 1984. + Langland, William. The Vision of Piers Plowman. In A.V.C. Schmidt ed. Langland: Vision of Piers Plowman: "B" Text, opening. Latin liturgical manuscript: Bod MS. Lat liturg. b. - 19, folio 4r. Taken from the digitized image described at . + 19, folio 4r. Taken from the digitized image described at . Lavrentev, Alexei, <ref target="http://ccfm.ens-lsh.fr/IMG/pdf/BFM-Mss_Encodage-XML.pdf">Manuel d’encodage XML-TEI étendu des transcriptions de manuscrits dans le projet BFM-Manuscrits</ref>, dernier enregistrement le 26 juin 2008. - - Lawrence, David Herbert. Autograph manuscript of Eloi, Eloi, lama + <bibl xml:id="PH-eg-06"><author>Lawrence, David Herbert</author>. Autograph manuscript of <title>Eloi, Eloi, lama sabachthani, Pierpont Morgan MA 1892; in p.129. - - Layamon. Brut, fol 65v of Bodleian MS. Rawlinson Poetry 32; + Layamon. Brut, fol 65v of Bodleian MS. Rawlinson Poetry 32; in 12(ii). Le Grand Robert de la langue française, 2004. - LeTourneau, Mark S. - English Grammar, 2001, New York: - Harcourt - p. 89. - - Leech, G., G. Myers, J. Thomas eds. + LeTourneau, Mark S. English Grammar, 2001, New York: + Harcourtp. 89. + Leech, G., G. Myers, J. Thomas eds. Spoken English on Computer: Transcription, Markup and Applications. Harlow: Longman, 1995. Leech, Geoffrey and Mick Short. Style in Fiction, London: - Longman, 1981, p.272. - - Lennon, John and McCartney, Paul. She + <publisher>Longman</publisher>, <date>1981</date>, <biblScope unit="pp">p.272</biblScope>.</bibl> + <bibl xml:id="COEDADD-eg-92"><author>Lennon, John</author> and <author>McCartney, Paul</author>. <title level="a">She Loves You. The Beatles Anthology 1. Capitol, 1995. Léry, Jean de, Histoire faict en la terre de Brésil, 1580. - - Lessing, Doris. Martha Quest. 1952, + Lessing, Doris. Martha Quest. 1952, pp. 52-53. Letter of Mikołaj Orlik to Mikołaj Serafin, Gródek, January 13 - [1438]. Edited by Skolimowska et al. Available from + [1438]. Edited by Skolimowska et al. Available from Lewis, Leopold Davis. The Bells, (1871), translated from Erckmann-Chatrian, Le Juif Polonais. - - Lewis, Wyndham. Tarr (1928), + Lewis, Wyndham. Tarr (1928), Jupiter, 1968, p. 17. 李白，《黃鶴樓送孟浩然之廣陵》。 李白，《靜夜思》。 @@ -924,12 +693,10 @@ $Id$ Address, 4 March 1865. In H. S. Commager, ed., Documents of American History, 5th ed Crofts American history series. New York: - Appleton-Century-Crofts, 1949, p.442. + Appleton-Century-Crofts, 1949, p.442. 劉康，《對話的喧囂：巴赫汀文化理論評述》，台北：麥田，2005，二版。 劉康，《對話的喧聲：巴赫汀文化理論述評》，台北：麥田，2005，頁20-23。 - - Longman Dictionary of Contemporary English. Harlow, + Longman Dictionary of Contemporary English. Harlow, Essex: Longman (1978). Lorris, Guillaume de et Meun, Jean deLe Roman de la Rose, 1230, @@ -953,28 +720,22 @@ $Id$ 魯迅，《狂人日記 》。 魯迅，《狂人日記》。 魯迅，《狂人日記》。 - - MacNeice, Louis. The Sunlight on the Garden In E.R. Dodds, The collected poems of Louis MacNeice, London: Faber, 1966. - Examples from MacWhinney, Brian, 88, 87, cited by Johansson, S. + Examples from MacWhinney, Brian, 88, 87, cited by Johansson, S. The approach of the Text Encoding Initiative to the encoding of spoken discourse In Leech, G., G. Myers, J. Thomas eds. Spoken English on Computer: Transcription, Markup and Applications. Harlow: Longman, 1995. - - Madan, Falconer, et al, A summary catalogue of western manuscripts - in the Bodleian Library at Oxford which have not hitherto been catalogued ... - Oxford, 1895-1953. 5: 515. + Madan, Falconer, et al, A summary catalogue of western manuscripts + in the Bodleian Library at Oxford which have not hitherto been catalogued ... Oxford, 1895-1953. 5: 515. Cited in Driscoll, M.J. P5-MS: A general purpose tagset for manuscript description in Digital Medievalist: - 2.1, (2006) - + 2.1, (2006) Maingeneau, Dominique, Analyser les textes de communication, 2007. Any issue of the Malawi Daily Times. @@ -982,17 +743,13 @@ $Id$ <bibl xml:id="fr-ex-Zazie" xml:lang="fr"><author>Malle, Louis</author>, <title level="a">Zazie dans le métro : script, l'Avant-scène cinéma, n° 104, juin 1970. - - Manuélian, Hélène, Schang, Emmanuel, XML, DTD et - TEI pour un dictionnaire étymologique des créoles, édition électronique, + Manuélian, Hélène, Schang, Emmanuel, XML, DTD et + TEI pour un dictionnaire étymologique des créoles, édition électronique, 12 Octobre 2007. - - The Manere of Good Lyuynge: fol. 126v of Bodleian MS Laud Misc 517; + The Manere of Good Lyuynge: fol. 126v of Bodleian MS Laud Misc 517; in , p.8. Marbury v. Madison, 1 Cranch, - 137 (1803), rpt. In H. S. Commager, ed., Documents of American History, 5th ed + 137 (1803), rpt. In H. S. Commager, ed., Documents of American History, 5th ed Crofts American history series. New York: Appleton-Century-Crofts, 1949, p.192. @@ -1004,11 +761,9 @@ $Id$ Sociologie et anthropologie, 1950. McCarthy, Niall, No Parachute: The Highest Falls People Survived, Statista, - November 18, 2020. . - McCarty, Willard. Introduction in Collaborative Research in the Digital + <date when="2020-11-18">November 18, 2020</date>. <ptr target="https://www.statista.com/chart/19708/known-occasions-where-people-survived-falls/"/>. </bibl> + <!-- See also https://en.wikipedia.org/wiki/Highest_falls_survived_without_a_parachute --> + <bibl xml:id="SOURCE-eg-01"><author>McCarty, Willard</author>. <title level="a">Introduction in Collaborative Research in the Digital Humanities: A volume in honour of Harold Short on the occasion of his 65th birthday, September 2010, ed. Marilyn Deegan and Willard McCarty. London: Ashgate @@ -1018,19 +773,14 @@ $Id$ Mendès-France, Pierre, Œuvres complètes, 1984-1985. 《孟子》〈三十三〉。 - - Miller, Henry. Death of a Salesman in + Miller, Henry. Death of a Salesman in Atkinson, Brooks, New Voices in the American Theatre, New York: - Modern Library, 1955, p.113. - - Milne, A. A. - The House at Pooh Corner. London: + Modern Library, 1955, p.113. + Milne, A. A. The House at Pooh Corner. London: Methuen & Co., 1928, p. 83. - - Milton, John. Paradise Lost: A poem in X books + Milton, John. Paradise Lost: A poem in X books (1667), I, 1-10. Milton, John. Poems of Mr John Milton, both English and Latin... (1645). @@ -1047,17 +797,13 @@ $Id$ 1721. Montherlant, Henry de , Pitié pour les femmes, 1936. - - Moore, George. Autograph manuscript of Memoirs of my dead + <bibl xml:id="PH-eg-03"><author>Moore, George</author>. Autograph manuscript of <title>Memoirs of my dead life, Pierpont Morgan MA 3421; in - - Moore, Thomas. Autograph manuscript of the second version of Lalla + <bibl xml:id="PH-eg-09"><author>Moore, Thomas</author>. Autograph manuscript of the second version of <title>Lalla Rookh, Pierpont Morgan MA 310; in 23. - - Moreland, Floyd L. and Rita M. Fleischer. Latin: An + <bibl xml:id="CO-eg-04"><author>Moreland, Floyd L.</author> and <author>Rita M. Fleischer</author>. <title>Latin: An Intensive Course, (1977) p.53. - - Des Minnesangs Frühling, Moser, Hugo, Helmut + Des Minnesangs Frühling, Moser, Hugo, Helmut Tervooren eds. 36., neugestaltete und erweiterte Auflage I Texte, Stuttgart: S. Hirzel Verlag, 1977. @@ -1066,8 +812,7 @@ $Id$ Monumenta Chartæ Papyraceæ Historiam Illustrantia; v. 13. Mréjen, Valérie, Eau sauvage, 2004. - - Zuigan calls himself "Master". Mumon Ekai. (In + Zuigan calls himself "Master". Mumon Ekai. (In The Gateless Gate, Case 12.) Mustafa Siddik Altinakar, René Walther (éds.), Hydraulique fluviale. Tome 16, Écoulement et @@ -1075,12 +820,9 @@ $Id$ <date>2008</date>.</bibl> <bibl xml:id="fr-ex-Tunis" xml:lang="fr"><editor>Mégnin, Michel</editor> (éd.), <title>Tunis 1900 Lehnert & Landrock photographes,2005. - - Nabokov, Vladimir - Pnin (1953) , p.14 + Nabokov, VladimirPnin (1953) , p.14 - - The New Penguin English Dictionary. London: + The New Penguin English Dictionary. London: Penguin Books (1986). Derived from @@ -1089,12 +831,10 @@ $Id$ Wellington, New Zealand. . - - Njal's saga. tr. Magnus Magnusson and Hermann + Njal's saga. tr. Magnus Magnusson and Hermann Palsson. Penguin. (1960), chapter 12, p.60. - - O'Casey, Sean. Time to go (1951). + O'Casey, Sean. Time to go (1951). Ollagnier, Jeanne, Main, 2008. Herodotus. On Libya, from the @@ -1106,37 +846,22 @@ $Id$ Myself, Collection MSS3829, part of the Papers of Walt Whitman, Clifton Waller Barrett Library of American Literature, Albert and Shirley Small Special Collections Library, University of Virginia. - Ormesson, Jean d', La Douane de mer, 1993. - - Orwell, George. Nineteen-Eighty-Four. + Ormesson, Jean d', La Douane de mer, 1993. + Orwell, George. Nineteen-Eighty-Four. London: Gollancz (1949). - - 大隅亜希子. 1996. 律令制下における権衡普及の実態: - 海産物の貢納単位を中心として. 史論 - 49. pp. 22–44. . - - Owen, Wilfred. Dulce et decorum est, from autograph + 大隅亜希子. 1996. 律令制下における権衡普及の実態: + 海産物の貢納単位を中心として. 史論49. pp. 22–44. . + Owen, Wilfred. Dulce et decorum est, from autograph manuscript in the English Faculty Library, Oxford University. - - Owenson, Sydney. The Wild Irish Girl. Ed. + Owenson, Sydney. The Wild Irish Girl. Ed. Kathryn Kirkpatrick. Oxford: Oxford University Press, 1999, p. 17. - - 擺夷文經，中央研究院歷史語言研究所 。 - Pascal, Blaise, Le Mémorial, in Pensées,1670. - - Payne, J. - Report on the compatibility of J P French's spoken corpus transcription - conventions with the TEI guidelines for transcription of spoken texts, Working Paper, Dec 1992, NERC WP8/WP4 122. - - Peacock, Thomas Love. Gryll Grange + Pascal, Blaise, Le Mémorial, in Pensées,1670. + Payne, J. Report on the compatibility of J P French's spoken corpus transcription + conventions with the TEI guidelines for transcription of spoken texts, Working Paper, Dec 1992, NERC WP8/WP4 122. + Peacock, Thomas Love. Gryll Grange (1861), chapter 1. Pennac, Daniel , La Petite marchande de prose, 1978. @@ -1150,35 +875,26 @@ $Id$ based on an example in Pereira, Fernando C.N. and Stuart M. Shieber, Prolog and Natural Language Analysis, Stanford: Center for the Study of Language and - Information. (1987), p.22. + Information. (1987), p.22. Pernoud, Régine, La Femme au temps des Cathédrales, 1982. - Perreault, Simon, vCard Format Specification - Internet Engineering Task Force (IETF) (2011). + Perreault, Simon, vCard Format SpecificationInternet Engineering Task Force (IETF) (2011). . - - Petit Larousse en Couleurs. Paris: + Petit Larousse en Couleurs. Paris: Larousse, (1990). - - Philipott, Thomas - Poems. (1646). - - Pinsky, Robert. Essays on Psychiatrists in Sadness and Happiness (1975). + Philipott, ThomasPoems. (1646). + Pinsky, Robert. Essays on Psychiatrists in Sadness and Happiness (1975). Pix, Mary. The False Friend (1699). Plautus, Titus Macchius. Asinaria, or the Comedy of Asses. Edited and translated by Wolfgang de Melo. Loeb Classical Library 60. Cambridge, MA: Harvard University Press (2011). - Plautus, Titus Macchius. Menaechmi. + Plautus, Titus Macchius. Menaechmi. Polac, Michel, Un fils unique : script, l'Avant-scène cinéma, n° 99, janvier. 1970. - - Pope, Alexander. The Rape of the Lock + Pope, Alexander. The Rape of the Lock (1714) III.7. Pope, Alexander. An Essay on Criticism (1711). @@ -1192,38 +908,28 @@ $Id$ Queneau, Raymond. Exercices de style. Paris: Gallimard, (1947), p. 192. - - 瓊瑤，《還珠格格》。 Queneau, Raymond , Journaux, 1914-1965. - - Rabelais, François. Gargantua Lyon, 1542 - Rabelais, François - Tiers livre des faictz et dictz Heroïques du noble Pantagruel... - (1546), adapted from the website at + Rabelais, FrançoisTiers livre des faictz et dictz Heroïques du noble Pantagruel... + (1546), adapted from the website at Renard, Jules, Journal : 1887-1910, 1910. Reference from the bibliography in Reps, Thomas William and Teitelbaum, Tim eds. The Synthesizer Generator: A system for constructing language-based editors, New York and Berlin: - Springer-Verlag, 1989, p.304. + Springer-Verlag, 1989, p.304. 日本法隆寺貝葉心經 (Wikipedia Sept 2008). Richardson, Samuel. Clarissa; - or the History of a Young Lady (1748), 2 Letter XIV. - - Robert, Paul. Le Petit Robert. Paris: + or the History of a Young Lady (1748), 2 Letter XIV. + Robert, Paul. Le Petit Robert. Paris: Dictionnaires Le Robert (1967). - Rohmer, Eric, Ma nuit chez Maud : script, l'Avant-scène cinéma, + Rohmer, Eric, Ma nuit chez Maud : script, l'Avant-scène cinéma, n°98, 2001. Romains, Jules, Knock, 1923. @@ -1231,36 +937,25 @@ $Id$ Bergerac, 1898. Roubaud, Jacques, La Boucle, 1993. - Rowling, J. K. - The Sorting Hat. In Harry Potter and the + <bibl xml:id="COHQQ-eg-35"><author>Rowling, J. K.</author><title level="a">The Sorting Hat. In Harry Potter and the Sorcerer's Stone, New York: Scholastic, Inc. (1999), chapter 7, p. 121. - - - - The Saga of the Volsungs: the Norse epic of Sigurd the Dragon + <bibl xml:id="AI-eg-01"><title level="m">The Saga of the Volsungs: the Norse epic of Sigurd the Dragon Slayer. trans. Jesse L. Byock. University of California Press (1990). Le Sanctoral du lectionnaire de l'office dominicain (ms. Rome, Sainte-Sabine XIV L 1, f.142r et 189r-230v, Ecclesiasticum - officium secundum ordinem fratrum praedicatorum), édition électronique par + officium secundum ordinem fratrum praedicatorum), édition électronique par l'Ecole nationale des chartes, d'après l'édition d'Anne-Élisabeth Urfels-Capot (Paris : Ecole nationale des chartes, 2007). - - 崎山理. 1985 - インドネシア語. 講座日本語学 - 11. 外国語との対照II. - 東京:明治書院 - 61-80 - + 崎山理. 1985インドネシア語. 講座日本語学11. 外国語との対照II. + 東京:明治書院61-80 三毛，〈沙漠中的飯店〉，《撒哈拉的故事》。 《三家詩鈔》，華培昌，藏於國家圖書館。 Sapir, Edward. Language: an introduction to the study of speech, New York: - Harcourt, Brace and World, 1921, p.79. + Harcourt, Brace and World, 1921, p.79. Shakespeare William, Richard III, 1597. Shakespeare, William. Henry V @@ -1275,17 +970,14 @@ $Id$ Cleopatra, IV.4, 14-21. Shakespeare, William. Merchant of Venice, I.ii, speech 5 (Portia). - Shakespeare, William. Macbeth, Act V, Scene 1. + Shakespeare, William. Macbeth, Act V, Scene 1. Shakespeare, William. Antony and Cleopatra (1623), V. ii. - Shakespeare, William. Hamlet In Stanley Wells and Gary Taylor eds. + Shakespeare, William. Hamlet In Stanley Wells and Gary Taylor eds. The Complete Works, Oxford: Clarendon Press, 1986, I.i. - Shakespeare, William. Hamlet, London: Valentine Simmes. + Shakespeare, William. Hamlet, London: Valentine Simmes. (1603), I.i. Shakespeare, William. The Tempest In Mr. William Shakespeares Comedies, Histories, & @@ -1305,8 +997,7 @@ $Id$ available: <ptr target="http://www.ancientwisdoms.ac.uk/"/>.</bibl> <bibl xml:id="DR-eg-08"><author>Shaw, George Bernard</author>. <title level="m">Heartbreak House: a fantasia in the Russian manner on English themes (1919). - Shaw, George Bernard. Pygmalion, 1913. + Shaw, George Bernard. Pygmalion, 1913. Shields, David. Dead Languages, HarperCollins Canada/Perennial Rack, rpt. 1990, p.10. @@ -1318,39 +1009,29 @@ $Id$ Smith, Adam. An Inquiry into the Nature and Causes of the Wealth of Nations, London. (1776), index to vol. 1. - - Smith, Sydney. Autograph letter. In Pierpont Morgan library; + Smith, Sydney. Autograph letter. In Pierpont Morgan library; 11. - - Smith, William. A New Classical Dictionary of Greek and + <bibl xml:id="SMITHWM"><author>Smith, William</author>. <title level="m">A New Classical Dictionary of Greek and Roman Biography, Mythology, and Geography, Partly Based Upon the Dictionary of Greek and Roman Biography and Mythology, New York: Harper - & Brothers, Publishers, 1860, 1026. - - Southey, Robert. Autograph manuscript of The Life of Cowper. + & Brothers, Publishers, 1860, 1026. + Southey, Robert. Autograph manuscript of The Life of Cowper. In Pierpont Morgan MA 412 ( 15). - Soyinka, Akinwande Oluwole Wole. Madmen and Specialists, London: + Soyinka, Akinwande Oluwole Wole. Madmen and Specialists, London: Methuen (1971). - - Spenser, Edmund. The Faerie Queene: Disposed into twelue + <bibl xml:id="VE-eg-01"><author>Spenser, Edmund</author>. <title level="m">The Faerie Queene: Disposed into twelue bookes, Fashioning XII. Morall vertues. (1596). - - Sterne, Laurence. The Life and Opinions of Tristram + <bibl xml:id="COHQHE-eg-13"><author>Sterne, Laurence</author>. <title level="m">The Life and Opinions of Tristram Shandy, Gentleman. (1760). - - Stow, John A survey of the cities of London and Westminster: + <bibl xml:id="STOW"><author>Stow, John </author><title>A survey of the cities of London and Westminster: containing the original, antiquity, increase, modern estate and government of those cities. Written at first in the year MDXCVIII. By John Stow, citizen and native of London. ... Now lastly, corrected, improved, and very much enlarged: ... by John Strype, ... In six books. ... (London c.1525 - London 1605). Sudetic, Chuck Serbs Tighten Grip On Eastern - Bosnia. New York Times, - April 20, 1992. + Bosnia. New York Times, April 20, 1992. - SUEtheTrex, Twitter biography. . Accessed March 25th, + SUEtheTrex, Twitter biography. . Accessed March 25th, 2020. Sutherland, L.S. and L.G. Mitchell eds. The Eighteenth century, The @@ -1358,64 +1039,45 @@ $Id$ , p.178. 蘇童，《妻妾成群》。 蘇軾，《定風波》。 - - Swift, Jonathan. Travels into Several Remote Nations of + <bibl xml:id="COEDCOR-eg-71"><author>Swift, Jonathan</author>. <title level="m">Travels into Several Remote Nations of the World, in Four Parts. By Lemuel Gulliver... (1735). Swift, Jonathan. Law is a bottomless pit, or the history of John Bull (1712). - - Swinburne, Algernon Charles. Poems and Ballads (First + <bibl xml:id="HD-eg-swinb"><author>Swinburne, Algernon Charles</author>. <title level="m">Poems and Ballads (First Series). London: Chatto & Windus. (1904). Swinnerton, Frank Arthur. The Georgian Literary Scene 1910-1935, 1938, London: J. M. Dent, p. 195. - - - 台灣，《結婚入盟誓》，1997年5月。 台灣區三碼與三加二碼郵遞區號 - 《台灣叢書》，伊能嘉矩著，藏於國立台灣大學圖書館。(http://catalog.ndap.org.tw/?URN=2155366 (Aug 2008)). + 《台灣叢書》，伊能嘉矩著，藏於國立台灣大學圖書館。(http://catalog.ndap.org.tw/?URN=2155366 (Aug 2008)). 唐．白居易．琵琶行 - - Taylor, John - The Cold Tearme or, The Frozen age, Or, The Metamorphosis of the Riuer of + <bibl xml:id="TAYLOR"><author>Taylor, John</author><title>The Cold Tearme or, The Frozen age, Or, The Metamorphosis of the Riuer of Thames. London, 1621. [STC (2nd ed.) 23910]. - - TEI Consortium - Call for Papers - TEI 2022 Newcastle, 2022. - - The Castle of the Fly, in Russian Fairy Tales, + TEI ConsortiumCall for Papers - TEI 2022 Newcastle, 2022. + The Castle of the Fly, in Russian Fairy Tales, translated by Norbert Guterman from the collections of Aleksandr Afanas'ev, illustrations by Alexander Alexeieff, folkloristic commentary by Roman Jakobson (New York: Pantheon Books, 1947, rpt. [n.d.]), p. 25. The Daily Telegraph, 21 Dec 1992. - The Guardian, - 26 Oct 1992, p. 2 - The Guardian, - 21 Dec 1992, p. 2. + The Guardian, 26 Oct 1992, p. 2 + The Guardian, 21 Dec 1992, p. 2. The Holy Bible, conteyning the Old Testament and the new... appointed to be read in Churches. (1611), Genesis 1:1. - The Independent, - 26 Oct 1775, headline. + The Independent, 26 Oct 1775, headline. Thurber, James. The 13 Clocks (1950). - Tolkien, J. R. R. - The Monsters and the Critics. London: + Tolkien, J. R. R.The Monsters and the Critics. London: George Allen & Unwin (1983). - - Townsend, Sue. The growing pains of Adrian Mole + Townsend, Sue. The growing pains of Adrian Mole (1984), p.43. - - Trollope, Anthony. An Autobiography + Trollope, Anthony. An Autobiography (1883). - - Trollope, Anthony. North America + Trollope, Anthony. North America (1862). Truffaut, François et Gruault, Jean, Les deux Anglaises et le continent : @@ -1424,29 +1086,17 @@ $Id$ <bibl xml:id="COBITY-eg-240"><author>Tufte, Edward R.</author>, <title level="m">Envisioning Information, Cheshire: Graphics Press. (1990). - - Ukraine Relief Fund - UBS - . + Ukraine Relief FundUBS. - United States Code Title 17, Section 107, found at . - - United States District Court for the Middle District of Pennsylvania. + United States Code Title 17, Section 107, found at . + United States District Court for the Middle District of Pennsylvania. Kitzmiller v. Dover Area School District et al.: 2005. - 04cv2688, p. 33. Available from and transcribed at . - + 04cv2688, p. 33. Available from and transcribed at . - Valéry, Paul, Monsieur Teste, 1929. - - Vergil (Publius Vergilius Naso). Aeneid, + Vergil (Publius Vergilius Naso). Aeneid, I.1. Verne, Jules, Cinq semaines en ballon, 1863. @@ -1454,106 +1104,65 @@ $Id$ Chasse au météore, 1908. Verne, Jules, Vingt mille lieues sous les mers, 1870. - - Vinge, Vernor - Across realtime - ch 10 (1986). + Vinge, VernorAcross realtimech 10 (1986). Viton de Saint-Allais, Nicolas , Dictionnaire encyclopédique de la noblesse de France, 1816. - - Vóluspá recto of folio 5 of the unique manuscript of the Elder Edda. Codex + Vóluspá recto of folio 5 of the unique manuscript of the Elder Edda. Codex Regius, ed. L. F. A. Wimmer and F. Jónsson (Copenhagen 1891). - - - - Wanklyn, M.D.G. et al. Gloucester Port Books, 1575-1765. + Wanklyn, M.D.G. et al. Gloucester Port Books, 1575-1765. Available from . - - Wanton, Joseph. Unpublished letter to Nicholas Brown and Co, - 1761 - Brown University Steering Committee on Slavery and Justice: Repository of - Historical Documents. (). - - Warriner, John E. - English Composition and Grammar (1988), p.280. - - Webster's Seventh Collegiate Dictionary. Springfield, Mass. - G. & C. Merriam Co. (1975). + Wanton, Joseph. Unpublished letter to Nicholas Brown and Co, + 1761Brown University Steering Committee on Slavery and Justice: Repository of + Historical Documents. (). + Warriner, John E. English Composition and Grammar (1988), p.280. + Webster's Seventh Collegiate Dictionary. Springfield, Mass. G. & C. Merriam Co. (1975). 魏飴，《小說鑑賞入門》，台北：萬卷樓，1999。 - Weil, Simone, Lettres à Antonio Atarès, in Oeuvres + <bibl xml:id="fr-ex-Weil-Atares" xml:lang="fr"><author>Weil, Simone</author>, <title level="a"> Lettres à Antonio Atarès, in Oeuvres complètes1988-. - - Williams, Nigel. The Wimbledon Poisoner + Williams, Nigel. The Wimbledon Poisoner (1990), p. 204. Winock, Michel, Jeanne et les siens : récit, 2003. - - Wölfflin, Heinrich, trans. Hottinger, Marie + Wölfflin, Heinrich, trans. Hottinger, Marie Donald Mackie (1932). Principles of art history: the problem - of the development of style in later art.. Originally published as Kunstgeschichtliche Grundbegriffe (1915). - - Woolf, Virginia. Mrs Dalloway (1925), + of the development of style in later art.. Originally published as Kunstgeschichtliche Grundbegriffe (1915). + Woolf, Virginia. Mrs Dalloway (1925), p.64, p.65. - - Wordsworth, William. Scorn not the sonnet in + Wordsworth, William. Scorn not the sonnet in Poetical Works (1827). - - Wordsworth, William. The Prelude (1850). - - Wrenn C. L. ed. Beowulf: with the Finnesburg + <bibl xml:id="CO-eg-08"><author>Wordsworth, William</author>. <title>The Prelude (1850). + Wrenn C. L. ed. Beowulf: with the Finnesburg fragment, London: Harrap (1953). - 吳承恩，《西遊記》。 - - - Wycherley, William. The Country Wife + Wycherley, William. The Country Wife (1675). - 夏宇，〈甜蜜的復仇〉，《備忘錄》。 蕭紅，《呼蘭河傳》。 - - 幼莘貢俚賀曉濤之新婚賀詞 余秋雨 元曲。馬致遠，《天淨沙：秋思》。 - - 張錯， 《西洋文學術與手冊》，台北：書林，2005。頁201。 - 珍．奧斯丁，《傲慢與偏見》。 - 中國青年守則 中國學位論文全文數據庫 周慧玲，《表演中國：女明星表演文化視覺政治1910-1945》，2004。 朱自清， 《憶》跋。 - - Zimman, Lal. Lal Zimman - , accessed February 1, + Zimman, Lal. Lal Zimman, accessed February 1, 2021. - - Zupko, Ronald Edward - British Weights & Measures: A History from Antiquity to the Seventeenth + <bibl xml:id="ZUPKO"><author>Zupko, Ronald Edward</author><title level="m">British Weights & Measures: A History from Antiquity to the Seventeenth Century. Madison: University of Wisconsin Press, 141-151. - - No source, made up for these Guidelines. Example is copied from the source of these Guidelines. Undetermined. - -
@@ -1714,9 +1323,7 @@ $Id$ Rahtz RelaxNG with Son of ODD - + Proceedings of Extreme Markup Languages 2004 @@ -3083,9 +2690,7 @@ $Id$ DeRose Markup overlap: a review and a horse - + Proceedings of Extreme Markup Languages 2004 @@ -3130,9 +2735,7 @@ $Id$ Witt Making CONCUR work - + Proceedings of Extreme Markup Languages 2005 @@ -3159,8 +2762,7 @@ $Id$ A framework for management of concurrent XML markup - + 2005 @@ -3200,8 +2802,7 @@ $Id$ - + 2004 @@ -3233,9 +2834,7 @@ $Id$ documents - + Proceedings of Extreme Markup Languages 2007 @@ -3491,8 +3090,7 @@ $Id$ originally prepared by Susan Schreibman and Kevin Hawkins for the TEI Education Special Interest Group, recoded in TEI P5 by Sabine Krott and Eva Radermacher. They should be regarded only as a snapshot of work in progress, to which further contributions and corrections are - welcomed (see further ).

+ welcomed (see further ).

Theory of Markup and XML @@ -3528,9 +3126,7 @@ $Id$ Rabbit/duck grammars: a validation method for overlapping structures - + Proceedings of Extreme Markup Languages 2006 @@ -4400,9 +3996,7 @@ $Id$ Lamport Document Production: Visual or Logical? - + Notices of the American Mathematical Society @@ -4669,9 +4263,7 @@ $Id$ Piez Beyond the 'Descriptive vs. Procedural' Distinction - + @@ -4765,9 +4357,7 @@ $Id$ From Data Representation to Data Model: Meta-Semantic Issues in the Evolution of SGML - + Computer Standards & Interfaces @@ -4926,9 +4516,7 @@ $Id$ An XML Document Corresponds to Which FRBR Group 1 Entity? - + @@ -5025,9 +4613,7 @@ $Id$ Data Structures for Etymology: Towards an Etymological Lexical Network - + BULAG: revue internationale annuelle @@ -5193,9 +4779,7 @@ $Id$ Drawing Inferences on the Basis of Markup - + @@ -5337,9 +4921,7 @@ $Id$ Weel The Concept of Markup - + Digital Text and the Gutenberg Heritage @@ -5388,9 +4970,7 @@ $Id$ Bauman Keying NAMEs: the WWP Approach - + Brown University Women Writers Project Newsletter @@ -5414,9 +4994,7 @@ $Id$ Flanders Odd Customizations - + Proceedings of Extreme Markup Languages 2004 @@ -5482,9 +5060,7 @@ $Id$ Bauman TEI HORSEing Around - + Proceedings of the Extreme Markup Languages 2005 @@ -5909,9 +5485,7 @@ $Id$ Nellhaus XML, TEI, Digital Libraries in the Humanities - + Portal: Libraries and the Academy @@ -5932,8 +5506,7 @@ $Id$ Building TEI DTDs and Schemas on demand - + 2003 @@ -6012,8 +5585,7 @@ $Id$ The Electronic Text Center Introduction to TEI and Guide to Document Preparation - + 1995 diff --git a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml index ce65a7a203..d097c0730f 100644 --- a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml +++ b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml @@ -1,15 +1,9 @@ - + -
Language Corpora - -

The term language corpus is used to mean a number of +

+ Language Corpora +

The term language corpus is used to mean a number of rather different things. It may refer simply to any collection of linguistic data (for example, written, spoken, signed, or multimodal), although many practitioners prefer to reserve it for collections which have @@ -21,7 +15,7 @@ purposes however, the distinguishing characteristic of a corpus is that its components have been selected or structured according to some conscious set of design criteria.

-

These design criteria may be very simple and undemanding, or very +

These design criteria may be very simple and undemanding, or very sophisticated. A corpus may be intended to represent (in the statistical sense) a particular linguistic variety or sublanguage, or it may be intended to represent all aspects of some assumed @@ -37,7 +31,7 @@ section ). For simplicity, therefore, our discussion largely concerns ways of encoding closed corpora, regarded as single but composite texts.

-

Language corpora are regarded by these Guidelines as +

Language corpora are regarded by these Guidelines as composite texts rather than unitary texts (on this distinction, see chapter ). This is because although each discrete sample of language in a corpus clearly @@ -50,7 +44,7 @@ may exhibit different structural properties (for example, some may be composed of verse, and others of prose), thus potentially requiring elements from different TEI modules.

-

Aside from these high-level structural differences, and possibly +

Aside from these high-level structural differences, and possibly differences of scale, the encoding of language corpora and the encoding of individual texts present identical sets of problems. Any of the encoding techniques and elements presented in other chapters of @@ -73,7 +67,7 @@ appropriate to a given application. In sum, it should not be assumed that only the matters specifically addressed in this chapter are of importance for corpus creators.

-

This chapter does however include some other material +

This chapter does however include some other material relevant to corpora and corpus-building, for which no other location appeared suitable. It begins with a review of the distinction between unitary and composite texts, and of the different methods provided by @@ -91,9 +85,9 @@ linguistics. Finally, section provides some general recommendations about the use of these Guidelines in the building of large corpora.

-
Varieties of Composite Text - -

Both unitary and composite texts may be encoded using these +

+ Varieties of Composite Text +

Both unitary and composite texts may be encoded using these Guidelines; composite texts, including corpora, will typically make use of the following tags for their top-level organization. Full descriptions of these may be found in @@ -101,30 +95,26 @@ chapter (for teiHeader), and chapter -language corpora -collections or anthologies -poem cycles and epistolary works (novels or essays written -in the form of collections or series of letters) -otherwise unitary texts, within which one or more subordinate +language corporacollections or anthologiespoem cycles and epistolary works (novels or essays written +in the form of collections or series of letters)otherwise unitary texts, within which one or more subordinate texts are embedded The elements listed above may be combined to encode each of these varieties of composite text in different ways.

-

In corpora, the component samples are clearly distinct texts, but the +

In corpora, the component samples are clearly distinct texts, but the systematic collection, standardized preparation, and common markup of the corpus often make it useful to treat the entire corpus as a unit, too. Some corpora may become so well established as to be regarded as texts in their own right; the Brown and LOB corpora are now close to achieving this status.

-

The teiCorpus element is intended for the encoding of +

The teiCorpus element is intended for the encoding of language corpora, though it may also be useful in encoding newspapers, electronic anthologies, and other disparate collections of material. The TEI element may be used in the same manner itself; the @@ -139,32 +129,12 @@ has a corpus-level teiHeader element, in which the corpus as a whole, and encoding practices common to multiple samples may be described. The overall structure of a TEI-conformant corpus is thus: - - - - - - - - - - - - + + Or, alternatively: - - - - - - - - - - - -

-

Header information which relates to the whole corpus rather than to + +

+

Header information which relates to the whole corpus rather than to individual components of it should be factored out and included in the teiHeader element prefixed to the whole. This two-level structure allows for contextual information to be specified at the @@ -175,7 +145,7 @@ specified only once: a variety of methods are provided for associating it with individual components of a corpus, as further described in section .

-

In some cases, the design of a corpus is reflected in its internal +

In some cases, the design of a corpus is reflected in its internal structure. For example, a corpus of newspaper extracts might be arranged to combine all stories of one type (reportage, editorial, reviews, etc.) into some higher-level grouping, possibly with sub-groups @@ -183,7 +153,7 @@ for date, region, etc. The teiCorpus element provides no direct support for reflecting such internal corpus structure in the markup: it treats the corpus as an undifferentiated series of components, each tagged TEI.

-

If it is essential to reflect a single permanent organization of a +

If it is essential to reflect a single permanent organization of a corpus into sub- and sub-sub-corpora, then the corpus or the high-level subcorpora may be encoded as composite texts, using the group element described below and in section . The @@ -199,7 +169,7 @@ cross-classification and misclassification of samples, and helps improve the flexibility with which parts of a corpus may be characterized for different applications.

-

Anthologies and collections are often treated as texts in their own +

Anthologies and collections are often treated as texts in their own right, if only for historical reasons. In conventional publishing, at least, anthologies are published as units, with single editorial responsibility and common front and back matter which may need to be @@ -207,7 +177,7 @@ included in their electronic encodings. The texts collected in the anthology, of course, may also need to be identifiable as distinct individual objects for study.

-

Poem cycles, epistolary novels, and epistolary essays differ from +

Poem cycles, epistolary novels, and epistolary essays differ from anthologies in that they are often written as single works, by single authors, for single occasions; nevertheless, it can be useful to treat their constituent parts as individual texts, as well as the cycle @@ -215,13 +185,13 @@ itself. Structurally, therefore, they may be treated in the same way as anthologies: in both cases, the body of the text is composed largely of other texts.

-

The group element is provided to simplify the encoding of +

The group element is provided to simplify the encoding of collections, anthologies, and cyclic works; as noted above, the group element can also be used to record the potentially complex internal structure of language corpora. For a full description, see chapter .

-

Some composite texts, finally, are neither corpora, nor anthologies, +

Some composite texts, finally, are neither corpora, nor anthologies, nor cyclic works: they are otherwise unitary texts within which other texts are embedded. In general, they may be treated in the same way as unitary texts, using the normal TEI and @@ -230,15 +200,17 @@ the text element. For further discussion, see chapter .

-

All composite texts share the characteristic that their different +

All composite texts share the characteristic that their different component texts may be of structurally similar or dissimilar types. If all component texts may all be encoded using the same module, then no problem arises. If however they require different modules, then these must be included in the TEI customization. This process is described in more detail in section . -

-
Contextual Information -

Contextual information is of particular importance for collections +

+
+
+ Contextual Information +

Contextual information is of particular importance for collections or corpora composed of samples from a variety of different kinds of text. Examples of such contextual information include: the age, sex, and geographical origins of participants in a language interaction, or @@ -251,7 +223,7 @@ throughout the corpus, or represented proportionately to the population being sampled), or as a selection criterion in analysing the corpus (for example, to investigate the language usage of some particular vector of social characteristics).

-

Such contextual information is potentially of equal importance for +

Such contextual information is potentially of equal importance for unitary texts, and these Guidelines accordingly make no particular distinction between the kinds of information which should be gathered for unitary and for composite texts. In either case, the information @@ -262,7 +234,7 @@ or split across all the component texts of a corpus, in their individual headers, or divided between the two. The association between an individual corpus text and the contextual information applicable to it may be made in a number of ways, as further discussed in section below.

-

Chapter , which should be read in conjunction with +

Chapter , which should be read in conjunction with the present section, describes in full the range of elements available for the encoding of information relating to the electronic file itself, for example its bibliographic description and those of the source or @@ -274,7 +246,7 @@ information about the creation and content of the corpus, such as the languages used within it and any descriptive classification system used (see section ); and version information documenting any changes made in the electronic text (see section ).

-

In addition to the elements defined by chapter , +

In addition to the elements defined by chapter , several other elements can be used in the TEI header if the additional module defined by this chapter is invoked. These additional tags make it possible to characterize the social or other situation within which a @@ -285,62 +257,21 @@ as for collections or corpora, it is more often recorded for the components of systematically developed corpora than for isolated texts, and thus this module is referred to as being for language corpora.

- -

When the module defined in this chapter is included in a schema, a +

When the module defined in this chapter is included in a schema, a number of additional elements become available within the profileDesc element of the TEI header (discussed in section ). These elements, members of the model.profileDescPart, are discussed in the remainder of the chapter. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

- -
The Text Description -

The textDesc element provides a full description of the +

+ The Text Description +

The textDesc element provides a full description of the situation within which a text was produced or experienced, and thus characterizes it in a way relatively independent of any a priori theory of text-types. It is provided as an alternative @@ -350,11 +281,10 @@ organized as a set of values and optional prose descriptions for the following eight situational parameters, each represented by one of the following eight elements:

-

These elements constitute a model class called model.textDescPart; new parameters may be defined +

These elements constitute a model class called model.textDescPart; new parameters may be defined by defining new elements and adding them to that class, as further described in .

- -

By default, a text description will contain each of the above +

By default, a text description will contain each of the above elements, supplied in the order specified. Except for the purpose element, which may be repeated to indicate multiple purposes, no element should appear more than once within a single text @@ -366,7 +296,7 @@ dimensions; in such cases, the situational parameter in question should be given the content not applicable or an equivalent phrase.

-

Texts may be described along many dimensions, according to many +

Texts may be described along many dimensions, according to many different taxonomies. No generally accepted consensus as to how such taxonomies should be defined has yet emerged, despite the best efforts of many corpus linguists, text linguists, sociolinguists, @@ -386,14 +316,10 @@ in the 1960s and 1970s by researchers such as Hymes, Halliday, and Crystal and Davy, but have rarely been implemented; one notable exception being the pioneering work on the Helsinki Diachronic Corpus of English, on which see - - it enables a relatively continuous characterization of texts (in -contrast to discrete categories based on type or topic) -it enables meaningful comparisons across corpora -it allows analysts to build and compare their own text-types -based on the particular parameters of interest to them -it is equally applicable to spoken, written, or signed texts

-

Two alternative approaches to the use of these parameters are + it enables a relatively continuous characterization of texts (in +contrast to discrete categories based on type or topic)it enables meaningful comparisons across corporait allows analysts to build and compare their own text-types +based on the particular parameters of interest to themit is equally applicable to spoken, written, or signed texts

+

Two alternative approaches to the use of these parameters are supported by these Guidelines. One is to use pre-existing taxonomies such as those used in subject classification or other types of text categorization. @@ -406,7 +332,7 @@ second approach is to develop an application-specific set of declaration, as described in chapters and .

-

Where the organizing principles of a corpus or collection so permit, +

Where the organizing principles of a corpus or collection so permit, it may be convenient to regard a particular set of values for the situational parameters listed in this section as forming a text-type in its own right; this may also be useful where @@ -418,176 +344,31 @@ text-types, provided that the catDesc component of the than a prose description. Particular texts may then be associated with such definitions using the mechanisms described in sections .

- -

Using these situational parameters, an informal domestic +

Using these situational parameters, an informal domestic conversation might be characterized as follows: - - informal face-to-face conversation - each text represents a continuously +informal face-to-face conversationeach text represents a continuously recorded interaction among the specified participants - - - plans for coming week, local affairs - mostly factual, some jokes - - - - - + plans for coming week, local affairsmostly factual, some jokes

-

The following example demonstrates how the same situational +

The following example demonstrates how the same situational parameters might be used to characterize a novel: - - print; part issues - - - - - - - - - +print; part issues

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
The Participant Description - -

The particDesc element in the profileDesc element + + + + + + + + + + +

+
+ The Participant Description +

The particDesc element in the profileDesc element provides additional information about the participants in a spoken text or, where this is judged appropriate, the persons named or depicted in a written text. When the detailed elements provided by @@ -598,15 +379,14 @@ other personal characteristics. Individually identified persons may also identified by a code which can then be used elsewhere within the encoded text, for example as the value of a who attribute.

- -

It should be noted that although the terms speaker or +

It should be noted that although the terms speaker or participant are used throughout this section, it is intended that the same mechanisms may be used to characterize fictional personæ or voices within a written text, except where otherwise stated. For the purposes of analysis of language usage, the information specified here should be equally applicable to written, spoken, or signed texts.

-

The element particDesc contains a description of the +

The element particDesc contains a description of the participants in an interaction, which may be supplied as straightforward prose, possibly containing a list of names, encoded using the usual list and name elements, or @@ -614,63 +394,38 @@ alternatively using the more specific and detailed listPerson element provided by the namesdates module described in .

-

For example, a participant in a recorded conversation might be +

For example, a participant in a recorded conversation might be described informally as follows: - -

Female informant, well-educated, born in Shropshire UK, 12 Jan +

Female informant, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. - Socio-Economic status B2 in the PEP classification scheme.

-

- -

Alternatively, when the namesdates module + Socio-Economic status B2 in the PEP classification scheme.

+

Alternatively, when the namesdates module is included in a schema, information about the same participant described above might be provided in a more structured way as follows: - - - 12 Jan 1950 - Shropshire, UK - - - English - French - - Long term resident of Hull - University postgraduate - Unknown - -

-

An identified character in a drama or a novel may also be regarded +12 Jan 1950Shropshire, UKEnglishFrenchLong term resident of HullUniversity postgraduateUnknown

+

An identified character in a drama or a novel may also be regarded as a participant in this sense, and encoded using the same techniques:It is particularly useful to define participants in a dramatic text in this way, since it enables the who attribute to be used to link sp elements to definitions for their speakers; see further section . - -

The chief speaking characters in this novel are - - Emma Woodhouse - Mr Darcy - - -

- +

The chief speaking characters in this novel are + Emma WoodhouseMr Darcy +

Here, the characters are simply listed without the detailed structure which use of the listPerson element permits.

- -
-
-The Setting Description -

The settingDesc element is used to describe the setting or +

+
+ The Setting Description +

The settingDesc element is used to describe the setting or settings in which language interaction takes place. It may contain a prose description, analogous to a stage description at the start of a play, stating in broad terms the locale, or a more detailed description of a series of such settings.

-

Each distinct setting is described by means of a setting +

Each distinct setting is described by means of a setting element. - - - + Individual settings may be associated with particular participants by @@ -684,105 +439,39 @@ to apply to all participants represented in the language interaction. Note however that it is not possible to encode different settings for the same participant: a participant is deemed to be a person within a specific setting.

-

The setting element may contain either a prose description +

The setting element may contain either a prose description or a selection of elements from the classes model.nameLike.agent, model.dateLike, or model.settingPart. By default, when the module defined by this chapter is included in a schema, these classes thus provide the following elements: - - - - - - - + Additional more specific naming elements such as orgName or persName may also be available if the namesdates module is also included in the schema.

-

The following example demonstrates the kind of background information +

The following example demonstrates the kind of background information often required to support transcriptions of language interactions, first encoded as a simple prose narrative: - -

The time is early spring, 1989. P1 and P2 are playing on the rug +

The time is early spring, 1989. P1 and P2 are playing on the rug of a suburban home in Bedford. P3 is doing the washing up at the sink. P4 (a radio announcer) is in a broadcasting studio in - London.

- + London.

The same information might be represented more formally in the following way: - - - Bedford - UK: South East - early spring, 1989 - rug of a suburban home - playing - - - Bedford - UK: South East - early spring, 1989 - at the sink - washing-up - - - London, UK - - broadcasting studio - radio performance - -

-

Again, a more detailed encoding for places is feasible if the +BedfordUK: South Eastearly spring, 1989rug of a suburban homeplayingBedfordUK: South Eastearly spring, 1989at the sinkwashing-upLondon, UKbroadcasting studioradio performance

+

Again, a more detailed encoding for places is feasible if the namesdates module is included in the schema. The above examples assume that only the general purpose name element supplied in the core module is available. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-
Associating Contextual + +

+
+
+
+ Associating Contextual Information with a Text -

This section discusses the association of the contextual information +

This section discusses the association of the contextual information held in the header with the individual elements making up a TEI text or corpus. Contextual information is held in elements of various kinds within the TEI header, as discussed elsewhere in this section and in @@ -793,19 +482,18 @@ uses a different encoding practice from another, or where one part relates to a different setting from another. In such situations, there will be more than one instance of a header element of the relevant type.

-

The TEI scheme allow for the following possibilities: - -A given element may appear in the corpus header only, in the -header of one or more texts only, or in both places -There may be multiple occurrences of certain elements in either +

The TEI scheme allow for the following possibilities: +A given element may appear in the corpus header only, in the +header of one or more texts only, or in both placesThere may be multiple occurrences of certain elements in either the corpus or a text header.

-

To simplify the exposition, we deal with these two possibilities +

To simplify the exposition, we deal with these two possibilities separately in what follows; however, they may be combined as desired.

-
Combining Corpus and Text Headers -

A TEI-conformant document may have more than one header only in the +

+ Combining Corpus and Text Headers +

A TEI-conformant document may have more than one header only in the case of a TEI corpus, which must have a header in its own right, as well as the obligatory header for each text. Every element specified in a corpus-header is understood as if it appeared within every text header @@ -814,7 +502,7 @@ corpus header supplements the specification for that text alone. If any element is specified in both corpus and text headers, the corpus header element is over-ridden for that text alone.

-

The titleStmt for a corpus text is understood to be +

The titleStmt for a corpus text is understood to be prefixed by the titleStmt given in the corpus header. All other optional elements of the fileDesc should be omitted from an individual corpus text header unless they differ from those @@ -825,56 +513,16 @@ header each piece of contextual information which is common to the whole of the corpus, while still allowing for individual texts to vary from this common denominator.

-

For example, the following schematic shows the structure of a corpus +

For example, the following schematic shows the structure of a corpus comprising three texts, the first and last of which share the same encoding description. The second one has its own encoding description. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-
Declarable Elements - -

Certain of the elements which can appear within a TEI header are + +

+
+
+ Declarable Elements +

Certain of the elements which can appear within a TEI header are known as declarable elements. These elements have in common the fact that they may be linked explicitly with a particular part of a text header or the corpus header by means of a decls attribute on @@ -882,97 +530,34 @@ that element. This linkage is used to over-ride the default association between declarations in the header and a corpus or corpus text. The only header elements which may be associated in this way are those which would not otherwise be meaningfully repeatable.

-

Declarable elements are all members of the class att.declarable; the corresponding declaring +

Declarable elements are all members of the class att.declarable; the corresponding declaring elements are all members of the class att.declaring. - - - -

+

+

An alphabetically ordered list of declarable elements follows: -

An alphabetically ordered list of declarable elements follows: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + Each of the above elements is repeatable within a single header; that is, there may be more than one instance of any declarable element type at a given level. When this occurs, the following rules apply. For each different type of declarable element which occurs more than once: - -each must bear a unique identifier -when occurring within the same parent element, exactly one element must be +each must bear a unique identifierwhen occurring within the same parent element, exactly one element must be specified as the default, by having a default attribute with the value "true".

-

In the following example, an editorial declaration contains two +

In the following example, an editorial declaration contains two possible correction policies, one identified as CorPol1 and the other as CorPol2. Since there are two, one of them (in this case CorPol1) should be -specified as the default: - -

...

- - -

...

- - -

...

-

...

- - For texts associated with the header in which +specified as the default:

...

...

...

...

For texts associated with the header in which this declaration appears, correction method CorPol1 will be assumed, unless they explicitly state otherwise. Here is the -structure of a text in which a division states otherwise: - - - - - - In this case, the contents of the divisions D1 and D3 +structure of a text in which a division states otherwise: In this case, the contents of the divisions D1 and D3 will both use correction policy CorPol1, and those of division D2 will use correction policy CorPol2.

-

The decls attribute is defined for any element which is a +

The decls attribute is defined for any element which is a member of the class declaring. This includes the major structural elements text, group, and div, as well as smaller structural units, down to the level of paragraphs in @@ -981,38 +566,18 @@ dictionaries. However, TEI recommended practice is to limit the number of multiple declarable elements used by a document as far as possible, for simplicity and ease of processing.

-

The identifier or identifiers to which the decls +

The identifier or identifiers to which the decls attribute points must follow two further restrictions: - -When decl references an element that itself contains multiple +When decl references an element that itself contains multiple elements of the same type, only the children elements with default -set to "true" are considered referenced. -Each element specified, explicitly or implicitly, by the list of +set to "true" are considered referenced.Each element specified, explicitly or implicitly, by the list of identifiers must be of a different kind.

-

To demonstrate how these rules operate, we now expand our earlier +

To demonstrate how these rules operate, we now expand our earlier example slightly: - - - - -

...

- -

...

- -

...

-

...

- - - -

...

-

...

-

...

-

...

- - +

...

...

...

...

...

...

...

...

-

This encoding description now has two editorial declarations, +

This encoding description now has two editorial declarations, identified as ED1 (the default) and ED2. For texts not specifying otherwise, ED1 will apply. If ED1 applies, correction method C1A and normalization method N1 apply, since these are the specified defaults @@ -1021,7 +586,7 @@ within ED1. In the same way, for a text specifying decls and normalization N2B will apply.

-

A finer grained approach is also possible. A text might specify +

A finer grained approach is also possible. A text might specify text decls='#C2B #N2A', to mix and match declarations as required. A tag such as text decls='#ED1 #ED2' would @@ -1030,35 +595,32 @@ a tag such as text decls='#ED2 #C1A' is also illegal, since in this context #ED2 is synonymous with the defaults for that editorial declaration, namely #C2A #N2B, resulting in a list that identifies two correction elements (C1A and C2A). -

-
Summary -

The rules determining which of the declarable elements are applicable +

+
+
+ Summary +

The rules determining which of the declarable elements are applicable at any point may be summarized as follows: - -If there is a single occurrence of a given declarable +If there is a single occurrence of a given declarable element in a corpus header, then it applies by default to all elements -within the corpus. -If there is a single occurrence of a given declarable +within the corpus.If there is a single occurrence of a given declarable element in the text header, then it applies by default to all elements -of that text irrespective of the contents of the corpus header. -Where there are multiple occurrences of declarable elements +of that text irrespective of the contents of the corpus header.Where there are multiple occurrences of declarable elements within a text’s header or its corpus header, - -each must have a unique value specified as the value -of its xml:id attribute; -one and only one must bear a default attribute with - the value true (or 1). -It is a semantic error for an element to be associated -with more than one occurrence of any declarable element. -Selecting an element which contains multiple occurrences of a +each must have a unique value specified as the value +of its xml:id attribute;one and only one must bear a default attribute with + the value true (or 1).It is a semantic error for an element to be associated +with more than one occurrence of any declarable element.Selecting an element which contains multiple occurrences of a given declarable element is semantically equivalent to selecting only -those contained elements which are specified as defaults. -An association made by one element applies by default +those contained elements which are specified as defaults.An association made by one element applies by default to all of its descendants. -

-
Linguistic Annotation of Corpora -

Language corpora often include analytic encodings or annotations, +

+
+
+
+ Linguistic Annotation of Corpora +

Language corpora often include analytic encodings or annotations, designed to support a variety of different views of language. The present Guidelines do not advocate any particular approach to linguistic annotation (or tagging); instead a number of @@ -1071,8 +633,9 @@ Guidelines.See in particular chapters , , and . The present section presents informally some particular applications of these general mechanisms to the specific practice of corpus linguistics.

-
Levels of Analysis -

By linguistic annotation we mean here any annotation +

+ Levels of Analysis +

By linguistic annotation we mean here any annotation determined by an analysis of linguistic features of the text, excluding as borderline cases both the formal structural properties of the text (e.g. its division into chapters or paragraphs) and descriptive @@ -1085,7 +648,7 @@ The contextual properties of a TEI text are fully documented in the TEI header, which is discussed in chapter , and in section of the present chapter.

-

Other forms of linguistic annotation may be applied at a number of +

Other forms of linguistic annotation may be applied at a number of levels in a text. A code (such as a word-class or part-of-speech code) may be associated with each word or token, or with groups of such tokens, which may be continuous, discontinuous, or nested. A code may @@ -1097,7 +660,7 @@ to place the annotated part of the text somewhere within a narrowly linguistic or discoursal domain of analysis, or within a more general semantic field, or any combination drawn from these and other domains.

-

The manner by which such annotations are generated and attached to +

The manner by which such annotations are generated and attached to the text may be entirely automatic, entirely manual, or a mixture. The ease and accuracy with which analysis may be automated may vary with the level at which the annotation is attached. The method employed should @@ -1106,12 +669,14 @@ description of the TEI header, as described in section . W annotation methods, the decls attribute should be used to indicate the fact, as further discussed in section .

-

An extended example of one form of linguistic analysis commonly +

An extended example of one form of linguistic analysis commonly practised in corpus linguistics is given in section .

-
-
Recommendations for the Encoding of Large Corpora -

These Guidelines include proposals for the identification and +

+
+
+ Recommendations for the Encoding of Large Corpora +

These Guidelines include proposals for the identification and encoding of a far greater variety of textual features and characteristics than is likely to be either feasible or desirable in any one language corpus, however large and ambitious. The reasoning @@ -1124,44 +689,30 @@ and change the names of existing elements. A discussion of the implications of such changes for TEI conformance is provided in chapter .

-

Because of the high cost of identifying and encoding many textual +

Because of the high cost of identifying and encoding many textual features, and the difficulty in ensuring consistent practice across very large corpora, encoders may find it convenient to divide the set of elements to be encoded into the following four categories: - -texts included within the corpus will always +texts included within the corpus will always encode textual features in this category, should they exist in the -text -textual features in this category will be +texttextual features in this category will be encoded wherever economically and practically feasible; where present -but not encoded, a note in the header should be made. -textual features in this category may or may not +but not encoded, a note in the header should be made.textual features in this category may or may not be encoded; no conclusion about the absence of such features can be inferred from the absence of the corresponding element in a given -text. - -textual features in this category are deliberately not encoded; they may be +text.textual features in this category are deliberately not encoded; they may be transcribed as unmarked up text, or represented as gap elements, or silently omitted, as appropriate. -

-
-
- Module for Language Corpora -

The module described in this chapter makes available the +

+
+
+ Module for Language Corpora +

The module described in this chapter makes available the following components: - - Metadata for Language Corpora - Corpus texts - Corpus linguistiques - 文集文本 - Corpus di testi - Textos do corpora - コーパスモジュール - + Metadata for Language CorporaCorpus textsCorpus linguistiques文集文本Corpus di testiTextos do corporaコーパスモジュール The selection and combination of modules to form a TEI schema is described in .

+
- -
\ No newline at end of file diff --git a/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml b/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml index 42b275d759..55299585a1 100644 --- a/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml +++ b/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml @@ -1,42 +1,30 @@ - + -
Certainty, Precision, and Responsibility -

Encoders of text often find it useful to indicate that some aspects +

+ Certainty, Precision, and Responsibility +

Encoders of text often find it useful to indicate that some aspects of the encoded text are problematic or uncertain, and to indicate who is responsible for various aspects of the markup of the electronic text. These Guidelines provide several methods of recording uncertainty about the text or its markup: - -the note element defined in section may +the note element defined in section may be used with a value of certainty for its type -attribute. -the certainty element defined in this chapter may be used +attribute.the certainty element defined in this chapter may be used to record the nature and degree of the uncertainty in a more structured -way. -the precision element defined in this chapter may be +way.the precision element defined in this chapter may be used to record the accuracy with which some numerical value (such as a -date or quantity) is provided by some other element or attribute. -the alt element defined in the module for +date or quantity) is provided by some other element or attribute.the alt element defined in the module for linking and segmentation may be used to provide alternative encodings for parts of a text, as described in section . There are three methods of indicating responsibility for different aspects of the electronic text: - -the TEI header records who is responsible for an electronic text +the TEI header records who is responsible for an electronic text by means of the respStmt element and other more specific elements (author, sponsor, funder, principal, etc.) used within the titleStmt, editionStmt, and -revisionDesc elements. -the note element may be used with a value of resp -or responsibility in its type attribute. -the respons element defined in this chapter may be used +revisionDesc elements.the note element may be used with a value of resp +or responsibility in its type attribute.the respons element defined in this chapter may be used to record fine-grained structured information about responsibility for individual tags in the text. No special steps are needed to use the note and respStmt elements, since they are defined in the core module and header @@ -46,50 +34,41 @@ chapter . To use the certainty, precision o respons elements, the module for certainty and responsibility should be selected.

- -

These three elements are all members of an attribute class called +

These three elements are all members of an attribute class called att.scoping from which they inherit the following attributes: - - - +

-

These attributes enable statements about certainty, precision, or +

These attributes enable statements about certainty, precision, or responsibility to be made with respect to the whole of a document, or any part or parts of it which can be identified using standard XML location methods. Several examples are given in the discussion of the certainty element below; the same mechanisms are available for all three elements discussed in this chapter.

-
Levels of Certainty -

Many types of uncertainty may be distinguished. The +

+ Levels of Certainty +

Many types of uncertainty may be distinguished. The certainty element is designed to encode the following sorts: - -a given tag may or may not correctly apply (e.g. a given word may -be a personal name, or perhaps not) -the precise point at which an element begins or ends is -uncertain -the value given for an attribute is uncertain -the content given for an element is unreliable for any reason.

-

The following types of uncertainty are not indicated +a given tag may or may not correctly apply (e.g. a given word may +be a personal name, or perhaps not)the precise point at which an element begins or ends is +uncertainthe value given for an attribute is uncertainthe content given for an element is unreliable for any reason.

+

The following types of uncertainty are not indicated with the certainty element: - -the numerical precision associated with a number or date (for +the numerical precision associated with a number or date (for this use the precision element discussed in ) - -the content of the document being transcribed is identifiable, +the content of the document being transcribed is identifiable, but may be read or understood in different ways (for this use the transcriptional elements such as unclear, -discussed in chapter ) -a transcriber, editor, or author wishes to indicate a level of +discussed in chapter )a transcriber, editor, or author wishes to indicate a level of confidence in a factual assertion made in the text (for this use the -interpretative mechanisms discussed in and ) -

-
Using Notes to Record Uncertainty -

The simplest way of recording uncertainty about markup is to attach a +

+ Using Notes to Record Uncertainty +

The simplest way of recording uncertainty about markup is to attach a note to the element or location about which one is unsure. In the following (invented) paragraph, for example, an encoder might be uncertain whether to mark Essex as a place name or a personal @@ -99,23 +78,25 @@ Using note, the uncertainty here may be recorded quite simply: Elizabeth went to Essex. She had always liked Essex.It is not clear here whether Essex refers to the place or to the nobleman. -MSM

-

Using the normal mechanisms, the note may be associated +

Using the normal mechanisms, the note may be associated unambiguously with specific elements of the text, thus: Elizabeth went to Essex. She had always liked Essex.It is not clear here whether Essex refers to the place or to the nobleman. If the latter, it should be tagged as a personal name. -Michael

-

The advantage of this technique is its relative simplicity. Its +

The advantage of this technique is its relative simplicity. Its disadvantage is that the nature and degree of uncertainty are not conveyed in any systematic way and thus are not susceptible to any sort -of automatic processing.

-
Structured Indications of Uncertainty -

To record uncertainty in a more structured way, susceptible of at +of automatic processing.

+
+
+ Structured Indications of Uncertainty +

To record uncertainty in a more structured way, susceptible of at least simple automatic processing, the certainty element may be used:

-

Returning to the example, the certainty element may be used to record doubts about +

Returning to the example, the certainty element may be used to record doubts about the proper encoding of Essex in several ways of varying precision. To record merely that we are not certain that Essex is in fact a place name, as it is tagged, we use the target @@ -133,14 +114,12 @@ element, or elsewhere in the same or another document. Its position is however significant when the target attribute is not specified as further discussed below.

-

We may wish to record the probability, assessed in some subjective +

We may wish to record the probability, assessed in some subjective way, that Essex really is a place name here. The degree attribute is used to indicate the degree of confidence associated with the certainty element, expressed as a number between 0 and 1: - - - + This expresses the point of view that there is a 60 percent chance of Essex being a place name here, and hence a 40 percent chance of its being a personal name. We can use two certainty elements to indicate the @@ -148,14 +127,8 @@ two probabilities independently. Both elements indicate the same location in the text, but the second provides an alternative choice of name identifier (in this case persName), which is given as the value of the assertedValue attribute: - - - - probably a placename, but possibly not - - may refer to the Earl of Essex

- -

In the simplest case, it is also possible to place the +probably a placename, but possibly notmay refer to the Earl of Essex

+

In the simplest case, it is also possible to place the certainty element within the element concerned: Elizabeth went to @@ -165,10 +138,9 @@ When no target is specified, by default the proposed certainty applies to its parent element, in this case the placeName element. The match attribute discussed below may be used to further vary this behaviour.

- -
Contingent Conditions - -

Finally, we may wish to make our probability estimates contingent +

+ Contingent Conditions +

Finally, we may wish to make our probability estimates contingent on some condition. In the passage Elizabeth went to Essex; she had always liked Essex, for example, we may feel there is a 60 percent chance that the county is meant, and a 40 percent chance that the earl is meant. But @@ -182,17 +154,13 @@ She had always liked Essex. - - probably a placename, but possibly not" - - may refer to the Earl of Essex" +probably a placename, but possibly not" +may refer to the Earl of Essex" - - if CE-PL1 is a placename, CE-PL2 certainly is" - - if CE-PL1 is a personal name, then so is CE-PL2 +if CE-PL1 is a placename, CE-PL2 certainly is" +if CE-PL1 is a personal name, then so is CE-PL2 When given conditions are listed, the certainty element is interpreted as claiming a given degree of confidence in a particular markup given the assertional content of the @@ -200,8 +168,7 @@ particular markup given the assertional content of the assertion is being made solely on the assumption that the interpretation indicated by the element named by the given attribute is actually correct.

- -

Conditional confidence may be less than 100 percent: given the sentence +

Conditional confidence may be less than 100 percent: given the sentence Ernest went to old Saybrook, we may interpret Saybrook as a personal name or a place name, assigning a 60 percent probability to the former. If it is a place name, there may be a 50 percent chance that the @@ -222,8 +189,7 @@ Note the use of the assertedValue on certainty elements cert3 and cert4 to reference the anchor element placed at the alternative starting point for the element.

- -

Multiplying the numeric values out, this markup may be interpreted as +

Multiplying the numeric values out, this markup may be interpreted as assigning specific probabilities to three different ways of marking up the sentence: Ernest went to old Saybrook. (0.6 * 0.9, or 0.54) @@ -235,9 +201,10 @@ that if Saybrook is (part of) a personal name, there is a place indicated, without however giving an alternative location; there is thus a 6 percent chance (0.1 × 0.6) that none of the alternatives given is correct.

-
-
Pervasive Conditions -

We may also wish to indicate confidence in some aspect +

+
+ Pervasive Conditions +

We may also wish to indicate confidence in some aspect of the tagging throughout a document, rather than (as discussed so far) in one particular instance. The match attribute may be used to supply a pattern identifying the portion of a document @@ -248,9 +215,7 @@ example, we wish to indicate a low degree of confidence that the persName elements used throughout the whole document have been correctly applied: - - - + No target has been supplied here, and so by default the certainty expressed would therefore apply to the parent @@ -258,21 +223,14 @@ element. However, in this case the XPath supplied as the value for match returns a set of all the persName elements in the document, independent of the current context. By contrast, in the following example - -

[...]

-
- -
- +

[...]

 only the persName elements within the second div element are in question. Similarly, we may indicate that we have more confidence in the persName tagging within those div elements which have a type value of checked: - - - + If an element in a document is matched by more than one match expression, then the most specific pattern applies. Specificity of @@ -288,47 +246,38 @@ first one (in document order) is applied. Only those statements of certainty which have matched in this sense are available for conditional application using the given attribute mentioned above.

-

When the match attribute is processed, the namespace bindings in +

When the match attribute is processed, the namespace bindings in force are those in effect at that point in the document. For example, - -

- - -
- +
 might be used to indicate a high degree of certainty about the content of any elements taken the namespace associated with the prefix my. This namespace prefix must be associated with an appropriate namespace definition, either on the certainty element itself, or on one of its ancestor elements.

-
- -
Content Uncertainty - -

Doubts about whether the content of an element is correct may also be expressed +

+
+ Content Uncertainty +

Doubts about whether the content of an element is correct may also be expressed by assigning to locus the value value. For example, if the source is hard to read and so the transcription is uncertain: I have a bun.

-

Degrees of confidence in the proper expansion of abbreviations may +

Degrees of confidence in the proper expansion of abbreviations may also be expressed, as in the following example:You will want to use Standard -Generalized Markup Language -Some Grandiose Methodology for Losers -SGML ... +Generalized Markup LanguageSome Grandiose Methodology for LosersSGML ...

-

The assertedValue attribute should be used to provide an +

The assertedValue attribute should be used to provide an alternative value for whatever aspect of the markup is in doubt: an alternative name, or the identifier of an alternative starting or ending point, as already shown, an alternative attribute value, or alternative element content, as in this example: I have a bun. - - a gun makes more sense in a holdup +a gun makes more sense in a holdup Since attribute values have no internal substructure, the assertedValue attribute is not generally useful for specifying alternative transcriptions; it cannot for example be used @@ -339,12 +288,10 @@ alternative element content, as in this example: certainty element allows for indications of uncertainty to be structured with at least as much detail and clarity as appears to be currently required in most ongoing text projects.

-
- - -
Target or Match? - -

As noted in , the target attribute +

+
+ Target or Match? +

As noted in , the target attribute may take any general teidata.pointer as values and may thus also contain an XPath expression of arbitrary complexity. Because full support for XPath is not provided by current processors, it is not @@ -357,81 +304,59 @@ syntactically much simpler than the equivalent xpath2 expression //*[@xml:id='A'] and is hence preferred throughout these guidelines.

-

For similar reasons, the certainty element may specify +

For similar reasons, the certainty element may specify both a target value (expressed as an URI) and a match value (expressed as an XPath). The former defines the context within which the latter is to be evaluated. As previously noted, if no value is supplied for target, the context within which the value of match should be evaluated is the parent element of the certainty element itself.

- -

A typical case where it may be convenient to specify both +

A typical case where it may be convenient to specify both target and match is that where we wish to indicate that the value of an attribute on some specific element is uncertain. In this case, the locus attribute takes the value value. For example, supposing there is only a 50 percent chance that the question was spoken by participant A: -Have you heard the election results? - or, equivalently and without the +Have you heard the election results? or, equivalently and without the need to define a target, -Have you heard the election results? - +Have you heard the election results?

- -

The match and target attributes together +

The match and target attributes together provide a powerful mechanism which can be used to indicate precision for a large number of assertions throughout an encoded document in an economical way. Some further examples follow: - - - + This encoding indicates that there is only a 0.2 certainty that the boundaries of all p elements in the document have been correctly identified.

-

- - - +

This encoding indicates that there is only a 0.2 certainty that the boundaries of the p elements contained by the element with xml:id value a101 have been correctly identified.

-

- - -Essex +

Essex This encoding indicates that there is only a 0.2 certainty that the value for the resp attribute on the given persName element is correct.

-

- - - +

This encoding indicates that there is only a 0.2 certainty that any value for the resp attribute is correct, wherever it appears in the document.

- -

- - +

This encoding indicates that there is only a 0.2 certainty that the value for the resp attribute of the element indicated by the pointer #dd001 is correct

- -

- - +

This encoding indicates that there is only a 0.2 certainty that the content of any element the resp attribute of which has the value #LB is correct, wherever it appears in the document.

- -

The certainty element and the other TEI mechanisms for +

The certainty element and the other TEI mechanisms for indicating uncertainty provide a range of methods of graduated complexity. Simple expressions of uncertainty may be made by using the note element. This is simple and convenient, and can @@ -442,7 +367,7 @@ are taken, the note element does not provide as much expressive power as the certainty element, and in cases where highly structured certainty information are needed, it is recommended that the certainty element be preferred.

- - - - - -
-
- -
- -
Indications of Precision -

As noted above, certainty about the accuracy of an encoding or its + + + + + +

+
+
+
+ Indications of Precision +

As noted above, certainty about the accuracy of an encoding or its content is not the same thing as the precision with which a value is specified. In the case of a date or a quantity, for example, we might be certain that the value given is imprecise, or uncertain @@ -471,31 +396,27 @@ about whether or not the value given is correct. The latter possibility would be represented by the certainty element discussed in the previous section; the former by the precision element discussed in this section.

-

The elements concerning which statements of precision are to be +

The elements concerning which statements of precision are to be made are identified using the same target and match attributes inherited from the att.scoping class discussed in the previous section and in the same way. Other aspects are provided by other attributes as further discussed below. - - - +

-

In several ways of indicating ranges of +

In several ways of indicating ranges of values were introduced. For example, if we know that a date falls between 1930 and 1935, without being certain exactly where, this fact may be encoded using attributes notBefore and notAfter, as in the following example: - -Early in the 1930s... +Early in the 1930s... Equally, if we know that every page of a manuscript has a width of at least 10 cm but no more than 30, we can use the attributes atLeast and atMost, as in the following examples: - - +

-

Suppose however that the precision with which the value +

Suppose however that the precision with which the value of such an attribute can be specified is variable. For example, suppose an event is dated about fifty years after the death of Augustus. In this case, the precision of one end of the range (the @@ -503,38 +424,29 @@ death of Augustus) is higher than the other, assuming we know when Augustus died. We can say that the latest possible date is probably 50 years after that, but with less confidence than we can attach to the earliest possible date.

-

The precision element allows us to indicate the two +

The precision element allows us to indicate the two attributes concerned and attach different levels of precision to them, using a similar mechanism as that provided for the certainty element: - -About 50 -years after the death of Augustus - - -

-

In much the same way, we may wish to indicate different levels of +About 50 +years after the death of Augustus

+

In much the same way, we may wish to indicate different levels of precision about the dating of either end of a historical period. For example, the elements defined for encoding personal data all bear a similar set of attributes to indicate normalized values for earliest or latest dates, etc. (see section ); the precision of these attribute values may be indicated in exactly the same way. For example, - -From the 1st of March to +From the 1st of March to some time in April of 1857. - - +

-

It may also be useful to indicate that the precisions given for +

It may also be useful to indicate that the precisions given for minimum and maximum quanta differ. For example, to indicate that all pages measure at least 10 cm wide, and at most about 30: - - - - +

-

The +

The stdDeviation attribute may be used to indicate the standard deviation for a range of values. The generic dim element introduced in might be used to record the average @@ -542,26 +454,23 @@ number of characters per line in a typescript. If in addition we wish to record the standard deviation for the values summarized by that average, this would require an additional precision element, as in the following example: - - - - +

-
- -
Attribution of Responsibility -

In general, attribution of responsibility for the transcription and +

+
+ Attribution of Responsibility +

In general, attribution of responsibility for the transcription and markup of an electronic text is made by respStmt elements within the header: specifically, within the title statement, the edition statement(s), and the revision history.

-

In some cases, however, more detailed element-by-element information +

In some cases, however, more detailed element-by-element information may be desired. For example, an encoder may wish to distinguish between the individuals responsible for transcribing the content and those responsible for determining that a given word or phrase constitutes a proper noun. Where such fine-grained attribution of responsibility is required, the respons element can be used.

-

This element allows one or more aspects of the markup to be +

This element allows one or more aspects of the markup to be attributed to a given individual. This element inherits the target and match attributes from the att.scoping class, in the same way as the @@ -570,7 +479,7 @@ attributed to a given individual. This element inherits the certainty element (see ). It inherits the resp and cert attributes from the att.global.responsibility class.

-

For example, the following encoding +

For example, the following encoding indicates that RC is responsible for transcribing an illegible word, and that PMWR is responsible for identifying that word as a proper noun, i.e. deciding to mark it with the persName @@ -580,37 +489,26 @@ element at the location indicated: - - - -

-

Similarly, in the following example, we indicate that RC is +

+

Similarly, in the following example, we indicate that RC is responsible for proposing the value of the rend attribute: - - - +

- - -
- -
The Certainty Module -

The module described in this chapter makes available the following + + + +

+
+ The Certainty Module +

The module described in this chapter makes available the following additional elements: - - Certainty and Uncertainty - Certainty, Precision, and Responsibility - Degré de certitude et responsabilité - 確定程度與不確定程度 - Certezza e incertezza - Certeza e incerteza - 確信度モジュール - +Certainty and UncertaintyCertainty, Precision, and ResponsibilityDegré de certitude et responsabilité確定程度與不確定程度Certezza e incertezzaCerteza e incerteza確信度モジュール The selection and combination of modules to form a TEI schema is described in .

-
\ No newline at end of file +
+
diff --git a/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml b/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml index e87690893b..90ec365a4e 100644 --- a/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml +++ b/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml @@ -1,22 +1,16 @@ - + -
-Languages and Character Sets -

The documents which users of these Guidelines may wish to encode +

+ Languages and Character Sets +

The documents which users of these Guidelines may wish to encode encompass all kinds of material, potentially expressed in the full range of written and spoken human languages, including the extinct, the non-existent, and the conjectural. Because of this wide scope, special attention has been paid to two particular aspects of the representation of linguistic information often taken for granted: language identification and character encoding.

-

Even within a single document, material in many different languages +

Even within a single document, material in many different languages may be encountered. Human culture, and the texts which embody it, is intrinsically multilingual, and shows no sign of ceasing to be so. Traditional philologists and modern computational linguists alike work @@ -28,7 +22,7 @@ documentation of endangered languages, is one aspect of this long standing tradition. Because of their historical importance, the needs of endangered and even extinct languages must be taken into account when formulating Guidelines and recommendations such as these.

-

Beyond the sheer number and diversity of human languages, it should +

Beyond the sheer number and diversity of human languages, it should be remembered that in their written forms they may deploy a huge variety of scripts or writing systems. These scripts are in turn composed of smaller units, which for simplicity we term here @@ -38,7 +32,7 @@ not only the constituent characters, but also the language and script. In this c address this requirement, and propose recommended mechanisms to indicate the languages, scripts and characters used in a document or a part thereof.

-

Identification of language is dealt with in . In summary, it recommends the use of pre-defined +

Identification of language is dealt with in . In summary, it recommends the use of pre-defined identifiers for a language where these are available, as they increasingly are, in part as a result of the twin pressures of an increasing demand for language-specific software and an increased @@ -46,7 +40,7 @@ interest in language documentation. Where such identifiers are not available or not standardized, these Guidelines recommend a method for documenting language identifiers and their significance, in the same way as other metadata is documented in the TEI header.

-

Standardization of the means available to represent characters and +

Standardization of the means available to represent characters and scripts has moved on considerably since the publication of the first version of these Guidelines. At that time, it was essential to explicitly document the characters and encoded character sets used by @@ -63,20 +57,16 @@ this chapter discusses in some detail the concepts and practice underlying this standard, and also introduces the methods available for extending beyond it, which are more fully discussed in .

- -
Language Identification - -

Identification of the language a document or part thereof is +

+ Language Identification +

Identification of the language a document or part thereof is written in is a crucial requirement for many envisioned usages of an electronic document. The TEI therefore accommodates this need in the -following way: - A global attribute xml:lang is defined for all TEI +following way:A global attribute xml:lang is defined for all TEI elements. Its value identifies the language and writing system - used. - The TEI header has a section set aside for the information - about the languages used in a document: see further . -

-

The value of the attribute xml:lang identifies the + used.The TEI header has a section set aside for the information + about the languages used in a document: see further .

+

The value of the attribute xml:lang identifies the language (and, optionally, script) using a coded value. For maximal compatibility with existing processes, the identifier for the language must be constructed as in Best Current Practice 47Currently @@ -86,8 +76,7 @@ documents may succeed these as the best current practice.. This same identifier has to be used to identify the corresponding language element in the TEI header, if one is present.

-

The first part of BCP 47 is called Tags for Identifying + <p>The first part of BCP 47 is called <ref target="#CH-BIBL-4"><title>Tags for Identifying Languages, and proposes the following mechanism for constructing an identifier (tag) for languages as administered by the Internet Assigned Numbers Authority (IANA). The tag is assembled from @@ -95,15 +84,12 @@ a sequence of subtags separated by the hyphen (-, U+002D) character. It gives the language (possibly further identified with a sublanguage), a script, and a region for the language, each possibly followed by a variant subtag.

-

The authoritative list of registered subtags is maintained by IANA -and is available at . +

The authoritative list of registered subtags is maintained by IANA +and is available at . For a good general overview of the construction of language tags, see -, -and for a practical step-by-step guide, see .

-

In addition to the list of registered subtags, BCP 47 provides +, +and for a practical step-by-step guide, see .

+

In addition to the list of registered subtags, BCP 47 provides extensions that can be employed by private convention. The constructs provided can thus be used to generate identifiers for any language, past and present, in any usage in any area of the world. If such @@ -111,8 +97,7 @@ private extensions are used within the context of the TEI, they should be documented within the language element of the TEI header, which might also provide a prose description of the language described by the language tag.

- -

While language, region, and script can be adequately identified +

While language, region, and script can be adequately identified using this mechanism, there is only very rough provision to express a dimension of time for the language of a document; those codes provided (e.g. grc for Greek, Ancient (to 1453)) might not @@ -121,20 +106,19 @@ might express the time window of the language used in the document by means of the extension mechanism defined in BCP 47 and relate that to a date element in the corresponding language section of the TEI header.

-

Equivalences to language identifiers by other authorities can be +

Equivalences to language identifiers by other authorities can be given in the language section as well, but no formal mechanism for doing so has been defined.

-

The scope of the language identification extends to the whole +

The scope of the language identification extends to the whole subtree of the document anchored at the element that carries the xml:lang attribute, including all elements and those -attributes, if any, where a language might apply.This excludes all attributes where a non-textual +attributes, if any, where a language might apply.This excludes all attributes where a non-textual datatype has been specified, for example tokens, boolean values, -dates, and predefined value lists.

- +dates, and predefined value lists.

+
- Characters and Character Sets -

All document encoding has to do with representing one thing by + Characters and Character Sets +

All document encoding has to do with representing one thing by another in an agreed and systematic way. Applied to the smallest distinctive units in any given writing system, which for the moment we may loosely call characters, such representation @@ -142,10 +126,10 @@ dates, and predefined value lists.

are partly historical and partly to do with conceptual unclarities about what is involved in identifying, encoding, processing and rendering the characters of a natural - language.

-
- Historical Considerations -

When the first methods of representing text for storage or + language.

+
+ Historical Considerations +

When the first methods of representing text for storage or transmission by machines were devised, long before the development of computers, the overriding aim was to identify the smallest set of symbols needed to convey the essential semantic @@ -157,8 +141,8 @@ dates, and predefined value lists.

regulate the storage and transmission devices. Such encodings, originally developed for telegraphy, strongly influenced the way the pioneers of computing conceived of and implemented the - handling of text, with consequences that are with us still.

-

For many years after the invention of computers, the way they + handling of text, with consequences that are with us still.

+

For many years after the invention of computers, the way they represented text continued to be constrained by the imperative to use expensive resources with maximal efficiency. Even when storage and processing costs began their dramatic fall, the @@ -174,7 +158,7 @@ dates, and predefined value lists.

character sets, joined with computer manufacturers and software houses to devise ways of mapping those character sets to numeric encodings and processing the resulting text data.

-

Unfortunately, in the early years there was little or no +

Unfortunately, in the early years there was little or no co-ordination among either the national standards bodies or the manufacturers concerned, so that although commercial necessity dictated that these various local standards were all compatible @@ -193,8 +177,8 @@ dates, and predefined value lists.

from basic Latin script. Many of the earliest projects that fed into the TEI were shaped in this developmental phase of the computerized representation of texts, and it was also the - context in which SGML was devised and finalized.

-

SGML had of necessity to offer ways of coping with multiple + context in which SGML was devised and finalized.

+

SGML had of necessity to offer ways of coping with multiple writing systems in multiple representations; or rather, it provided a framework within which SGML-compliant applications capable of handling such multiple representations might be @@ -208,19 +192,24 @@ dates, and predefined value lists.

as an international standard, and the emergence of XML and related technologies which are committed to the theory and practice of character representation which Unicode embodies. -

-
Terminology and Key - Concepts

Before the significance of Unicode and the +

+
+
+ Terminology and Key + Concepts +

Before the significance of Unicode and the implications of the association between XML and Unicode can be adequately explained, it is necessary to clarify some key concepts and attempt to establish an adequately precise - terminology for them.

-

- - Examples of the latin a, in both lower and upper case, rendered with different fonts. - Examples of the latin a, in both lower and upper case, rendered with different fonts. -

-

+ terminology for them.

+

+

+ + Examples of the latin a, in both lower and upper case, rendered with different fonts. + Examples of the latin a, in both lower and upper case, rendered with different fonts. +
+

+

The word character will not of itself take us very far towards greater terminological precision. It tends to be used to refer indiscriminately both to the visible symbol on a @@ -247,7 +236,7 @@ dates, and predefined value lists.

standing for the same abstract character. The distinction between abstract characters and glyphs is fundamental to all machine processing of documents.

-

In most scholarly encoding projects, the accurate recording of +

In most scholarly encoding projects, the accurate recording of the abstract characters which make up the text is of prime importance, because it is the essential prerequisite of digitizing and processing the document without semantic loss. In @@ -261,7 +250,7 @@ dates, and predefined value lists.

sufficient information to allow an exact visual representation of the glyphs in the source text or manuscript to be recreated.

-

The importance of this distinction between information content +

The importance of this distinction between information content and its visual representation is not always immediately apparent to people unused to the specific complexities of text handling by machine. Such users tend to ask first what (in order of @@ -278,8 +267,8 @@ dates, and predefined value lists.

immediate rendering wishes at the price of making their underlying document unintelligible to other users (or even to the original user in other times and places) because it encodes - the abstract character in an idiosyncratic way.

-

That said, there will certainly be documents or projects where + the abstract character in an idiosyncratic way.

+

That said, there will certainly be documents or projects where it is a matter of scholarly significance that the compositor or scribe chose to represent a given abstract character using one particular glyph or set of strokes rather than a @@ -289,8 +278,8 @@ dates, and predefined value lists.

in most cases will not) involve a notation that visually resembles the original, any more than italicized text in an original document will be represented by the use of italic - characters in the encoded version.

-

A collection of the abstract characters needed to represent + characters in the encoded version.

+

A collection of the abstract characters needed to represent documents in a given writing system is known as a character set, and the character set or character repertoire of a processing or @@ -310,7 +299,7 @@ dates, and predefined value lists.

assigned a numerical code point (or in some instances a sequence of code points) which unambiguously identifies the character concerned.

-

It is now possible to use this terminology to +

It is now possible to use this terminology to say what Unicode is: it is a coded character set, devised and actively maintained by an international public body, where each abstract character is identified by a unique name and assigned a @@ -327,11 +316,12 @@ dates, and predefined value lists.

from its status as an international public standard; and, perhaps most importantly, the fact that today it is implemented by almost every provider of hardware and software platforms - worldwide.

-
- Abstract Characters, Glyphs, and Encoding Scheme - Design -

The distinction between abstract characters and glyphs can be + worldwide.

+
+
+ Abstract Characters, Glyphs, and Encoding Scheme + Design +

The distinction between abstract characters and glyphs can be crucial when devising an encoding scheme. When performing searches, text retrieval, or creating concordances, users of electronic text will expect the system to recognize and treat @@ -342,19 +332,16 @@ dates, and predefined value lists.

letter or symbol is a character or a glyphic variant. The Unicode Consortium and an ISO work group (ISO/IEC JTC1 SC2/WG2) have developed a detailed model of the relationship - between characters and glyphs. This model, presented in Unicode Technical + between characters and glyphs. This model, presented in Unicode Technical Report 17: Character Encoding Model, is the underpinning of much standards work since, including the current chapter.

-

The model makes explicit the distinction between two different +

The model makes explicit the distinction between two different properties of the components of written language: - - their content, i.e. its meaning and phonetic value - (represented by characters) their graphical - appearance (represented by glyphs). - -

-

When searching for information, a system generally operates +their content, i.e. its meaning and phonetic value + (represented by characters)their graphical + appearance (represented by glyphs). +

+

When searching for information, a system generally operates on the content aspects of characters, with little or no attention to their appearance. A layout or formatting process, on the other hand, must of necessity be concerned with the exact @@ -363,16 +350,13 @@ dates, and predefined value lists.

feature, but in general the kind of text encoding described in these Guidelines tends to focus on content rather than appearance (see further ).

-

An encoder wishing to record information about which glyphs +

An encoder wishing to record information about which glyphs are present in a given document may do so at either or both of two levels: - - the level of character encoding, using an appropriate - Unicode code point to represent the glyph concerned - the markup level, with the glyph indicated via - appropriate elements or attributes -

-

The encoding practice adopted may be guided by, among other +the level of character encoding, using an appropriate + Unicode code point to represent the glyph concerned the markup level, with the glyph indicated via + appropriate elements or attributes

+

The encoding practice adopted may be guided by, among other things, an assessment of the most frequent uses to which the encoded text will be put. For example, if recognition of identical characters represented by a variety of glyphs is the @@ -387,17 +371,17 @@ dates, and predefined value lists.

such choices be documented in the TEI header. Such documentation cannot of itself guarantee proper display of the desired glyph but at least makes the intention of the encoder - discoverable.

-

At present the Unicode Standard does not offer detailed + discoverable.

+

At present the Unicode Standard does not offer detailed specifications for the encoding of glyph variations. These Guidelines do give some recommendations; some discussion of related matters is given in , and offers some features for the definition of variant - glyphs.

- -
- Entry of Characters -

The entry of characters was much more complicated before the near-universal + glyphs.

+
+
+ Entry of Characters +

The entry of characters was much more complicated before the near-universal adoption of Unicode, for which there are Input Method Editors (IMEs) available in most languages and fonts that provide glyphs for the full range of the Unicode specification. In those rare situations where there is @@ -413,17 +397,16 @@ dates, and predefined value lists.

anything but readable and it is all too easy for the wrong character to be entered in error and retained undetected. Where characters are not defined in Unicode, these Guidelines provide advice - on the strategies available for handling their representation in Chapter 25 Representation of non-standard Characters and + on the strategies available for handling their representation in Chapter 25 Representation of non-standard Characters and Glyphs.

- -
- Output of Characters -

The rendering of the encoded text is a complicated process that +

+
+ Output of Characters +

The rendering of the encoded text is a complicated process that depends largely on the purpose, external requirements, local equipment and so forth, it is thus outside the scope of coverage for these Guidelines.

-

It might however nevertheless be helpful to put some of the +

It might however nevertheless be helpful to put some of the terminology used for the rendering process in the context of the discussion of this chapter. As was mentioned above, Unicode encodes abstract characters, not specific glyphs. For any @@ -440,7 +423,7 @@ dates, and predefined value lists.

follows specific rules of how to calculate the distance between characters, how much whitespace occurs between words, at which points line breaks might occur and so forth.

-

If we concern ourselves only with the rendering process of the +

If we concern ourselves only with the rendering process of the characters themselves, leaving out all these other parameters, we will realize that of all the information required for this process, only a small amount will be drawn from the encoded text itself. This @@ -453,7 +436,7 @@ dates, and predefined value lists.

ligatures where necessary) and the language or even area this character is printed for to accommodate different typesetting traditions and differences in the usage of glyphs.

-

A TEI document might provide some of the information that is +

A TEI document might provide some of the information that is required for this process, for example by identifying the linguistic context with the xml:lang attribute. The selection of fonts and sizes is usually done in a stylesheet, @@ -464,10 +447,11 @@ dates, and predefined value lists.

Web Consortium provides recommendations for two standard stylesheet languages: either CSS or XSL could be used for this purpose.

- -
Unicode and - XML -

XML was designed with Unicode in mind as its means of representing +

+
+ Unicode and + XML +

XML was designed with Unicode in mind as its means of representing abstract characters. It is possible to use other character encoding schemes, but in general they are best avoided, as you run the risk of encountering compatibility issues with different XML processors, @@ -479,13 +463,13 @@ dates, and predefined value lists.

is in UTF-8 format. Doing so merely means that processors will treat the content therein as if it were UTF-8, and may fail to process the document if it is not. For further discussion of UTF-8, see the - section below on .

- -
- Special Aspects of Unicode Character Definitions -
- Compatibility Characters -

The principles of Unicode are judiciously tempered with + section below on .

+
+
+ Special Aspects of Unicode Character Definitions +
+ Compatibility Characters +

The principles of Unicode are judiciously tempered with pragmatism. This means, among other things, that the actual repertoire of characters which the standard encodes, especially those parts dating from its earlier days, include a number of @@ -526,11 +510,12 @@ dates, and predefined value lists.

of glyphs, and indexing and retrieval software will need to treat it as such. Where a digraph occurs in a source text, it should normally be encoded using the appropriate code point for - the single abstract character which it represents.

-
- Precomposed and Combining Characters and - Normalization -

The treatment of characters with + the single abstract character which it represents.

+
+
+ Precomposed and Combining Characters and + Normalization +

The treatment of characters with diacritical marks within Unicode shows a similar combination of rigour and pragmatism. It is obvious enough that it would be feasible to represent many characters with diacritical marks in @@ -570,8 +555,8 @@ dates, and predefined value lists.

discusses normalization issues and outlines some relevant principles. An authoritative reference is Unicode Standard Annex #15 Unicode Normalization Formsavailable at - .

-

It is important that every Unicode-based project should agree + .

+

It is important that every Unicode-based project should agree on, consistently implement, and fully document a comprehensive and coherent normalization practice. As well as ensuring data integrity within a given project, a consistently implemented and properly @@ -581,10 +566,10 @@ dates, and predefined value lists.

will provide mechanisms for converting between normalization forms, so it is easy in practice to ensure that all documents in a project are in a consistent form, even if different methods are used to enter data.

- -
- Character Semantics -

In addition to the Universal Character Set itself, the +

+
+ Character Semantics +

In addition to the Universal Character Set itself, the Unicode Consortium maintains a database of additional character semantics. This includes names for each character code point and normative @@ -594,7 +579,7 @@ dates, and predefined value lists.

needed for correctly processing this character for different purposes. It is an important reference in determining which Unicode code point to use to encode a certain character.

-

In addition to the printed documentation and lists made +

In addition to the printed documentation and lists made available by the Unicode consortium, the information it contains may also be accessed by a number of search systems over the Web (e.g. ). Examples of @@ -607,12 +592,12 @@ dates, and predefined value lists.

in the PUA, it is desirable that any relevant additional information about the characters concerned should be recorded in an analogous way, as further discussed under .

- - -
- Issues Arising from the Internal Representations of - Unicode -

In theory it should not be necessary for encoders to have any +

+ +
+ Issues Arising from the Internal Representations of + Unicode +

In theory it should not be necessary for encoders to have any knowledge of the various ways in which Unicode code points can be represented internally within a document or in the memory of a processing system, but experience shows that problems @@ -627,10 +612,10 @@ dates, and predefined value lists.

Internationalization document, Choosing & applying a character encoding at -

-
- Encoding Errors Related to UTF-8 -

The code points assigned by Unicode 3.0 and later are +

+
+ Encoding Errors Related to UTF-8 +

The code points assigned by Unicode 3.0 and later are notionally 32-bit integers, and the most straightforward way to represent each such integer in computer storage would be to use 4 eight-bit bytes. However, many of the code points for @@ -641,7 +626,8 @@ dates, and predefined value lists.

two bytes alone. This accounts for the use of UTF-8 and UTF-16 and their special place in the XML standard. UTF-8 and UTF-16 are ways of representing 32-bit code points in an economical - way.

UTF-8 is a variable length encoding: the more + way.

+

UTF-8 is a variable length encoding: the more significant bits there are in the underlying code point (or in everyday terminology the bigger the number used to represent the character), the more bytes UTF-8 uses to encode it. What @@ -656,7 +642,7 @@ dates, and predefined value lists.

encoding being explicitly declared: the processor will regard it as being in the UTF-8 representation of Unicode and be able to handle it correctly on that basis.

-

However, even within the domain of Latin-based scripts, some +

However, even within the domain of Latin-based scripts, some projects have documents which use characters from 8 bit extensions to ASCII, e.g. those in the ISO-8859-n series of encodings, and the way characters which under ISO-8859-n use @@ -676,7 +662,7 @@ dates, and predefined value lists.

the underlying code-point value, many of the single-byte eight-bit values employed in ISO-8859-n encodings are illegal in UTF-8.

-

This complicated situation has a simple consequence which can +

This complicated situation has a simple consequence which can cause great bewilderment. XML processors will effortlessly handle character data in pure 7-bit ASCII without that encoding needing to be declared to the parser, and will similarly accept @@ -696,7 +682,7 @@ dates, and predefined value lists.

smattering of French words). These types of error may or may not manifest in actual processing errors, and may only become visible as garbage characters in the eventual display of documents.

-

In projects that routinely handle documents in non-Latin +

In projects that routinely handle documents in non-Latin scripts, everyone is well aware of the need to ensure correct and consistent encoding, so in such places mixed encoding problems seldom arise, and when they do are readily identified @@ -714,7 +700,8 @@ dates, and predefined value lists.

these encoding issues and develop procedures which assure consistency and integrity of encoding and its correct declaration, including the use of appropriate software for - transcoding and verification.

+ transcoding and verification.

+ - + diff --git a/P5/Source/Guidelines/en/CO-CoreElements.xml b/P5/Source/Guidelines/en/CO-CoreElements.xml index 8ee380d944..eee1df0ce2 100644 --- a/P5/Source/Guidelines/en/CO-CoreElements.xml +++ b/P5/Source/Guidelines/en/CO-CoreElements.xml @@ -1,15 +1,9 @@ - +
-Elements Available in All TEI Documents -

This chapter describes elements which may appear in any kind of text + Elements Available in All TEI Documents +

This chapter describes elements which may appear in any kind of text and the tags used to mark them in all TEI documents. Most of these elements are freely floating phrases, which can appear at any point within the textual structure, although they should generally be contained @@ -21,40 +15,35 @@ own. In the general case, they contain only a few words, and are often identifiable in a conventionally printed text by the use of typographic conventions such as shifts of font, use of quotation or other punctuation marks, or other changes in layout.

-

This chapter begins by describing the p tag used to mark +

This chapter begins by describing the p tag used to mark paragraphs, the prototypical formal unit for running text in many TEI modules. This is followed, in section , by a discussion of some specific problems associated with the interpretation of conventional punctuation, and the methods proposed by these Guidelines for resolving ambiguities therein.

- -

The next section (section ) describes a number +

The next section (section ) describes a number of phrase-level elements commonly marked by typographic features (and thus well-represented in conventional markup languages). These include features commonly marked by font shifts (section ) and features commonly marked by quotation marks (section ) as well as such features as terms, cited words, and glosses (section ).

- -

Section introduces some phrase-level elements +

Section introduces some phrase-level elements which may be used to record simple editorial interventions, such as emendation or correction of the encoded text. The elements described here constitute a simple subset of the full mechanisms for encoding such information (described in full in chapter ), which should be adequate to most commonly encountered situations.

- -

The next section (section ) describes several +

The next section (section ) describes several phrase-level and inter-level elements which, although often of interest for analysis or processing, are rarely explicitly identified in conventional printing. These include names (section ), numbers and measures (section ), dates and times (section ), abbreviations (section ), and addresses (section ).

- -

In the same way, the following section (section ) presents only a subset of the facilities available +

In the same way, the following section (section ) presents only a subset of the facilities available for the encoding of cross-references or text-linkage. The full story may be found in chapter ; the tags presented here are intended to be usable for a wide variety of simple applications.

- -

Sections , and , describe +

Sections , and , describe two kinds of quasi-structural elements: lists and notes. These may appear either within chunk-level elements such as paragraphs, or between them. Several kinds of lists are catered for, of an arbitrary @@ -62,43 +51,43 @@ complexity. The section on notes discusses both notes found in the source and simple mechanisms for adding annotations of an interpretive nature during the encoding; again, only a subset of the facilities described in full elsewhere (specifically, in chapter ) is discussed.

-

Section introduces some simple ways of +

Section introduces some simple ways of representing graphic or other non-textual content found in a text. A fuller discussion of the multimedia facilities supported by these Guidelines may be found in chapters and .

-

Next, section , describes methods of +

Next, section , describes methods of encoding within a text the conventional system or systems used when making references to the text. Some reference systems have attained canonical authority and should be recorded to make the text useable in normal work; in other cases, a convenient reference system should be created by the creator or analyst of an electronic text.

-

Like lists and notes, the bibliographic citations discussed in +

Like lists and notes, the bibliographic citations discussed in section , may be regarded as structural elements in their own right. A range of possibilities is presented for the encoding of bibliographic citations or references, which may be treated as simple phrases within a running text, or as highly-structured components suitable for inclusion in a bibliographic database.

-

Additional elements for the encoding of passages of verse or drama +

Additional elements for the encoding of passages of verse or drama (whether prose or verse) are discussed in section .

-

The chapter concludes with a technical overview of the structure and +

The chapter concludes with a technical overview of the structure and organization of the module described here. This should be read in conjunction with chapter , describing the structure of -the TEI document type definition.

-
Paragraphs -

Paragraphs in modern printed or online text are typically visually +the TEI document type definition.

+
+ Paragraphs +

Paragraphs in modern printed or online text are typically visually offset with whitespace or an indented first line. But paragraphs are not simply blocks of text. The paragraph may be thought of as a mid-level unit of sense, a coherent grouping of sentences. Paragraphs may, in turn, be grouped into larger divisions, such as chapters. Because it is a unit of sense rather than simply a block of text, the p element in TEI may contain other structures displayed as blocks, such as lists or quotes. - This distinguishes it from the p + This distinguishes it from the p element in HTML, which is primarily a block of text, and from the ab (anonymous block) element described in which may be used as an alternative to the paragraph in cases that require a chunk-level container which is not necessarily a sense unit and which may have different structural properties.

-

The paragraph can be understood in the context of the distinct forms of textual +

The paragraph can be understood in the context of the distinct forms of textual division discussed in : chunk, phrase, and inter-level. Chunk-level elements are paragraphs and other elements which have similar @@ -111,25 +100,24 @@ the TEI document type definition.

organization is still needed. ab may contain other abs, may use the type attribute, and does not necessarily represent a coherent set of statements.

-

Paragraphs can contain many of the other elements described within this chapter, +

Paragraphs can contain many of the other elements described within this chapter, as well as other elements which are specific to individual text types. Because paragraphs may appear in different customizations, their possible contents may vary in different kinds of documents. In particular, additional elements not listed in this chapter may appear in paragraphs. However, the elements described in this chapter are available in all kinds of text unless they are excluded by a customization.

-

The paragraph is marked using the p element: +

The paragraph is marked using the p element:

-

If a consistent internal subdivision of paragraphs is desired, the +

If a consistent internal subdivision of paragraphs is desired, the s or seg (segment) elements may be used, as discussed in chapters and respectively. More usually, however, paragraphs have no firm internal structure, but contain prose encoded as a mix of characters, entity references, phrases marked as described in the rest of this chapter, and embedded elements like lists, figures, or tables.

-

The following example demonstrates a basic application of the p tag for an indented passage in a printed book: - -

It is in vain to say human beings ought to be satisfied with tranquillity: +

The following example demonstrates a basic application of the p tag for an indented passage in a printed book: +

It is in vain to say human beings ought to be satisfied with tranquillity: they must have action; and they will make it if they cannot find it. Millions are condemned to a stiller doom than mine, and millions are in silent revolt against their lot. Nobody knows how many rebellions besides political rebellions ferment @@ -140,23 +128,19 @@ embedded elements like lists, figures, or tables.

it is narrow-minded in their more privileged fellow-creatures to say that they ought to confine themselves to making puddings and knitting stockings, to playing on the piano and embroidering bags. It is thoughtless to condemn them, or laugh at them, if they - seek to do more or learn more than custom has pronounced necessary for their sex.

- + seek to do more or learn more than custom has pronounced necessary for their sex.

-

This news story shows typically short journalistic paragraphs: +

This news story shows typically short journalistic paragraphs: SARAJEVO, Bosnia and Herzegovina, April 19

Serbs seized more territory in this struggling new country today as the United States Air Force ended a two-day airlift of humanitarian - aid into the capital, Sarajevo.

-

International relief workers called on European Community nations + aid into the capital, Sarajevo.

International relief workers called on European Community nations to step up their humanitarian aid to the former Yugoslav republic, - in conjunction with new American aid flights if necessary.

-

A special envoy from the European Community, Colin Doyle, harshly + in conjunction with new American aid flights if necessary.

A special envoy from the European Community, Colin Doyle, harshly condemned the decision by Serbs to shell Sarajevo on Saturday night during a visit to the Bosnian capital by a senior American official, - Deputy Assistant Secretary of State Ralph R. Johnson.

-

...

+ Deputy Assistant Secretary of State Ralph R. Johnson.

...

-

The following extract from a Russian fairy tale demonstrates +

The following extract from a Russian fairy tale demonstrates how other phrase level elements (in this case q elements representing direct speech; see section ) may be nested within, but not across, paragraphs: @@ -165,28 +149,24 @@ There came to the castle the Crawling Louse. Who, who's in the castle? Who, who's in your house? said the Crawling Louse. I, I, the Languishing Fly. And who art thou?I'm the Crawling Louse. -

-

Then came to the castle the Leaping Flea. Who, +

Then came to the castle the Leaping Flea. Who, who's in the castle? said the Leaping Flea. I, I, the Languishing Fly, and I, the Crawling Louse. And who art thou?I'm the Leaping Flea. -

-

Then came to the castle the Mischievous Mosquito. +

Then came to the castle the Mischievous Mosquito. Who, who's in the castle? said the Mischievous Mosquito. I, I, the Languishing Fly, and I, the Crawling Louse, and I, the Leaping Flea. And who art thou?I'm the Mischievous Mosquito.

- - - - - -
-
Treatment of Punctuation - -

Punctuation marks cause two distinct classes of problem for text + + + +

+
+ Treatment of Punctuation +

Punctuation marks cause two distinct classes of problem for text markup: the marks may not be available in the character set used, and they may be significantly ambiguous. To some extent, the availability of @@ -206,16 +186,15 @@ character) may be used to mark it explicitly, as further discussed in . Where the character used for a punctuation mark is not available in Unicode, the g element and other facilities described in chapter may also be used to mark its presence.

- -
Functions of Punctuation - -

Punctuation is itself a form of markup, historically introduced to +

+ Functions of Punctuation +

Punctuation is itself a form of markup, historically introduced to provide the reader with an indication about how the text should be read. As such, it is unsurprising that encoders will often wish to encode directly the purpose for which punctuation was provided, as well as, or even instead of, the punctuation itself. We discuss some typical cases below.

-

The Full stop (period) +

The Full stop (period) may mark (orthographic) sentence boundaries, abbreviations, decimal points, or serve as a visual aid in printing numbers. These usages can be distinguished by tagging S-units, abbreviations, and numbers, as @@ -224,7 +203,7 @@ and respectively. However, there are independent reasons for tagging these, whether or not they are marked by full stops, and the polysemy of the full stop itself is perhaps no different from that of any other character in the writing system.

-

The Question mark +

The Question mark and exclamation mark usually mark the end of orthographic sentences, but may also be used as a mid-sentence comment by the author (! to express @@ -234,20 +213,18 @@ Such usages may be distinguished by marking S-units, in which case the mid-sentence uses of these punctuation marks may be left unmarked, or tagged using the pc element discussed in .

-

Dashes are used for a variety of +

Dashes are used for a variety of purposes: as a mark of omission, insertion, or interruption; to show where a new speaker takes over (in dialogue); or to introduce a list item. In the latter two cases particularly, it is clearly desirable to mark the function as well as its rendition using the elements q or item, on which see section , and section , respectively.

- -

Quotation marks may be removed from +

Quotation marks may be removed from text contained by q or quote elements on editorial grounds, or they may be marked in a variety of ways; see the discussion of quotation and related features in section .

- -

Apostrophes should be distinguished from +

Apostrophes should be distinguished from single quote marks. As with hyphens, this disambiguation is best performed by selecting the appropriate Unicode character, though it may also be represented by using appropriate XML markup for quotations as @@ -255,22 +232,21 @@ suggested above. However, apostrophes have a variety of uses. In English they mark contractions, genitive forms, and (occasionally) plural forms. Full disambiguation of these uses belongs to the level of linguistic analysis and interpretation.

-

Parentheses +

Parentheses and other marks of suspension such as dashes or ellipses are often used to signal information about the syntactic structure of a text fragment. Full disambiguation of their uses also belongs to the level of linguistic analysis and interpretation, and will therefore need to use the mechanisms discussed in chapter .

-

Where punctuation marks are disambiguated by tagging their assumed +

Where punctuation marks are disambiguated by tagging their assumed function in the text (for example, quotation), it may be debated whether they should be excluded or left as part of the text. In the case of quotation marks, it may be more convenient to distinguish opening from closing marks simply by using the appropriate Unicode character than to use the q element, with or without an indication of rendition.

- -

Where segmentation of a text is performed automatically, the +

Where segmentation of a text is performed automatically, the accuracy of the result may be considerably enhanced by a first pass in which the function of different punctuation characters is explicitly marked. This need not be done for all cases, but only where the @@ -285,13 +261,11 @@ is available (or using the g element where it is not) or by an explicit encoding using pc. The particular method adopted will vary depending upon the feature concerned and upon the purpose of the project. -

- -
- -
Hyphenation - -

Hyphenation as a phenomenon is generally of most concern when +

+
+
+ Hyphenation +

Hyphenation as a phenomenon is generally of most concern when producing formatted text for display in print or on screen: different languages and systems have developed quite sophisticated sets of rules about where hyphens may be introduced and for what reason. These @@ -307,8 +281,7 @@ reasons. The hard hyphen (U+2010) is distinguished from the minus sign also from the soft hyphen (U+00AD) which may appear in born digital documents to indicate places where it is acceptable to insert a hyphen when the document is formatted.

- -

Historically, the hard hyphen has been used in printed or +

Historically, the hard hyphen has been used in printed or manuscript documents for two distinct purposes. In many languages, it is used between words to show that they function as a single syntactic or lexical unit. For example, in French, est-ce @@ -324,8 +297,7 @@ lexical item is spelled. Deciding whether a compound is to be decomposed into its constituent parts, and if so how, is a different question, involving consideration of many other phenomena in addition to the simple presence of a hyphen.

- -

When it appears at the end of a printed or written line however, +

When it appears at the end of a printed or written line however, the hard hyphen generally indicates that—contrary to what might be expected—a word is not yet complete, but continues on the next line (or over the next page or column or other boundary). The hyphen @@ -341,15 +313,12 @@ like this: is ambiguous: there is no simple way of deciding which of the two spellings was intended.

- -

As elsewhere, therefore, encoders have a range of choices: - -They +

As elsewhere, therefore, encoders have a range of choices: +They may decide simply to remove any end-of-line hyphenation from the encoded text, on the grounds that its presence is purely a secondary matter of formatting. This will obviously apply also if line endings -are themselves regarded as unimportant. -Alternatively, they may decide to record the presence of the +are themselves regarded as unimportant.Alternatively, they may decide to record the presence of the hyphen, perhaps on the grounds that it provides useful morphological information; perhaps in order to retain information about the visual appearance of the original source. In either case, they need to decide @@ -363,13 +332,11 @@ appropriate symbolic value for one or more of the attributes on the For example, the example above could be encoded with a force value of "inter" to indicate that the punctuation mark may or may not be a word separator (See also ). tea-pot - - + A similar range of possibilities applies equally to the representation of other common punctuation marks, notably quotation marks, as discussed in .

- -

The text data of which XML documents are +

The text data of which XML documents are composed is decomposable into smaller units, here called orthographic tokens, even if those units are not explicitly indicated by the XML markup. The ambiguity of the @@ -385,8 +352,7 @@ breaking. However, it is generally unsafe to assume that whitespace adjacent to markup tags will always be preserved, and it is decidedly unsafe to assume that markup tags themselves are equivalent to whitespace.

- -

The lb, pb, and cb elements are notable +

The lb, pb, and cb elements are notable exceptions to this general rule, since their function is precisely to represent (or replace) line, page, or column breaks, which, as noted above, are generally considered to be equivalent to whitespace. These @@ -394,8 +360,7 @@ elements provide a more reliable way of preserving the lineation, pagination, etc of a source document, since the encoder should not assume that (untagged) line breaks etc. in an XML source file will necessarily be preserved.

- -

To control the intended tokenization, the encoder may use the +

To control the intended tokenization, the encoder may use the break attribute on such elements to indicate whether or not the element is to be regarded as equivalent to whitespace. This attribute can take the values yes or no to @@ -404,8 +369,7 @@ boundary. The value maybe is also available, for cases where the encoder does not wish (or is unable) to determine whether the orthographic token concerned is broken by the line ending.

- -

As a final complication, it should be noted that in some languages, +

As a final complication, it should be noted that in some languages, particularly German and Dutch, the spelling of a word may be altered in the presence of end of line hyphenation. For example, in Dutch, the word opaatje (granddad), @@ -421,12 +385,11 @@ as such it may be encoded using the choice element discussed in , or the more sophisticated mechanisms for linguistic analysis discussed in chapter .

-
-
- - -
Highlighting and Quotation -

This section deals with a variety of textual features, all of +

+
+
+ Highlighting and Quotation +

This section deals with a variety of textual features, all of which have in common that they are frequently realized in conventional printing practice by the use of such features as underlining, italic fonts, or quotation marks, collectively referred to here as @@ -434,14 +397,12 @@ fonts, or quotation marks, collectively referred to here as phenomenon and alternate approaches to encoding it, this section describes ways of encoding the following textual features, all of which are conventionally rendered using some kind of highlighting: - -emphasis, foreign words and other linguistically distinct uses -of highlighting -representation of speech and thought, quotation, etc. -technical terms, glosses, etc. +emphasis, foreign words and other linguistically distinct uses +of highlightingrepresentation of speech and thought, quotation, etc.technical terms, glosses, etc.

-
What Is Highlighting? -

By highlighting we mean the use of any +

+ What Is Highlighting? +

By highlighting we mean the use of any combination ofhighlighting typographic features (font, size, hue, etc.) in a printed or written text in order to distinguish some passage of a text from its surroundings.Although the way in which a spoken text is performed, @@ -455,31 +416,25 @@ characteristic of the passage highlighted; this section describes the elements recommended by these Guidelines for the encoding of such textual features.

-

In conventionally printed modern texts, highlighting is often +

In conventionally printed modern texts, highlighting is often employed to identify words or phrases which are regarded as being one or more of the following: - -distinct in some way—as foreign, dialectal, -archaic, technical, etc. -emphatic, and which would for example be stressed when spoken -not part of the body of the text, for example cross-references, -titles, headings, labels, etc. -identified with a distinct narrative stream, for example an -internal monologue or commentary. -attributed by the narrator to some other agency, either within the -text or outside it: for example, direct speech or quotation. -set apart from the text in some other way: for example, +distinct in some way—as foreign, dialectal, +archaic, technical, etc.emphatic, and which would for example be stressed when spokennot part of the body of the text, for example cross-references, +titles, headings, labels, etc.identified with a distinct narrative stream, for example an +internal monologue or commentary.attributed by the narrator to some other agency, either within the +text or outside it: for example, direct speech or quotation.set apart from the text in some other way: for example, proverbial phrases, words mentioned but not used, names of persons and places in older texts, editorial corrections or additions, etc.

-

The textual functions indicated by highlighting may not be rendered +

The textual functions indicated by highlighting may not be rendered consistently in different parts of a text or in different texts. (For example, a foreign word may appear in italics if the surrounding text is in roman, but in roman if the surrounding text is in italics.) For this reason, these Guidelines distinguish between the encoding of rendering itself and the encoding of the underlying feature expressed by it.

-

Highlighting as such may be encoded by using one of the global +

Highlighting as such may be encoded by using one of the global attributes rend, rendition, or style (see further ). This allows the encoder both to specify the function of a highlighted phrase or word, by selecting the @@ -489,12 +444,9 @@ attribute. If the encoder wishes to offer no interpretation of the feature underlying the use of highlighting in the source text, then the hi element may be used, which indicates only that the text so tagged was highlighted in some way. - - - + The hi element is provided by the model.hiLike class.

- -

The possible values carried by the rend attribute are +

The possible values carried by the rend attribute are not formally defined in this version of the Guidelines. It may be used to document any peculiarity of the way a given segment of text was rendered in the original source text, and may thus express a very @@ -508,21 +460,17 @@ fragments expressed using such a language which have been predefined in the TEI header using the rendition element discussed in section .

- -

Where it is both appropriate and feasible, these Guidelines recommend +

Where it is both appropriate and feasible, these Guidelines recommend that the textual feature marked by the highlighting should be encoded, rather than just the simple fact of the highlighting. This is for the following reasons: - -the same kind of highlighting may be used for different purposes -in different contexts -the same textual function may be highlighted in different ways in -different contexts -for analytic purposes, it is in general more useful to know the +the same kind of highlighting may be used for different purposes +in different contextsthe same textual function may be highlighted in different ways in +different contextsfor analytic purposes, it is in general more useful to know the intended function of a highlighted phrase than simply that it is distinct.

-

In many, if not most, cases the underlying function of a +

In many, if not most, cases the underlying function of a highlighted phrase will be obvious and non-controversial, since the distinctions indicated by a change of highlighting correspond with distinctions discussed elsewhere in these Guidelines. The elements @@ -532,7 +480,7 @@ of the model.emphLike class. This and the constitute the model.highlighted class, which is a phrase level class. Members of this class may appear anywhere within paragraph level elements.

-

The distinction between the two classes is simple, and typified by +

The distinction between the two classes is simple, and typified by the two elements hi and emph: the former marks simply that a passage is typographically distinct in some way, while the latter asserts that a passage is linguistically emphasized for @@ -545,17 +493,20 @@ transcription of some older materials, or in the preparation of material for the study of typographic practice). In such cases, the hi element or some other element from the model.hiLike class should be used.

-

Elements which are sometimes realized by typographic distinction but +

Elements which are sometimes realized by typographic distinction but which are not discussed in this section include title (discussed in section ) and name (discussed in section ). -

-
Emphasis, Foreign Words, and Unusual Language -

This subsection discusses the following elements: +

+
+
+ Emphasis, Foreign Words, and Unusual Language +

This subsection discusses the following elements: These elements are all members of the model.emphLike class.

-
Foreign Words or Expressions -

Words or phrases which are not in the main language of the text +

+ Foreign Words or Expressions +

Words or phrases which are not in the main language of the text should be tagged as such, at least where the fact is indicated in the text. Where the word or phrase concerned is already distinguished from the rest of the text by virtue of its function (for example, because @@ -572,8 +523,7 @@ provide a peg onto which the xml:lang may be attached. hoc? said the Bee Master. Wax-moth only succeed when weak bees let them in.

- -

The foreign element should not be used to represent foreign words +

The foreign element should not be used to represent foreign words which are mentioned or glossed within the text: for these use the appropriate element from section below. Compare the following example sentences: @@ -584,19 +534,23 @@ pronounce with your mouth full. piece of light, buttery, pastry that is usually eaten for breakfast, especially in France.

-

Elements which do not explicitly state the language of their +

Elements which do not explicitly state the language of their content by means of an xml:lang attribute are understood to inherit a value for it from their parent element. In the general case, therefore, it is recommended practice to supply a default value for xml:lang on the root TEI or text element, as further discussed in section

- - - - -
-
Emphatic Words and Phrases -

The emph element is provided to mark words or phrases + + + + + + + +

+
+ Emphatic Words and Phrases +

The emph element is provided to mark words or phrases which are linguistically emphatic or stressed. Text which is only typographically emphasized falls into the class of highlighted text, and may be tagged with the hi @@ -625,7 +579,7 @@ in a similar way: What does Christopher Robin do in the morning nowadays?

-

In cases where the rendition of a source needs to be indicated +

In cases where the rendition of a source needs to be indicated several times in a document, it may be more convenient to provide a default value using the rendition element in the header. If a small number of distinct values are required, it may also be @@ -633,17 +587,11 @@ convenient to define them all by means of a series of rendition element which can then be referenced from the elements in question by means of the global rendition attribute: Here Thou, great Anna! - whom three Realms obey, -Doth sometimes Counsel take — - and sometimes Tea. - -font-style: italic - + whom three Realms obey,Doth sometimes Counsel take — + and sometimes Tea.font-style: italic Further information on the use of the rendition element is provided at .

- - -

The hi element is used to mark words or phrases which are +

The hi element is used to mark words or phrases which are highlighted in some way, but for which identification of the intended distinction is difficult, controversial, or impossible. It enables an encoder simply to record the fact of highlighting, possibly describing @@ -655,7 +603,7 @@ representing simply typographic distinctions during a first pass, and then replacing the hi elements with more specific elements in a second pass.

-

Some simple examples: +

Some simple examples: And this Indenture further witnesseth that the said Walter Shandy, merchant, in consideration of the said intended marriage ... @@ -680,13 +628,14 @@ In a second pass, the element soCalled might be preferred as a means of indicating that the narrator is distancing himself from this usage.

- - - - -
-
Other Linguistically Distinct Material -

For some kinds of analysis, it may be desirable to encode the + + + + +

+
+ Other Linguistically Distinct Material +

For some kinds of analysis, it may be desirable to encode the linguistic distinctiveness of words and phrases with more delicacy than is allowed by the foreign element. The distinct element is provided for this purpose. Its attributes allow for @@ -697,7 +646,7 @@ phrase which assigns it to some register, sub-language, etc. No recommendations as to the set of values for this attribute are provided at this time, as little consensus exists in the field.

-

Alternatively, the remaining three attributes may be used in +

Alternatively, the remaining three attributes may be used in combination to place a word or phrase on a three-dimensional scale sometimes used in descriptive linguistics, as for example in Mattheier et al, 1988. @@ -715,7 +664,7 @@ are made for the values of these attributes at this time; the encoder should provide a description of the scheme used in the appropriate section of the header (see section ).

-

Examples: +

Examples: Next morning a boy in that dormitory confided to his bosom friend, a fag of Macrea's, that there was trouble in their midst which @@ -736,39 +685,30 @@ kinds of analysis suggested here by means of the simple annotation element note described in section , or the span element described in section .

- - - -
-
Quotation - -

One form of presentational variation found particularly frequently in + + + +

+
+
+ Quotation +

One form of presentational variation found particularly frequently in written and printed texts is the use of quotation marks. As with the typographic variations discussed in the preceding section, it is generally helpful to separate the encoding of the underlying textual feature (for example, a quotation or a piece of direct speech) from the encoding of its rendering (for example, the use of a particular style of quotation marks).

- -

This section discusses the following elements, all of which are often +

This section discusses the following elements, all of which are often rendered by the use of quotation marks: - - - - - - - - - + The elements mentioned and soCalled are members of the class model.emphLike while q stems from model.hiLike; the element said is a member of the class model.attributable in its own right, while cit and quote are members of model.quoteLike, a subclass of model.attributable. This class is a subclass of model.inter; hence all of these elements are permitted both within and between paragraph-level elements.

- -

The most common and important use of quotation marks is, of +

The most common and important use of quotation marks is, of course, to mark quotation, by which we mean simply any part of the text which the author or narrator wishes to attribute to some agency other than the narrative voice. The q element @@ -787,18 +727,17 @@ permitted both within and between paragraph-level elements.

appropriate for a case where a word or phrase is being discussed in the body of a text rather than forming part of the text directly.

-

As noted above, if the distinction among these various reasons why +

As noted above, if the distinction among these various reasons why a passage is offset from surrounding text cannot be made reliably, or is not of interest, then any representation of speech, thought, or writing may simply be marked using the q element.

-

Quotation may be indicated in a printed source by changes in type +

Quotation may be indicated in a printed source by changes in type face, by special punctuation marks (single or double or angled quotes, dashes, etc.) and by layout (indented paragraphs, etc.), or it may not be explicitly represented at all. If these characteristics are of interest, one or other of the global rend or rendition attributes discussed in section may be used to record them.

- -

Quotation marks themselves may, like other punctuation marks, be +

Quotation marks themselves may, like other punctuation marks, be felt for some purposes to be worth retaining within a text, quite independently of their description by the rend attribute. This should generally be done using the appropriate Unicode @@ -833,16 +772,14 @@ referenced using the rendition attribute as follows:

- -

Whatever policy is adopted, the encoder should document the +

Whatever policy is adopted, the encoder should document the decision in some way, for example by using the quotation element provided in the TEI header (see ) to indicate that quotation marks have not been retained in the encoding; their presence in the source is implied by the rendition attribute values supplied.

- -

Whether or not the quotation marks are suppressed, their presence +

Whether or not the quotation marks are suppressed, their presence and nature may be described using some appropriate set of conventions in the rend attribute. These conventions may be entirely idiosyncratic, and hence not necessarily useful for interchange, as @@ -855,32 +792,24 @@ attribute values supplied. the lighted tomahawk began flourishing about me in the dark.

- -

Such passages might more effectively be encoded without loss of +

Such passages might more effectively be encoded without loss of rendering information by using the rendition attribute and its associated rendition element as described in section . If the rendition of passages tagged as said is generally uniform throughout a text, then the rendition element may used to specify a default rendering, in which case the same section might simply be tagged: - -Who-e debel +Who-e debel you? — he at last said — you no speak-e, damme, I kill-e. And so saying, the lighted tomahawk began flourishing about me in the dark. - - content:"‘"; - content:"’"; - +content:"‘";content:"’";

- - - -

As members of the att.ascribed.directed class, +

As members of the att.ascribed.directed class, elements said and q share the following attributes: These may be used to make explicit who is speaking and who is being spoken to: @@ -889,13 +818,7 @@ These may be used to make explicit who is speaking and who is being spoken to: — Pas grand-chose. — Il fait beau, dit Robert. - - - Adolphe - Albert - Robert - - + AdolpheAlbertRobert The who attribute may be supplied whether @@ -909,7 +832,7 @@ These may be used to make explicit who is speaking and who is being spoken to: component of the TEI header, as further discussed in but for simple cases like the above, a simple list of speakers located in the front or back matter of the text may suffice.

-

It may also be useful to distinguish +

It may also be useful to distinguish representations of speech from representations of thought, in modern printed texts often indicated by a change of typeface. The aloud attribute is provided for this purpose, as in this @@ -919,64 +842,37 @@ These may be used to make explicit who is speaking and who is being spoken to: Analyst with Winebox! That's what you called him, you callous bastard, didn't you? Eh? Eh?

-

Quoted matter may be embedded within quoted matter, as when one +

Quoted matter may be embedded within quoted matter, as when one speaker reports the speech of another: Spaulding, he came down into the office just this day eight weeks with this very paper in his hand, and he says:— I wish to the Lord, Mr. Wilson, that I was a - red-headed man. - - - Wilson - Spaulding reported by Wilson - - + red-headed man.WilsonSpaulding reported by Wilson

-

Direct speech nested in this way is treated in the same way as +

Direct speech nested in this way is treated in the same way as elsewhere: a change of rendition may occur, but the same element should be used. An encoder may however choose to distinguish between direct speech which contains quotations from extra-textual matter and direct speech itself, as in the following example:

The Lord! The Lord! It is Sakya Muni himself, the lama half sobbed; and under his breath began the wonderful Buddhist - invocation:- - - To Him the Way — the Law — Apart — - Whom Maya held beneath her heart - Ananda's Lord — the Bodhisat - + invocation:-To Him the Way — the Law — Apart —Whom Maya held beneath her heartAnanda's Lord — the Bodhisat And He is here! The Most Excellent Law is here also. My pilgrimage is well begun. And what work! What work!

-

Quotations from other works are often accompanied by a reference to +

Quotations from other works are often accompanied by a reference to their source. The cit element may be used to group together the quotation and its associated bibliographic reference, which should be encoded using the elements for bibliographic references discussed in section , as in the following example. -

- Chapter 1 - - - Since I can do no good because a woman - Reach constantly at something that is near it. - - - The Maid's Tragedy - Beaumont and Fletcher - - -

Miss Brooke had that kind of beauty which seems to be thrown into - relief by poor dress...

-
+
Chapter 1Since I can do no good because a womanReach constantly at something that is near it.The Maid's TragedyBeaumont and Fletcher

Miss Brooke had that kind of beauty which seems to be thrown into + relief by poor dress...

 Like other bibliographic references, the citation associated with a quotation may be represented simply by a cross-reference, as in this example: Lexicography has shown little sign of being affected by the work of followers of J.R. Firth, probably best summarized - in his slogan, - You shall know a word by the company it keeps. - (Firth, 1957) - + in his slogan, You shall know a word by the company it keeps.(Firth, 1957) It is also common for quotations to be separated from their bibliographic reference by intervening text, which makes the use of cit impractical. In such circumstances, @@ -990,22 +886,16 @@ overshadows the historical content. source could also be used to point to a complete external bibliographic reference in a listBibl elsewhere in the document, or external to it.

- - -

Unlike most of the other elements discussed in this chapter, direct +

Unlike most of the other elements discussed in this chapter, direct speech and quotations may frequently contain other high-level elements such as paragraphs or verse lines, as well as being themselves contained by such elements. Three possible solutions exist for this well-known structural problem: - - the quotation is broken into segments, each of which is - entirely contained within a paragraph - the quotation is marked up using stand-off markup - the quotation boundaries are represented by empty - segment boundary delimiter elements - + the quotation is broken into segments, each of which is + entirely contained within a paragraphthe quotation is marked up using stand-off markupthe quotation boundaries are represented by empty + segment boundary delimiter elements For further discussion and several examples, see chapter .

-

Finally, in this section, the element soCalled is provided +

Finally, in this section, the element soCalled is provided for all cases in which quotation marks are used to distance the quoted text from the narrator or speaker. Common examples include the scare quotes often found in newspaper headlines and @@ -1013,7 +903,7 @@ overshadows the historical content. an assertion: PM dodges election threat in interview

-

The same element should be used to mark a variety of special ironic +

The same element should be used to mark a variety of special ironic usages. Some further examples follow: He hated good books. Croissants indeed! toast not good enough for you? @@ -1026,25 +916,24 @@ overshadows the historical content. language is necessarily restricted to finite strings.

- - - - - - - - -
- -
-
Terms and Glosses, Ruby Annotations, and Equivalents and Descriptions + + + + + + + + +
+
+
+ Terms and Glosses, Ruby Annotations, and Equivalents and Descriptions

This section describes a set of textual elements which are used to provide a gloss, alternate identification, or description of something.

- -
Terms and Glosses - -

Technical terms are often italicized or emboldened upon first mention +

+ Terms and Glosses +

Technical terms are often italicized or emboldened upon first mention in printed texts; an explanation or gloss is sometimes given in quotation marks. Linguistic analyses conventionally cite words in languages under discussion in italics, providing a gloss immediately @@ -1052,14 +941,11 @@ overshadows the historical content. individual words or phrases are mentioned (formentionvs. useusevs. mention example, as examples) rather than used may mark them either with italics or with quotation marks, and will gloss - them less regularly. - - - + them less regularly. These elements are also members of the class model.emphLike.

-

A term may appear with or without a gloss, as may a +

A term may appear with or without a gloss, as may a mentioned element. Where the gloss is present, it may be linked to the term it is glossing by means of its target attribute. To establish such a link, the encoder should give an @@ -1077,13 +963,13 @@ overshadows the historical content. parser, and much of the history of NLP over the last 20 years has been occupied with the design of parsers.

-

In the absence of a gloss in the source text, +

In the absence of a gloss in the source text, a term can also be associated with a gloss or definition by means of its ref attribute, as in this imaginary example: We discuss Leech's concept of discoursal point of view below. Here, the value #TDPV2 references some other XML element in the same document. This might be, for example, an entry in a list of technical vocabulary given in the document header, or in an appendix. This attribute could also reference an entry in some centrally maintained terminological database, perhaps using one of the pointing mechanisms discussed in section .

-

Note that the element term is intended for use with words +

Note that the element term is intended for use with words or phrases identified as terminological in nature; where words or phrases are simply being cited, discussed, or glossed in a text, it will often be more appropriate to use the mentioned element, @@ -1095,8 +981,7 @@ overshadows the historical content. second syllable of the word, and its participial derivative lutheis released, accented on the last.

- -

For technical terminology in particular, and generally in +

For technical terminology in particular, and generally in terminological studies, it may be useful to associate an instance of a term within a text with a canonical definition for it, which is stored either elsewhere in the same text (for example in a glossary of terms) @@ -1105,13 +990,13 @@ overshadows the historical content. in section below are available on the term element for this purpose.

- - - - - - -
Some Further Examples + + + + + +
+ Some Further Examples

As a simple example of the elements discussed here and in , consider the following sentence: @@ -1186,109 +1071,59 @@ overshadows the historical content. -

+

+
- -
- Ruby Annotations - -

The word ruby (or rubi) refers + Ruby Annotations +

The word ruby (or rubi) refers to a particular method of glossing runs of text which is common in East Asian scripts. In horizontally-oriented text, ruby annotations typically appear above the text being glossed, while in vertical runs of text they may appear to the left or right, or both, also oriented vertically. An English example of a ruby annotation might look like this:

-
- +
+ +

In Japanese, furigana (振り仮名) ruby annotations are often used to provide pronunciation guidance for readers; characters from the largely phonetic hiragana or katakana syllabaries accompany Chinese characters, like this:

- -
- The first line of a news story from NHK News Web Easy intended for Japanese +
+ + The first line of a news story from NHK News Web Easy intended for Japanese learners, in which every word composed of Chinese characters has a ruby gloss. -
- -

Pinyin ruby annotations are also used in Chinese to provide pronunciation guidance, +

+

Pinyin ruby annotations are also used in Chinese to provide pronunciation guidance, and Zhuyin (注音) phonetic symbols (commonly known as bopomofo) are used in Taiwan for the same purpose.

- -

The TEI schema provides many different ways of encoding glosses and annotations, from the +

The TEI schema provides many different ways of encoding glosses and annotations, from the simple and flexible note element to a native implementation of the Web Annotation Data Model (). However, ruby is a particular, distinct, and widely-used form of annotation that appears in script, print, calligraphy, and web pages, and the TEI therefore provides specific elements for it: - - - - - - The rt element is a member of att.placement, and thus the + + The rt element is a member of att.placement, and thus the place attribute may be used to indicate where the ruby gloss is with respect to the base text: - - - + The most relevant suggested values of place for ruby text are above, below, left, and right.

- -

In its simplest representation, a glossed form consists of an rb (ruby base) element containing the +

In its simplest representation, a glossed form consists of an rb (ruby base) element containing the base form, an rt (ruby text) element containing the gloss, and a ruby element which wraps them together: - -

- - - 大学 - だいがく - - -

- - +

大学だいがく

 In the example above, the word 大学 (daigaku = university) is provided with a phonation gloss in hiragana. The full gloss is applied to the complete word. However, it might instead be broken down by character: - -

- - - 大 - だい - - - 学 - がく - - -

- - +

大だい学がく

 Here is a similar example from Taiwan using bopomofo (pinyin - píngzi = bottle)Taken from Wikipedia.: - -

- - - 瓶 - ㄆㄧㄥˊ - - - 子 - ˙ㄗ - - -

- + píngzi = bottle)Taken from Wikipedia.: +

瓶ㄆㄧㄥˊ子˙ㄗ

 Where place is not provided, the default assumption is that the @@ -1297,17 +1132,13 @@ overshadows the historical content. a detailed guide to writing modes and text directionality.

- -

The same ruby base may be accompanied by more than one gloss. +

The same ruby base may be accompanied by more than one gloss. Here, the Japanese word 打球場 (dakyūba, or billiard hall) is glossed with two different pronunciations: biriādo (its English equivalent) and dakyū, a phonation guide for the first two characters. -

- - Billiard hall with two ruby glosses. - 国文学研究資料館所蔵：：英国／龍動新繁昌記. -
+
Billiard hall with two ruby glosses. + 国文学研究資料館所蔵：：英国／龍動新繁昌記.
This example is intriguing in that the right-side ruby glosses apply to the first and second characters respectively, but @@ -1318,63 +1149,23 @@ overshadows the historical content. as demonstrated for 大学 above, but with nesting: - -

- - - - - 打 - ダ - - - 球 - キウ - +

打ダ球キウ 場 - - ビリヤード - - -

- + ビリヤード

We could also use a standoff approach with anchor elements and pointers: - -

- - - - 打 +

打 球 場 - - - ビリヤード - ダ - キウ - - -

- + + ビリヤードダキウ

Alternatively, if the encoding itself already includes segmentation below the word level, we can use the existing elements instead of adding anchors: - -

- - - 打球場 - ビリヤード - ダ - キウ - - -

- +

打球場ビリヤードダキウ

 Multiple ruby annotations can appear in the same alignment relative to the main text. For example, there might be two annotations on the right. We use this instance to exemplify two ways of encoding this phenomenon, dependent on the interpretation of the text. @@ -1382,109 +1173,61 @@ overshadows the historical content. assumed to appear in their document sequence. The first of the two rt elements would appear to the right of the ruby base (rb), while the second would appear to the right of the first rt element Taken from Wikipedia.: - -

- - - ㄅ - B - 博 - - -

- +

ㄅB博

 Alternatively, a nested approach can be used. With nested ruby elements, the structure suggests that the second rt element is glossing both the rb and the rt element: - -

- - - - - ㄅ - B - - - 博 - - -

- +

ㄅB博

- - -

The rt element is a member of att.written: - - - + so the hand attribute can be used where the ruby text constitutes an annotation in a different hand from the ruby base: -

- - Base text with a ruby gloss in a different hand. - リクシ ソウモク チョウジュウ チュウギョ ソ ズカイ。 東京大学総合図書館 (General Library in the University of Tokyo, JAPAN). -
+
Base text with a ruby gloss in a different hand. + リクシ ソウモク チョウジュウ チュウギョ ソ ズカイ。 東京大学総合図書館 (General Library in the University of Tokyo, JAPAN).
- -

- - - 蘝蔓 - ヤブカラシ - +

蘝蔓ヤブカラシ 于野 -

- +

- -

The current support for ruby is rudimentary, and in future releases of the +

The current support for ruby is rudimentary, and in future releases of the Guidelines we expect to see more development of these features and recommendations. While ruby is included for use with East Asian languages, encoders may find other contexts in which these elements are useful.

- - - + +
-
Equivalents and Descriptions

Another group of elements is used to supply different kinds of names for objects described by the TEI. Examples of this are documentation of elements, attributes, classes (and also attribute values where appropriate), and description of glyphs. - - - - - + Along with the gloss element mentioned above, these elements constitute the model.identSynonyms class. They are described in more detail in .

-
- -
Simple Editorial Changes -

As in editing a printed text, so in encoding a text in electronic +

+ Simple Editorial Changes +

As in editing a printed text, so in encoding a text in electronic form, it may be necessary to accommodate editorial comment on the text and to render account of any changes made to the text in preparing it. The tags described in this section may be used to record such editorial interventions, whether made by the encoder, by the editor of a printed edition used as a copy text, by earlier editors, or by the copyists of manuscripts.

- -

The tags described here handle most common types of editorial +

The tags described here handle most common types of editorial intervention and stereotyped comment; where less structured commentary of other types is to be included, it may be marked using the note element described in section . @@ -1497,8 +1240,7 @@ of large or heterogeneous spans of text, the mechanisms described in chapter should be used. To encode multiple witnesses of a particular text, a similar mechanism designed specifically for critical editions is described in chapter .

- -

For most of the elements discussed here, some encoders +

For most of the elements discussed here, some encoders may wish to indicate both a responsibility, that is, a code indicating the person or agency responsible for making the editorial intervention in question, and also @@ -1510,22 +1252,15 @@ specifically for critical editions is described in chapter .< att.dimensions. Any of the elements discussed here thus may potentially carry any of the following optional attributes: - - - - - +

- -

Many of the elements discussed here can be used in two ways. Their +

Many of the elements discussed here can be used in two ways. Their primary purpose is to indicate that the text encoded as the element's content represents an editorial intervention (or non-intervention) of a specific kind, indicated by the element itself. However, pairs or other meaningful groupings of such elements can also be supplied, wrapped within a special purpose choice element: - - - + This element enables the encoder to represent for example a text in its original uncorrected and unaltered form, alongside the same text in one or more edited @@ -1534,35 +1269,31 @@ forms. This usage permits software to switch automatically between one a stylesheet may be set to display either the text in its original form or after the application of editorial interventions of particular kinds.

-

Elements which can be combined in this way constitute the +

Elements which can be combined in this way constitute the model.choicePart class. The default members of this class are sic, corr, reg, orig, unclear, supplied, abbr, expan, ex, am and seg; some of their functions and usage are described further below.

-

Three categories of editorial intervention are discussed in this +

Three categories of editorial intervention are discussed in this section: - -indication or correction of apparent errors -indication or regularization of variant, irregular, -non-standard, or eccentric forms -editorial additions, suppressions, and +indication or correction of apparent errors indication or regularization of variant, irregular, +non-standard, or eccentric formseditorial additions, suppressions, and omissions

-

A more extended treatment of the use of these tags in +

A more extended treatment of the use of these tags in transcriptional and editorial work is given in chapter .

-
Apparent Errors -

When the copy text is manifestly faulty, an encoder or transcriber +

+ Apparent Errors +

When the copy text is manifestly faulty, an encoder or transcriber may elect simply to correct it without comment, although for scholarly purposes it will often be more generally useful to record both the correction and the original state of the text. The elements described here enable all three approaches, and allows the last to be done in such a way as make it easy for software to present either the original or the correction. - - - - -

The following examples show alternative treatment of the same + +

+

The following examples show alternative treatment of the same material. The copy text reads: Another property of computer-assisted historical research is that data modelling must permit any one textual feature or @@ -1571,39 +1302,32 @@ model and to allow the researcher to draw on several such models simultaneously, for example, to select from a machine-readable text those marginal comments which indicate that the date's mentioned in the main body of the text are incorrect.

-

An encoder may choose to correct the typographic error, either +

An encoder may choose to correct the typographic error, either silently or with an indication that a correction has been made, as follows: … marginal comments which indicate that the dates -mentioned in the main body of the text are incorrect.

Alternatively, the encoder may simply record the typographic +mentioned in the main body of the text are incorrect.

+

Alternatively, the encoder may simply record the typographic error without correcting it, either without comment or with a sic element to indicate the error is not a transcription error in the encoding: … marginal comments which indicate that the date's -mentioned in the main body of the text are incorrect.

If the encoder elects both to record the original source text +mentioned in the main body of the text are incorrect.

+

If the encoder elects both to record the original source text and to provide a correction for the sake of word-search and other programs, both sic and corr are used, wrapped in a choice: … marginal comments which indicate that the - - dates - date's - mentioned in the main body of the text are + datesdate's mentioned in the main body of the text are incorrect.The sic and corr elements can appear in either order.

-

If it is desired to indicate the person or edition responsible for +

If it is desired to indicate the person or edition responsible for the emendation, this might be done as follows: … marginal comments which indicate that the - - dates - date's - mentioned in the main body of the text are + datesdate's mentioned in the main body of the text are incorrect. - -editor -C.M. Sperberg-McQueen - +editorC.M. Sperberg-McQueen Here the resp attribute has been used to indicate responsibility for the correction. Its value (#msm) is an @@ -1623,7 +1347,7 @@ confidence in a particular correction, as in the following example: An AutumnAntony it was, That grew the more by reaping See further the discussion in section .

-

Where, as here, the correction takes the form of adding text not otherwise +

Where, as here, the correction takes the form of adding text not otherwise present in the text being encoded, the encoder should use the corr element. Where the correction is present in the text being encoded, and consists of some combination of visible @@ -1638,13 +1362,16 @@ and other elements to support the detailed encoding of authorial or scribal interventions of this kind are all provided by the module described in chapter .

- - - - - -
Regularization and -Normalization

When the source text makes extensive use of + + + + + +

+
+ Regularization and +Normalization +

When the source text makes extensive use of variant forms or non-standard spellings, it may be desirable for a number of reasons to regularize it: that is, to provide standard or regularized @@ -1653,34 +1380,36 @@ contexts, the term regularization has a narrower and more specific significance than that proposed here: the reg element may be used for any kind of regularization, including normalization, standardization, and -modernization.

As with other such changes to the copy +modernization.

+

As with other such changes to the copy text, the changes may be made silently (in which case the TEI header should specify the types of silent changes made) or may be explicitly marked using the following elements: - - - - -

Typical applications for these elements include the production of +

+

Typical applications for these elements include the production of editions intended for student or lay readers, linguistic research in which spelling or usage variation is not the main question at issue, -production of spelling dictionaries, etc.

Consider this 16th-century text: +production of spelling dictionaries, etc.

+

Consider this 16th-century text: how godly a dede it is to overthrowe so wicked a race the world may judge: for my part I thinke there canot -be a greater sacryfice to God.

An encoder may choose to preserve the original spelling of this +be a greater sacryfice to God.

+

An encoder may choose to preserve the original spelling of this text, but simply flag it as nonstandard by using the orig element with no attributes specified, as follows:

...how godly a dede it is to overthrowe so wicked a race the world may judge: for my part I thinke there canot be a greater -sacryfice to God

Alternatively, the encoder may simply indicate that certain words +sacryfice to God

+

Alternatively, the encoder may simply indicate that certain words have been modernized by using the reg element with no attributes specified, as follows:

...how godly a deed it is to overthrow so wicked a race the world may judge: for my part I think there cannot be a greater -sacrifice to God.

Alternatively, the encoder may elect to record both old and new +sacrifice to God.

+

Alternatively, the encoder may elect to record both old and new spellings, so that (for example) the same electronic text may serve as the basis of an old- or new-spelling edition:

...how godly a dededeed it is to @@ -1688,27 +1417,23 @@ the basis of an old- or new-spelling edition: world may judge: for my part I thinkethink there canotcannot be a greater sacryficesacrifice to God.

-

As elsewhere, the resp attribute may be used to specify the agency +

+

As elsewhere, the resp attribute may be used to specify the agency responsible for the regularization.

- - - - -
-
Additions, Deletions, and Omissions -

The following elements are used to indicate when words or phrases + + + + +

+
+ Additions, Deletions, and Omissions +

The following elements are used to indicate when words or phrases have been omitted from, added to, or marked for deletion from, a text. Like the other editorial elements, they allow for a wide range of editorial practices: - - - - - - -

-

Encoders may choose to omit parts of the copy text for reasons +

+

Encoders may choose to omit parts of the copy text for reasons ranging from illegibility of the source or impossibility of transcribing it, to editorial policy, e.g. a systematic exclusion of poetry or prose from an encoding. The full details of the policy @@ -1726,7 +1451,7 @@ attributes unit and quantity, or more descriptively using the extent attribute. Other, more detailed, options are also available for representing dimensions of any kind; see further .

-

The desc element may be used to supply a description of +

The desc element may be used to supply a description of the material omitted, where that is considered useful: irrelevant commentary … Their arrangement with respect to Jupiter and to each other was as follows: @@ -1738,8 +1463,7 @@ west; …

- -

The ellipsis element provides a means to encode the +

The ellipsis element provides a means to encode the deliberate, marked omission of content in a source document. Within ellipsis, a required metamark is used to represent the characters or markings in the source that indicate the presence @@ -1750,144 +1474,80 @@ west; … when they indicate repetition of the same content, as in this example: - - - Tent supplies - - - nylon tent - - - 1 - - - - - steel stakes - - - 6 - - - - - fiberglass poles - - - - " - 6 - - - -
- -

- -

The ellipsis element may also apply to literary passages + Tent suppliesnylon tent1steel stakes6fiberglass poles"6
 +

+

The ellipsis element may also apply to literary passages that omit the full names of places or people, leaving their identities to the imagination of the reader, as in the next example. - -

I leave Dublin to-morrow for M—— house. It is situated in the county of ——, on the north-west coast of Connaught, which I am told is the classic ground of Ireland.

- +

I leave Dublin to-morrow for M—— house. It is situated in the county of ——, on the north-west coast of Connaught, which I am told is the classic ground of Ireland.

-

A manuscript of song lyrics provides a more complex example of ellipsis to encode a marked omission that begins in the middle of a verse line. -

- - A manuscript from Cancioneiro da Biblioteca Nacional +

A manuscript of song lyrics provides a more complex example of ellipsis to encode a marked omission that begins in the middle of a verse line. +

A manuscript from Cancioneiro da Biblioteca Nacional [1525-1526] in Biblioteca Nacional de Portugal, representing song lyrics and the beginning of a chorus. On the last line visible in this image, a marking of three dots and a line, ·:—, indicates that the rest of the chorus should follow - after this point. -
+ after this point.
Our encoding of the passage shows the use of ellipsis with supplied to contain the omitted content. - - - Amıgas sey eu ben dunha molher - Que se trabalha de uosco buscar - Mal a uossamigo polo matar - Mays todaquestamiga ela quer - ꜒ - Por que nunca con el pode poer - Queo podesse por amigauer - - - E buscalhi con uosco quanto mal - Ela mays pode aquesto sei eu - E todaquestela faz polo seu - E poreste pẏte non por al - ꜒ - Por que nunca - - ·:— - - con el pode poer - Queo podesse por amigauer - - - - + Amıgas sey eu ben dunha molherQue se trabalha de uosco buscarMal a uossamigo polo matarMays todaquestamiga ela quer꜒Por que nunca con el pode poerQueo podesse por amigauerE buscalhi con uosco quanto malEla mays pode aquesto sei euE todaquestela faz polo seuE poreste pẏte non por al꜒Por que nunca·:—con el pode poerQueo podesse por amigauer

-

The add and del elements may be used to record +

The add and del elements may be used to record where words or phrases have been added or deleted in the copy text. They are not appropriate where longer passages have been added or deleted, which span several elements; for these, the elements addSpan and delSpan described in chapter should be used.

-

Additions to a text may be recorded for a number of reasons. +

Additions to a text may be recorded for a number of reasons. Sometimes they are marked in a distinctive way in the source text, for example by brackets or insertion above the line (supralinear insertion),additionssupralinearinsertionssupralinearsupralinear insertions as in the following example, taken from a 19th century manuscript: The story I am going to relate is true as to its main facts, and as to the consequences of these facts from which this tale takes its title. -

The add element should not be used to mark editorial +

+

The add element should not be used to mark editorial changes, such as supplying a word omitted by mistake from the source text or a passage present in another version. In these cases, either the corr or supplied tags should be used, as discussed above in section , and in section -, respectively.

The unclear element is used to mark passages in the +, respectively.

+

The unclear element is used to mark passages in the original which cannot be read with confidence, or about which the transcriber is uncertain for other reasons, as for example when transcribing a partially inaudible or illegible source. Its reason and resp attributes are used, as with the gap element, to indicate the cause of uncertainty and the -person responsible for the conjectured reading.

For example: -And where the sandy mountain Fenwick scald -The sea between +person responsible for the conjectured reading.

+

For example: +And where the sandy mountain Fenwick scaldThe sea between yet hence his pray'r prevail'd or from a spoken text:

... and then marbled queen...

-

Where the material affected is entirely illegible or inaudible, the +

Where the material affected is entirely illegible or inaudible, the gap element discussed above should be used in preference.

-

The del element is used to mark material which is deleted in +

The del element is used to mark material which is deleted in the source but which can still be read with some degree of confidence, as opposed to material which has been omitted by the encoder or transcriber either because it is entirely illegible or for some other reason. This is of particular importance in transcribing manuscript material, though deletion is also found in printed texts, sometimes for humorous purposes: -One day I will sojourn to your shores -I live in the middle of England -But! -Norway! My soul resides in your watery -fiords fyords fiiords -Inlets. -

The rend attribute may be used to distinguish different +One day I will sojourn to your shoresI live in the middle of EnglandBut!Norway! My soul resides in your watery +fiords fyords fiiordsInlets. +

+

The rend attribute may be used to distinguish different methods of deletion in manuscript or typescript material, as in this line from the typescript of Eliot's Waste Land: Mein Frisch schwebt weht der Wind

-

Deletion in manuscript or typescript is often associated with +

Deletion in manuscript or typescript is often associated with addition: -Inviolable - Inexplicable +InviolableInexplicable splendour of Corinthian white and gold The subst element discussed in provides a way of grouping additions and deletions of this kind.

-

The del element should not be used where the deletion is +

The del element should not be used where the deletion is such that material cannot be read with confidence, or read at all, or where the material has been omitted by the transcriber or editor for some other reason. Where the material deleted cannot be read with @@ -1904,46 +1564,40 @@ be marked with the supplied and surplus elements del. These two sets of elements allow the encoder to distinguish editorial changes from those visible in the source text.

- - - - - - - - - -
-
Names, Numbers, Dates, Abbreviations, and Addresses - -

This section describes a number of textual features which it is + + + + + + + +

+
+
+ Names, Numbers, Dates, Abbreviations, and Addresses +

This section describes a number of textual features which it is often convenient to distinguish from their surrounding text. Names, dates, and numbers are likely to be of particular importance to the scholar treating a text as source for a database; distinguishing such items from the surrounding text is however equally important to the scholar primarily interested in lexis.

- -

The treatment of these textual features proposed here is not +

The treatment of these textual features proposed here is not intended to be exhaustive: fuller treatments for names, numbers, measures, and dates are provided in the names and dates module (see chapter ); more detailed treatment of abbreviations is provided by the transcription module (see section ).

- -
Referring Strings -

A referring string is a phrase which refers to some +

+ Referring Strings +

A referring string is a phrase which refers to some person, place, object, etc. Two elements are provided to mark such strings: - - - - + Both the name and rs elements are members of the att.typed class, from which they inherit the following attributes: which may be used to further categorize the kind of object referred to.

- -

Examples include: +

Examples include:

My dear Mr. Bennet, said his lady to @@ -1957,12 +1611,14 @@ cent, and gave bond.

Circumlocution Office never, on any account whatsoever, to give a straightforward answer, Mr Barnacle said, Possibly.

-

As the following example shows, the rs element may be used +

+

As the following example shows, the rs element may be used for any reference to a person, place, etc., not only to references in the form of a proper noun or noun phrase.

My dear Mr. Bennet, said his lady to him one day ...

-

The name element by contrast is provided for the special +

+

The name element by contrast is provided for the special case of referencing strings which consist only of proper nouns; it may be used synonymously with the rs element, or nested within it if a referring string contains a mixture of common and proper nouns. @@ -1974,7 +1630,7 @@ As the following example shows, a proper name may be nested within a referring string: His Excellency the Life President, Ngwazi Dr H. Kamuzu Banda

-

Simply tagging something as a name is generally not enough to +

Simply tagging something as a name is generally not enough to enable automatic processing of personal names into the canonical forms usually required for reference purposes. The name as it appears in the text may be inconsistently spelled, partial, or vague. Moreover, name @@ -1982,8 +1638,7 @@ prefixes such as van or de la may or may not be included as part of the reference form of a name, depending on the language and country of origin of the bearer.

- -

Two issues arise in this context: firstly, there may be a need to +

Two issues arise in this context: firstly, there may be a need to encode a regularized form of a name, distinct from the actual form in the source to hand; secondly, there may be a need to identify the particular person, place, etc. referred to by the name, irrespective @@ -1991,13 +1646,11 @@ of whether the name itself is normalized or not. The element reg, introduced in is provided for the former purpose; the attributes key or ref for the latter.

- -

The key and ref attributes are common to all +

The key and ref attributes are common to all members of the att.canonical class and are defined as follows:

- -

A very useful application for them is as a means of gathering +

A very useful application for them is as a means of gathering together all references to the same individual or location scattered throughout a document: @@ -2008,34 +1661,28 @@ throughout a document: Netherfield Park is let at last? - -

Mme. de Volanges +

Mme. de Volanges marie sa fille: c'est encore un secret; mais elle m'en a fait part hier.

- -

The value of the key attribute may be an unexpanded +

The value of the key attribute may be an unexpanded code, as in the examples above, with no particular significance. More usually however, it will be an externally defined code of some kind, as provided by a standard reference source. - -

Heathrow

+

Heathrow

- -

The standard reference source should be documented, for example using a taxonomy element in the TEI header.

- -

The ref attribute can be used to point directly +

The standard reference source should be documented, for example using a taxonomy element in the TEI header.

+

The ref attribute can be used to point directly to some other resource providing more information about the entity named by the element, such as an authority record in a database, an encylopaedia entry, another element in the same or a different document etc. - -

Heathrow

+

Heathrow

-

This use should be distinguished from the use of a nested +

This use should be distinguished from the use of a nested reg (regularization) element to provide the standard form of a referring string, as in this example:

My personal life during the administration of Col. Polk @@ -2043,30 +1690,23 @@ the administration of Col. Polk suspended enjoyments and pursuits of private and professional spheres

- -

No particular syntax is proposed for the values of the key +

No particular syntax is proposed for the values of the key attribute, since its form will depend entirely on practice within a given project. For the same reason, this attribute is not recommended in data interchange, since there is no way of ensuring that the values used by one project are distinct from those used by another. In such a situation, a preferable approach for magic tokens which follows standard practice on the Web is to use a ref attribute whose value is a tag URI as defined in RFC 4151. For example: - -

Mme. de Volanges marie sa fille: c'est encore un secret; -mais elle m'en a fait part hier.

- +

Mme. de Volanges marie sa fille: c'est encore un secret; +mais elle m'en a fait part hier.

 The inclusion of the domain name of the party responsible for tagging (theworksoflaclos.org), as specified in RFC 4151, helps ensure uniqueness of magic token values across TEI encoding projects, allowing for improved interchange of TEI documents.

- -

The choice element discussed in may be +

The choice element discussed in may be used if it is desired to record both a normalized form of a name and the name used in the source being encoded: - -

-Walter de la Mare -de la Mare, Walter - +

Walter de la Marede la Mare, Walter was born at Charlton, in Kent, in 1873.

-

The index element discussed in may be +

+

The index element discussed in may be more appropriate if the function of the regularization is to provide a consistent index:

Montaillou is not a large parish. @@ -2084,56 +1724,40 @@ specialized elements described in chapter or the analytical tools described in chapter should be used.

- - - - - -
-
Addresses - -

These Guidelines propose the following elements to distinguish + + + + +

+
+ Addresses +

These Guidelines propose the following elements to distinguish postal and electronic addresses: - - - - + These two elements constitute the class of model.addressLike elements; for other kinds of address this class may be extended by adding new elements if necessary.

-

These Guidelines provide no particular means for encoding the +

These Guidelines provide no particular means for encoding the substructure of an email address (for example, distinguishing the local part from the domain part), nor of distinguishing personal email addresses from generic or fictitious ones. - -info@tei-c.org - + info@tei-c.org

- -

The simplest way of encoding a postal address is to regard it as a series +

The simplest way of encoding a postal address is to regard it as a series of distinct lines, just as they might be written on an envelope. The following element supports this view: Here is an example of a postal address encoded using this approach: -

- 110 Southmoor Road, - Oxford OX2 6RB, - UK -
+
110 Southmoor Road,Oxford OX2 6RB,UK

-

Alternatively, an address may be encoded as a structure of +

Alternatively, an address may be encoded as a structure of more semantically rich elements. The class model.addrPart element class identifies a number -of such possible components: - - - - Any number of +of such possible components: Any number of elements from the model.addrPart class may appear within an address and in any order. None of them is required.

- -

Where code letters are commonly used in addresses (for +

Where code letters are commonly used in addresses (for example, to identify regions or countries) a useful practice is to supply the full name of the region or country as the content of the element, but to supply the abbreviatory code as the value of the @@ -2144,71 +1768,49 @@ the general-purpose name element or (when the additional module for names and dates is included) the more specialized elements provided for that purpose.

- -

Using just the elements defined by the core module, the above +

Using just the elements defined by the core module, the above address could thus be represented as follows: -

- 110 Southmoor Road - Oxford - OX2 6RB - United Kingdom -
+
110 Southmoor RoadOxfordOX2 6RBUnited Kingdom

- -

The order of elements within an address is highly culture-specific, +

The order of elements within an address is highly culture-specific, and is therefore unconstrained: -

- Università di Bologna - Italy - 40126 - Bologna - via Marsala 24 -
+
Università di BolognaItaly40126Bolognavia Marsala 24

- -

A telephone number (normally outside of the address +

A telephone number (normally outside of the address element) might be tagged with an addrLine and ref that points to the phone number using the tel URI scheme: - - (201) 555 0123 -

- -

For further discussion of ways of regularizing the names of places, + (201) 555 0123

+

For further discussion of ways of regularizing the names of places, see section . A full postal address may also include the name of the addressee, tagged as above using the general purpose name element.

- -

When a schema includes the names and dates +

When a schema includes the names and dates module discussed in chapter , a large number of more specific elements such as country or settlement will be available from the class model.addrPart. The above example might then be encoded as follows: -

- 110 Southmoor Road - Oxford - OX2 6RB - United Kingdom -
-

- - - - - - - -
-
Numbers and +
110 Southmoor RoadOxfordOX2 6RBUnited Kingdom
 +

+ + + + + + + + +
+
+ Numbers and Measures -

This section describes elements provided for the simple encoding +

This section describes elements provided for the simple encoding of numbers and measurements and gives some indication of circumstances in which this may usefully be done. The following phrase level elements are provided for this purpose:

- -

Like names or abbreviations, numbers can occur virtually anywhere +

Like names or abbreviations, numbers can occur virtually anywhere in a text. Numbers are special in that they can be written with either letters or digits (twenty-one, xxi, and 21) and their @@ -2217,7 +1819,7 @@ presentation is language-dependent (e.g. English English 123,456.78 equals French 123.456,78).

-

For many kinds of application, e.g. natural-language processing or +

For many kinds of application, e.g. natural-language processing or machine translation, numbers are not regarded as lexical in the same way as other parts of a text. For these and other applications, the num element provides a @@ -2226,29 +1828,20 @@ For other kinds of application, numbers are only useful if normalized: here the num element is useful precisely because it provides a standardized way of representing a numerical value.

-

For example: - xxxiii -twenty-one -ten percent -10% -5th - one half -1/2 +

For example: + xxxiiitwenty-oneten percent10%5th + one half1/2

- -

Sometimes it may be desired to mark something as numerical +

Sometimes it may be desired to mark something as numerical which cannot be accurately normalized, for example an expression such as dozens; less frequently the number may be recognisable linguistically as such but may use a notation with which the encoder is unfamiliar. To help in these situations, the num element may also bear either or both of the following attributes from the att.ranging class: - - - +

- -

In its fullest form, a measure consists of a number, a phrase +

In its fullest form, a measure consists of a number, a phrase expressing units of measure and a phrase expressing the commodity being measured, though not all of these components need be present in every case. It may be helpful to distinguish measures from surrounding @@ -2257,23 +1850,10 @@ particular notation or system of abbreviations which the encoder does not wish to regard as lexical. Secondly, a quantitative application may wish to distinguish and normalize the internal components of a measure, in order to perform calculations on them.

- -

Consider, as an example of the first case, the following list of +

Consider, as an example of the first case, the following list of Celia's charms, in which the encoder has chosen to make explicit the measurements: -

-Unimportant -Small and round -Green -White -yellow -Mobile -13¾" -11" - - - -
+
UnimportantSmall and roundGreenWhiteyellowMobile13¾"11"
 In the same way, it may be convenient to mark representations of currency which might otherwise be misinterpreted as @@ -2282,39 +1862,23 @@ lexical:

...the sum of 12s 6d...

-

In general, normalization of a measure will require specification +

In general, normalization of a measure will require specification of one or more of its three parts: the quantity, the units, and possibly also the commodity being measured. This is accomplished by supplying values for the three attributes quantity, unit, and commodity, which are supplied by the att.measurement class: - - - + With these attributes, the measurement of Celia's neck may be specified in a normalized form: - -13¾" - + 13¾" Such techniques are particularly useful when representing historical data such as inventories: - - - ii bags hops - - six trusses Woolen and linen goods - - 5 tonnes coale - - +ii bags hopssix trusses Woolen and linen goods5 tonnes coale

-

In addition to normalization, the attributes of the att.ranging class may be used to supply the mininum or maximum values - of a range, or of an approximate measurement: - - - -

In a cadaver I have found it +

In addition to normalization, the attributes of the att.ranging class may be used to supply the mininum or maximum values + of a range, or of an approximate measurement: +

In a cadaver I have found it holding more than three ounces. [...] Then we may suppose in man that a single heart beat @@ -2322,74 +1886,51 @@ data such as inventories: a half ounce, three drams, or even one dram of blood, which because of the valvular block could not flow back that way into - the heart.

- + the heart.

-

The measureGrp element is provided as a means of grouping +

The measureGrp element is provided as a means of grouping several related measurements together, either because the measurement involves several dimensions (for example height and width) or to avoid the need to repeat all the normalizing attributes: - - -xiv -v -x - - + xivvx

-

The unit element may be applied when units of measurement require more detailed encoding about the system they belong to or the what kind of phenomenon they designate. +

The unit element may be applied when units of measurement require more detailed encoding about the system they belong to or the what kind of phenomenon they designate. The unit element may carry the unit attribute to indicate a standard value, as well as other optional attributes for indicating type, language, and other distinguishing characteristics. - - - - - - + A measure element may contain a combination of num and unit elements: - - 1, 2, 5, 7 - millimètres - + 1, 2, 5, 7millimètres The unit element may also be nested to indicate a complex unit and its component parts, for example, to indicate that rate combines space and time: - -

Light travels at 3×10^10 - - cm per second - .

- +

Light travels at 3×10^10 + cm per second + .

- - - - - - -
-
Dates and Times -

Dates and times, like numbers, can appear in widely varying + + + + + + +

+
+ Dates and Times +

Dates and times, like numbers, can appear in widely varying culture- and language-dependent forms, and can pose similar problems in automatic language processing. Such elements constitute the model.dateLike class, of which the default members are: - - - - + These elements have some additional attributes by virtue of being members of the att.datable and att.duration classes which, in turn, are members of the att.datable.w3c and att.duration.w3c classes. In particular, the when and calendar attributes will be discussed here: - - - - +

-

Dates can occur virtually anywhere in a text, but in some contexts +

Dates can occur virtually anywhere in a text, but in some contexts (e.g. bibliographic citations) their encoding is recommended or required rather than optional. Times can also appear anywhere but encoding these is more generally optional.

-

Partial dates or times (e.g. 1990, +

Partial dates or times (e.g. 1990, September 1990, twelvish) can be expressed in the when attribute by simply omitting a part of the value @@ -2397,18 +1938,18 @@ supplied. Imprecise dates or times (for example early August, some time after ten and before twelve) may be expressed as date or time ranges.

-

These mechanisms are useful primarily for fully specified dates or +

These mechanisms are useful primarily for fully specified dates or times known with certainty. If component parts of dates or times are to be marked up, or if a more complex analysis of the meaning of a temporal expression is required, the techniques described in chapter should be used in preference to the simple method outlined here.

-

Where the certainty (i.e. reliability) of the date or time is +

Where the certainty (i.e. reliability) of the date or time is in question, the encoder should record this fact using the mechanisms discussed in chapter . The same chapter also discusses various methods of recording the precision of numerical or temporal assertions.

-

The when attribute is a useful way of normalizing or +

The when attribute is a useful way of normalizing or disambiguating dates and times which can appear in many formats, as the following examples show: 12/2/1980 @@ -2417,20 +1958,11 @@ in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic the Two Hundredth and first and of the University the Eighty-Sixth.

-

The when attribute always supplies a normalized +

The when attribute always supplies a normalized representation of the date given as content of the date element. The format used should be a valid W3C schema datatype.The datatypes are taken from the W3C Recommendation XML Schema Part 2: Datatypes Second Edition. The permitted datatypes are: - -date -gYear -gMonth -gDay -gYearMonth -gMonthDay -time -dateTime - +dategYeargMonthgDaygYearMonthgMonthDaytimedateTime There is one exception: these Guidelines permit a time to be expressed as only a number of hours, or as a number of hours and minutes, as per ISO 8601:2004 section 4.2.2.3 and 4.3.3. @@ -2439,68 +1971,57 @@ datatypes require that the minutes and seconds be included in the normalized value if they are to be correctly processed for example when sorting. Some typical examples follow: - -The year 2001 -September 2001 -11 Sep 01 -9/11 -September -Eleventh of the month - -Sept 11th, 12 minutes before 9 am -Note in the last example the use of a normalized representation for + The year 2001September 200111 Sep 019/11SeptemberEleventh of the monthSept 11th, 12 minutes before 9 amNote in the last example the use of a normalized representation for the date string which includes a time: this example could thus equally well be tagged using the time element.

-

The following examples demonstrate the use of the +

The following examples demonstrate the use of the date element to mark a period of time:

Those five years — 1918 to 1923 — had been, he suspected, somehow very important.

- -

The Eddic poems are preserved in a unique +

The Eddic poems are preserved in a unique manuscript (Codex Regius 2365) from the second half of the thirteenth century, and Hervarar saga dates from around 1300.

-

The calendar attribute may be used to specify a date in +

The calendar attribute may be used to specify a date in any calendar system; if the when attribute is also supplied, it should specify the equivalent date in the Gregorian calendar.

- - - - - - -
-
Abbreviations and Their Expansions -

It is sometimes desirable to mark abbreviations in the copy text, + + + + + +

+
+ Abbreviations and Their Expansions +

It is sometimes desirable to mark abbreviations in the copy text, whether to trigger special processing for them, to provide the full form of the word or phrase abbreviated, or to allow for different possible expansions of the abbreviation. Abbreviations may be transcribed as they stand, or expanded; they may be left unmarked, or marked using these tags: - - - - -

The abbr element is useful as a means of distinguishing + +

+

The abbr element is useful as a means of distinguishing semi-lexical items such as acronyms or jargon: We can sum up the above discussion as follows: the identity of a CC is defined by that calibration of values which motivates the elements of its GSP; ... Every manufacturer of 3GL or 4GL languages is currently nailing on OOP extensions. -

The type attribute may be used to distinguish types - of abbreviation by their function:Dr. M. Deegan is +

+

The type attribute may be used to distinguish types + of abbreviation by their function:Dr.M. Deegan is the Director of the CTI Centre for Textual Studies.

-

Abbreviations such as Dr. M. above may be +

Abbreviations such as Dr. M. above may be treated as two abbreviations, as above, or as one: Dr. M. Deegan is the Director of the CTI Centre for Textual Studies.

-

The expan element may be used simply to record that an +

The expan element may be used simply to record that an abbreviation has been silently expanded by the encoder, perhaps for reasons of house style or editorial policy. It should always include the whole of an abbreviated phrase or word. More @@ -2508,41 +2029,37 @@ usually however this will be combined with the abbr element inside a choice element to record both the abbreviation and its expansion: the -World Wide Web Consortium -W3C +World Wide Web ConsortiumW3C Nested abbreviations may also be handled in this way: RELAX NGregular language for XMLextensible markup language, next generation

- -

Abbreviation is a particularly important feature of manuscript +

Abbreviation is a particularly important feature of manuscript and other source materials, the transcription of which needs more detailed treatment than is possible using these simple elements. A more detailed set of recommendations is discussed in , which includes additional elements made available for the purpose by the transcr module.

- - - - - -
-
Simple Links and Cross-References - -

Cross-references or links between one location in a document and one or more + + + + +

+
+
+ Simple Links and Cross-References +

Cross-references or links between one location in a document and one or more other locations, either in the same or different XML documents, may be encoded using the elements ptr and ref, as discussed in this section. These elements both point from one location in a document, the place that the element itself appears, to another (or to several), specified by means of a target attribute, supplied by the att.pointing class: - - - + Linkages of several other kinds are also provided for in these guidelines; see further chapter .

-

The value of the target attribute, wherever it appears, +

The value of the target attribute, wherever it appears, provides a way of pointing to some other element using a method standardized by the W3C consortium, and known as the XPointer mechanism. This permits a range of complexity, from the very simple @@ -2556,33 +2073,28 @@ The complete XPointer specification is managed by the W3C, and ; for a discussion of TEI schemes for XPointer, see -.

- -
- -
- +.

Alternatively, if no explicit link is to be encoded, but it is simply required to mark the phrase as a cross-reference, the ref element may be used without a target attribute.

-

For an introduction to the use of links in general, see . The complete XPointer specification is managed by the W3C, , , and ; for a discussion of +

For an introduction to the use of links in general, see . The complete XPointer specification is managed by the W3C, , , and ; for a discussion of TEI schemes for XPointer, see .

-

- -

-

The elements ptr and ref are the default members +

+ + + + +

+

The elements ptr and ref are the default members of the phrase-level model class model.ptrLike. As members of the classes att.pointing, att.typed, att.cReferencing, and att.internetMedia they also carry the following attributes: - - - - +

-

The two elements may be used in the same +

The two elements may be used in the same way; the difference between them is simply that while the ptr element is empty, the ref element may contain phrases specifying, or describing more exactly, the target of a cross-reference, @@ -2591,24 +2103,23 @@ a human-readable pointer, in the simplest case a ref element need not identify its target in any other way. For example: See section 12 on page 34.

-

More usually, it will be desirable to identify the target of the +

More usually, it will be desirable to identify the target of the cross-reference using either the target or the cRef attribute, so that processing software can access it directly, for example to implement a linkage, to generate an appropriate reference, or to give an error message if it cannot be found. Assuming that section 12 in the previous example has been tagged - - + then the same cross-reference might more exactly be encoded as See especially section 12 on page 34.

-

If the cross-reference itself is to be generated according to a +

If the cross-reference itself is to be generated according to a fixed pattern, or if no text is to appear in the body of the cross-reference, the ptr element would be used as follows: See in particular .

-

The cRef attribute may be used to express the target of +

The cRef attribute may be used to express the target of a cross reference using some canonical referencing scheme, such as those typically used for ancient texts. In this case, the referencing scheme must be defined using the cRefPattern or citeStructure elements @@ -2617,22 +2128,16 @@ to translate the value of the cRef attribute into a conventional pointer value, such as one that might be supplied by the target attribute. It is an error to supply both cRef and target values.

-

When the target attribute is used, a cross reference may point to any number of locations simultaneously, +

When the target attribute is used, a cross reference may point to any number of locations simultaneously, simply by giving more than one identifier as the value of its target attribute. This may be particularly useful where an analytic index is to be encoded, as in the following example: - - Saints aid rejected in mel. - Sallets censured - Sanguine mel. signs - Scilla or sea onyon, a purger of mel. - +Saints aid rejected in mel. Sallets censured Sanguine mel. signs Scilla or sea onyon, a purger of mel. Here the targets of the cross-references are simply page numbers; it is assumed that corresponding elements with identifiers p299, p143, etc. have been provided in the body of the text: - - + ... ... @@ -2644,7 +2149,7 @@ the body of the text: ...

-

A similar method may be used to link annotations on a text with the +

A similar method may be used to link annotations on a text with the sigla used to encode their points of attachment in a text. For example: @@ -2653,7 +2158,7 @@ annotated text ⁵¹ text of annotation

-

The type attribute may be used, +

The type attribute may be used, as elsewhere, to categorize the cross-reference according to any system of importance to the encoder. If bibliographic references require special processing (e.g. in order to provide a consistent @@ -2672,54 +2177,48 @@ object being referenced here is a bibliographic entry rather than a simple cross-reference to an illustration, as is the first ptr. In either case, the value of the target attribute is a pointer to some other element. -

The ptr and ref elements have many applications in +

+

The ptr and ref elements have many applications in addition to the simple cross-referencing facilities illustrated in this section. In conjunction with the analytic tools discussed in chapters , , and , they may be used to link analyses of a text to their object, to combine corresponding segments of a text, or to align segments of a text with a -temporal or other axis or with each other.

-

Where the target attribute of ptr or ref +temporal or other axis or with each other.

+

Where the target attribute of ptr or ref points to an external resource available on the network, the mimeType attribute may be used to specify the mime type of that resource; this may be important for to enable appropriate processing. For example: - -

The current version of the TEI Guidelines source code +

The current version of the TEI Guidelines source code is available in the TEI GitHub Repository; guidelines-en.xml is the root document used to create the English version - of these Guidelines.

- -

- - - - -
-
Lists -

The following elements are provided for the encoding of lists, + of these Guidelines.

+

+ + + + +
+
+ Lists +

The following elements are provided for the encoding of lists, their constituent items, and the labels or headings associated with them:

-

The list element may be used to mark any kind of +

The list element may be used to mark any kind of list: numbered, lettered, bulleted, or unmarked. Lists formatted as such in the copy text should in general be encoded using this element, with an appropriate value for the rend attribute. Suggested values for rend include: - - bulleted (items preceded by bullets or similar markings) - inline (items rendered within continuous prose, with no linebreaks) - numbered (items preceded by numbers or letters) - simple (items rendered as blocks, but with no bullet or number) - + bulleted (items preceded by bullets or similar markings)inline (items rendered within continuous prose, with no linebreaks)numbered (items preceded by numbers or letters)simple (items rendered as blocks, but with no bullet or number) Some of these values may of course be combined; a list may be inline, but also be rendered with numbers. An example appears below. For more sophisticated and detailed description of list rendering, consider using the style attribute with Cascading Stylesheet properties and values, as described in the W3C's CSS Lists and Counters Module Level 3.

- -

Each distinct item in the list should be encoded as a distinct +

Each distinct item in the list should be encoded as a distinct item element. If the numbering or other identification for the items in a list is unremarkable and may be reconstructed by any processing program, no enumerator need be specified. If however an @@ -2729,66 +2228,35 @@ using a label element. The following examples are thus equivalent: I will add two facts, which have seldom occurred in the composition of six, or even five quartos. - - - My first rough manuscript, without any -intermediate copy, has been sent to the press. - - Not a sheet has been seen by any human +My first rough manuscript, without any +intermediate copy, has been sent to the press.Not a sheet has been seen by any human eyes, excepting those of the author and the printer: -the faults and the merits are exclusively my own. - +the faults and the merits are exclusively my own. I will add two facts, which have seldom occurred in the composition of six, or even five quartos. - - My first rough manuscript, without any -intermediate copy, has been sent to the press. - Not a sheet has been seen by any human +My first rough manuscript, without any +intermediate copy, has been sent to the press.Not a sheet has been seen by any human eyes, excepting those of the author and the printer: -the faults and the merits are exclusively my own. - +the faults and the merits are exclusively my own. The two styles may not be mixed in the same list: if one item is preceded by a label, all must be.

-

A list need not necessarily be displayed in list format. For +

A list need not necessarily be displayed in list format. For example, the following is a reasonable encoding of a list which (in the original) is simply printed as a single paragraph: On those remote pages it is written that animals are -divided into - those that belong to the Emperor, - embalmed ones, - those that are trained, - suckling pigs, - mermaids, - fabulous ones, - stray dogs, - those that are included in this classification, - those that tremble as if they were mad, - innumerable ones, - those drawn with a very fine camel's-hair brush, - others, - those that have just broken a flower vase, - those that resemble flies from a distance. - +divided into those that belong to the Emperor, embalmed ones, those that are trained, suckling pigs, mermaids, fabulous ones, stray dogs, those that are included in this classification, those that tremble as if they were mad, innumerable ones, those drawn with a very fine camel's-hair brush, others, those that have just broken a flower vase, those that resemble flies from a distance.

-

A list may be given a heading or title, for which the head +

A list may be given a heading or title, for which the head element should be used, as in the next example, which also demonstrates simple use of the label element to mark a tabular or glossary list in which each item is associated with a word or phrase rather than a numeric or alphabetic enumerator: - - Report of the conduct and progress of Ernest Pontifex. - Upper Vth form — half term ending Midsummer 1851 - Idle listless and unimproving - ditto - ditto - Orderly - - Not satisfactory, on account of his great - unpunctuality and inattention to duties - +Report of the conduct and progress of Ernest Pontifex. + Upper Vth form — half term ending Midsummer 1851Idle listless and unimprovingdittodittoOrderlyNot satisfactory, on account of his great + unpunctuality and inattention to duties

-

In such a list, the individual items have internal structure. In +

In such a list, the individual items have internal structure. In complex cases, where list items contain many components, the list is better treated as a table, tablesand @@ -2797,33 +2265,12 @@ table is the glossary list, which should be marked by the tag list type="gloss". In such lists, each label element contains a term and each item its gloss; it is a semantic error for a list tagged with type="gloss" not to have labels. For example: - - Unit Three — Vocabulary - bitter, harsh - field - hear, listen (to) - war - good - +Unit Three — Vocabularybitter, harshfieldhear, listen (to)wargood Additionally, the term and gloss elements discussed in section might be used to make explicit the role that each column in the glossary list has, as follows: - - Unit Three — Vocabulary - - bitter, harsh - - field - - hear, listen (to) - - war - - good - +Unit Three — Vocabularybitter, harshfieldhear, listen (to)wargood Note in the above examples the use of the global xml:lang attribute to specify on the label (or term) element what language the term is from. For further discussion of the @@ -2833,86 +2280,63 @@ glossary would distinguish the headword forms from the grammatical information (principal parts and gender), perhaps using elements taken from .

-

In addition to the head element used to supply +

In addition to the head element used to supply a title or heading for the whole list, headings for the two columns of a glossary-style list may be specified using the two special elements headLabel and headItem: The simple, straightforward statement of an idea is preferable to the use of a worn-out expression. - - TRITE - SIMPLE, STRAIGHTFORWARD - stop fighting, make peace - disorganized - friendly - completely honest - near death - +TRITESIMPLE, STRAIGHTFORWARDstop fighting, make peacedisorganizedfriendlycompletely honestnear death

-

The elements label, head, headLabel, and +

The elements label, head, headLabel, and headItem may contain only phrase-level elements. The item element however may contain paragraphs or other chunks, including other lists. In this example, a glossary list contains two items, each of which is itself a simple list: - - - - - I am cast upon a horrible desolate island, void - of all hope of recovery. - I am singled out and separated as it were from - all the world to be miserable. - I am divided from mankind — a solitaire; one - banished from human society. - - - - - - But I am alive; and not drowned, as all my - ship's company were. - But I am singled out, too, from all the ship's - crew, to be spared from death... - But I am not starved, and perishing on a barren place, - affording no sustenances.... - - - +I am cast upon a horrible desolate island, void + of all hope of recovery.I am singled out and separated as it were from + all the world to be miserable.I am divided from mankind — a solitaire; one + banished from human society.But I am alive; and not drowned, as all my + ship's company were.But I am singled out, too, from all the ship's + crew, to be spared from death...But I am not starved, and perishing on a barren place, + affording no sustenances....

-

Lists of different types may be nested to arbitrary depths in this +

Lists of different types may be nested to arbitrary depths in this way.

- - - - - - - - -
-
Notes, Annotation, and Indexing -
Notes and Simple Annotation -

The following element is provided for the encoding of + + + + + + + + +

+
+ Notes, Annotation, and Indexing +
+ Notes and Simple Annotation +

The following element is provided for the encoding of discursive notes, whether already present in the copy text or supplied by the encoder:

-

A note is any additional comment found in a text, marked in some way as being +

A note is any additional comment found in a text, marked in some way as being out of the main textual stream. All notes should be marked using the same tag, note, whether they appear as block notes in the main text area, at the foot of the page, at the end of the chapter or volume, in the margin, or in some other place.

-

Notes may be in a different hand or typeface, may be authorial or +

Notes may be in a different hand or typeface, may be authorial or editorial, and may have been added later. Attributes may be used to specify these and other characteristics of notes, as detailed below.

-

A note is usually attached to a specific point or span within a text, which we +

A note is usually attached to a specific point or span within a text, which we term here its point of attachment. In conventional printed text, the point of attachment is represented by some siglum such as a star or cross, or a superscript digit.

-

When encoding such a text, it is conventional to replace this +

When encoding such a text, it is conventional to replace this siglum by the content of the annotation, duly marked up with a note element. This may not always be possible for example with marginal notes, which may not be anchored to @@ -2931,45 +2355,33 @@ indicate the point of attachment. It is also possible to encode the point of attachment itself, using the ptr or ref element, pointing from that to the body of the note placed elsewhere.

-

In cases where the note is +

In cases where the note is applied not to a point but to a span of text, not itself represented as a TEI element, the target attribute may use an appropriate pointer expression, for example using the range() function to specify the span of attachment.

-

For further discussion of pointing +

For further discussion of pointing to points and spans in the text, see section .

-

In the following example, the type attribute is used to +

In the following example, the type attribute is used to categorise the note as a gloss: -The self-same moment I could pray -And from my neck so free -The albatross fell off, and sank -Like lead into the sea. +The self-same moment I could prayAnd from my neck so freeThe albatross fell off, and sankLike lead into the sea. The spell begins to break As the note appears within an l element, we may infer that its point of attachment is in the margin adjacent to the line in question. In the following version of the same text, however, it may be inferred that the note applies to the whole of the stanza: -The self-same moment I could pray -And from my neck so free -The albatross fell off, and sank -Like lead into the sea. -The spell begins to break - +The self-same moment I could prayAnd from my neck so freeThe albatross fell off, and sankLike lead into the sea.The spell begins to break

-

This type of annotation, very common in the early printed texts +

This type of annotation, very common in the early printed texts which Coleridge may be presumed to be imitating in this case, may also be regarded as providing a heading or descriptive label for the passage concerned. The encoder may therefore prefer to use the label element to represent it, as in the following case: -The self-same moment I could pray -And from my neck so free -The albatross fell off, and sank -Like lead into the sea. - +The self-same moment I could prayAnd from my neck so freeThe albatross fell off, and sankLike lead into the sea.

-

In the following example, a note which appears at the foot of the +

In the following example, a note which appears at the foot of the page in the printed source is given at its point of attachment within the text. The global n attribute is used to indicate the note number: Collections are ensembles of @@ -2981,7 +2393,7 @@ explain below why we use the uncommon term the sense of class found in older logical writings. The elements ...

-

In addition to transcribing notes already present in the copy text, +

In addition to transcribing notes already present in the copy text, researchers may wish to add their own notes or comments to it. The note element may be used for either purpose, but it will usually be advisable to distinguish the two categories. One way might @@ -2991,51 +2403,41 @@ derive from many sources, or where a more precise attribution is required, the resp attribute may be used to point to a definition of the person or other agency responsible for the content of the note.

-

As a simple example, an edition of the Ancient + <p>As a simple example, an edition of the <title>Ancient Mariner might include both Coleridge's original glosses and those of a modern commentator: - - -The self-same moment I could pray; +The self-same moment I could pray; The spell begins to break The turning point of the poem... - - + For this to be valid, the codes #JLL and #STC must point to some more information identifying the agency concerned. The syntax used is identical to that used for other cross-references, as discussed in ; thus in this case, the TEI header for this text might contain a title statement like the following: - - -The Rime of the Ancient Mariner: an annotated edition -Samuel Taylor Coleridge -John Livingston Lowes - -

- -

When annotating the electronic text by means of analytic notes in + The Rime of the Ancient Mariner: an annotated editionSamuel Taylor ColeridgeJohn Livingston Lowes

+

When annotating the electronic text by means of analytic notes in some structured vocabulary, e.g. to specify the topics or themes of a text, the span and interp elements may be more effective than the free form note element; these elements are available when the module for simple analysis is selected (see section ).

- -
Encoding Grouped Notes -

The following element is provided for the grouping of notes: +

+ Encoding Grouped Notes +

The following element is provided for the grouping of notes:

-

+

A text may have multiple alternative versions of the same note, such as the same annotation expressed in multiple languages, or both an extensive note and a short form for different audiences. In such cases multiple note elements may be grouped within a noteGrp element.

-

+

Typically, the note elements within a noteGrp would be differentiated by use of attributes such as xml:lang or type, while sharing the same point of attachment. This differentiation @@ -3043,30 +2445,25 @@ can be made either implicitly in case of inline notes, or explicitly via a target attribute, which may be specified on the noteGrp itself.

- -

The simple example below demonstrates the grouping of a short and a full version of +

The simple example below demonstrates the grouping of a short and a full version of the same note, where the short version might be intended for use in contexts with space constraints. - -

... reuerendos dominos archiepiscopum et canonicos Leopolienses +

... reuerendos dominos archiepiscopum et canonicos Leopolienses in duplicibus Quatuortemporibus - - Quatuor Tempora, so called dry fast days. - Quatuor Tempora, so called dry fast days (Wednesday, Friday, and Saturday) + Quatuor Tempora, so called dry fast days.Quatuor Tempora, so called dry fast days (Wednesday, Friday, and Saturday) falling on each of the quarters of the year. In the first quarter they were called Cinerum (following Ash Wednesday), second Spiritus (following Pentecost), third Crucis (after the Exaltation of the Holy Cross, September 14th), and Luciae in the fourth (after the feast of St. Lucia, December 13th). - - + totaliter expediui. -

- +

-
-
-
Index Entries -

The indexing of scholarly texts is a skilled activity, involving +

+
+
+ Index Entries +

The indexing of scholarly texts is a skilled activity, involving substantial amounts of human judgment and analysis. It should not therefore be assumed that simple searching and information retrieval software will be able to meet all the needs addressed by a well-crafted manual @@ -3075,8 +2472,9 @@ text search. The role of an index is to provide access via keywords and phrases which are not necessarily present in the text itself, but must be added by the skill of the indexer.

-
Pre-existing Indexes -

When encoding a pre-existing text, therefore, if such an index +

+ Pre-existing Indexes +

When encoding a pre-existing text, therefore, if such an index is present it may be advisable to retain it along with the text, rather than attempt to regenerate it automatically. Elements discussed elsewhere in these Guidelines may be used for this purpose. For @@ -3086,52 +2484,34 @@ to mark the section of the text containing the index and the entry being represented by an item element, possibly containing within it a series of ptr or ref elements, as follows: -

- - -Women, how cause of mel. 193; their vanity in +
Women, how cause of mel. 193; their vanity in apparell taxed, 527; their counterfeit tears 547; their vices 601, commended, -624. -Wormwood, good against mel. 443 -World taxed, 181 -Writers of the cure of mel. 295 - - -
 +624.Wormwood, good against mel. 443World taxed, 181Writers of the cure of mel. 295

-

Note that this simple representation does not capture the nested +

Note that this simple representation does not capture the nested structure of the first of these index entries. A more accurate representation might entail the use of nested lists like the following: Women, - how cause of mel. 193; - their vanity in apparell taxed, 527; - their counterfeit tears 547; - their vices - 601, - commended, 624. - - + how cause of mel. 193;their vanity in apparell taxed, 527;their counterfeit tears 547;their vices + 601, commended, 624.

-

The page references, encoded simply as ref elements above, +

The page references, encoded simply as ref elements above, might also include direct links to the appropriate location in the encoded text, using (for example) a target attribute to supply the identifier of an associated pb element: - - - -624 - + 624 For further discussion of this and alternative ways of encoding such links see the discussion in section . Note that similar methods may also be used to encode a table of contents, as further exemplified in section .

-
-
Auto-generated Indexes -

It can also be useful, however, to generate a new index from a +

+
+ Auto-generated Indexes +

It can also be useful, however, to generate a new index from a machine-readable text, whether the text is being written for the first time with the tags here defined, or as an addition to a text transcribed from some other source. Depending on the complexity of the text and its subject @@ -3140,14 +2520,12 @@ the needs of scholarly users. However it can assist a professional indexer to construct a fully adequate index, which might then be post-edited into the digital text, marked-up along the lines already suggested for preserving pre-existing index material.

-

Indexes generally contain both references to specific pages or +

Indexes generally contain both references to specific pages or sections and references to page ranges or sequences. The same element is used in either case: - - - +

-

Like the interp element described in +

Like the interp element described in this element may be used simply to provide descriptive or interpretive label of some kind for any location within a text, to be processed in any way by analytic software, but its main purpose is to facilitate @@ -3162,18 +2540,16 @@ text, such as the following (the exact form of the PI is of course dependent on the application software in use): ]]> Alternatively, the special purpose divGen element might be used.

-

In the simplest case, a single headword is supplied by +

In the simplest case, a single headword is supplied by a term element contained by an index element:

The students understand procedures for Arabic lemmatisation - - Lemmatization, Arabic -and are beginning to build parsers.

+Lemmatization, Arabicand are beginning to build parsers.

-

The effect of this is to document an index entry for the term +

The effect of this is to document an index entry for the term Lemmatization, Arabic, which when processed could reference the location of the original index element.

-

If the subject of Arabic lemmatization is treated at length +

If the subject of Arabic lemmatization is treated at length in a text, then the index entry generated may need to reference a sequence of locations (e.g. page numbers). In such a case it will be necessary to identify the end of the relevant span of text as well as its starting point. This is most conveniently @@ -3184,19 +2560,17 @@ attribute, as in this example:

We now turn to the topic of Arabic lemmatisation - - Lemmatization, Arabic - concerning which it is important to note [...] +Lemmatization, Arabic concerning which it is important to note [...] and now we can build our parser.

-

This would generate the same index entries as the previous example, +

This would generate the same index entries as the previous example, but the reference would be to the whole span of text between the location of the index element and the location of the element identified by the code ALAMEND, rather than a single point, and thus might (for example) include a sequence of page numbers.

-

Although the position of the index element in the text +

Although the position of the index element in the text provides the target location that will be specified in the generated index entry, no part of the text itself is used to construct that entry. Index terms appearing in the entry come solely from the content of term @@ -3204,7 +2578,7 @@ elements, which consequently may have to repeat words or phrases from the text proper. This need not be done verbatim, thus giving scope for normalization of spelling (as in the example above) or other modifications which may assist generation of an index in a desired form or sequence.

-

Sometimes, for example when +

Sometimes, for example when index terms are taken from a different language or consist of mathematical formulae or other expressions, even a normalized form of an index term may be insufficient for an application to @@ -3219,17 +2593,11 @@ entry is to contain some non-Unicode character or glyph represented by the g element discussed in chapter . In the following example, we assume that somewhere a definition for this glyph has been provided using the elements described in chapter , and given the code PrinceGlyph: - - - - - -

The Artist formerly known as Prince ...

+

The Artist formerly known as Prince ...

 Note that if no value is supplied for the sortKey attribute, a sorting application should always use the content of the term element as a sort key.

- -

It is common practice to compile more than one index for a given text. +

It is common practice to compile more than one index for a given text. A biography of a poet, for example, may offer an index of references to poems by the subject of the study, another index of works by other writers, an index of places or historical personages etc. The indexName @@ -3240,8 +2608,7 @@ more specific indexes: coincidentally, born in Ashford (Kent)Ashford...

- -

Multi-level indexing is particularly common in scholarly +

Multi-level indexing is particularly common in scholarly documents. For example, as well as entries such as TEI, or markup, an index may contain structured entries like TEI, markup practices, index terms, where a top level entry TEI @@ -3255,50 +2622,24 @@ suppose that we wish to make a structured index entry for then be encoded with nested index elements:

The students understand procedures for Arabic lemmatisation - - lemmatization - - arabic - - + lemmatizationarabic ...

-

The index entry from Burton's Anatomy of + <p>The index entry from Burton's <title>Anatomy of Melancholy quoted above might be generated in a similar way. To generate such an entry, the body of the text might include, at page 193, an index element such as - - - Women - - how cause of mel. - - -. Similarly, page 601 of the body text would include + Womenhow cause of mel.. Similarly, page 601 of the body text would include an index element like the following: - - Women - - their vices - - + Womentheir vices while the index element at page 624 would have a structure like the following: - - Women - - their vices - - commended - - - + Womentheir vicescommended

-

When processing such index elements, the duplication +

When processing such index elements, the duplication required to make the structure explicit will normally be removed, so as to produce entries like those quoted above. However, this is not required by the encoding recommended here.

- -

As noted above, either a processing instruction or a divGen +

As noted above, either a processing instruction or a divGen element may be used to mark the place at which an index generated from index elements should be inserted into the output of a processing program; typically but not necessarily this will be at some point @@ -3308,35 +2649,19 @@ should be used to specify which kind of index is to be generated, and its value should correspond with that of the indexName attribute on the relevant index elements. - - -

- Bibliography - - ... - -
- - - +
Bibliography ...

-

As this example shows, the global +

As this example shows, the global n attribute may also be used to specify a name or identifier for the generated index itself in the usual way. Any additional headings etc. required for the generated index must be specified as content of the divGen element. - - - - An Index of Names - - - + An Index of Names

-

If a processing instruction is used, then these parameters for the +

If a processing instruction is used, then these parameters for the generated index may be supplied in some other way.

-

One final feature frequently found in manually-created indexes to +

One final feature frequently found in manually-created indexes to printed works cannot readily be encoded by the means provided here, namely cross-references internal to the index term listing. For example, if all references to the TEI in a text have been indexed @@ -3345,16 +2670,17 @@ also be helpful to include an entry under the term TEI containing some text such as see Text Encoding Initiative. Such internal cross-references must be added as part of the post-editing phase for an auto-generated index.

- - - - - -
-
-
-
Graphics and Other Non-textual Components -

Graphics, such as illustrations or diagrams, appear in many + + + + + +

+
+
+
+ Graphics and Other Non-textual Components +

Graphics, such as illustrations or diagrams, appear in many different kinds of text, and often with different purposes. Audio or video clips may also appear. In some cases, such media form an integral part of a text (indeed, some texts—comic @@ -3369,27 +2695,18 @@ digital, media such as graphics and other non-textual components may be particularly salient, but their inclusion in an archival form of the document concerned remains an editorial decision.

-

Considered as structural components, media may be anchored to a particular point in +

Considered as structural components, media may be anchored to a particular point in the text, or they may float either completely freely, or within some defined scope, such as a chapter or section. Time-based media such as audio or video may need to be synchronized with particular parts of a written text. Media of all kinds often contain associated text such as a heading or label. These Guidelines provide the following different elements to indicate their appearance within a text: - - - - - - +

-

Media files may be encoded in a number of different ways: - -in some non-XML or binary format such as PNG, JPEG, MP3, MP4 etc. -in an XML format such as SVG -in a TEI XML format such as the notation for graphs and trees -described in - In the last two cases, the presence of the graphic +

Media files may be encoded in a number of different ways: +in some non-XML or binary format such as PNG, JPEG, MP3, MP4 etc.in an XML format such as SVGin a TEI XML format such as the notation for graphs and trees +described in In the last two cases, the presence of the graphic will be indicated by an appropriate XML element, drawn from the SVG namespace in the second case, and its content will fully define the graphic to be produced. In the first case, however, one of the elements @@ -3401,17 +2718,12 @@ it is small, the media information may be embedded directly within the document using some suitable binary format such as Base64; in this case the binaryObject element may be used to contain it.

- -

The elements graphic, media, and binaryObject are made +

The elements graphic, media, and binaryObject are made available as members of the class model.graphicLike when this module is included in a schema. These elements are also members of the class att.media, from which they inherit the following attributes: - - - -

- -

For example, the following passage indicates that a copy of the image +

+

For example, the following passage indicates that a copy of the image found in the source text may be recovered from the URL zigzag2.png and that this image is in PNG format:

These were the four lines I moved in @@ -3426,18 +2738,16 @@ to Navarre, -- and the indented curve B. which is the short airing when I was there with the Lady Baussiere and her page, -- I have not taken the least frisk -...

- +...

-

-

The media elements are phrase +

+

The media elements are phrase level elements which may be used anywhere that textual content is permitted, within but not between paragraphs or headings. In the following example, the encoder has decided to treat a specific printer's ornament as a heading: - -.

-

The figure element discussed in + .

+

The figure element discussed in provides additional capabilities, for example the ability to combine a number of images into a hierarchically organized structure or a block of images. The figure element carries a type @@ -3445,16 +2755,15 @@ attribute, which can be used to distinguish different kinds of graphic component within a single work, for example, maps as opposed to illustrations. It also provides the ability to associate an image with additional information such as a heading or a description.

- - - - - - - -
-
Reference Systems -

By reference system we mean the system by which names + + + + + +

+
+ Reference Systems +

By reference system we mean the system by which names or references are associated with particular passages of a text (e.g. Ps. 23:3 for the third verse of Psalm 23 or Amores 2.10.7 for Ovid's Amores, book 2, poem 10, line @@ -3467,30 +2776,26 @@ texts). Where one exists, the traditional reference system for a text should be preserved in an electronic transcript of it, if only to make it easier to compare electronic and non-electronic versions of the text.

-

Reference systems may be recorded in TEI-encoded texts in any of the +

Reference systems may be recorded in TEI-encoded texts in any of the following ways: - -where a reference system exists, and is based on the same +where a reference system exists, and is based on the same logical structure as that of the text's markup, the reference for a passage may be recorded as the value of the global xml:id or n attribute on an appropriate tag, or may be constructed by combining attribute values from several levels of tags, as described below in section . - -where there is no pre-existing reference system, the global + where there is no pre-existing reference system, the global xml:id or n attributes may be used to construct one (e.g. collections and corpora created in electronic form), as described below in section . - -where a reference system exists which is not based on the same + where a reference system exists which is not based on the same logical structure as that of the text's markup (for example, one based on the page and line numbers of particular editions of the text rather than on the structural divisions of it), any of a variety of methods for encoding the logical structure representing the reference system may be employed, as described in chapter . - -where a reference system exists which does not correspond to any + where a reference system exists which does not correspond to any particular logical structure, or where the logical structure concerned is of no interest to the encoder except as a means of supporting the referencing system, then references may be encoded by means of @@ -3502,7 +2807,7 @@ The specific method used to record traditional or new reference systems for a text should be declared in the TEI header, as further described in section and in section .

-

When a text has no pre-existing associated reference system of any +

When a text has no pre-existing associated reference system of any kind, these Guidelines recommend as a minimum that at least the page boundaries of the source text be marked using one of the methods outlined in this section. Retaining page breaks in the markup is also @@ -3511,8 +2816,9 @@ own. Line breaks in prose texts may be, but need not be, tagged.Using the xml:id and n Attributes -

When traditional reference schemes represent a hierarchical +

+ Using the xml:id and n Attributes +

When traditional reference schemes represent a hierarchical structuring of the text which mirrors that of the marked-up document, the n attribute defined for all elements may be used to indicate the traditional identifier of the relevant structural units. The @@ -3520,7 +2826,7 @@ the traditional identifier of the relevant structural units. The sections or list items in the copy text if the copy-text numbering is important for some reason, for example because the numbers are out of sequence.

-

For example, a traditional reference to Ovid's +

For example, a traditional reference to Ovid's Amores might be Amores 2.10.7—book 2, poem 10, line 7. Book, poem, and line are structural units of the work and will therefore be tagged in @@ -3529,42 +2835,14 @@ discussion of structural units in verse collections.) In such cases, it is convenient to record traditional reference numbers of the structural units using the n attribute. The relevant tags for our example would be: - - - - - - - - ... - ... - - ... - - - - - + ... ... ...

-

One may also place the entire standard reference for each portion of +

One may also place the entire standard reference for each portion of the text into the appropriate value for the n attribute, though for obvious reasons this takes more space in the file: - - - - - - - - ... - - - - - - + ...

-

If the names used by the traditional reference system can be +

If the names used by the traditional reference system can be formulated as identifiers, then the references can be given as values for the xml:id attribute; this requires that the reference be given without internal spaces, begin with a letter or underscore, @@ -3573,28 +2851,16 @@ underscores, full stops, and the various combining and extender characters, as defined by the XML specification. Unlike values for the n attribute, values for the xml:id attribute must be unique throughout the document. Our example then looks like -this: - - - - - - ... - - - - - - +this: ...

-

To document the usage and to allow automatic processing of these +

To document the usage and to allow automatic processing of these standard references, it is recommended that the TEI header be used to declare whether standard references are recorded in the n or xml:id attributes and which elements may carry standard references or portions of them. For examples of declarations for the reference systems just shown, see section .

-

Using the n attribute one can specify only a single +

Using the n attribute one can specify only a single standard referencing system, a limitation not without problems, since some editions may define structural units differently and thus create alternative reference systems. For example, another edition of the @@ -3602,20 +2868,20 @@ alternative reference systems. For example, another edition of the therefore would specify the same line as Amores 2.9.31. In order to record both of these reference systems one could employ any of a variety of methods discussed in chapter . -

-
Creating New Reference Systems -

If a text has no canonical reference system of its own, a new custom reference +

+
+
+ Creating New Reference Systems +

If a text has no canonical reference system of its own, a new custom reference system may be used.

- -

The global attributes n and xml:id may be used to +

The global attributes n and xml:id may be used to assign reference identifiers to segments of the text. Identifiers specified by either attribute apply to the entire element for which they are given. xml:id attributes must be unique within a single document, and xml:id values must begin with a letter. No such restrictions are made on the values of n attributes.

- -

Determining a referencing system for a TEI encoding depends on many factors +

Determining a referencing system for a TEI encoding depends on many factors that may either be derived from textual structure, or influenced by extra-textual contingencies such as project and file management concerns. It is important, therefore, that the attribute used, the elements which can bear standard @@ -3623,13 +2889,11 @@ system may be used.

identifiers, should all be declared in the header as described in section .

- -

The Guidelines do not recommend one specific method for creating new referencing +

The Guidelines do not recommend one specific method for creating new referencing systems; however, the rest of this section lists some possibly useful strategies.

- -
- Referencing system derived from markup -

+

+ Referencing system derived from markup +

A new referencing system may be derived from the structure of the electronic text, specifically from the markup of the text. As with any reference system intended for long-term use, it is important to see the @@ -3640,7 +2904,7 @@ system may be used.

system may always be created beside the old one if out-of-sequence numbers must be avoided.)

-

A convenient method of mechanically generating unique values for +

A convenient method of mechanically generating unique values for xml:id or n attributes based on the structure of the document is to construct, for each element, a domain-style address comprising a series of components separated by full @@ -3656,7 +2920,7 @@ system may be used.

indicating which element in the sequence of nodes at each level is to be selected. To make the resulting identifier a valid XML identifier, it may need to be prefixed with an unchanging alphabetic letter.

-

Identifiers generated with these methods should use the text +

Identifiers generated with these methods should use the text element as their starting point, rather than the TEI or body elements. The TEI element may be taken as a starting point only if identifiers need to be generated for the @@ -3667,42 +2931,16 @@ system may be used.

In collections and corpora, the component corresponding to the root may be replaced by the unique identifier assigned to the text or sample.

-

In the following example, each element within the text +

In the following example, each element within the text element has been given a typed-path identifier as its xml:id value, and an untyped-path identifier as its n value; the latter are prefixed with the string AB, which may be imagined to be the general identifier for this text. - - -

-

...

-
- - ... - -
-

...

-
- - -

...

-

...

-
- ... -

...

-

...

-
-
- ... -

...

-

...

-
- - +

...

...

...

...

...

...

...

...

...

...

...

The typed and untyped path methods are convenient, but are in no way required for anyone creating a reference system.

-

If the xml:id attribute is used to record the reference +

If the xml:id attribute is used to record the reference identifiers generated, each value should record the entire path. If the n attribute is used, each value may record either the entire path or only the subpath from the parent element. The attribute @@ -3710,52 +2948,46 @@ system may be used.

the method for constructing standard reference identifiers, should all be declared in the header as described in section .

-
- -
- Referencing systems based on project conventions -

A reference system may be based on an agreed project-specific convention for xml:id attributes. +

+
+ Referencing systems based on project conventions +

A reference system may be based on an agreed project-specific convention for xml:id attributes. Every convention will have strengths and weaknesses and it is left to encoders to make a decision that enables them to locate information in their TEI document.

- -

Here are some examples of referencing systems that have been used in TEI project: - - identifiers constructed with a +

Here are some examples of referencing systems that have been used in TEI project: + identifiers constructed with a number of characters from the main document title, followed by an incremental number. E.g. HOL001, HOL002, etc. using a fixed number of digits; or without - fixed digits: HOL1, HOL2, etc. - identifiers constructed on + fixed digits: HOL1, HOL2, etc. identifiers constructed on the markup itself, as described in the previous section. To facilitate uniqueness in a corpus, each identifier may be prefixed with the identifier of the root TEI element. - E.g. RootID-Body-p-1. - computed identifiers using either a + E.g. RootID-Body-p-1. computed identifiers using either a randomized algorithm or a universally unique identifier (UUID) algorithm. Note that XSLT's function generate-id() only guarantees identifier unique - to the document being processed. - + to the document being processed.

- -

XML well-formedness requires only that xml:id attributes be unique within a single document. +

XML well-formedness requires only that xml:id attributes be unique within a single document. However, it is also worth keeping in mind that for operating with referencing systems across a corpus of TEI files it is helpful (or even necessary in some circumstances) to have unique identifiers across the whole corpus.

-

Values of xml:id may be either populated computationally or manually. In the latter +

Values of xml:id may be either populated computationally or manually. In the latter case, it is advisable to put measures in place to avoid human error. Custom data types and Schematron rules may be defined in a customization ODD, and a check digit may be added to prevent unwanted changes. A check digit is computed from the value of an identifier and appended to the value itself. If the identifier is changed, the check digit would therefore invalidate it.

-
- -
-
Milestone -Elements

Where the desired reference system does not +

+
+
+ Milestone +Elements +

Where the desired reference system does not correspond to any particular structural hierarchy, or the document combines multiple structural hierarchies (as further discussed in ), simpler though less expressive methods may be necessary. In such cases the simplest solution may be just to mark up changes in the reference system where they occur, by using one or more of the following milestone elements:

-

These elements simply mark the points in a text at which some +

These elements simply mark the points in a text at which some category in a reference system changes. They have no content but subdivide the text into regions, rather in the same way as milestones mark points along a road, thus implicitly dividing it into segments. @@ -3769,7 +3001,7 @@ reference system based on milestones cannot readily be checked by an XML parser, so it will be the responsibility of the encoder or the application software to ensure that they are given in the correct order.

-

Milestone elements are often used as a simple means of capturing +

Milestone elements are often used as a simple means of capturing the original appearance of an early printed text, which will rarely coincide exactly with structural units, but they are generally useful wherever a text has two or more competing @@ -3781,96 +3013,46 @@ chapter-based structure using div1 elements, with parts end; or the reverse. Thus, an encoding in which chapters are regarded as more important than parts might encode some work in which chapter three begins in part one and is concluded in part two as -follows: - - -

- - -

- - -

- -

- - - +follows:

An encoding of the same work in which parts are regarded as more important than chapters might begin as follows: - - - - -

- -

- -

- - -

- -

- - - +

-

Similarly, when tagging dramatic verse one may wish to privilege stanzas +

Similarly, when tagging dramatic verse one may wish to privilege stanzas and lines over speeches and speakers, particularly where speeches cross line and line group boundaries. One might also wish to mark changes in narrative voice in a prose text. In either case, a milestone tag may be used to indicate change of speaker: - - Oh what is this I cannot see - With icy hands gets a hold on me - Oh I am Death, none can excel - I open the doors of heaven and hell - -

Milestone tags also make it possible to record the reference systems +Oh what is this I cannot seeWith icy hands gets a hold on meOh I am Death, none can excelI open the doors of heaven and hell +

+

Milestone tags also make it possible to record the reference systems used in a number of different editions of the same work. The reference system of any one edition can be recreated from a text in which all are marked by simply ignoring all elements that do not specify that edition on their ed attribute.

-

As a simple example, assuming that edition E1 of some collection of +

As a simple example, assuming that edition E1 of some collection of poems regards the first two poems as constituting the first book, while edition E2 regards the first poem as prefatory, a markup scheme like the following might be adopted: - - - - - - - - - +

-

In this case no n value is specified, since the numbers +

In this case no n value is specified, since the numbers rise predictably and the application can keep a count from the start of the document, if desired.

-

The value of the n attribute may but need not include the +

The value of the n attribute may but need not include the identifiers used for any larger sections. That is, either of the following styles is legitimate: - - - - - + or - - - - - +

-

When using milestone tags, line numbers may be supplied for +

When using milestone tags, line numbers may be supplied for every line or only periodically (every fifth, every tenth line). The latter may be simpler; the former is more reliable.

-

The style of numbering used in the values of n is +

The style of numbering used in the values of n is unrestricted: for the example above, I.i, I.ii, and I.iii could have been used equally well if preferred. The special value unnumbered should be reserved for marking @@ -3878,24 +3060,24 @@ sections of text which fall outside the normal numbering system (e.g. chapter heads, poem numbers, titles, or speaker attributions in a verse drama).

-

By default, there are no constraints on the values supplied for +

By default, there are no constraints on the values supplied for the ed attribute. If it is felt appropriate to enforce such a restriction, the techniques described in may be used, for example to specify that the attribute must specify one of a predefined set of values.

-

See below, section , for examples of +

See below, section , for examples of declarations for the reference systems just shown.

-

Milestone elements may be used to mark any kind of shift in the +

Milestone elements may be used to mark any kind of shift in the properties associated with a piece of text, whether or not would normally be considered a reference system. For example, they may be used to mark changes in narrative voice in a prose text, or changes of speaker in a dramatic text, where these are not marked using structural elements such as sp, perhaps in order to avoid a clash of hierarchies.

- -

As noted in above, milestone elements such + +

As noted in above, milestone elements such as lb or pb represent whitespace and are therefore by default assumed to occur between orthographic tokens in the text, where these are not otherwise indicated. By default it is reasonable to assume that @@ -3917,16 +3099,17 @@ Where hyphenation appears before a line or page break, the encoder may or may not choose to record the fact, either explicitly using an appropriate Unicode character, or descriptively for example by means of the rend attribute; see further .

- - - - - - - -
-
Declaring Reference Systems -

Whatever kind of reference system is used in an electronic text, it + + + + + + + +

+
+ Declaring Reference Systems +

Whatever kind of reference system is used in an electronic text, it is recommended that the TEI header contain a description of its construction in the refsDecl element described in section . As described there, the declaration @@ -3934,132 +3117,75 @@ may consist either of a formal declaration using the cRefPattern or citeStructure elements, or an informal description in prose. One of the former is recommended because unlike prose they can be processed by software.

- -

The three examples given in section would be declared as follows. The first example encodes +

The three examples given in section would be declared as follows. The first example encodes the standard references for Ovid's Amores one level at a time, using the n attribute on the div1, div2, div3, and l tags. The header section for such - an encoding should look something like this: - - - -

A canonical reference is assembled with - - the name of the : the - n of a div1, - a space, - the number of the : the - n of a child div2, - a full stop - the number of the : the - n of a child div3, - the line number: the n value of a - child l - -

- - -

Same as above, but without the last component (full - stop followed by the l's n.

- - -

Same as above, but without the poem component (full - stop followed by the div3's n.

- - - - + an encoding should look something like this:

A canonical reference is assembled with + the name of the : the + n of a div1,a space,the number of the : the + n of a child div2,a full stopthe number of the : the + n of a child div3,the line number: the n value of a + child l +

Same as above, but without the last component (full + stop followed by the l's n.

Same as above, but without the poem component (full + stop followed by the div3's n.

-

The second example encodes the same reference system, again using +

The second example encodes the same reference system, again using the n attribute on the div1, div2, div3, and l tags, but giving the reference string in full on each tag. If canonical references are made only to lines, the -reference system could be declared as follows: - - +reference system could be declared as follows: Since the entire regular expression is enclosed as a parenthetical subgroup, the entire canonical reference string is sought as the value of the n attribute on an l element.

-

In order to handle references to poems as well as to individual +

In order to handle references to poems as well as to individual lines, the declaration for the reference system must be more complicated: - - - - + This declaration indicates that the entire reference string must be sought as the value of the n attribute on a div1, div2, div3, or l element.

-

The third example encodes the same reference system, this time +

The third example encodes the same reference system, this time giving the entire reference string as the value of the xml:id attribute on the relevant tags. The reference system declaration for such an encoding could be: - - - + although in general there seems to be little advantage in this case: it is no more difficult to use a standard relative URI reference as the value of target.

-

In cases where a more complete formal declaration of text structure is desirable, +

In cases where a more complete formal declaration of text structure is desirable, for example in systems that will present the contents of a large TEI file in smaller chunks, the citeStructure element may be used. This method permits canonical references to be resolved and also allows them to be extracted, so that, for example, a list of resolvable citations may be generated from the document. The example from the Amores above could be implemented using citeStructure thus: - - - - - - - - - - -

-

citeStructure also provides a method for attaching informational properties to +

+

citeStructure also provides a method for attaching informational properties to units of structure, by means of the citeData element. The work, book, and poem divisions above might all have head elements which provide a title for the section. If we wish that information to be extractable, we can use citeData to specify where it is to be found: - - - - - - - - - - - - - - + The example above maps the head element to the Dublin Core property title. For convenience, property URIs may be abbreviated using prefixDef.

-

Reference systems recorded by means of milestone tags can also be +

Reference systems recorded by means of milestone tags can also be declared; the following prose description could be used to declare the example given in section . - -

Standard references to work, book, poem, and line may be - constructed from the milestone tags in the text.

- +

Standard references to work, book, poem, and line may be + constructed from the milestone tags in the text.

 Or in this way, using a formal declaration for this reference scheme derived from edition E1. - - - - - - +

-
-
Bibliographic Citations and References -

Bibliographic references (that is, full descriptions of bibliographic +

+
+
+ Bibliographic Citations and References +

Bibliographic references (that is, full descriptions of bibliographic items such as books, articles, films, broadcasts, songs, etc.) or pointers to them may appear at various places in a TEI text. They are required at several points within the TEI header's source description, @@ -4069,15 +3195,11 @@ collected together in a list as a distinct part of a text; detailed bibliographic descriptions of manuscript or other source materials may also be required. These Guidelines propose a number of specialized elements to encode such descriptions, which together constitute the model.biblLike class. - - - + Lists of such elements may also be encoded using the following element: - - +

- -

In printed texts, the individual constituents of a bibliographic +

In printed texts, the individual constituents of a bibliographic reference are conventionally marked off from each other and from the flow of text by such features as bracketing, italics, special punctuation conventions, underlining, etc. In electronic texts, such @@ -4090,8 +3212,7 @@ component of a title. quite apart from the need to distinguish the reference itself as a textual object with particular linguistic properties.

- -

It should be emphasized that for references as for other textual +

It should be emphasized that for references as for other textual features, the primary or sole consideration is not how the text should be formatted when it is printed or displayed. The distinctions permitted by the scheme outlined here may not necessarily be all that particular @@ -4112,8 +3233,7 @@ fuller account of that practice as applied to electronic texts see section ; for a brief mention of related library standards see section .

- -

The most commonly used elements in the model.biblLike class are biblStruct and +

The most commonly used elements in the model.biblLike class are biblStruct and bibl. biblStruct will usually be easier to process mechanically than bibl because its structure is more constrained and predictable. It is suited to situations in which the @@ -4125,8 +3245,7 @@ directly within a biblStruct element; instead, the presence and order of child elements must be used to reconstruct the punctuation required by a particular style.

- -

By contrast, bibl allows for considerable flexibility in +

By contrast, bibl allows for considerable flexibility in that it can include both delimiting punctuation and unmarked-up text; and its constituents can also be ordered in any way. This makes it suitable for marking up bibliographies in existing @@ -4141,7 +3260,7 @@ exact sequence required by the target rendering, including any necessary punctuation and linking words, rather than using an XSLT stylesheet or similar to reorder and punctuate the data.

-

+

The third element in the model.biblLike class, biblFull, has a content model based on the fileDesc element of the @@ -4167,11 +3286,9 @@ ISBD-derived citation formats (such as ANSI/NISO Z39.29 and ГОСТ 7.1) are not entirely conformant to ISBD either, since they may begin with a statement of authorship that does not map to the ISBD statement of responsibility.

- - - -
Methods of Encoding Bibliographic References and Lists of References -

+

+ Methods of Encoding Bibliographic References and Lists of References +

The members of the model.biblLike class all share a number of possible component sub-elements. For the bibl and biblStruct elements, exactly the same @@ -4179,7 +3296,7 @@ sub-elements are concerned, and they are described together in section ; for the biblFull element, the sub-elements concerned are fully described in section .

-

Different levels of specific tagging may be appropriate in different +

Different levels of specific tagging may be appropriate in different situations. In some cases, it may be felt necessary to mark just the extent of the reference itself, with perhaps a few distinctions being made within it (for example, between the part of the reference which @@ -4196,7 +3313,7 @@ reference at all: was Tufte's Envisioning Information, although he may never have actually read it.

-

Some bibliographic references are extremely elliptical, often only a +

Some bibliographic references are extremely elliptical, often only a string of the form Baxter, 1983. If no further details of Baxter's book are given in the source text and none is supplied by the encoder, then the reference thus given should be tagged as a @@ -4213,53 +3330,24 @@ a full long-form reference found elsewhere in the text. The usual encoding of short-form references such as Baxter, 1983 is not as bibl elements but as cross-references to such elements; see section -below.

-

In cases where the encoder wishes to impose more structure on the +below.

+

In cases where the encoder wishes to impose more structure on the bibliographic information, for example to make sure it conforms to a particular stylesheet or retrieval processor, the biblStruct element should be used. Note that several of the features in this and later examples are explained later in the current section. - - - - - Edward - R. - Tufte - - 6506403994 - https://id.loc.gov/authorities/names/n50012763.html - - Envisioning Information - - Cheshire, Conn. - Graphics Press - - - - +EdwardR.Tufte6506403994https://id.loc.gov/authorities/names/n50012763.htmlEnvisioning InformationCheshire, Conn.Graphics Press

-

A more complex and detailed bibliographic structure is provided by the +

A more complex and detailed bibliographic structure is provided by the biblFull element defined in the TEI header module. This element is provided as a means of embedding the file description of one existing digital text within that of another (see further section ); however, its use is not confined to digital texts, and it may be used in the same way as any other bibliographic element, as in this example: - - - Envisioning Information - Tufte, Edward R[olf] - - 126 pp. - - Graphics Press - Cheshire, Conn. USA - 1990 - - +Envisioning InformationTufte, Edward R[olf]126 pp.Graphics PressCheshire, Conn. USA1990

-

A list of bibliographic items, of whatever kind, may be treated in +

A list of bibliographic items, of whatever kind, may be treated in the same way as any other list (see section ). Alternatively, the specialized listBibl element may be used. The difference between the two is that a list contains @@ -4325,62 +3413,39 @@ element, though the following example combines both fully structured items, the key information is marked up, but it is presented in an order which makes it suitable for direct rendering, with the punctuation included.

- -

The listBibl element is most appropriate +

The listBibl element is most appropriate for a more formal bibliography. The same bibl or biblStruct elements may however be embedded within an ordinary list, thus allowing them to be mixed with running prose or presented informally, as in the following version of the same example: - - Bibliography - - - Nelson, T. H. - Replacing the printed word: + <egXML xmlns="http://www.tei-c.org/ns/Examples" source="#NONE"><list><head>Bibliography</head><item><bibl xml:id="NEL80"><author>Nelson, T. H.</author><title level="a">Replacing the printed word: a complete literary system. Information Processing '80: Proceedings of the IFIPS Congress, October 1980. - Simon H. Lavington - North-Holland: + Simon H. LavingtonNorth-Holland: Amsterdam, 1980. pp 1013–23 - - Apparently a draft of section 4 of - Literary Machines. - - - - Ted Nelson: Literary Machines - (privately published, 1987) - - - - Baxter, Glen - Glen Baxter His Life: the years of struggle + Apparently a draft of section 4 of + Literary Machines.Ted Nelson: Literary Machines + (privately published, 1987)Baxter, GlenGlen Baxter His Life: the years of struggle London: Thames and Hudson, 1988. - - - +

-
-
Components of Bibliographic References - -

This section discusses commonly occurring components of +

+
+ Components of Bibliographic References +

This section discusses commonly occurring components of bibliographic references and elements used for encoding them. They fall into four groups: - -elements for grouping components of the analytic, +elements for grouping components of the analytic, monographic, and series levels in a -structured bibliographic reference -titles of various kinds, and statements of intellectual -responsibility (authorship, etc.) -information relating to the publication, pagination, etc. of an +structured bibliographic referencetitles of various kinds, and statements of intellectual +responsibility (authorship, etc.)information relating to the publication, pagination, etc. of an item (most of these -constitute the default members of the model.biblPart class) -annotation, commentary, and further detail The +constitute the default members of the model.biblPart class) annotation, commentary, and further detail The following sections describe the elements which may be used to represent such information within a bibl or biblStruct element. Within the former, elements from the @@ -4390,21 +3455,19 @@ within the latter, such of these elements as exist for a given reference must be distinguished, and must also be presented in a specific order, discussed further below (section ).

-
Analytic, Monographic, and Series Levels -

In common library practice a clear distinction is made between an +

+ Analytic, Monographic, and Series Levels +

In common library practice a clear distinction is made between an individual item within a larger collection and a free-standing book, journal, or collection. Similarly a book in a series is distinguished sharply from the series within which it appears. An article forming part of a collection which itself appears in a series thus has a bibliographic description with three quite distinct levels of information: - -the analytic level, giving the title, author, etc., of the article; - -the monographic +the analytic level, giving the title, author, etc., of the article; + the monographic level, giving the title, editor, etc., of the collection; - -the series + the series level, giving the title of the series, possibly the names of its editors, etc., and the number of the volume within that series. @@ -4412,34 +3475,27 @@ In the same way, an article in a journal requires at least two levels of information: the analytic level describing the article itself, and the monographic level describing the journal.

-

A different identifying number may be supplied for any of these +

A different identifying number may be supplied for any of these three items, that is, for the analytic item, the monographic item, or the series.

-

Within bibl, these three levels may be distinguished simply by the use +

Within bibl, these three levels may be distinguished simply by the use of the level attribute on title. They may also be distinguished through the practice of employing nested bibl elements. In this example, for instance, the monograph-level component of the reference is encapsulated in its own bibl within the main bibl for the article: - - - Beaupaire + Beaupaire (Edmond), A propos de la rue de la Femme-sans-Tête, - - La Cité, + La Cité, janvier 1911, pp. 5-17. - - - +

- -

Within biblStruct, the levels are distinguished by the use of the +

Within biblStruct, the levels are distinguished by the use of the following distinct elements:

- -

For purposes of TEI encoding, journals and anthologies are both +

For purposes of TEI encoding, journals and anthologies are both treated as monographs; a journal title should thus be tagged as a title level="j" element within a monogr element. Individual articles in the journal or @@ -4455,133 +3511,75 @@ typically use a different entry for each publication, while academic footnoting practice typically treats all publications of the same article in a single entry.)

-

The biblScope element is used to supply further +

The biblScope element is used to supply further information about the location of some part of a bibliographic reference. It specifies where to find the component in which it appears within the immediately preceding component of a different level.

-

In the following example, Schacter's article +

In the following example, Schacter's article Iolaos appeared on pages 64 to 70 of a volume entitled Herakles to Poseidon, which was itself the second of a four volumes published together under the title Cults of Boitia; this last title constituted the 38th volume in the series of Bulletin of the Institute of Classical Studies Supplements: - - -Albert Schachter -Iolaos - - -Herakles to Poseidon -1986 -64-70 - - -Cults of Boiotia -London -4 vols. -2 - - -Bulletin of the Institute of Classical Studies -Supplements -38 - - - + Albert SchachterIolaosHerakles to Poseidon198664-70Cults of BoiotiaLondon4 vols.2Bulletin of the Institute of Classical Studies +Supplements38

- -

In the following example, the article cited has been published +

In the following example, the article cited has been published twice, once in a journal (where it appeared in volume 40, on pages 3 -46 of the issue of October 1986) and once as a free-standing item, which appeared as number 11 of a German language series. - - - - Thaller - Manfred - A Draft Proposal for a Standard for the - Coding of Machine Readable Sources - - - - Historical Social Research - - October 1986 - - 40 - 3-46 - - Modelling Historical Data: + <egXML xmlns="http://www.tei-c.org/ns/Examples" source="#NONE"><biblStruct><analytic><author><persName><surname>Thaller</surname><forename>Manfred</forename></persName></author><title level="a">A Draft Proposal for a Standard for the + Coding of Machine Readable SourcesHistorical Social ResearchOctober 1986403-46Modelling Historical Data: Towards a Standard for Encoding and - Exchanging Machine-Readable Texts - DanielI. - Greenstein - - St. Katharinen - Max-Planck-Institut für Geschichte + Exchanging Machine-Readable TextsDanielI.GreensteinSt. KatharinenMax-Planck-Institut für Geschichte In Kommission bei - Scripta Mercaturae Verlag - - - - - Halbgraue Reihe - zur Historischen Fachinformatik - - Herausgegeben von - Manfred Thaller - Max-Planck-Institut für Geschichte - - Serie A: Historische Quellenkunden - 11 - - + Scripta Mercaturae VerlagHalbgraue Reihe + zur Historischen FachinformatikHerausgegeben vonManfred ThallerMax-Planck-Institut für GeschichteSerie A: Historische Quellenkunden11

- - -

The practice of analytic vs. monographic citation, as described here, +

The practice of analytic vs. monographic citation, as described here, should be distinguished from the practice of including within one citation a reference to another work, which the encoder considers to be related to in some way: see further below.

-

If an identifier is available for the analytic item, it should be +

If an identifier is available for the analytic item, it should be represented by means of an idno element placed within the analytic element, as in the following example where a DOI (Digital Object identifier) is supplied for the article in question.

- - - - - -James -H. -Coombs - - -Allen -Renear - - -Steven -J. -DeRose - -Markup Systems and The Future of Scholarly Text + <egXML xmlns="http://www.tei-c.org/ns/Examples" source="#NONE"> + <biblStruct> + <analytic> + <author> + <forename>James</forename> + <forename>H.</forename> + <surname>Coombs</surname> + </author> + <author> + <forename>Allen</forename> + <surname>Renear</surname> + </author> + <author> + <forename>Steven</forename> + <forename>J.</forename> + <surname>DeRose</surname> + </author> + <title level="a">Markup Systems and The Future of Scholarly Text Processing -10.1145/32206.32209 -http://xml.coverpages.org/coombs.html - - -Communications of the ACM -1987 -30 -11 -933–947 - - - -

Punctuation must not appear between the elements within a + 10.1145/32206.32209 + http://xml.coverpages.org/coombs.html + + + Communications of the ACM + + 1987 + + 30 + 11 + 933–947 + + + +

Punctuation must not appear between the elements within a structured bibliographic entry encoded with biblStruct or biblFull, unless it is contained within the elements it delimits. When (as in most of the examples in this chapter) entries are encoded without any @@ -4589,29 +3587,15 @@ inter-element punctuation, they can be usually be processed more easily by rendering systems able to output bibliographic references in any of several styles.

-

Within a bibl however, it is possible and often convenient +

Within a bibl however, it is possible and often convenient to include punctuation. - - - - - Nelson, - T. - H. - - - 1980. + Nelson, + T.H.1980. Replacing the printed word: a complete literary system. In Information Processing '80: Proceedings of the IFIPS Congress, October 1980, ed. - - - Simon - H. - Lavington - - , + SimonH.Lavington, 1013-23. Amsterdam: North- Holland. (Apparently a draft of section 4 of @@ -4624,42 +3608,30 @@ markup approach can provide easy rendering, if only one styleguide is targeted, or an original source document uses a specific styleguide, while still allowing for automated recovery of key data items such as names of authors, titles etc.

- - - - - - -
-
Titles, Authors, and Editors -

Bibliographic references typically include the + + + + + +

+
+ Titles, Authors, and Editors +

Bibliographic references typically include the title of the work being cited and the names of those intellectually responsible for it. For articles in journals or collections, such statements should appear both for the analytic and for the monographic level. The following elements are provided for tagging such elements: - - - - - - - - - - - - + The elements author, editor, respStmt, meeting, sponsor, funder, and principal are the default members of the model.respLike class, a subclass of the model.biblPart class to which the constituents of the bibl element belong.

- -

In bibliographic references, all titles should be tagged as such, +

In bibliographic references, all titles should be tagged as such, whether analytic, monographic, or series titles. The single element title is used for all these cases. When it appears directly within an analytic, monogr, or series element, title is interpreted as belonging to the appropriate level. However, it is recommended that the level attribute be used to signal this explicitly.

-

It is a semantic error to +

It is a semantic error to give a value for the level attribute which is inconsistent with the context. The level value a implies the analytic level; the values @@ -4669,35 +3641,19 @@ the analytic, monogr, or series element; if it is enclosed only indirectly (i.e., nested more deeply), no semantic error need be present. For example, the analytic title may contain a monographic title, as in the following example: - - - - - Lucy - Allen - Paton - - - Notes on Manuscripts of the + <egXML xmlns="http://www.tei-c.org/ns/Examples" source="#NONE"><biblStruct><analytic><author ref="http://id.loc.gov/authorities/names/no2001067434"><persName><forename>Lucy</forename><forename>Allen</forename><surname>Paton</surname></persName></author><title>Notes on Manuscripts of the <title level="m" xml:lang="fr">Prophécies de Merlin - - - - PMLA - 1913 - 8 - 122 - + PMLA19138122 In this case, the analytic title Notes on Manuscripts of the Prophécies de Merlin needs no level attribute because it is directly contained by an analytic element; the monographic title contained within it, Prophécies de Merlin, is not semantically erroneous because it is not directly contained by the analytic element.

-

In some bibliographic applications, it may prove useful to +

In some bibliographic applications, it may prove useful to distinguish main titles from subordinate titles, parallel titles, etc. The type attribute is provided to allow this distinction to be recorded.

-

The following reference, from a national standard for bibliographic +

The following reference, from a national standard for bibliographic references, illustrates this type of analysis with its distinction between main and subordinate titles. Note that this uses the more flexible @@ -4717,7 +3673,7 @@ components of the reference (notably the authors).

-

Slightly more complex is the distinction made below among main, +

Slightly more complex is the distinction made below among main, subordinate, and parallel titles, in an example from the same source (p. 63). The punctuation and the bibliographic analysis are those given in ANSI Z39.29-1977; the punctuation is in the style prescribed by the @@ -4739,8 +3695,7 @@ elements of the reference. New York: Broude Brothers; [1951] (B.B. 59). vi, 685 p.

- -

The elements author and editor have fairly +

The elements author and editor have fairly obvious significance for printed books and articles; for other kinds of bibliographic items their proper usage may be less obvious. The @@ -4756,18 +3711,19 @@ compiler, may however be marked by means of the editor element, optionally using the role attribute to specify the nature of their responsibility more exactly.

-

Many bibliographic and Linked Data applications require disambiguation +

Many bibliographic and Linked Data applications require disambiguation of author names using unique identifiers. Both the author and editor elements may contain one or more idno elements, to supply such identifiers. Alternatively, if only a single identifier is to be recorded, the key or ref attribute may be used, as further discussed in .

- - John Warrack. „Es waren seine letzten Töne!“ + + John Warrack. „Es waren seine letzten Töne!“ In Joachim Veit and Frank Ziegler eds. Weber-Studien Bd. 3, Mainz (1996), pp.300–317 - -

For anyone else with responsibility for the work, the + + +

For anyone else with responsibility for the work, the respStmt element should be used. The nature of the responsibility is indicated by means of a resp element, and the person, organization, etc. responsible by a name, @@ -4778,12 +3734,12 @@ naming elements (name, persName, orgName, or rs) followed by one or more resp elements, or at least one resp element followed by one or more of the four naming elements.

-

Examples of +

Examples of secondary responsibility of this kind include the roles of illustrator, translator, encoder, and annotator. The respStmt element may also be used for editors, if it is desired to record the specific terms in which their role is described.

-

Examples of author and editor may be found in +

Examples of author and editor may be found in sections , and ; wherever author and editor may occur, the respStmt element may also occur. When one of these elements precedes or @@ -4791,7 +3747,7 @@ immediately follows a title, it applies to that title; when it follows an edition element or occurs within an edition statement, it applies to the edition in question.

-

In this example, the respStmt elements apply to the work as +

In this example, the respStmt elements apply to the work as a whole, not merely to the first edition: - - Lominandze, DG. +Lominandze, DG. Cyclotron waves in plasma. - - Translated by - AN. Dellis - ; - - edited by - SM. Hamberger - . - 1st ed. - Oxford: + Translated byAN. Dellis; + edited bySM. Hamberger. + 1st ed.Oxford: Pergamon Press, 1981. - 206 p. - International series in natural philosophy. + 206 p.International series in natural philosophy. Translation of: Ciklotronnye volny v plazme. 0-08-021680-3. - - +

-

This example retains the original punctuation and editorial conventions of +

This example retains the original punctuation and editorial conventions of the source (ISO 690:1987) and is therefore encoded using the bibl element.

-

In the following example, by contrast, the respStmt element applies +

In the following example, by contrast, the respStmt element applies to the edition, and not to the collection per se (Moser and Tervooren were not responsible for the first thirty-five printings). As is permissible within a biblStruct element, the component elements @@ -4836,134 +3782,60 @@ have been reordered from their appearance on the title page of the volume in order to ensure the correct relationship of the collection title, the edition statement, and the statement of responsibility. - - - Des Minnesangs Frühling - Mit 1 Faksimile - 36., neugestaltete und erweiterte Auflage - - Unter Benutzung der Ausgaben von Karl + Des Minnesangs FrühlingMit 1 Faksimile36., neugestaltete und erweiterte AuflageUnter Benutzung der Ausgaben von Karl Lachmann und Moriz Haupt, Friedrich - Vogt und Carl von Kraus bearbeitet von - Hugo Moser - Helmut Tervooren - - - Stuttgart - S. Hirzel Verlag - 1977 - - I Texte - - + Vogt und Carl von Kraus bearbeitet vonHugo MoserHelmut TervoorenStuttgartS. Hirzel Verlag1977I Texte

-

The party with a particular responsibility for the intellectual +

The party with a particular responsibility for the intellectual content may vary over time. Likewise, a given individal's responsibility or role may change over time. These situations may be recorded with the respStmt element. For example, the following could be used when one proofreader took over for another. - - proofreading - Ashley Cross - Loren Noveck - + proofreadingAshley CrossLoren Noveck The following example records the fact that one individual had two distinctly different intellectual responsibilities at different times. - - Erica Dillon - annotated uncredited citations - encoded named entities - + Erica Dillonannotated uncredited citationsencoded named entities

-

Another form of responsibility arises when a +

Another form of responsibility arises when a work is published as the outcome of a conference, workshop or similar meeting. The meeting element may be used to supply this information, as in the following example: - - - Proceedings of a workshop on corpus resources - - Programme Organizer - Geoffrey Leech - - DTI Speech and Language Technology Club meeting, 3-4 - January 1990, Wadham College, Oxford - Oxford - - - + Proceedings of a workshop on corpus resourcesProgramme OrganizerGeoffrey LeechDTI Speech and Language Technology Club meeting, 3-4 + January 1990, Wadham College, OxfordOxford

- - - - - - - - - -
-
Document Identifiers -

Many bibliographic references include identifiers for a work to help with precise identification of an appropriate document. For example, a book in the Short Title Catalogue could be referenced with its STC number: - - - - - John - Downame - - Foure treatises tending to disswade all Christians from foure no lesse hainous then common sinnes - 7141 - - At London - Imprinted by Felix Kyngston, for William Welby, and are to be sold at his shop in Pauls Church-yard at the signe of the Greyhound - 1609 - - - - + + + + + + + + +

+
+ Document Identifiers +

Many bibliographic references include identifiers for a work to help with precise identification of an appropriate document. For example, a book in the Short Title Catalogue could be referenced with its STC number: + JohnDownameFoure treatises tending to disswade all Christians from foure no lesse hainous then common sinnes7141At LondonImprinted by Felix Kyngston, for William Welby, and are to be sold at his shop in Pauls Church-yard at the signe of the Greyhound1609

-

However, some bibliographic references actually require identifiers of various types because they do not include a statement of the title and the names of those intellectually responsible for it. The following elements may be used for such purposes: - - - - - - +

However, some bibliographic references actually require identifiers of various types because they do not include a statement of the title and the names of those intellectually responsible for it. The following elements may be used for such purposes: +

-

For example, a citation to a patent typically includes a country or organization code (a two-character code identifying a patent authority) and a serial number for the patent (whose structure varies by patent authority). The citation might also contain a kind code (which characterizes a particular publication for the patent and which corresponds to a specific stage in the patent procedure) and the date when the patent was filed with or published by the issuing authority. For bibliographic references to patents, the above elements may be used as follows: - -orgName, within authority, may be used to contain the code of the patent authority. The type attribute may be used to specify the type of patent authority (such as a national patent office or a supra-national patent organization). -idno may be used to contain the serial number assigned by the corresponding patent authority. -classCode may be used to contain the kind code of the patent document. -date may be used to contain the date of the patent document. The type attribute may be used to specify whether this corresponds to the filing date of a patent application or the publication date of a patent publication. - +

For example, a citation to a patent typically includes a country or organization code (a two-character code identifying a patent authority) and a serial number for the patent (whose structure varies by patent authority). The citation might also contain a kind code (which characterizes a particular publication for the patent and which corresponds to a specific stage in the patent procedure) and the date when the patent was filed with or published by the issuing authority. For bibliographic references to patents, the above elements may be used as follows: +orgName, within authority, may be used to contain the code of the patent authority. The type attribute may be used to specify the type of patent authority (such as a national patent office or a supra-national patent organization).idno may be used to contain the serial number assigned by the corresponding patent authority.classCode may be used to contain the kind code of the patent document.date may be used to contain the date of the patent document. The type attribute may be used to specify whether this corresponds to the filing date of a patent application or the publication date of a patent publication.

-

The following reference illustrates an encoding for a patent +

The following reference illustrates an encoding for a patent publication which might be cited in print as United States patent US 6,885,550 B1, issued April 26, 2005: - - - - - US - - 6885550 - - B1 - April 26, 2005 - - - - + US6885550B1April 26, 2005

-
-
Imprint, Size of a Document, and Reprint Information -

By imprint is meant all the information +

+
+ Imprint, Size of a Document, and Reprint Information +

By imprint is meant all the information relating to the publication of a work: the person or organization by whose authority and in whose name a bibliographic entity such as a book is made public or distributed (whether a commercial publisher or @@ -4974,15 +3846,7 @@ pages in a print publication (or equivalent information for non-print materials), and possibly also the specific location of the material being cited within its containing publication. The following elements are provided to hold this information: - - - - - - - - - + Members of the model classes model.imprintPart and model.dateLike @@ -4990,12 +3854,9 @@ may appear inside an imprint element in a specific location within a biblStruct, or alternatively, they may appear alongside any other bibliographic component inside a bibl. - - - - +

-

For bibliographic purposes, usually only the place (or places) of +

For bibliographic purposes, usually only the place (or places) of publication are required, possibly including the name of the country, rather than a full address; the element pubPlace is provided for this purpose. Where however the full postal address is likely to @@ -5007,240 +3868,88 @@ section may be used; this involves no claim that the information given is either a full address or the name of a city.

-

The name of the publisher of an item should be marked using the +

The name of the publisher of an item should be marked using the publisher element even if the item is made public (published) by an organization other than a conventional publisher, as is frequently the case with technical reports: - - - Nicholas, Charles K. - Welsch, Lawrence A. - On the interchangeability of SGML and ODA - NISTIR 4681 - - Gaithersburg, MD - + Nicholas, Charles K.Welsch, Lawrence A.On the interchangeability of SGML and ODANISTIR 4681Gaithersburg, MD National Institute of Standards and Technology - - January 1992 - - 19 pp. - - + January 199219 pp. and with dissertations: - - - Hansen, W. - Creation of hierarchic text - with a computer display - ANL-7818 - Ph.D. dissertation - - Dept. of Computer Science, Stanford Univ. - Stanford, CA - June 1971 - - - +Hansen, W.Creation of hierarchic text + with a computer displayANL-7818Ph.D. dissertationDept. of Computer Science, Stanford Univ.Stanford, CAJune 1971

-

In this second example, the idno element is used to +

In this second example, the idno element is used to provide the identifier allocated to the thesis by the Argonne National Laboratory. Since it applies to the monographic element, the idno should be provided as a direct child of the monogr element, rather than elsewhere in the biblStruct element.

-

The specialist elements publisher and distributor +

The specialist elements publisher and distributor are provided to cover the most common roles related to the production and distribution of a bibliographical item, but other roles such as printer and bookseller may also need to be encoded, and respStmt is available inside imprint for this purpose.

- -

When an item has been reprinted, especially reprinted without change +

When an item has been reprinted, especially reprinted without change from a specific earlier edition, the reprint may appear in a monogr element with only the imprint and other details of the reprint. In the following example, a microform reprint has been issued without any change in the title or authorship. The series statement here applies only to the second monogr element. - - - Shirley, James - The gentlemen of Venice - a tragi-comedie presented at the private - house in Salisbury Court by Her Majesties servants - [Microform] - - London - H. Moseley - 1655 - - 78 p. - - - - New York - Readex Microprint - 1953 - - 1 microprint card, 23 x 15 cm. - - - Three centuries of drama: English, 1642–1700 - - +Shirley, JamesThe gentlemen of Venicea tragi-comedie presented at the private + house in Salisbury Court by Her Majesties servants[Microform]LondonH. Moseley165578 p.New YorkReadex Microprint19531 microprint card, 23 x 15 cm.Three centuries of drama: English, 1642–1700

-

This encoding can be extended to the case of patent documents, where the same patent application is published, with or without changes, at different stages of the patenting procedure. In this case, the kind code and, optionally, the publication date characterize different publications of the same patent application during the procedure. For example: - - - - - EP - - 1558513 - - A1 - - - - - - B1 - - - - - +

This encoding can be extended to the case of patent documents, where the same patent application is published, with or without changes, at different stages of the patenting procedure. In this case, the kind code and, optionally, the publication date characterize different publications of the same patent application during the procedure. For example: + EP1558513A1B1

-

The above bibliographic reference discloses different publications of the patent EP1558513 during the patenting procedure. The first publication from 3 August 2005 has the kind code "A1" indicating that it is a published patent application comprising the European search report issued after carrying out the search at the European Patent Office, whereas the second publication from 9 September 2009 has the kind code "B1" indicating that it was published after the patent application has been granted.

-

An alternative way of handling the above situations would be to use the +

The above bibliographic reference discloses different publications of the patent EP1558513 during the patenting procedure. The first publication from 3 August 2005 has the kind code "A1" indicating that it is a published patent application comprising the European search report issued after carrying out the search at the European Patent Office, whereas the second publication from 9 September 2009 has the kind code "B1" indicating that it was published after the patent application has been granted.

+

An alternative way of handling the above situations would be to use the relatedItem element described in section below.

-
-
-Scopes and Ranges in Bibliographic Citations -

Many bibliographic citations contain data limiting the citation to one +

+
+ Scopes and Ranges in Bibliographic Citations +

Many bibliographic citations contain data limiting the citation to one or more volumes, issues, or pages, or to a name or number of a subdivison of the host work. These come in two varieties: - -the scope of a bibliographic reference (encoded using biblScope) -the range of a work cited (encoded using citedRange) - +the scope of a bibliographic reference (encoded using biblScope)the range of a work cited (encoded using citedRange) Where it is desired to distinguish different classes of such information (volume number, page number, chapter number, etc.), the unit attribute may be used with any convenient typology (see the element definitions for biblScope and citedRange for some suggested values).

-

A scope of a bibliographic reference defines that the entire work +

A scope of a bibliographic reference defines that the entire work cited may be found in particular volumes, issues, pages, etc. For example: - - - - - Wrigley - E. - A. - - - Parish registers and the historian - - - - - Steel - D. - J. - - - - - Steel - A. - E. - F. - - - General sources of births, marriages and deaths before 1837 - - London - Society of Genealogists - - - 155–167 - - - National index of parish registers - 1 - - + WrigleyE.A.Parish registers and the historianSteelD.J.SteelA.E.F.General sources of births, marriages and deaths before 1837LondonSociety of Genealogists155–167National index of parish registers1

-

The unit attribute on biblScope is optional: +

The unit attribute on biblScope is optional: both the following are legal examples: - - - Boguraev, Branimir - Neff, Mary - Text Representation, Dictionary Structure, - and Lexical Knowledge - - - Literary & Linguistic Computing - - 1992 - - 7 - 2 - 110-112 - - - - - Chesnutt, David - Historical Editions in the States - - - Computers and the Humanities - - (December, 1991): - - 25.6 - 377–380 - - + Boguraev, BranimirNeff, MaryText Representation, Dictionary Structure, + and Lexical KnowledgeLiterary & Linguistic Computing199272110-112 +Chesnutt, DavidHistorical Editions in the StatesComputers and the Humanities(December, 1991):25.6377–380

-

On the other hand, a cited range encodes that the author cited +

On the other hand, a cited range encodes that the author cited only the portion defined by this range. For example, a footnote following a quotation from page 378 of Historical Editions in the States that includes a full bibliographic reference would be encoded using biblStruct as follows: - - - Chesnutt, David - Historical Editions in the States - - - Computers and the Humanities - - (December, 1991): - - 25.6 - 377–380 - - 378 - + Chesnutt, DavidHistorical Editions in the StatesComputers and the Humanities(December, 1991):25.6377–380378

- - - - - - - -
-
Series Information -

Series information may (in bibl elements) or must (in + + + + + + + +

+
+ Series Information +

Series information may (in bibl elements) or must (in biblStruct elements) be enclosed in a series element or (in a biblFull element) a seriesStmt element. The title of the series may be tagged title level="s", the @@ -5249,95 +3958,40 @@ statements for the series (e.g. the name and affiliation of the editor, as in the example in section ) may be tagged editor or respStmt. Any identifier associated with the series itself should be marked using the idno element. -

-
Related Items -

In bibliographic parlance, a related item is any +

+
+
+ Related Items +

In bibliographic parlance, a related item is any bibliographic item which, though related to that being defined, is distinct from it. The distinction between analytic and monographic items made above may be thought of as a special case of this kind of related item. More usually however, the term is applied to such items as translations, continuations, different versions, parts, etc.

-

The element relatedItem is provided as a means of documenting such +

The element relatedItem is provided as a means of documenting such associated items: - - -

- -

In the following example, the first biblStruct describes a +

+

In the following example, the first biblStruct describes a facsimile edition, and the second describes the work of which it is a facsimile. The relation between the facsimile and its source is represented by means of a relatedItem within the first description, which points to the description of the source. - - - Swinburne, Algernon Charles - Swinburne's <title level="m">Atalanta in Calydon: A Facsimile of the - First Edition - Georges Lafourcade - - London - Oxford UP - 1930 - - - - - - - - - - Swinburne, Algernon Charles - Atalanta in Calydon - - London - Edward Moxon - 1865 - - - - + Swinburne, Algernon CharlesSwinburne's <title level="m">Atalanta in Calydon: A Facsimile of the + First EditionGeorges LafourcadeLondonOxford UP1930 Swinburne, Algernon CharlesAtalanta in CalydonLondonEdward Moxon1865

- -

The ref element in the above example could be +

The ref element in the above example could be replaced by the referenced biblStruct itself since a relatedItem may contain any form of bibliographic reference. For example, one of the examples quoted above might also be encoded as follows: - - - Shirley, James - The gentlemen of Venice - - New York - Readex Microprint - 1953 - - 1 microprint card, 23 x 15 cm. - - - Three centuries of drama: English, 1642–1700 - - - - Shirley, James - The gentlemen of Venice - a tragi-comedie presented at the private - house in Salisbury Court by Her Majesties servants - - London - H. Moseley - 1655 - - 78 p. - - + Shirley, JamesThe gentlemen of VeniceNew YorkReadex Microprint19531 microprint card, 23 x 15 cm.Three centuries of drama: English, 1642–1700Shirley, JamesThe gentlemen of Venicea tragi-comedie presented at the private + house in Salisbury Court by Her Majesties servantsLondonH. Moseley165578 p.

-

The type attribute should be used to indicate the +

The type attribute should be used to indicate the relationship between the bibliographic item and any relatedItem it contains or points to. The relationships may be transitive (for example translatedAs or @@ -5345,98 +3999,66 @@ be transitive (for example translatedAs or otherEdition). The subtype attribute may be used to provide a more detailed classification, where this is appropriate. Some further examples follow: - - - Tolkien, J.R.R. - Den hobbit - aus dem Engleschen iwwersat - Henry Wickens - - Esch-sur-Sûre - Op der Lay S. àr. L - 2002 - - - - - Tolkien, J.R.R. -The Hobbit. - Collins - 1997 - - - + Tolkien, J.R.R.Den hobbitaus dem Engleschen iwwersatHenry WickensEsch-sur-SûreOp der Lay S. àr. L2002Tolkien, J.R.R.The Hobbit. + Collins1997 In this example, a full bibliographic description of the edition used as source for the translation is provided within the content of the relatedItem. Alternatively this might be provided by means of a link, in which case the relatedItem would be empty: - - - +

- - - - - - - - - -
-
Notes and Statement of Language -

Explanatory notes about the publication of unusual items, the form of + + + + + + + + + +

+
+ Notes and Statement of Language +

Explanatory notes about the publication of unusual items, the form of an item (e.g. [Score] or [Microform]), or its provenance (e.g. translation of ...) may be tagged using the note element. The same element may be used for any descriptive annotation of a bibliographic entry in a database.

-

For example: - - Coombs, James H., Allen H. Renear, - and Steven J. DeRose. - Markup Systems and the Future of Scholarly -Text Processing. - Communications of the ACM - 30.11 (November 1987): 933–947. - Classic polemic supporting descriptive over procedural - markup in scholarly work. - +

For example: + Coombs, James H., Allen H. Renear, + and Steven J. DeRose.Markup Systems and the Future of Scholarly +Text Processing.Communications of the ACM30.11 (November 1987): 933–947.Classic polemic supporting descriptive over procedural + markup in scholarly work.

-

+

The textLang element may be used to record information about the languages used within a bibliographic item. This element can take the form of a simple note such as: - -Latin, with some glosses in Anglo-Saxon and French - + Latin, with some glosses in Anglo-Saxon and French However, it is generally recommended where feasible to use the mainLang attribute to record the chief language of the bibliographic item, and optionally the otherLangs to identify other languages used in the work. For example: - -Latin, with some glosses in Anglo-Saxon and French - + Latin, with some glosses in Anglo-Saxon and French

-

The mainLang and otherLangs attributes should both provide language identifiers +

The mainLang and otherLangs attributes should both provide language identifiers in the same form as used for xml:lang as described at . Where additional detail is needed correctly to describe a language, or to discuss its deployment in a given text, this should be done using the langUsage element in the TEI header, within which individual language elements document the languages used: see .

-

A description, in French, of a work predominantly in German, but also with some Latin might +

A description, in French, of a work predominantly in German, but also with some Latin might have a textLang like the following: - -allemand et latin - For more information about the use of textLang in manuscript descriptions + allemand et latin For more information about the use of textLang in manuscript descriptions see: .

- -
-
Order of Components within References -

The order of elements in bibl elements is not constrained. +

+
+ Order of Components within References +

The order of elements in bibl elements is not constrained.

-

In biblStruct elements, the analytic element, if +

In biblStruct elements, the analytic element, if it occurs, must come first, followed by one or more monogr and series elements, which may appear intermingled (as long as a monogr element comes first), and then zero or more of the @@ -5449,26 +4071,25 @@ be given together. Within monogr, the author, editor, and statements of responsibility may either come first or else follow the monographic title(s). Following these, the elements listed below, if present, must appear in the following order: - -notes on the publication (and meeting elements -describing the conference, in the case of a proceedings volume) -edition elements, each followed by any related -editor or respStmt elements -imprint -biblScope +notes on the publication (and meeting elements +describing the conference, in the case of a proceedings volume)edition elements, each followed by any related +editor or respStmt elementsimprintbiblScope Within imprint, the elements allowed may appear in any order.

-

Finally, within the series information in a +

Finally, within the series information in a biblStruct, the sequence of elements is not constrained.

-

If more detailed structuring of a bibliographic description is +

If more detailed structuring of a bibliographic description is required, the biblFull element should be used. This is not further described here, as its contents are essentially equivalent to those of the fileDesc element in the teiHeader, which is fully described in section . -

-
Bibliographic Pointers -

References which are pointers to bibliographic items, of whatever +

+
+
+
+ Bibliographic Pointers +

References which are pointers to bibliographic items, of whatever kind, should be treated in the same way as other cross-references (see section ). As discussed in that section, cross-referencing within TEI texts is in general represented by means of @@ -5481,166 +4102,69 @@ or is not to be encoded, the ptr element is used, as in the following example: As shown above () ...

-

Where the form of the reference is important, or contains additional qualifying information +

Where the form of the reference is important, or contains additional qualifying information which is to be kept but distinguished from the surrounding text, the ref element - should be used, as in the following example: Nelson claims (ibid, passim) ... It may + should be used, as in the following example: Nelson claims (ibid, passim) ... It may be important to distinguish between the short form of a bibliographic reference and some qualifying or additional information. The latter should not appear within the scope of the ref element when this is the case, as for example in an application concerned to - normalize bibliographic references: Nelson claims (Nelson [1980] pages 13–37) + normalize bibliographic references: Nelson claims (Nelson [1980] pages 13–37) ... If it is desired to capture additional information like this in a short-form reference, then bibl may be used with the corresp attribute pointing to - the full bibliographic reference: Nelson claims (Nelson [1980] pages 13–37) ... + the full bibliographic reference: Nelson claims (Nelson [1980] pages 13–37) ...

-

The ref element may also be used to provide a reference to a copy of the bibliographic item itself, particularly if this is available online, as in the following example: - - - - -Suzana -Sukovic - -Beyond the Scriptorium: The Role of the Library in Text -Encoding -https://www.dlib.org/dlib/january02/sukovic/01sukovic.html - - -D-Lib - -8 -1 -2002 - - - - +

The ref element may also be used to provide a reference to a copy of the bibliographic item itself, particularly if this is available online, as in the following example: + SuzanaSukovicBeyond the Scriptorium: The Role of the Library in Text +Encodinghttps://www.dlib.org/dlib/january02/sukovic/01sukovic.htmlD-Lib812002

-

The ptr element may be used as a child element of biblStruct to refer to the online catalog record of this bibliographic item: - - - - - - Germain - Brice - - - Description de la ville de Paris et de tout ce qu’elle contient de plus remarquable, par Germain Brice ; enrichie d’un nouveau plan et de figures dessinées et gravées correctement. 7e édition, revue et augmentée par l’auteur - - 1717 - Paris - F. Fournier - - In-12 - - - - +

The ptr element may be used as a child element of biblStruct to refer to the online catalog record of this bibliographic item: + GermainBriceDescription de la ville de Paris et de tout ce qu’elle contient de plus remarquable, par Germain Brice ; enrichie d’un nouveau plan et de figures dessinées et gravées correctement. 7e édition, revue et augmentée par l’auteur1717ParisF. FournierIn-12

-
- -
Relationship to Other Bibliographic Schemes - -

The bibliographic tagging defined here can capture the distinctions +

+
+ Relationship to Other Bibliographic Schemes +

The bibliographic tagging defined here can capture the distinctions required by most bibliographic encoding systems; for the benefit of users of some commonly used systems, the following lists of equivalences are offered, showing the relationship of the markup defined here to the fields defined for bibliographic records in the Scribe, BibTeX, and ProCite systems.

-

Listed below are the equivalences between the various bibliographic fields +

Listed below are the equivalences between the various bibliographic fields defined for use in the Scribe and BibTeX systems of bibliographic databases and the elements defined in this module.The BibTeX scheme is intentionally compatible with that of Scribe, although it omits some fields used by Scribe. Hence only one list of fields is given here. Elements and structures available in the module defined here which have no analogues in Scribe and BibTeX are not noted. - - - tag as placeName or address - - tag as note - - tag as author - - tag as title level="m" or title within - monogr - - tag as biblScope unit="chap" - - used only to record date entry was made in the bibliographic database; - not supported - - tag as edition - - tag as editor or respStmt - - tag as multiple editor or respStmt elements - - use the reg element, possibly inside a choice element, inside either an author or name - - use the reg element, possibly inside a choice element, inside a name type="org" - - tag as note, possibly using the form note - place="inline" - - used only for issuer of technical reports; tag as publisher - - tag as title level="j" or title within - monogr - - used to specify an alternate sort key for the bibliographic item, for - use instead of author's or editor's name; not supported - - tag as meeting or as note - - use date; if the date is not in a trivially parseable form, use +tag as placeName or addresstag as notetag as authortag as title level="m" or title within + monogrtag as biblScope unit="chap"used only to record date entry was made in the bibliographic database; + not supportedtag as editiontag as editor or respStmttag as multiple editor or respStmt elementsuse the reg element, possibly inside a choice element, inside either an author or nameuse the reg element, possibly inside a choice element, inside a name type="org"tag as note, possibly using the form note + place="inline"used only for issuer of technical reports; tag as publishertag as title level="j" or title within + monogrused to specify an alternate sort key for the bibliographic item, for + use instead of author's or editor's name; not supportedtag as meeting or as noteuse date; if the date is not in a trivially parseable form, use the when attribute to provide a normalized equivalent in one of - the format from XML Schema Part 2: Datatypes Second Edition - - tag as note - - tag as biblScope unit="issue" or biblScope + the format from XML Schema Part 2: Datatypes Second Editiontag as notetag as biblScope unit="issue" or biblScope unit="number"; for technical report numbers, use idno - type="docno" - - used only for sponsor of conference; use name type="org" - within respStmt within meeting element - - tag as biblScope unit="pp" - - tag as publisher - - used only for institutions at which thesis work is done; tag as - publisher - - tag as title level="s" or title within - series - - tag as title in appropriate context or with appropriate - level value - - tag as biblScope unit="volume" - - tag as date; if the date is not in a trivially parseable form, + type="docno"used only for sponsor of conference; use name type="org" + within respStmt within meeting elementtag as biblScope unit="pp"tag as publisherused only for institutions at which thesis work is done; tag as + publishertag as title level="s" or title within + seriestag as title in appropriate context or with appropriate + level valuetag as biblScope unit="volume"tag as date; if the date is not in a trivially parseable form, use the when attribute to provide an ISO-format - equivalent - -

- -
Passages of Verse or Drama -

The following elements are included in the core module for the + equivalent +

+
+
+
+ Passages of Verse or Drama +

The following elements are included in the core module for the convenience of those encoding texts which include mixtures of prose, verse and drama.

-

Full details of other, more specialized, elements for the encoding of +

Full details of other, more specialized, elements for the encoding of texts which are predominantly verse or drama are described in the appropriate chapter of part three (for verse, see the verse base described in chapter ; for performance texts, see the @@ -5649,17 +4173,16 @@ describe only the elements listed above, all of which can appear in any text, whichever of the three modes prose, verse, or drama may predominate in it.

- -
Core Tags for Verse -

Like other written texts, verse texts or poems may be +

+ Core Tags for Verse +

Like other written texts, verse texts or poems may be hierarchically subdivided, for example into books or cantos. These structural subdivisions should be encoded using the general purpose div or div1 (etc.) elements described below in chapters and . The fundamental unit of a verse text is the verse line rather than the paragraph, however.

- -

The l element is used to mark up verse lines, that is +

The l element is used to mark up verse lines, that is metrical rather than typographic lines. In some modern or free verse, it may be hard to decide whether the typographic line is to be regarded as a verse line or not, but the distinction is quite clear @@ -5672,13 +4195,7 @@ there is no need to introduce an lb tag at the start of every l element, but only at places where a new typographic line starts within a metrical line, as in the following example: - -Of Mans First Disobedience, and the Fruit -Of that Forbidden Tree, whose mortal tast -Brought Death into the World, and all our woe, -With loss of Eden, till one greater Man -Restore us, and regain the blissful Seat... - +Of Mans First Disobedience, and the FruitOf that Forbidden Tree, whose mortal tastBrought Death into the World, and all our woe,With loss of Eden, till one greater ManRestore us, and regain the blissful Seat... In the original copy text, the presence of an ornamental capital at the start of the poem means that the measure is not wide enough to @@ -5688,7 +4205,7 @@ this encoding makes no attempt to preserve information about the whitespace or indentation associated with either kind of line; if regarded as essential, this information would be recorded using the rend or rendition attributes discussed in .

-

The l element should not be used to represent typographic +

The l element should not be used to represent typographic lines in non-verse materials: if the line-breaking points in a prose text are considered important for analysis, they should be marked with the lb element. Alternatively, a neutral segmentation element @@ -5698,8 +4215,7 @@ discussion of these elements in chapter . The model.divPart class, along with elements from the model.pLike (paragraph-like) class.

- -

In some verse forms, regular groupings of lines are regarded as units +

In some verse forms, regular groupings of lines are regarded as units of some kind, often identified by a regular verse scheme. In stichic verse and couplets, groups of lines analogous to paragraphs are often indicated by indentation. In other verse forms, lines are grouped into @@ -5713,306 +4229,140 @@ line group where this is felt desirable, as in the following example. This example also demonstrates the rend attribute to indicate whether or not a line is indented. - - Come fill up the Glass, - Round, round let it pass, - 'Till our Reason be lost in our Wine: - Leave Conscience's Rules - To Women and Fools, - This only can make us divine. - - - Then a Mohock, a Mohock I'll be, - No Laws shall restrain - Our Libertine Reign, - We'll riot, drink on, and be free. - +Come fill up the Glass,Round, round let it pass,'Till our Reason be lost in our Wine:Leave Conscience's RulesTo Women and Fools,This only can make us divine.Then a Mohock, a Mohock I'll be,No Laws shall restrainOur Libertine Reign,We'll riot, drink on, and be free.

-

For some kinds of analysis, it may be useful to identify different +

For some kinds of analysis, it may be useful to identify different kinds of line group within the same piece of verse. Such line groups may self-nest, in much the same way as the un-numbered div element described in chapter . For example: - - - Thus speaks the Muse, and bends her brow severe:— - “Did I, Lætitia, lend my choicest lays, - And crown thy youthful head with freshest bays, - That all the' expectance of thy full-grown year - Should lie inert and fruitless? O revere - Those sacred gifts whose meed is deathless praise, - Whose potent charms the' enraptured soul can raise - Far from the vapours of this earthly sphere! - - - Seize, seize the lyre! resume the lofty strain! - 'T is time, 't is time! hark how the nations round - With jocund notes of liberty resound,— - And thy own Corsica has burst her chain! - O let the song to Britain's shores rebound, - Where Freedom's once-loved voice is heard, - alas! in vain.” - - +Thus speaks the Muse, and bends her brow severe:—“Did I, Lætitia, lend my choicest lays,And crown thy youthful head with freshest bays,That all the' expectance of thy full-grown yearShould lie inert and fruitless? O revereThose sacred gifts whose meed is deathless praise,Whose potent charms the' enraptured soul can raiseFar from the vapours of this earthly sphere!Seize, seize the lyre! resume the lofty strain!'T is time, 't is time! hark how the nations roundWith jocund notes of liberty resound,—And thy own Corsica has burst her chain!O let the song to Britain's shores rebound,Where Freedom's once-loved voice is heard, + alas! in vain.”

-

It is often the case that verse line boundaries conflict with the +

It is often the case that verse line boundaries conflict with the boundaries of other structural elements. In the following example, the single verse line A Workeman in't... welcome is interrupted by a stage direction: -Thou fumblest Eros, and my Queenes a Squire -More tight at this, then thou: Dispatch. O Loue, -That thou couldst see my Warres to day, and knew'st -The Royall Occupation, thou should'st see -A Workeman in't. -Enter an Armed Soldier. -Good morrow to thee, welcome. +Thou fumblest Eros, and my Queenes a SquireMore tight at this, then thou: Dispatch. O Loue,That thou couldst see my Warres to day, and knew'stThe Royall Occupation, thou should'st seeA Workeman in't.Enter an Armed Soldier.Good morrow to thee, welcome. In this encoding, the part attribute is used, as with div, to indicate that the last two l elements should be regarded as the initial and final parts of a single line, rather than as two lines.

- -

The same technique may be used where verse lines are collected +

The same technique may be used where verse lines are collected together into units such as verse paragraphs: - - -Unprofitably travelling toward the grave, -Like a false steward who hath much received -And renders nothing back. - -Was it for this -That one, the fairest of all rivers, loved -To blend his murmurs with my nurse's song, - - +Unprofitably travelling toward the grave,Like a false steward who hath much receivedAnd renders nothing back.Was it for thisThat one, the fairest of all rivers, lovedTo blend his murmurs with my nurse's song,

-

The part attribute may also be attached to an lg +

The part attribute may also be attached to an lg element to indicate that it is incomplete, for example because it forms part of a group that is divided between two speakers, as in the following example: - - First Voice - - But why drives on that ship so fast - Withouten wave or wind? - - - - Second Voice - - The air is cut away before, - And closes from behind. - - +First VoiceBut why drives on that ship so fastWithouten wave or wind?Second VoiceThe air is cut away before,And closes from behind.

-

For alternative methods of aligning groups of lines which do not form +

For alternative methods of aligning groups of lines which do not form simple hierarchic groups, or which are discontinuous, see the more detailed discussion in chapter . For discussion of other elements and attributes specific to the encoding of verse, see chapter .

- - - - - -
-
Core Tags for Drama

Like other written texts, dramatic and other performance + + + + +

+
+ Core Tags for Drama +

Like other written texts, dramatic and other performance texts such as cinema or TV scripts are often hierarchically organized, for example into acts and scenes. These structural subdivisions should be encoded using the general purpose div or div1 (etc.) elements described below in chapters and . Within these divisions, the body of a performance text typically consists of speeches, often prefixed by a phrase indicating who is speaking, and occasionally interspersed with stage directions -of various kinds.

In the following simple example, each speech consists of a single +of various kinds.

+

In the following simple example, each speech consists of a single paragraph: - - Scene 2. - Peachum, Filch. - - FILCH. -

Sir, Black Moll hath sent word her Trial comes on in +Scene 2.Peachum, Filch.FILCH.

Sir, Black Moll hath sent word her Trial comes on in the Afternoon, and she hopes you will order Matters - so as to bring her off.

- - - PEACHUM. -

Why, she may plead her Belly at worst; to my + so as to bring her off.

PEACHUM.

Why, she may plead her Belly at worst; to my Knowledge she hath taken care of that Security. But, as the Wench is very active and industrious, - you may satisfy her that I'll soften the Evidence.

- - - FILCH. -

Tom Gagg, sir, is found guilty.

- - + you may satisfy her that I'll soften the Evidence.

FILCH.

Tom Gagg, sir, is found guilty.

-

In the following example, each speech consists of a sequence of verse +

In the following example, each speech consists of a sequence of verse lines, some of them being marked as metrically incomplete: - - ACT I - - SCENE I - Enter Barnardo and Francisco, - two Sentinels, at several doors - Barn - Who's there? - - Fran - Nay, answer me. Stand and unfold yourself. - - Barn - Long live the King! - - Fran - Barnardo? - - Barn - He. - - Fran - You come most carefully upon your hour. - - Barn - 'Tis now struck twelve. Get thee to bed, Francisco. - - Fran - For this relief much thanks. 'Tis bitter cold, - And I am sick at heart. - - - +ACT ISCENE IEnter Barnardo and Francisco, + two Sentinels, at several doorsBarnWho's there?FranNay, answer me. Stand and unfold yourself.BarnLong live the King!FranBarnardo?BarnHe.FranYou come most carefully upon your hour.Barn'Tis now struck twelve. Get thee to bed, Francisco.FranFor this relief much thanks. 'Tis bitter cold,And I am sick at heart.

-

In some cases, as here in the First Quarto of Hamlet, +

In some cases, as here in the First Quarto of Hamlet, the printed speaker attributions need to be supplemented by use of the who attribute; again, the lines are marked as complete or incomplete: Enter two Centinels. Now call'd Bernardo & -Francesco. - 1. - Stand: who is that? - - 2. - Tis I. - - 1. - O you come most carefully vpon your watch, - - 2. - And if you meete Marcellus and Horatio, - The partners of my watch, bid them make haste. - - 1. - I will: See who goes there. - -Enter Horatio and Marcellus. - +Francesco.1.Stand: who is that?2.Tis I.1.O you come most carefully vpon your watch,2.And if you meete Marcellus and Horatio,The partners of my watch, bid them make haste.1.I will: See who goes there.Enter Horatio and Marcellus.

-

By contrast with the preceding examples, the following encodes an +

By contrast with the preceding examples, the following encodes an early printed edition without making any assumption about which parts are prose or verse: - - - Actus primus, Scena prima. - A tempestuous +Actus primus, Scena prima.A tempestuous noise of Thunder and Lightning heard: Enter - a Ship-master, and a Boteswaine. - - Master.

Bote-swaine.

- - - Botes.

Heere Master: What cheere?

- - - Mast. -

Good: Speake to th' Mariners: fall + a Ship-master, and a Boteswaine.Master.

Bote-swaine.

Botes.

Heere Master: What cheere?

Mast.

Good: Speake to th' Mariners: fall too't, yarely, or we run our selues a ground, bestirre, bestirre. Exit. -

- - Enter Mariners. - - Botes. -

Heigh my hearts, cheerely, cheerely my harts: yare, +

Enter Mariners.Botes.

Heigh my hearts, cheerely, cheerely my harts: yare, yare: Take in the toppe-sale: Tend to th' Masters whistle: - Blow till thou burst thy winde, if roome e-nough.

- - - + Blow till thou burst thy winde, if roome e-nough.

-

The sp and stage elements should also be used to +

The sp and stage elements should also be used to mark parts of a text otherwise in prose which are presented as if they were dialogue in a play. The following example is taken from a 19th century novel in which passages of narrative and passages of dialogue are mixed within the same chapter: -The reverend Doctor Opimian -

I do not think I have named a single unpresentable fish.

- -Mr Gryll -

Bream, Doctor: there is not much to be said for bream.

- -The Reverend Doctor Opimian -

On the contrary, sir, I think there is much to be said for him. - In the first place ...

-

Fish, Miss Gryll — I could discourse to you on fish by the - hour: but for the present I will forbear ...

- +The reverend Doctor Opimian

I do not think I have named a single unpresentable fish.

Mr Gryll

Bream, Doctor: there is not much to be said for bream.

The Reverend Doctor Opimian

On the contrary, sir, I think there is much to be said for him. + In the first place ...

Fish, Miss Gryll — I could discourse to you on fish by the + hour: but for the present I will forbear ...

 - - Lord Curryfin - (after a pause). -

Mass as the second grave-digger says - in Hamlet, I cannot tell.

- -

A chorus of laughter dissolved the sitting.

 +Lord Curryfin(after a pause).

Mass as the second grave-digger says + in Hamlet, I cannot tell.

A chorus of laughter dissolved the sitting.

- - - - - - -
-
- Overview of the Core Module -

All the elements described in this chapter are provided by the + + + + + +

+
+
+ Overview of the Core Module +

All the elements described in this chapter are provided by the core module. - - Common Core - Elements common to all TEI documents - Éléments disponibles pour tous les documents TEI - 所有TEI文件所通用的元素 - Elementi comuni a tutti i documenti TEI - Elementos comuns a todos os documentos TEI - コアモジュール - + Common CoreElements common to all TEI documentsÉléments disponibles pour tous les documents TEI所有TEI文件所通用的元素Elementi comuni a tutti i documenti TEIElementos comuns a todos os documentos TEIコアモジュール The selection and combination of modules to form a TEI schema is described in .

- - - - - - - - - - - - - - - - - - -
+ + + + + + + + + + + + + + + + + + +
diff --git a/P5/Source/Guidelines/en/COL-Colophon.xml b/P5/Source/Guidelines/en/COL-Colophon.xml index 359a9c35b6..c2a68263f4 100644 --- a/P5/Source/Guidelines/en/COL-Colophon.xml +++ b/P5/Source/Guidelines/en/COL-Colophon.xml @@ -1,15 +1,6 @@ - - - + -
Colophon

The text of this manual was prepared electronically on a variety of @@ -17,13 +8,10 @@ $Id$ groups and working committees of the TEI; all have been revised by the editors to achieve greater uniformity of style and greater consistency in the tag set.

-

The web release of the Guidelines was created using a library of XSLT stylesheets to convert to XHTML; the PDF version for printing was produced by conversion to LaTeX markup, processed using XeLaTeX. The XSLT libraries were written by Sebastian Rahtz.

- -

Almost every available SGML and XML editor or processing program has been used at one time or another by the TEI; but without the open source implementations of XML parsers, editors and @@ -32,12 +20,10 @@ $Id$ individuals. We would also like to thank the staff at SyncRO Soft SRL, creators of the oXygen editor, for their support for the TEI during the creation on P5.

-

Many volunteers contributed to the preparation of this release of the Guidelines; we particularly note the work of Sabine Krott, Eva Radermacher and Arianna Ciula for their work in structuring the bibliographies.

-

The production and release process for TEI P5 was originally developed by Sebastian Rahtz for the TEI Technical Council.

diff --git a/P5/Source/Guidelines/en/DEPRECATIONS.xml b/P5/Source/Guidelines/en/DEPRECATIONS.xml index 9e4f84cd10..3a84b28bfa 100644 --- a/P5/Source/Guidelines/en/DEPRECATIONS.xml +++ b/P5/Source/Guidelines/en/DEPRECATIONS.xml @@ -1,11 +1,5 @@ - +
Deprecations @@ -13,8 +7,7 @@ $Id$ Items Scheduled to be Removed

This appendix provides a partial list of items (elements, attributes, attribute values, datatypes etc.) which are deprecated - in this revision of the TEI Guidelines (revision of TEI P5 ).

+ in this revision of the TEI Guidelines (revision of TEI P5 ).

diff --git a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml index 22fb2907c6..55fe11fbca 100644 --- a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml +++ b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml @@ -1,16 +1,9 @@ - +
Dictionaries - -

This chapter defines a module for encoding lexical resources of all +

This chapter defines a module for encoding lexical resources of all kinds, in particular human-oriented monolingual and multilingual dictionaries, glossaries, and similar documents. The elements described here may also be useful in the @@ -21,8 +14,7 @@ within other documents. Dictionaries are most familiar in their printed form; however, increasing numbers of dictionaries exist also in electronic forms which are independent of any particular printed form, but from which various displays can be produced.

- -

Both typographically and structurally, print dictionaries are +

Both typographically and structurally, print dictionaries are extremely complex. Such lexical resources are moreover of interest to many communities with different and sometimes conflicting goals. As a result, many general problems of text encoding are particularly @@ -31,8 +23,7 @@ encoding scheme may be required in the future.We refer the reader to previous and current discussions of a common format for encoding lexical resources. For example, ; ; ; ; ; ; ; and ; . Two problems are particularly prominent.

- -

First, because the structure of dictionary entries varies widely +

First, because the structure of dictionary entries varies widely both among and within dictionaries, the simplest way for an encoding scheme to accommodate the entire range of structures actually encountered is to allow virtually any element to appear virtually @@ -48,8 +39,7 @@ same elements, but allows them to combine much more freely. It is however recommended that entry be used in preference to entryFree wherever possible. These elements and their contents are described in sections , , and .

- -

Second, since so much of the information in printed dictionaries is +

Second, since so much of the information in printed dictionaries is implicit or highly compressed, their encoding requires clear thought about whether it is to capture the precise typographic form of the source text or the underlying structure of the information it @@ -67,16 +57,14 @@ between related elements of the two encodings. Problems of recording these two different views of dictionary data are discussed in section , together with mechanisms for retaining both views when this is desired.

- -

To deal with this complexity, and in particular to account for the +

To deal with this complexity, and in particular to account for the wide variety of linguistic contexts within which a dictionary may be designed, it can be necessary to customize or change the schema by providing more restriction or possibly alternate content models for the elements defined in this chapter. Section illustrates this with the provision of a closed set of values for grammatical descriptors.

- -

This chapter contains a large number of examples taken from +

This chapter contains a large number of examples taken from existing print dictionaries; in each case, the original source is identified. In presenting such examples, we have tried to retain the original typographic appearance of the example as well as presenting a @@ -88,71 +76,39 @@ entries is rendered with a full stop, while within the sample transcriptions hyphenation and syllabification points are indicated by a vertical bar |, regardless of their appearance in the source text.

- -
-Dictionary Body and Overall Structure - -

Overall, dictionaries have the same structure of front matter, +

+ Dictionary Body and Overall Structure +

Overall, dictionaries have the same structure of front matter, body, and back matter familiar from other texts. In addition, this module defines entry, entryFree, and superEntry as component-level elements which can occur directly within a text division or the text body.

- -

The following tags can therefore be used to mark the gross structure of a +

The following tags can therefore be used to mark the gross structure of a printed dictionary; the dictionary-specific tags are discussed further -in the following section. - - - - - - - - -

- -

As members of the classes att.entryLike and +in the following section.

+

As members of the classes att.entryLike and att.sortable, entry and entryFree share the following -attributes: - - - +attributes:

- -

The front and back matter of a dictionary may well contain +

The front and back matter of a dictionary may well contain specialized material such as lists of common and proper nouns, grammatical tables, gazetteers, a guide to the use of the dictionary, etc. These should be tagged using elements defined elsewhere in these Guidelines, chiefly in the core module (chapter ) together with the specialized dictionary elements defined in this chapter.

- -

The body element consists of a set of +

The body element consists of a set of entries, optionally grouped into one or several div elements. These text divisions might, for example, correspond to sections for different letters of the alphabet, or to sections for different languages in a bilingual dictionary, as in the following example: - - -

English-French -
cat
 -
dog
 -
horse
 -
-
-French-English -
chat
 -
chien
 -
cheval
 -
- - -

- -

In a +

English-French
cat
dog
horse
French-English
chat
chien
cheval
+

+ +

In a print dictionary, the entries are typically typographically distinct entities, each headed by some morphological form of the lexical item described (the headword), and sorted in alphabetical @@ -163,8 +119,7 @@ distinct successive items, each marked as an entry or to distinguish different types of entries, for example main entries, related entries, run-on entries, or entries for cross-references, etc.

- -

Some dictionaries provide distinct entries for homographs, on the +

Some dictionaries provide distinct entries for homographs, on the basis of etymology, part-of-speech, or both, and typically provide a numeric superscript on the headword identifying the homograph number. In these cases each homograph should be encoded as a separate @@ -178,69 +133,37 @@ be recorded, the global attribute n may be used for this purpose. In some dictionaries, homographs are treated in distinct parts of the same entry; in these cases, they may be separated by use of the hom element, for which see section .

- -

A sort key, given in the sortKey attribute, is often +

A sort key, given in the sortKey attribute, is often required for superentries and entries, especially in cases where the order of entries does not follow the local character-set collating sequence (as, for example, when an entry for 3D appears at the place where three-D would appear).

- - - -

A dictionary with no internal divisions might thus have a structure like +

A dictionary with no internal divisions might thus have a structure like the following; a superEntry is shown grouping two homograph -entries. - - -

- manifestation -
- - -
- émeute -
 - - -
- grève -
- - -
- grève -
- - - - -

- - - - - - - - - - - - - - - - - - - - - -
-
-The Structure of Dictionary Entries - -

A simple dictionary entry may contain information about the form of +entries.

manifestation
émeute
grève
grève
 +

+ + + + + + + + + + + + + + + + + + +
+
+ The Structure of Dictionary Entries +

A simple dictionary entry may contain information about the form of the word treated, its grammatical characterization, its definition, synonyms, or translation equivalents, its etymology, cross-references to other entries, usage information, and examples. These we refer to @@ -257,8 +180,7 @@ within top-level constituents. The top-level constituents of dictionary entries are described in section , and documented more fully, together with their phrase-level sub-constituents, in section .

- -

In addition, however, dictionary entries often have a complex +

In addition, however, dictionary entries often have a complex hierarchical structure. For example, an entry may consist of two or more sub-parts, each corresponding to information for a different part-of-speech homograph of the headword. The entry (or part-of-speech @@ -269,11 +191,9 @@ we call a level; at any level in an entry, any or all of the constituent parts of dictionary entries may appear. The hierarchical levels of dictionary entries are documented in section .

- -
-Hierarchical Levels - -

The outermost structural level of an entry is marked with the +

+ Hierarchical Levels +

The outermost structural level of an entry is marked with the elements entry or entryFree. The hom element marks the subdivision of entries into homographs differing in their part-of-speech. The sense element marks the subdivision @@ -289,180 +209,42 @@ structure is represented by the re (related entry) element, which is discussed in section . Finally, the element dictScrap may be used at any point in the hierarchy to delimit parts of the dictionary entry which are structurally -anomalous, as further discussed in section . - - - - - - -

-

For example, an entry with two senses will have the following structure: - - - - - +anomalous, as further discussed in section .

-

An entry with two homographs, the first with two senses and the second with three - (one of which has two sub-senses), may have a structure like this: - - - - - - - - - - - - - - - In some dictionaries, homographs have separate entries; in +

For example, an entry with two senses will have the following structure: +

+

An entry with two homographs, the first with two senses and the second with three + (one of which has two sub-senses), may have a structure like this: In some dictionaries, homographs have separate entries; in such a case, as noted in section , the two homographs may be - treated as entries, optionally grouped in a superEntry: - - - - - - - - - - - - - - - + treated as entries, optionally grouped in a superEntry:

-

The hierarchic structure of a dictionary entry is enforced by the +

The hierarchic structure of a dictionary entry is enforced by the structures defined in this module. The content model for entry specifies that entries do not nest, that homographs nest within entries, and that senses nest within entries, homographs, or senses, and may be nested to any depth to reflect the embedding of sub-senses. Any of the top-level constituents (def, usg, form, etc.) can appear at any level (i.e., -within entries, homographs, or senses). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +within entries, homographs, or senses).

-
-
-Groups and Constituents - -

As noted above, dictionary entries, and subordinate levels within dictionary entries, +

+
+ Groups and Constituents +

As noted above, dictionary entries, and subordinate levels within dictionary entries, may comprise several constituent parts, each providing a different type of information about the word treated. The top-level constituents of -dictionary entries are: -information about the form of the word treated (orthography, -pronunciation, hyphenation, etc.) -grammatical information (part of speech, grammatical sub-categorization, -etc.) -definitions or translations into another language -etymology -examples -usage information -cross-references to other entries -notes -entries (often of reduced form) for related words, typically called +dictionary entries are:information about the form of the word treated (orthography, +pronunciation, hyphenation, etc.)grammatical information (part of speech, grammatical sub-categorization, +etc.)definitions or translations into another languageetymologyexamplesusage informationcross-references to other entriesnotesentries (often of reduced form) for related words, typically called related entries - - Any of the hierarchical levels (entry, entryFree, + Any of the hierarchical levels (entry, entryFree, hom, and sense) may contain any of these top-level constituents, since information about word form, particular grammatical information, special pronunciation, usage information, etc., may apply to an entire entry, or to only one homograph, or only to a particular sense. The examples below illustrate this point.

-

The following elements are used to encode these top-level constituents: - - - - - - - - - - -

-

In a simple entry with no internal hierarchy, all top-level constituents can appear +

The following elements are used to encode these top-level constituents: +

+

In a simple entry with no internal hierarchy, all top-level constituents can appear as children of entry. - -com.peti.tor -/k@m"petit@(r)/ n person who competes. OALD - - -

-competitor -com|peti|tor -k@m"petit@(r) -
- -n - -person who competes. - - +com.peti.tor/k@m"petit@(r)/ n person who competes. OALD +
competitorcom|peti|tork@m"petit@(r)
nperson who competes. For the elements which appear within the form and gramGrp elements of this and other examples, see below, section , and section .

-

Any top-level constituent can appear at any level when the +

Any top-level constituent can appear at any level when the hierarchical structure of the entry is more complex. The most obvious examples are def and cit, which appear at the sense level when -several senses or translations exist: -disproof - (dɪsˈpru:f) n 1 facts that disprove something 2 the +several senses or translations exist:disproof(dɪsˈpru:f)n1 facts that disprove something 2 the act of disproving. CED - - -

-disproof -dɪsˈpru:f -
- -n - - -facts that disprove something - - -the act of disproving - - - +
disproofdɪsˈpru:f
nfacts that disprove somethingthe act of disproving

-

For ease of processing of such entries containing multiple senses along with those containing +

For ease of processing of such entries containing multiple senses along with those containing only a single sense, it is recommended to use sense in all entries to wrap those elements relating to a particular word sense.

-

In the following example, gramGrp is used to distinguish two homographs: -bray -/breI/ n cry of an ass; sound of a trumpet. ∙ vt [VP2A] +

In the following example, gramGrp is used to distinguish two homographs:bray/breI/ n cry of an ass; sound of a trumpet. ∙ vt [VP2A] make a cry or sound of this kind. OALD - - -

-bray -breI -
- - -n - - -cry of an ass; sound of a trumpet. - - - - -vt -VP2A - - -make a cry or sound of this kind. - - - - +
braybreI
ncry of an ass; sound of a trumpet.vtVP2Amake a cry or sound of this kind.

-

Information of the same kind can appear at different levels within the same entry; -here, grammatical information occurs both at entry and homograph level. -ca.reen -/k@"ri:n/ vt,vi 1 [VP6A] turn (a ship) on one side for +

Information of the same kind can appear at different levels within the same entry; +here, grammatical information occurs both at entry and homograph level.ca.reen/k@"ri:n/ vt,vi 1 [VP6A] turn (a ship) on one side for cleaning, repairing, etc. 2 [VP6A, 2A] (cause to) tilt, lean over to one side. OALD - - -

-careen -ca|reen -k@"ri:n -
- -vt -vi - - - -VP6A - -turn (a ship) on one side for cleaning, repairing, etc. - - - -VP6A -VP2A - -(cause to) tilt, lean over to one side. - - - +
careenca|reenk@"ri:n
vtviVP6Aturn (a ship) on one side for cleaning, repairing, etc.VP6AVP2A(cause to) tilt, lean over to one side.

-

Alone among the constituent groups, form can appear at the +

Alone among the constituent groups, form can appear at the superEntry level as well as at the entry, hom, and -sense levels: -a.ban.don 1/@"band@n/ +sense levels:a.ban.don 1/@"band@n/ v [T1] 1 to leave completely and for ever; desert: The sailors abandoned the burning ship. 2 …abandon 2 n [U] the state when one's feelings and actions are uncontrolled; freedom from control...LDOCE - - -

-abandon -a|ban|don -@"band@n -
- - -v -T1 - - -to leave completely and for ever … - - - - - -n -U - - -the state when one's feelings and actions are uncontrolled; freedom -from control… - - - - -

-
-
-
-Top-level Constituents of Entries -

This section describes the top-level constituents of dictionary entries, together with -the phrase-level constituents peculiar to each. -the form element, which groups orthographic information and +

abandona|ban|don@"band@n
vT1to leave completely and for ever … nUthe state when one's feelings and actions are uncontrolled; freedom +from control… +

+
+
+
+ Top-level Constituents of Entries +

This section describes the top-level constituents of dictionary entries, together with +the phrase-level constituents peculiar to each.the form element, which groups orthographic information and pronunciations, is described in section - -the gramGrp element, which groups elements for the grammatical +the gramGrp element, which groups elements for the grammatical characterization of the headword, is described in section - -the def element, which describes the meaning of the headword, is +the def element, which describes the meaning of the headword, is described in section - -the etym element and its special phrase-level elements are documented +the etym element and its special phrase-level elements are documented in section - -the cit element and its specific applications are described in +the cit element and its specific applications are described in section and section - -the usg, lbl, xr, and note elements are +the usg, lbl, xr, and note elements are described in section - -the re element, which marks nested entries for related words, is +the re element, which marks nested entries for related words, is described in section - - +

-
-Information on Written and Spoken Forms -

Dictionary entries most often begin with information about the form of the word to +

+ Information on Written and Spoken Forms +

Dictionary entries most often begin with information about the form of the word to which the entry applies. Typically, the orthographic form of the word, sometimes marked for syllabification or hyphenation, is the first item in an entry. Other information about the word, including variant or alternate forms, inflected forms, pronunciation, etc., is also often given.

-

The following elements should be used to encode this information: the form +

The following elements should be used to encode this information: the form element groups one or more occurrences of any of them; it can also be recursively nested to reflect more complex sub-grouping of information about word -form(s), as shown in the examples. - - - - - - - - -

-

In addition to those listed above, the following elements, which encode morphological -details of the form, may also occur within form elements: - - - - - - - - - - - - Of these, the gram element is most general, and all of the +form(s), as shown in the examples. +

+

In addition to those listed above, the following elements, which encode morphological +details of the form, may also occur within form elements: Of these, the gram element is most general, and all of the others are synonymous with a gram element with appropriate values (gen, number, case, etc.) for the type attribute.

-

The use of these elements as children of form is deprecated; instead, they +

The use of these elements as children of form is deprecated; instead, they should always be children of a gramGrp within form when describing that particular form of the word.

-

Different dictionaries use different means to mark hyphenation, +

Different dictionaries use different means to mark hyphenation, syllabification, and stress, and they often use some unusual glyphs (e.g., the middle dot for hyphenation). All of these glyphs are in the Unicode character set, as discussed in . When transcribing representations of pronunciation @@ -764,37 +405,20 @@ the International Phonetic Alphabet should be used. It may be convenient (as has been done in the text of this chapter) to use a simple transliteration scheme for this; such a scheme should however be properly documented in the header.

-

In the simplest case, nothing is given but the orthography: -

-doom-laden -
- +

In the simplest case, nothing is given but the orthography:

doom-laden

-

Often, however, pronunciation is given. -soucoupe [sukup] … DNT - -

-soucoupe -sukup -
- +

Often, however, pronunciation is given.soucoupe [sukup] … DNT +

soucoupesukup

-

For a variety of reasons including ease of processing, it may be desired to split +

For a variety of reasons including ease of processing, it may be desired to split into separate elements information which is collapsed into a single element in the source text; orthography and hyphenation may for example be transcribed as separate elements, although given together in the source text. For a discussion of the issues involved, and of methods for retaining both the presentation form and the interpreted form, see section .

-

This example splits orthography and hyphenation, and adds syllabification because it -differs from hyphenation: -ar.ea … W7 - -

-area -ar|ea -ar|e|a -
- +

This example splits orthography and hyphenation, and adds syllabification because it +differs from hyphenation:ar.ea … W7 +

areaar|eaar|e|a

-

Multiple orthographic forms may be given, e.g. to illustrate a word's inflectional -pattern: -brag … vb brags, bragging, bragged … CED - -

-brag -
- -vb - -
-brags -bragging -bragged -
- Or the inflectional pattern may be indicated by reference to a table of -paradigms, as here: -horrifier -[ORifje] (7) vt … [C/R] - -
-horrifier -ORifje - -7 - - -
- - +

Multiple orthographic forms may be given, e.g. to illustrate a word's inflectional +pattern:brag … vb brags, bragging, bragged … CED +

brag
vb
bragsbraggingbragged
Or the inflectional pattern may be indicated by reference to a table of +paradigms, as here:horrifier[ORifje] (7) vt … [C/R] +
horrifierORifje7

- -

Explanatory labels may be attached to alternate forms: -MTBF -abbreviation for mean time between failures CED - - -

-MTBF -
-
-abbreviation for -mean time between failures -
- - +

Explanatory labels may be attached to alternate forms:MTBFabbreviation for mean time between failures CED +

MTBF
abbreviation formean time between failures

-

When multiple orthographic forms are given, a pronunciation may be associated with -all of them, as here: -biryani or biriani - (ˌbɪrɪˈa:nɪ) … CED - -

-biryani -biriani -ˌbɪrɪˈa:nɪ -
- +

When multiple orthographic forms are given, a pronunciation may be associated with +all of them, as here:biryaniorbiriani(ˌbɪrɪˈa:nɪ) … CED +

biryanibirianiˌbɪrɪˈa:nɪ

-

In other cases, different pronunciations are provided for different orthographic +

In other cases, different pronunciations are provided for different orthographic forms; here, the form element is repeated to associate the first orthographic form explicitly with the first pronunciation, and the second -orthographic form with the second pronunciation: -mackle - (ˈmækᵊl) or macule (ˈmækju:l) … CED - -

-mackle -ˈmækᵊl -
-
-macule -ˈmækju:l -
- +orthographic form with the second pronunciation:mackle(ˈmækᵊl)ormacule(ˈmækju:l) … CED +
mackleˈmækᵊl
maculeˈmækju:l

-

Recursive nesting of the form element can preserve relations among elements +

Recursive nesting of the form element can preserve relations among elements that are implicit in the text. For example, in the CED entry for hospitaller, it is clear that U.S. is associated only with hospitaler, but that the pronunciation applies to both forms. The following encoding preserves these -relations: - hospitaller or US hospitaler (ˈhɒspɪtələ) … CED - -

-hospitaller - -US -hospitaler -
-ˈhɒspɪtələ - - - -

- - - - - - - - - - - - - - - - - - - - - - - - - -
-
-Grammatical Information -

The gramGrp element groups grammatical information, such as part of speech, +relations:hospitalleror UShospitaler(ˈhɒspɪtələ) … CED +

hospitallerUShospitaler
ˈhɒspɪtələ + +

+ + + + + + + + + + + + + + + + + + + + + + +
+
+ Grammatical Information +

The gramGrp element groups grammatical information, such as part of speech, subcategorization information (e.g., syntactic patterns for verbs, count/mass distinctions for nouns), etc. It can contain any of the morphological elements defined in section for form and can appear as a child of entry, form, sense, cit, or any other element containing content about which -there is grammatical information. For example, in the entry - pinna (ˈpɪnə) n, - pl -nae (-ni:) or -nas CED, the +there is grammatical information. For example, in the entry pinna(ˈpɪnə)n, + pl-nae (-ni:) or -nas CED, the word defined can be either singular or plural; the pl. specification applies only to the inflected forms provided. Compare this with pants (paents) pl. n., where pl. applies to the headword itself.

-

As noted above in section , the elements for morphological +

As noted above in section , the elements for morphological information are simply shorthand for the general purpose gram element. Consider this entry for the French word médire: - -médire v.t. ind. (de) … PLC This entry can be -tagged using specialized grammatical elements: -

-médire -
- -v -t ind -de - - Or using the gram element: -
-médire -
- -v -t ind -de - - +médire v.t. ind. (de) … PLC This entry can be +tagged using specialized grammatical elements:
médire
vt indde Or using the gram element:
médire
vt indde

-

Like form, gramGrp can be repeated, recursively nested, or used at -the sense level to show relations among elements. -isotope adj. et n. m. … DNT - -

-isotope -
- -adj - - -n -m - - +

Like form, gramGrp can be repeated, recursively nested, or used at +the sense level to show relations among elements.isotope adj. et n. m. … DNT +

isotope
adjnm @@ -1028,104 +551,39 @@ the sense level to show relations among elements. - - wits (wɪts) pl n 1 +wits(wɪts)pl n1 (sometimes singular) the ability to reason and act, esp quickly … CED - - -
-wits -wɪts -
- -pl -n - - - -sometimes singular - -the ability to reason and act, esp quickly … - - - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
-Sense Information -

Dictionaries may describe the meanings of words in a wide variety of different +

witswɪts
plnsometimes singularthe ability to reason and act, esp quickly … +

+ + + + + + +
+
+ Sense Information +

Dictionaries may describe the meanings of words in a wide variety of different ways—by means of synonyms, paraphrases, translations into other languages, formal definitions in various highly stylized forms, etc. No attempt is made here to distinguish all the different forms which sense information may take; all of them may be tagged using the def element described in section .

-

As a special case it is frequently desirable to distinguish +

As a special case it is frequently desirable to distinguish the provision of translation equivalents in other languages from other forms of sense information; the use of cit type="translation" (which groups a translation equivalent with related information such as its grammatical description) for this purpose is described in section .

- -
-Definitions -

Dictionary definitions are those pieces of prose in a dictionary entry that +

+ Definitions +

Dictionary definitions are those pieces of prose in a dictionary entry that describe the meaning of some lexical item. Most often, definitions describe the headword of the entry; in some cases, they describe translated texts, examples, etc.; see cit type="translation", section , and @@ -1135,74 +593,24 @@ etc.; see cit type="translation", section , an group a set of smaller elements. The close analysis of definition text, such as the tagging of hypernyms, typical objects, etc., is not covered by these Guidelines.

-

Definitions may occur directly within an entry; when multiple +

Definitions may occur directly within an entry; when multiple definitions are given, they are typically identified as belonging to -distinct senses, as here: demigod (…) n. 1.a. a being who is part mortal, part +distinct senses, as here:demigod (…) n. 1.a. a being who is part mortal, part god. b. a lesser deity. 2. a godlike person. CP - - -

-demigod - … -
- -n - - - -a being who is part mortal, part god. - - -a lesser deity. - - - -a godlike person. - - - +
demigod …
na being who is part mortal, part god.a lesser deity.a godlike person.

-

In multilingual dictionaries, it is sometimes possible to distinguish translation +

In multilingual dictionaries, it is sometimes possible to distinguish translation equivalents from definitions proper; here a def element is -distinguished from the translation information within which it appears. -rémoulade -[Remulad] nf remoulade, rémoulade (dressing containing mustard and herbs). CR - - -

-rémoulade -Remulad -
- -n -f - - -remoulade -rémoulade -dressing containing mustard and herbs - - - -

- - - - - - - - - - - - - - -
-
-Translation Equivalents -

Multilingual dictionaries contain information about translations of a given word +distinguished from the translation information within which it appears.rémoulade[Remulad] nf remoulade, rémoulade (dressing containing mustard and herbs). CR +

rémouladeRemulad
nfremouladerémouladedressing containing mustard and herbs +

+ + + +
+
+ Translation Equivalents +

Multilingual dictionaries contain information about translations of a given word in some source language for one or more target languages. Minimally, the dictionary provides the corresponding translation in the target language; other material, such as morphological information (gender, case), various kinds of @@ -1210,7 +618,7 @@ usage restrictions, etc., may also be given. If translation equivalents are to be distinguished from other kinds of sense information, they may be encoded using cit type="translation". The global xml:lang attribute should be used to specify the target language.

-

As in monolingual dictionaries, the sense element is used in +

As in monolingual dictionaries, the sense element is used in multilingual dictionaries to group information (forms, grammatical information, usage, translation(s), etc.) about a given sense of a word where necessary. Information about the individual translation equivalents within a sense is @@ -1218,143 +626,44 @@ grouped using cit type="translation". This information may include th translation text (tagged q or quote), morphological information (gen, case, etc.), usage notes (usg), translation labels (lbl), and definitions (def).When -bibliographic data is provided, the quote element should be used. - - - +bibliographic data is provided, the quote element should be used.

-

Note how in the following example, different translation +

Note how in the following example, different translation equivalents are grouped into the same or different senses, following -the punctuation of the source and the usage labels: -dresser … (a) (Theat) habilleur m, -euse f; +the punctuation of the source and the usage labels:dresser … (a) (Theat) habilleur m, -euse f; (Comm: window ~) étalagiste mf. she's a stylish ~ elle s'habille avec chic; V hair. (b) (tool) (for wood) raboteuse f; (for stone) rabotin m. CR - - -

-dresser -
- - -Theat - -habilleur - -m - - - --euse - -f - - - - -Comm -
-window - -
- -étalagiste - -mf - - - - -she's a stylish - - -elle s'habille avec chic - - -V. hair - - - -tool - -for wood - -raboteuse - -f - - - - -for stone - -rabotin - -m - - - - - - - - - - +
dresser
Theathabilleurm-eusefComm
window +
étalagistemfshe's a stylish +elle s'habille avec chicV. hair +toolfor woodraboteuseffor stonerabotinm

-

In the following example, a distinction is made between the +

In the following example, a distinction is made between the translation equivalent (OAS) and a descriptive phrase providing -further information for the user of the dictionary. -O.A.S. ... nf (abrév de Organisation de l'Armée secrète) OAS (illegal military organization supporting French rule of +further information for the user of the dictionary.O.A.S. ... nf (abrév de Organisation de l'Armée secrète) OAS (illegal military organization supporting French rule of Algeria). CR - - - - -OAS -illegal military organization supporting French rule of -Algeria - - - +OASillegal military organization supporting French rule of +Algeria

-

Note that cit type="translation" may also be used in monolingual +

Note that cit type="translation" may also be used in monolingual dictionaries when a translation is given for a foreign word: - -havdalah or havdoloh Hebrew +havdalahorhavdolohHebrew (havdaˈla; Yiddish havˈdɔlə) n Judaism the ceremony marking the end of the sabbath or of a festival, including the blessings over wine, candles and spices [literally: separation] CED - - -

-havdalah -havdoloh - -n - -
- -Judaism -the ceremony marking the end of the sabbath or of a festival, -including the blessings over wine, candles and spices - - -literally -separation - - - -

-
-
-
-Etymological Information -

The element etym marks a block of etymological information. Etymologies may +

havdalahhavdolohn
Judaismthe ceremony marking the end of the sabbath or of a festival, +including the blessings over wine, candles and spicesliterallyseparation +

+
+
+
+ Etymological Information +

The element etym marks a block of etymological information. Etymologies may contain highly structured lists of words in an order indicating their descent from each other, but often also include related words and forms outside the direct line of descent, for comparison. Not infrequently, etymologies include commentary of @@ -1364,137 +673,67 @@ entire intellectual structure of the etymology or record the precise interrelati of all the words mentioned. It is, however, feasible to mark some of the more obvious phrase-level elements frequently found in etymologies, using tags defined in the core module or elsewhere in this chapter. Of particular relevance for the -markup of etymologies are: - - - - - - - - - -

-

As in other prose, individual word forms mentioned in an etymological description are +markup of etymologies are: +

+

As in other prose, individual word forms mentioned in an etymological description are tagged with mentioned elements. Pronunciations, usage labels, and glosses can be tagged using the pron, usg, and gloss elements defined elsewhere in these Guidelines. In addition, the lang element may be used to identify a particular language name where it appears, in addition to using the xml:lang attribute of the mentioned element.

-

Examples: -abismo m. (del gr. a priv. y byssos, fondo). Sima, gran +

Examples:abismo m. (del gr. a priv. y byssos, fondo). Sima, gran profundidad. … - - -

-abismo -
-del gr. +
abismo
del gr. a priv. y byssos, fondo - - - - - -neume -\'n(y)üm\ n [F, fr. ML pneuma, neuma, fr. Gk pneuma + +neume\'n(y)üm\ n [F, fr. ML pneuma, neuma, fr. Gk pneuma breath — more at pneumatic]: any of various symbols used in the notation of Gregorian chant … [WNC] - - - - -F fr. ML +F fr. ML pneuma neuma fr. Gk pneuma breath more at - - -any of various symbols used in the notation of Gregorian chant - - - - - - - -

- - - - - -
-
-Other Information -
-Examples -

Dictionaries typically include examples of word use, usually accompanying +any of various symbols used in the notation of Gregorian chant +

+ + + + +
+
+ Other Information +
+ Examples +

Dictionaries typically include examples of word use, usually accompanying definitions or translations. In some cases, the examples are quotations from another source, and are occasionally followed by a citation to the author.

-

The cit type="example" element contains usage examples and associated +

The cit type="example" element contains usage examples and associated information; the example text itself should be enclosed in a q or quote element. The cit element associates a quotation with -a bibliographic reference to its source. - - - - +a bibliographic reference to its source.

-

Examples frequently abbreviate the headword, and so their transcription will +

Examples frequently abbreviate the headword, and so their transcription will frequently make use of the oRef element described below in section .

-

Examples: -multiplex -/…/ adj tech having many parts: the multiplex eye +

Examples:multiplex/…/ adj tech having many parts: the multiplex eye of the fly. LDOCE - -the multiplex eye of the fly. - Or when one wants a more comprehensive representation of -examples: - -the multiplex eye of the fly. - - As the following example shows, cit can also contain elements -such as pron, def, etc. -some … 4. (S~ and any are used with more): Give me ~ more/s@'mO:(r)/ OALD +the multiplex eye of the fly. Or when one wants a more comprehensive representation of +examples:the multiplex eye of the fly. As the following example shows, cit can also contain elements +such as pron, def, etc.some … 4. (S~ and any are used with more): Give me ~ more/s@'mO:(r)/ OALD - - - - and any are used with + and any are used with more - - -Give me more -s@'mO:(r) - - - In multilingual dictionaries, examples may also be accompanied by -translations: -horrifier … vt to horrify. elle était +Give me mores@'mO:(r) In multilingual dictionaries, examples may also be accompanied by +translations:horrifier … vt to horrify. elle était horrifiée par la dépense she was horrified at the expense. CR - - - - -to horrify - - -elle était horrifiée par la dépense - -she was horrified at the expense. - - - - +to horrifyelle était horrifiée par la dépenseshe was horrified at the expense. @@ -1529,182 +768,42 @@ horrifiée par la dépense she was horrified at the expense. -valeur … n. f. … 2. Vx. Vaillance, bravoure +with a bibl element:valeur … n. f. … 2. Vx. Vaillance, bravoure (spécial., au combat). La valeur n'attend pas le nombre des années (Corneille). … DNT - - -Vx. -Vaillance, bravoure (spécial., au combat) - -La valeur n'attend pas le nombre des années - -Corneille - - - - +Vx.Vaillance, bravoure (spécial., au combat)La valeur n'attend pas le nombre des annéesCorneille

-
-
-Usage Information and Other Labels - -

Most dictionaries provide restrictive labels and phrases indicating +

+
+ Usage Information and Other Labels +

Most dictionaries provide restrictive labels and phrases indicating the usage of given words or particular senses. Other phrases, not necessarily related to usage, may also be attached to forms, translations, cross-references, and examples. The following elements are provided -to mark up such labels: - - - As indicated in the following section (), the +to mark up such labels: As indicated in the following section (), the lbl element may be used for any kind of significative phrase or label within the text. The usg element is a specialization of this to mark usage labels in particular. Usage labels typically -indicate -temporal use (archaic, obsolete, etc.) -register (slang, formal, taboo, ironic, facetious, etc.) -style (literal, figurative, etc.) -connotative effect (e.g. derogatory, offensive) -subject field (Astronomy, Philosophy, etc.) -national or regional use (Australian, U.S., Midland dialect, -etc.) - Many dictionaries provide an explanation and/or a list of such usage +indicate temporal use (archaic, obsolete, etc.)register (slang, formal, taboo, ironic, facetious, etc.)style (literal, figurative, etc.)connotative effect (e.g. derogatory, offensive)subject field (Astronomy, Philosophy, etc.)national or regional use (Australian, U.S., Midland dialect, +etc.) Many dictionaries provide an explanation and/or a list of such usage labels in a preface or appendix. The type of the usage information may be indicated in the type attribute on the usg element. Some -typical values are: - -geographic area - -temporal, historical era (archaic, old, etc.) - -domain - -register - -style (figurative, literal, etc.) - -preference level (chiefly, usually, etc.) - -acceptability - -language for foreign words, spellings pronunciations, etc. - -grammatical usage - In addition to this kind of information, multilingual dictionaries often +typical values are:geographic areatemporal, historical era (archaic, old, etc.)domainregisterstyle (figurative, literal, etc.)preference level (chiefly, usually, etc.)acceptabilitylanguage for foreign words, spellings pronunciations, etc.grammatical usage In addition to this kind of information, multilingual dictionaries often provide semantic cues to help the user determine the right sense of a word in the source language (and hence the correct translation). These include synonyms, concept subdivisions, typical subjects and objects, typical verb complements, etc. These labels may also be marked with the usg element; sample values for the type attribute in these -cases include: - -synonym given to show use - -hypernym given to show usage - -collocation given to show usage - -typical complement - -typical object - -typical subject - -typical verb - -unclassifiable piece of information to guide sense choice - -

-

In this entry, one spelling is marked as geographically restricted: -colour or US color … CED - -

-colour - -US -color -
- - +cases include:synonym given to show usehypernym given to show usagecollocation given to show usagetypical complementtypical objecttypical subjecttypical verbunclassifiable piece of information to guide sense choice +

+

In this entry, one spelling is marked as geographically restricted:colouror UScolor … CED +

colourUScolor

-

In the next example, usage labels are used to indicate domains, register, and -synonyms associated with different senses: -palette -[palEt] nf (a) (Peinture: lit, fig) palette. (b) +

In the next example, usage labels are used to indicate domains, register, and +synonyms associated with different senses:palette[palEt] nf (a) (Peinture: lit, fig) palette. (b) (Boucherie) shoulder. (c) (aube de roue) paddle; (battoir à linge) beetle; (Manutention, Constr) pallet. CR - - -Peinture -lit -fig - -palette - - - -Boucherie - -shoulder - - - - -aube de roue - -paddle - - - -battoir à linge - -beetle - - - -Manutention -Constr - -pallet - - - - +PeinturelitfigpaletteBoucherieshoulderaube de rouepaddlebattoir à lingebeetleManutentionConstrpallet

-

When the usage label is hard to classify, it may be described as a hint: -rempaillage […] nm reseating, rebottoming (with straw). CR +

When the usage label is hard to classify, it may be described as a hint:rempaillage […] nm reseating, rebottoming (with straw). CR - - - -reseating -rebottoming -with straw - - - -

- - - - - -
-
-Cross-References to Other Entries -

Dictionary entries frequently refer to information in other entries, often using +reseatingrebottomingwith straw +

+ + + + +
+
+ Cross-References to Other Entries +

Dictionary entries frequently refer to information in other entries, often using extremely dense notations to convey the headword of the entry to be sought, the particular part of the entry being referred to, and the nature of the information to be sought there (synonyms, antonyms, usage notes, etymology, an illustration, etc.)

-

Cross-references may be tagged in dictionaries using the ref and +

Cross-references may be tagged in dictionaries using the ref and ptr elements defined in the core module (section ). In addition, the xr element may be used to group all the information relating to a cross-reference. - - - - - - -

-

As in other types of text, the actual pointing element (e.g. ref or + +

+

As in other types of text, the actual pointing element (e.g. ref or ptr) is used to tag the cross-reference target proper (in dictionaries, usually the headword, possibly accompanied by a homograph number, a sense number, or other further restriction specifying what portion of the @@ -1774,28 +858,12 @@ The xr element is used to group the target with any accompanying phrases or symbols used to label the cross-reference; the cross-reference label itself may be encoded with lbl or may remain untagged. Both of the following are thus -legitimate: -glee … Compare madrigal (1) +legitimate: glee … Compare madrigal (1) CED - - -

-glee -
-Compare - - - -
- - - -hostellerie Syn. de hôtellerie (sens 1). DNT - - -Syn. de -hôtellerie (sens 1). - In addition to using, or not using, lbl to mark the +
glee
Compare +
 +hostellerie Syn. de hôtellerie (sens 1). DNT +Syn. dehôtellerie (sens 1). In addition to using, or not using, lbl to mark the cross-reference label, the two examples differ in another way. The former assumes that the first sense of madrigal has the identifier madrigal.1, and that the specific form of the reference in the @@ -1806,46 +874,15 @@ attribute of the ref element, however, the second example does assume implicitly either that some software could usefully parse the phrase tagged as a ref and find the location referred to, or else that such processing will not be necessary.

-

The type attribute on the pointing element or on the xr +

The type attribute on the pointing element or on the xr element may be used to indicate what kind of cross-reference is being made, using any convenient typology. Since different dictionaries may label the same kind of cross-reference in different ways, it may be useful to give normalized indications in the type attribute, enabling the encoder to distinguish -irregular forms of cross-reference more reliably: -rose2 … vb the past tense of rise CED - - -

-rose -
- -the past tense of -rise - - - - -
-rise -
- - - from cross-references for synonyms and the like: -antagonist … syn see adverse +irregular forms of cross-reference more reliably:rose2 … vb the past tense of rise CED +
rose
the past tense ofrise
rise
 from cross-references for synonyms and the like:antagonist … syn see adverse W7 - - -syn see -adverse - - - -
-adverse -
- - -Strictly speaking, the reference above is not to the entry for +syn seeadverse
adverse
Strictly speaking, the reference above is not to the entry for adverse, but to the list of synonyms found within that entry. In some cases, the cross-reference is to a particular subset of the -meanings of the entry in question: -globe …V. armillaire (sphère) +meanings of the entry in question:globe …V. armillaire (sphère) PR - -V. armillaire +V. armillaire sphère - - +

- -

Cross-references occasionally occur in definition texts, example +

Cross-references occasionally occur in definition texts, example texts, etc., or may be free-standing within an entry. These may typically be encoded using ref or ptr, without an enclosing xr. For example: - -entacher … Acte entaché de +entacher … Acte entaché de nullité, contenant un vice de forme ou passé par un incapable*. DNT The asterisk signals a reference to the entry for -incapable. -contenant un vice de forme ou passé par un . - +incapable.contenant un vice de forme ou passé par un . In some cases, the form in the definition is inflected, and thus ref must -be used to indicate more exactly the intended target, as here: -justifier …4. IMPRIM Donner a (une ligne) une longeur +be used to indicate more exactly the intended target, as here:justifier …4. IMPRIM Donner a (une ligne) une longeur convenable au moyen de blancs (2, sens 1, 3). DNT - - -imprim -Donner a (une ligne) une longeur convenable au moyen de +imprimDonner a (une ligne) une longeur convenable au moyen de blancs (2, sens 1, 3) - - - - - - - -... - - - - - +...

- - - - - - - - - - - - - - -
-
-Notes within Entries -

Dictionaries may include extensive explanatory notes about usage, grammar, + + + +

+
+ Notes within Entries +

Dictionaries may include extensive explanatory notes about usage, grammar, context, etc. within entries. Very often, such notes appear as a separate section at the end of an entry. The standard note element should be used for -such material. - - -

-

For example: -neither - (ˈnaɪðə, ˈni:ðə) -determiner 1a not one nor the other (of two); +such material. +

+

For example:neither(ˈnaɪðə, ˈni:ðə)determiner1a not one nor the other (of two); not either: neither foot is swollen … usage A verb following a compound subject that uses neither… should be in the singular if both subjects are in the singular: neither Jack nor John has done the work CED - - -

-neither -ˈnaɪðə, -ˈni:ðə -
- - -neither foot is swollen - -A verb following a compound subject +
neitherˈnaɪðə, +ˈni:ðə
neither foot is swollenA verb following a compound subject that uses neither… should be in the singular if both subjects are in the singular: neither Jack nor John has done the work - - - -

-

The formal declaration for note is given in section .

-
-
-
-Related Entries -

The re element encloses a degenerate entry which appears in the body of + +

+

The formal declaration for note is given in section .

+
+
+
+ Related Entries +

The re element encloses a degenerate entry which appears in the body of another entry for some purpose. Many dictionaries include related entries for direct derivatives or inflected forms of the entry word, or for compound words, phrases, collocations, and idioms containing the entry word.

-

Related entries can be complex, and may in fact include any of the information to be +

Related entries can be complex, and may in fact include any of the information to be found in a regular entry. Therefore, the re element is defined to contain the same elements as an entry element.

-

Examples: -bevvy - (ˈbɛvɪ) informal n, pl -vies 1 a drink, esp an +

Examples:bevvy(ˈbɛvɪ)informal n, pl -vies 1 a drink, esp an alcoholic one: we had a few bevvies last night 2 a session of drinking. ▷ vb -vies, -vying, -vied (intr) 3 to drink alcohol [probably from Old French bevee, buvee, drinking] > 'bevvied adj CED - - -

-bevvy -ˈbɛvɪ -
-informal - - -n - - -a drink, esp. an alcoholic one: we had a few bevvies last night. - - - - - -vb - - -to drink alcohol - - -probably from Old French +
bevvyˈbɛvɪ
informalna drink, esp. an alcoholic one: we had a few bevvies last night.vbto drink alcoholprobably from Old French bevee, buvee drinking - - -
-bevvied -
- -adj - - - - -

- - - - - - - - - - - - - - - - - - -
-
-
-Headword and Pronunciation References -

Examples, definitions, etymologies, and occasionally other elements such as +

bevvied
adj +

+ + + +
+
+
+ Headword and Pronunciation References +

Examples, definitions, etymologies, and occasionally other elements such as cross-references, orthographic forms, etc., often contain a shortened or iconic reference to the headword, rather than repeating the headword itself. The references may be to the orthographic form or to the pronunciation, to the form given or to a variant of that -form. The following elements are used to encode such iconic references to a headword: - - - +form. The following elements are used to encode such iconic references to a headword:

-

These elements all inherit the following attributes from the class att.pointing +

These elements all inherit the following attributes from the class att.pointing which may optionally be used to resolve any -ambiguity about the headword form being referred to. - -

-

Headword references come in a variety of formats: - -indicates a reference to the full form of the headword - -gives a prefix to be affixed to the headword - -gives a suffix to be affixed to the headword - -gives the first letter in uppercase, indicating that the headword is -capitalized - -gives a prefix and a suffix to be affixed to the headword - -gives the initial of the word followed by a full stop, to indicate reference -to the full form of the headword - -refers to a capitalized form of the headword - -

-

The oRef element should be used for iconic or shortened references to the +ambiguity about the headword form being referred to.

+

Headword references come in a variety of formats:indicates a reference to the full form of the headwordgives a prefix to be affixed to the headwordgives a suffix to be affixed to the headwordgives the first letter in uppercase, indicating that the headword is +capitalizedgives a prefix and a suffix to be affixed to the headwordgives the initial of the word followed by a full stop, to indicate reference +to the full form of the headwordrefers to a capitalized form of the headword +

+

The oRef element should be used for iconic or shortened references to the orthographic form(s) of the headword itself. It is an empty element and replaces, rather than enclosing, the reference. Note that the reference to a headword is not necessarily -a simple string replacement. In the example -colour1, (US = color) …~ films; ~ TV; Red, blue and yellow +a simple string replacement. In the example colour1, (US = color) …~ films; ~ TV; Red, blue and yellow are ~s. OALD, the tilde stands for either headword form (colour, color).

-

Examples: -colonel … army officer above a lieutenant-~. OALD - -army officer above a lieutenant- - - +

Examples:colonel … army officer above a lieutenant-~. OALD +army officer above a lieutenant- + @@ -2108,11 +1019,8 @@ are ~s. OALD, the tilde stands for either head I don't milk in my tea--> - -academy … The Royal A~ of Arts OALD - -The Royal of Arts - +academy … The Royal A~ of Arts OALD +The Royal of Arts @@ -2169,26 +1077,11 @@ are ~s. OALD, the tilde stands for either head

-

The following example demonstrates the use of the target attribute to refer to -a specific form of the headword: -vag- or vago- comb form … : vagus nerve +

The following example demonstrates the use of the target attribute to refer to +a specific form of the headword:vag- or vago- comb form … : vagus nerve < vagal > < vagotomy > W7 - - -

-vag- -vago- -
-vagus nerve - - -al - -tomy - - - +
vag-vago-
vagus nervealtomy @@ -2270,105 +1163,60 @@ a specific form of the headword:

-

In many cases the reference is not to the orthographic form of the headword, but rather +

In many cases the reference is not to the orthographic form of the headword, but rather to another form of the headword—usually to an inflected form. In these cases, the element oRef should be used; this element may take as its content the string as it -appears in the text. -take … < Mr Burton took us for +appears in the text.take … < Mr Burton took us for French > NPEG - - -Mr Burton took us for French - - - -take … < was quite ~n with him +Mr Burton took us for French +take … < was quite ~n with him > NPEG - - -was quite n with him - - +was quite n with him

-

The next example shows a discontinuous reference, using the +

The next example shows a discontinuous reference, using the attributes next and prev, which are defined in the additional module for linking, segmentation, and alignment (see chapter ) and therefore require that -that module be selected in addition to that for dictionaries. -mix up… < it's easy to mix her up with her sister > NPEG - - -it's easy to mix -her up with her sister - - +that module be selected in addition to that for dictionaries.mix up… < it's easy to mix her up with her sister > NPEG +it's easy to mix +her up with her sister

-

In addition, some dictionaries make reference to the pronunciation of the headword in the +

In addition, some dictionaries make reference to the pronunciation of the headword in the pronunciation of related entries, variants, or examples. The pRef -element should be used for such references. -hors d'oeuvre -/,aw'duhv (Fr O:r dœvr)/ n, pl hors d'oeuvres also hors +element should be used for such references.hors d'oeuvre/,aw'duhv (Fr O:r dœvr)/ n, pl hors d'oeuvres also hors d'oeuvre /'duhv(z) (Fr ~)/ NPEG - -

-hors d'oeuvre -,aw'duhv - -Fr -O:r dœvr -
- -
-pl -hors d'oeuvres -hors d'oeuvre -'duhv(z) - -Fr - - - -
- - +
hors d'oeuvre,aw'duhvFrO:r dœvr
plhors d'oeuvreshors d'oeuvre'duhv(z)Fr

-

Because headword and pronunciation references can occur virtually anywhere in an entry, +

Because headword and pronunciation references can occur virtually anywhere in an entry, the oRef and pRef elements may appear within any other element defined for dictionary entries.

-

Since existing printed dictionaries use different conventions for headword references +

Since existing printed dictionaries use different conventions for headword references (swung dash, first letter abbreviated form, capitalization, or italicization of the word, etc.) the exact method used should be documented in the header.

- - - - - - - - - - -
-
-Typographic and Lexical Information in Dictionary Data -

Among the many possible views of dictionaries, it is useful to distinguish at least the + + + + + + + +

+
+ Typographic and Lexical Information in Dictionary Data +

Among the many possible views of dictionaries, it is useful to distinguish at least the following three, which help to clarify some issues raised with particular urgency by dictionaries, on account of the complexity of both their typography and their -information structure. -(a) the typographic view—the +information structure.(a) the typographic view—the two-dimensional printed page, including information about line and page breaks -and other features of layout -(b) the editorial view—the one-dimensional sequence of tokens +and other features of layout (b) the editorial view—the one-dimensional sequence of tokens which can be seen as the input to the typesetting process; the wording and punctuation of the text and the sequencing of items are visible in this view, -but specifics of the typographic realization are not -(c) the lexical view—this view includes the underlying +but specifics of the typographic realization are not (c) the lexical view—this view includes the underlying information represented in a dictionary, without concern for its exact textual -form - +form

-

For example, a domain indication in a dictionary entry might be broken over a line and +

For example, a domain indication in a dictionary entry might be broken over a line and therefore hyphenated (naut- ical); the typographic view of the dictionary preserves this information. In a purely editorial view, the particular form in which the domain name is given in the @@ -2378,7 +1226,7 @@ plausibly be included in either a strictly typographic or an editorial view. In lexical view, the only information preserved concerning domain would be some standard symbol or string representing the nautical domain (e.g. naut.) regardless of the form in which it appears in the printed dictionary.

-

In practice, publishers begin with the lexical view—i.e., lexical data as it might +

In practice, publishers begin with the lexical view—i.e., lexical data as it might appear in a database—and generate first the editorial view, which reflects editorial choices for a particular dictionary (such as the use of the abbreviation Naut. for nautical, the fonts in which different types of information are to be @@ -2390,7 +1238,7 @@ preserve the typographic or editorial views as a reference text, perhaps as a gu against the loss or misinterpretation of information in the translation process. Some researchers may wish to retain all three views, and study their interrelations, since research questions may well span all three views.

-

In general, an electronic encoding of a text will allow the recovery of at least one view +

In general, an electronic encoding of a text will allow the recovery of at least one view of that text (the one which guided the encoding); if editorial and typographic practices are consistently applied in the production of a printed dictionary, or if exceptions to the rules are consistently recorded in the electronic encoding, then it is in @@ -2401,7 +1249,7 @@ of methods by which this compression is achieved, the complexity of formulating completely explicit rules for editorial and typographic practice, and the relative rarity of complete consistency in the application of such rules, all make the mechanical transformation of information from one view into another something of a vexed question.

-

This section describes some principles which may be useful in capturing one or the other +

This section describes some principles which may be useful in capturing one or the other of these views as consistently and completely as possible, and describes some methods of attempting to capture more than one view in a single encoding. Only the editorial and lexical views are explicitly treated here; for methods of recording the physical or @@ -2412,20 +1260,16 @@ and of the ana and inst attributes to link feature structu transcription of the editorial view of a dictionary, are not discussed here (for feature structures, see chapter . For linkage of textual form and underlying information, see chapter ).

-
-Editorial View -

Common practice in encoding texts of all sorts relies on principles such as the +

+ Editorial View +

Common practice in encoding texts of all sorts relies on principles such as the following, which can be used successfully to capture the editorial view when -encoding a dictionary: -All characters of the source text should be retained, with the possible -exception of rendition text (for which see further below). -Characters appearing in the source text should typically be given as +encoding a dictionary:All characters of the source text should be retained, with the possible +exception of rendition text (for which see further below). Characters appearing in the source text should typically be given as character data content in the document, rather than as the value of an -attribute; again, rendition text may optionally be excepted from this rule. -Apart from the characters or graphics in the source text, nothing else +attribute; again, rendition text may optionally be excepted from this rule. Apart from the characters or graphics in the source text, nothing else should appear as content in the document, although it may be given in -attribute values. -The material in the source text should appear in the encoding in the same +attribute values. The material in the source text should appear in the encoding in the same order. Complications of the character sequence by footnotes, marginal notes, etc., text wrapping around illustrations, etc., may be dealt with by the usual means (for notes, see section ).Complications of sequence caused by marginal or interlinear @@ -2434,10 +1278,9 @@ unconventional page layouts, as in concrete poetry, magazines with imaginative graphic designers, and texts about the nature of typography as a medium, typically do not occur in dictionaries, and so are not discussed here. - - +

-

In a very conservative transcription of the editorial view of a text, rendition +

In a very conservative transcription of the editorial view of a text, rendition characters (e.g. the commas, parentheses, etc., used in dictionary entries to signal boundaries among parts of the entry) and rendition text (for example, conjunctions joining alternate headwords, etc.) are @@ -2451,46 +1294,20 @@ source text; the original sequence retained or recovered from a conservative transcription of the editorial view is, of course, the one established during the transcription by the encoder.

-

Consider, for example, the following entry: - pinna (ˈpɪnə) n, pl -nae (-ni:) or +

Consider, for example, the following entry:pinna (ˈpɪnə) n, pl -nae (-ni:) or -nas 1 any leaflet of a pinnate compound leaf 2 zoology a feather, wing, fin, or similarly shaped part 3 another name for auricle (2). [C18: via New Latin from Latin: wing, feather, fin] CED A conservative encoding of the editorial view of this -entry, which retains all rendition text, might resemble the following: - -

-pinna -ˈpɪnə -
- -n, -
-pl - --nae -(-ni:) -
or -nas - -1 any leaflet of a pinnate compound leaf - -2 zoology +entry, which retains all rendition text, might resemble the following:
pinnaˈpɪnə
n,
pl-nae(-ni:)
or -nas +1 any leaflet of a pinnate compound leaf +2 zoology a feather, wing, fin, or similarly shaped part - -3 -another name for -auricle (2) - - -[C18: via New Latin from Latin: +3 another name forauricle (2) +[C18: via New Latin from Latin: wing, feather, -fin] - - -
- - +fin]

-

A somewhat simplified encoding of the editorial view of this entry might exploit the +

A somewhat simplified encoding of the editorial view of this entry might exploit the fact that rendition text is often systematically recoverable. For example, parentheses consistently appear around pronunciation in this dictionary, and thus are effectively implied by the start- and end-tags for pron.The omission of rendition text is particularly common in systems @@ -2500,153 +1317,59 @@ attempting to maintain it manually in the electronic text. In such an encoding, removing the tags should exactly reproduce the sequence of characters in the source, minus rendition text. The original character sequence can be recovered fully by replacing tags with any rendition text they imply.

-

Encoding in this way, the example given above might resemble the following. The +

Encoding in this way, the example given above might resemble the following. The tagUsage element in the header would be used to record the following -patterns of rendition text: -parentheses appear around pron elements -commas appear before inflected forms -the word or appears before alternate forms -brackets appear around the etymology -full stops appear after pos, inflection information, and sense -numbers -senses are numbered in sequence unless otherwise specified using the -global n attribute - - - -

-pinna -"pIn@ -
- -n - -
-pl - --nae --ni: -
--nas - - -any leaflet of a pinnate compound leaf. - - -Zoology -a feather, wing, fin, or similarly shaped part. - - - -another name for -auricle (sense 2). - - - -C18: via New Latin from Latin: +patterns of rendition text:parentheses appear around pron elementscommas appear before inflected formsthe word or appears before alternate formsbrackets appear around the etymologyfull stops appear after pos, inflection information, and sense +numberssenses are numbered in sequence unless otherwise specified using the +global n attribute +
pinna"pIn@
n
pl-nae-ni:
-nasany leaflet of a pinnate compound leaf.Zoologya feather, wing, fin, or similarly shaped part.another name forauricle (sense 2).C18: via New Latin from Latin: wing, feather, fin - - - +

-

When rendition text is omitted, it is recommended that the means to regenerate it be +

When rendition text is omitted, it is recommended that the means to regenerate it be fully documented, using the tagUsage element of the TEI header.

-

If rendition text is used systematically in a dictionary, with only a few mistakes or +

If rendition text is used systematically in a dictionary, with only a few mistakes or exceptions, the global attribute rend may be used on any tag to flag exceptions to the normal treatment. The values of the rend attribute are not prescribed, but it can be used with values such as no-comma, no-left-paren, etc. Specific values can be documented using the rendition element in the TEI header.

-

In the following (imaginary) example, no left parenthesis precedes the -pronunciation: -biryani or biriani %bIrI"A:nI) any of a +

In the following (imaginary) example, no left parenthesis precedes the +pronunciation:biryani or biriani %bIrI"A:nI) any of a variety of Indian dishes … [from Urdu] This irregularity can be recorded -thus: - -

-biryani -biriani -%bIrI"A:nI -
-any of a variety of Indian dishes … -from Urdu - - - +thus:
biryanibiriani%bIrI"A:nI
any of a variety of Indian dishes … from Urdu +

-
-
-Lexical View -

If the text to be interchanged retains only the lexical view of the text, there may +

+
+ Lexical View +

If the text to be interchanged retains only the lexical view of the text, there may be no concern for the recoverability of the editorial (not to speak of the typographic) view of the text. However, it is strongly recommended that the TEI header be used to document fully the nature of all alterations to the original data, such as normalization of domain names, expansion of inflected forms, etc.

-

In an encoding of the lexical view of a text, there are degrees of departure from the +

In an encoding of the lexical view of a text, there are degrees of departure from the original data: normalizing inconsistent forms like nautical, naut., Naut., etc., to nautical is a relatively slight alteration; expansion of delay -ed -ing to delay, delayed, delaying is a more substantial departure. Still more severe is the rearranging of the order of -information in entries; for example: -reorganizing the order of elements in an entry to show their -relationship, as in clem (klɛm) -or clam vb clems, clemming, clemmed - or clams, clamming, clammed CED where in a strictly lexical view one +information in entries; for example:reorganizing the order of elements in an entry to show their +relationship, as in clem(klɛm)orclamvbclems, clemming, clemmedorclams, clamming, clammedCED where in a strictly lexical view one might wish to group clem and clam with their respective -inflected forms. -splitting an entry into two separate entries, as in -celi.bacy /"selIb@sI/ n [U] state of living +inflected forms. splitting an entry into two separate entries, as in celi.bacy /"selIb@sI/ n [U] state of living unmarried, esp as a religious obligation. celi.bate /"selIb@t/ n [C] unmarried person (esp a priest who has taken a vow not to marry). OALD For some purposes, this entry might usefully be split into an -entry for celibacy and a separate entry for celibate. - -

-

An encoding which captures the lexical view of the example given in the previous -section might look something like the following. In this encoding: -abbreviated forms have been silently expanded -some forms have been moved to allow related forms to be grouped together -the part of speech information has been moved to allow all forms to be -given together -the cross-reference to auricle has been simplified - - - -

-pinna -"pIn@ - -pl - -pinnae -'pIni: -
-pinnas - - - -n - - -any leaflet of a pinnate compound leaf. - - -Zoology -a feather, wing, fin, or similarly shaped part. - - - - - - - -C18: via New Latin from Latin: +entry for celibacy and a separate entry for celibate. +

+

An encoding which captures the lexical view of the example given in the previous +section might look something like the following. In this encoding:abbreviated forms have been silently expandedsome forms have been moved to allow related forms to be grouped togetherthe part of speech information has been moved to allow all forms to be +given togetherthe cross-reference to auricle has been simplified +

pinna"pIn@plpinnae'pIni:
pinnasnany leaflet of a pinnate compound leaf.Zoologya feather, wing, fin, or similarly shaped part.C18: via New Latin from Latin: wing, feather, fin - - - +

-

Whether the given dictionary encoding focusses on the lexical view and thus approaches the status of +

Whether the given dictionary encoding focusses on the lexical view and thus approaches the status of lexical databases, or uses the typographic/editorial view approach and needs to communicate the sometimes informally stated values for the particular descriptive features, the issue of interoperability of the content and of the container objects becomes relevant, in view of the growing @@ -2659,169 +1382,94 @@ In order to signal that this variety of surface markers in fact indicate the sam underlying value, it is possible to align them with an external inventory of standardized values. The TEI provides the att.datcat attribute class for the purpose of aligning grammatical (or indeed any sort of) categories as well as their values with a reference taxonomy of shared data categories.

-

In the example below, a fragment of the entry for isotope cited +

In the example below, a fragment of the entry for isotope cited in section is adorned by references to standardized definitions for part of speech (datcat) and adjective (valueDatcat). Depending on the status and extent of the dictionary, various strategies may be used to reduce the -redundancy of references. - - -

-isotope -
- -adj - - - - +redundancy of references.
isotope
adj In the above example, alignment is performed against the CLARIN Concept Registry.

-
-
-Retaining Both Views -

It is sometimes desirable to retain both the lexical and the editorial view, in which +

+
+ Retaining Both Views +

It is sometimes desirable to retain both the lexical and the editorial view, in which case a potential conflict exists between the two. When there is a conflict between the encodings for the lexical and editorial views, the principles described in the following sections may be applied.

-
-Using Attribute Values to Capture Alternate Views -

If the order of the data is the same in both views, then both views may be +

+ Using Attribute Values to Capture Alternate Views +

If the order of the data is the same in both views, then both views may be captured by encoding one dominant view in the character data content of the document, and encoding the other using attribute values on the appropriate elements. If all tags were to be removed, the remaining characters would be those of the dominant view of the text.

-

The attribute class att.lexicographic (which +

The attribute class att.lexicographic (which includes the attributes norm and org from class att.lexicographic.normalized) is used to provide attributes for use in encoding multiple views of the same dictionary entry. These attributes are available for use on all elements defined in this chapter when the base module for dictionaries is selected.

-

When the editorial view is dominant, the following attributes may be used to -capture the lexical view: - - -

-

When the lexical view is dominant, the following attributes may be used to record -the editorial view: - - - +

When the editorial view is dominant, the following attributes may be used to +capture the lexical view:

-

One attribute is useful in either view: - - +

When the lexical view is dominant, the following attributes may be used to record +the editorial view:

-

For example, if the source text had the domain label naut., it might be -encoded as follows. With the editorial view dominant: -naut. - The lexical view of the same label would transcribe the normalized form +

One attribute is useful in either view: +

+

For example, if the source text had the domain label naut., it might be +encoded as follows. With the editorial view dominant:naut. The lexical view of the same label would transcribe the normalized form as content of the usg element, the typographic form as an attribute -value: -nautical - +value:nautical

-

If the source text gives inflectional information for the verb +

If the source text gives inflectional information for the verb delay as delay, -ed, -ing, it might usefully be expanded to delayed, delayed, delaying. An encoding of the editorial view -might take this form: -

-delay - --ed - - -
--ing - - - - Note the use of the tns tag with null content, to enable the +might take this form:
delay-ed
-ing
 Note the use of the tns tag with null content, to enable the representation of implicit information even though it has no print realization.

-

The lexical view might be encoded thus: -

-delay - -delayed -pst -pstp -
-
-delaying -prsp -
- - +

The lexical view might be encoded thus:

delaydelayedpstpstp
delayingprsp

- - - -

A particular problem may be posed by the common practice of presenting two + +

A particular problem may be posed by the common practice of presenting two alternate forms of a word in a single string, by marking some parts of the word as optional in some forms. The following entry is for a word which can be -spelled either thyrostimuline or thyréostimuline: -thyr(é)ostimuline [tiR(e)ostimylin] … With the -editorial view dominant, this entry might begin thus: -

-thyr(é)ostimuline -tiR(e)ostimylin -
- +spelled either thyrostimuline or thyréostimuline:thyr(é)ostimuline [tiR(e)ostimylin] … With the +editorial view dominant, this entry might begin thus:
thyr(é)ostimulinetiR(e)ostimylin
 With the lexical view dominant, however, two orth and two pron elements would be encoded, in order to disentangle the two forms; the orig attribute would be used to record the typographic -presentation of the information in the source. -
-thyrostimuline -tiRostimylin -
-
-thyréostimuline -tiReostimylin -
- +presentation of the information in the source.
thyrostimulinetiRostimylin
thyréostimulinetiReostimylin

- -

This example might also be encoded using the opt attribute combined -with the attributes next and prev defined in chapter . -

-thyr -é -ostimuline -tiR -e -ostimylin -
- +

This example might also be encoded using the opt attribute combined +with the attributes next and prev defined in chapter .

thyréostimulinetiReostimylin

-

Note that this transcription preserves both the lexical and +

Note that this transcription preserves both the lexical and editorial views in a single encoding. However, it has the disadvantage that the strings corresponding to entire words do not appear in the encoding uninterrupted, and therefore complex processing is required to retrieve them from the encoded text. The use of the opt attribute is recommended, however, when long spans of text are involved, or when the optional part contains embedded tags.

- -

For example, the following gives two definitions in one text: +

For example, the following gives two definitions in one text: picture drawn with coloured chalk made into crayons, and coloured chalk made into crayons: - pas.tel /"pastl US: pa"stel/ n -1 (picture drawn with) coloured chalk made into crayons. 2… OALD

A simple encoding solution +pas.tel /"pastl US: pa"stel/ n +1 (picture drawn with) coloured chalk made into crayons. 2… OALD

+

A simple encoding solution would be to leave the definition text unanalysed, but this might be felt inadequate since it does not show that there are two -definitions. A possible alternative encoding would be: coloured -chalk made into crayons picture drawn with coloured chalk -made into crayons

This transcribes +definitions. A possible alternative encoding would be:coloured +chalk made into crayonspicture drawn with coloured chalk +made into crayons

+

This transcribes some characters of the source text twice, however, which deviates from the usual practice. The following encoding records both the editorial -and lexical views: - picture drawn -with coloured chalk made into -crayons

+ - -
-
-Recording Original Locations of Transposed Elements -

The attributes described in the previous section are useful only when the order +

+
+ Recording Original Locations of Transposed Elements +

The attributes described in the previous section are useful only when the order of material is the same in both the editorial and the lexical view. When the two views impose different orders on the data, the standard linking mechanisms may be used to show the original location of material transposed in an encoding of the lexical view.

-

If the original is only slightly modified, the anchor element may be +

If the original is only slightly modified, the anchor element may be used to mark the original location of the material, and the location attribute may be used on the lexical encoding of that material to indicate its original location(s). Like those in the preceding section, this attribute is -defined for the attribute class att.lexicographic: - - -

-

For example: -pinna - (ˈpɪnə) n, pl - -nae (-ni:) or -nas CED - -

-pinna -ˈpɪnə - - -pl - --nae --ni: - --nas - - - -n - - +defined for the attribute class att.lexicographic: +

+

For example:pinna(ˈpɪnə)n, pl-nae (-ni:) or -nas CED +

pinnaˈpɪnəpl-nae-ni:-nasn @@ -3004,14 +1629,12 @@ defined for the attribute class att.lexicographic: -->

-
-
- -
-
-Unstructured Entries - -

The content model for the entry element provides an entry +

+
+
+
+ Unstructured Entries +

The content model for the entry element provides an entry structure suitable for many average dictionaries, as well as many regular entries in more exotic dictionaries. However, the structure of some dictionaries does not allow the restrictions imposed by the @@ -3023,15 +1646,13 @@ contain phrase level elements, but it can itself appear at any point within a dictionary entry where any of the structural components of a dictionary entry are permitted. As such, it acts as a container for otherwise anomalous parts of an entry.

- -

The entryFree element places no constraints at all upon +

The entryFree element places no constraints at all upon the entry: any element defined in this chapter, as well as all the normal phrase-level and inter-level elements, can appear anywhere within it. With the entryFree element, the encoder is free to use any element anywhere, as well as to use or omit grouping elements such as form, gramGrp, etc.

- -

The entryFree element allows the encoding of entries which +

The entryFree element allows the encoding of entries which violate the structure specified for the entry element. For example, in the following entry from a dictionary already in electronic form, it is necessary to include a pron element @@ -3043,69 +1664,37 @@ ps="n"> one who is partly divine and partly human (in Gk myth, etc) the son of a god and a mortal woman, egHercules "h3:kjUli:z ]]> - - -

-demigod -demi|god -"demIgQd -
- -n - -one who is partly divine and partly human -(in Gk myth, etc) the son of a god and a mortal woman, eg -Hercules -"h3:kjUli:z - - +
demigoddemi|god"demIgQd
none who is partly divine and partly human(in Gk myth, etc) the son of a god and a mortal woman, eg +Hercules"h3:kjUli:z

-

The entryFree element also makes it possible to transcribe a dictionary using +

The entryFree element also makes it possible to transcribe a dictionary using only phrase-level (atomic) elements—that is, using no grouping elements at all. This can be desirable if the encoder wants a completely flat view, with no indication of or commitment to the association of one element with another. The following encoding uses no grouping elements, and keeps -all rendition text: - biryani or biriani - (ˌbɪrɪˈa:nɪ) n any of a variety of Indian dishes … [from +all rendition text:biryaniorbiriani(ˌbɪrɪˈa:nɪ)n any of a variety of Indian dishes … [from Urdu] CED - - -biryani or biriani +biryani or biriani (ˌbɪrɪˈa:nɪ) any of a variety of Indian dishes … [from Urdu] - - +

-

Here is an alternative way of representing the same structure, this time using -dictScrap: - - -biryani or biriani +

Here is an alternative way of representing the same structure, this time using +dictScrap:biryani or biriani (ˌbɪrɪˈa:nɪ) any of a variety of Indian dishes … [from Urdu] - - - +

-
-
- The Dictionary Module -

The module defined in this chapter makes available the following +

+
+ The Dictionary Module +

The module defined in this chapter makes available the following components: - - Dictionaries - Dictionaries - Dictionnaires - 紙本字典 - Dizionari a stampa - Dicionários impressos - 辞書モジュール - + DictionariesDictionariesDictionnaires紙本字典Dizionari a stampaDicionários impressos辞書モジュール The selection and combination of modules to form a TEI schema is described in .

-
+
diff --git a/P5/Source/Guidelines/en/DR-PerformanceTexts.xml b/P5/Source/Guidelines/en/DR-PerformanceTexts.xml index 31bab48b4b..e55b7bc6f4 100644 --- a/P5/Source/Guidelines/en/DR-PerformanceTexts.xml +++ b/P5/Source/Guidelines/en/DR-PerformanceTexts.xml @@ -1,21 +1,13 @@ - - - + - -
Performance Texts -

This module is intended for use when encoding printed dramatic +

+ Performance Texts +

This module is intended for use when encoding printed dramatic texts, screen plays or radio scripts, and written transcriptions of any other form of performance. -

-

Section discusses elements such as cast lists, +

+

Section discusses elements such as cast lists, which can appear only in the front or back matter of printed dramatic texts. Section discusses the structural components of performance texts: these include major structural @@ -30,32 +22,29 @@ Finally, section discusses a small number of additional elements characteristic of screen plays and radio or television scripts, as well as some elements for representing technical stage directions such as lighting or blocking.

- -

The default structure for dramatic texts is similar to that +

The default structure for dramatic texts is similar to that defined by chapter , as further discussed in section .

- -

Two element classes are used by this module. +

Two element classes are used by this module. The model.frontPart.drama class supplies specialized elements which can appear only in the front or back matter of performance texts. The model.stageLike class supplies a set of elements for stage directions and similar items such as camera movements, which can occur between or within speeches.

- - - - - -
Front and Back Matter + + + +
+ Front and Back Matter -

In dramatic texts, as in all TEI-conformant documents, the header +

In dramatic texts, as in all TEI-conformant documents, the header element is followed by a text element, which contains optional front and back matter, and either a body or else a group of nested text elements. For more information on these, see chapter .

-

The front and back elements are most likely to be +

The front and back elements are most likely to be of use when encoding preliminary materials in published performance texts. When the module defined by this chapter is included in a schema, the following additional elements not generally @@ -63,8 +52,7 @@ found in other forms of text become available as part of the front or back matter:

- -

Elements for encoding each of these specific kinds of front matter +

Elements for encoding each of these specific kinds of front matter are discussed in the remainder of this section, in the order given above. In addition, the front matter of dramatic texts may include the same elements as that of any other kind of text, notably title @@ -73,23 +61,22 @@ elements discussed in this section and instead use constructions of the type div type="performance" or div1 type="set".

- -

Most other material in the front matter of a performance text will be +

Most other material in the front matter of a performance text will be marked with the default text structure elements described in chapter . For example, the title page, dedication, other commendatory material, preface, etc., in a printed text should be encoded using div or div1 elements, containing headings, paragraphs, and other core tags.

- - - - - - - -
The Set Element -

A special form of note describing the setting of a dramatic text + + + + + + +

+ The Set Element +

A special form of note describing the setting of a dramatic text (that is, the time and place of its action) is sometimes found in the front matter. @@ -98,46 +85,22 @@ in the body of the play, but such descriptions should be marked as stage directions, not set. The set element should be used only where the description forms part of the front matter, as in the following examples: - - - ... - -

The action of the play is set in Chicago's + ...

The action of the play is set in Chicago's Southside, sometime between World War II and the - present.

- - - - Peer Gynt - -
-
-
-
- Note on the Translation -

...

-
-
- Characters - -
-

The action, which opens in the beginning of the nineteenth + present.

 +Peer Gynt
Note on the Translation

...

Characters

The action, which opens in the beginning of the nineteenth century, and ends around the 1860s, takes place partly in Gudbrandsdalen, and on the mountains around it, partly on the coast of Morocco, in the desert of Sahara, in a madhouse at Cairo, at sea, - etc.

 -

- - + etc.

- - - - - -
-
Prologues and Epilogues -

Many plays in the Western tradition include in their front matter a + + + +

+
+ Prologues and Epilogues +

Many plays in the Western tradition include in their front matter a prologue, spoken by an actor, generally not in character. Similar speeches often also occur at the end of the play, as epilogues. The elements prologue and epilogue are provided for the @@ -146,55 +109,18 @@ appropriate. A prologue may be encoded just like a distinct poem, as in the following example: - - - Prologue, spoken by Mr. Hart - Poets like Cudgel'd Bullys, never do - At first, or second blow, submit to you; - But will provoke you still, and ne're have done, - Till you are weary first, with laying on: - We patiently you see, give up to you, - Our Poets, Virgins, nay our Matrons too. - - - The Persons - ... - - The SCENE -

London

- - - +Prologue, spoken by Mr. HartPoets like Cudgel'd Bullys, never doAt first, or second blow, submit to you;But will provoke you still, and ne're have done,Till you are weary first, with laying on:We patiently you see, give up to you,Our Poets, Virgins, nay our Matrons too.The Persons ... The SCENE

London

-

A prologue or epilogue may also be encoded as a speech, using the +

A prologue or epilogue may also be encoded as a speech, using the sp element described in section . This is particularly appropriate where stage directions, etc., are involved, as in the following example: - - Written by Colley Cibber, Esq - and spoken by Mrs. Cibber - - - Since Fate has robb'd me of the hapless Youth, - For whom my heart had hoarded up its truth; - By all the Laws of Love and Honour, now, - I'm free again to chuse, — and one of you - - - Suppose I search the sober Gallery; — No, - There's none but Prentices — & Cuckolds all a row: - And these, I doubt, are those that make 'em so. - - Pointing to the Boxes. - - 'Tis very well, enjoy the jest: - - - +Written by Colley Cibber, Esq + and spoken by Mrs. CibberSince Fate has robb'd me of the hapless Youth,For whom my heart had hoarded up its truth;By all the Laws of Love and Honour, now,I'm free again to chuse, — and one of youSuppose I search the sober Gallery; — No,There's none but Prentices — & Cuckolds all a row:And these, I doubt, are those that make 'em so.Pointing to the Boxes.'Tis very well, enjoy the jest:

-

In cases where the prologue or epilogue is clearly a significant part +

In cases where the prologue or epilogue is clearly a significant part of the dramatic action, it may be preferable to include it in the body of a text, rather than in the front or back matter. In such cases, the encoder (and theatrical tradition) will determine whether or not to @@ -203,91 +129,25 @@ play. In the First Folio version of Shakespeare's Tempest, for example, Prospero's final speech is clearly marked off as a distinct textual unit by the headings and layout of the page, and might therefore be encoded as back matter: - - - - - I'le deliver all, - And promise you calme Seas, auspicious gales, - Be free and fare thou well: please you, draw neere. - Exeunt omnes. - - - - - - Epilogue, spoken by Prospero. - - Now my Charmes are all ore-throwne, - And what strength I have's mine owne - As you from crimes would pardon'd be, - Let your Indulgence set me free. - Exit - - -

The Scene, an un-inhabited Island.

- - - Names of the Actors. - Alonso, K. of Naples - Sebastian, his Brother. - Prospero, the right Duke of Millaine. - - FINIS - - +I'le deliver all,And promise you calme Seas, auspicious gales,Be free and fare thou well: please you, draw neere.Exeunt omnes.Epilogue, spoken by Prospero.Now my Charmes are all ore-throwne,And what strength I have's mine owneAs you from crimes would pardon'd be,Let your Indulgence set me free.Exit

The Scene, an un-inhabited Island.

Names of the Actors.Alonso, K. of NaplesSebastian, his Brother.Prospero, the right Duke of Millaine.FINIS

-

In many modern editions, the editors have chosen to regard +

In many modern editions, the editors have chosen to regard Prospero's speech as a part of the preceding scene: - - Prospero - I'll deliver all, - And promise you calm seas, auspicious gales, - Be free and fare thou well. Exit Ariel +ProsperoI'll deliver all,And promise you calm seas, auspicious gales,Be free and fare thou well. Exit Ariel Please you, draw near. Exeunt all but Prospero - Epilogue - Now my charms are all o'erthrown, - And what strength I have's mine own - As you from crimes would pardoned be, - Let your indulgence set me free. - -He awaits applause, then exit. + Epilogue Now my charms are all o'erthrown,And what strength I have's mine ownAs you from crimes would pardoned be,Let your indulgence set me free.He awaits applause, then exit.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
Records of Performances -

Performance texts are not only printed in books to be read, they are + + + + +

+
+ Records of Performances +

Performance texts are not only printed in books to be read, they are also performed. It is common practice therefore to include within the front matter of a printed dramatic text some brief account of particular performances, using the following element: @@ -297,90 +157,48 @@ information relating to the actual performance of a play or screenplay, whether it specifies how the play should be performed in general or how it was performed in practice on some occasion.

-

Performance information may include complex structures such as cast +

Performance information may include complex structures such as cast lists, or paragraphs describing the date and location of a performance, details about the setting portrayed in the performance and so forth. (See the discussion of these specialized structures in section above.) If information for more than one performance is being recorded, then more than one performance element should be used, wherever possible.

-

Names of persons, places, and dates of particular significance within +

Names of persons, places, and dates of particular significance within the performance record may be explicitly marked using the general purpose name, rs type="place" and date elements described in section . No particular elements for such features as stagehouses, directors, etc., are proposed at this time.

-

For example: - - Death of a Salesman -

A New Play by Arthur Miller

-

Staged by Elia Kazan

- - Cast - (in order of appearance) - - Willy Loman - Lee J. Cobb - - - Linda - Mildred Dunnock - - - Biff - Arthur Kennedy - - - Happy - Cameron Mitchell - - - -

The setting and lighting were designed by - Jo Mielziner.

-

The incidental music was composed by Alex North.

-

The costumes were designed by Julia Sze.

-

Presented by Kermit Bloomgarden +

For example: +Death of a Salesman

A New Play by Arthur Miller

Staged by Elia Kazan

Cast(in order of appearance)Willy LomanLee J. CobbLindaMildred DunnockBiffArthur KennedyHappyCameron Mitchell

The setting and lighting were designed by + Jo Mielziner.

The incidental music was composed by Alex North.

The costumes were designed by Julia Sze.

Presented by Kermit Bloomgarden and Walter Fried at the Morosco Theatre in New York on - February 10, 1949.

- + February 10, 1949.

Or: - -

La Machine Infernale a été +

La Machine Infernale a été représentée pour la première fois au théâtre Louis-Jouvet (Comédie des Champs-élysées) le 10 avril 1934, avec les décors et les costumes de - Christian Bérard. ...

- + Christian Bérard. ...

- - - - - - - - - - - - - - - -
-
Cast Lists -

A cast list is a specialized form of list, + + + +

+
+ Cast Lists +

A cast list is a specialized form of list, conventionally found at the start or end of a play, usually listing all the speaking and non-speaking roles in the play, often with additional description (Cataplasma, a maker of Periwigges and Attires) or @@ -389,92 +207,68 @@ Rutter). Cast lists may be encoded with the general purpose list element described in section , but for more detailed work the following specialized elements are provided: -

A castItem element may contain any mixture of elements +

+

A castItem element may contain any mixture of elements taken from the model.castItemPart class, members of which (when this module is included) are: - - + Cast lists often have an internal structure of their own; it is quite usual to find, for example, nobility and commoners, or male and female roles, presented in different groups or sublists. Roles are also often grouped together by their function, for example: - -Sons of Cato: - -Portius -Marcus +Sons of Cato: +PortiusMarcus

-

A cast list relating to a specific performance may be accompanied by +

A cast list relating to a specific performance may be accompanied by notes about the time or place of that performance, indicating (for example) the name of the theatre where the play was first presented, the name of the producer or director, and so forth. When the cast list relates to a specific performance, it should be embedded within a performance element (see section ), as in the following example: - -

The first performance in Great Britain of Waiting for +<egXML xmlns="http://www.tei-c.org/ns/Examples" source="#DRCAST-eg-16"><performance><p>The first performance in Great Britain of <title>Waiting for Godot was given at the Arts Theatre, London, on 3rd August 1955. It was directed by Peter Hall, and the décor was by Peter - Snow. The cast was as follows:

- - Estragon: Peter Woodthorpe - Vladimir: Paul Daneman - ... - - + Snow. The cast was as follows:

Estragon: Peter WoodthorpeVladimir: Paul Daneman ...

-

In this example, the castItem elements have no substructure. +

In this example, the castItem elements have no substructure. If desired, however, their components may be more finely distinguished using the elements role, roleDesc, and actor. For example, the second cast item above might be encoded as follows: - - Vladimir: - Paul Daneman - +Vladimir: + Paul Daneman

-

The ref attribute on actor may be used to associate the name +

The ref attribute on actor may be used to associate the name with information about the real-world person identified, as further discussed in section ND. In the previous example, we might associate the name of Paul Daneman with his entry in a widely used bibliography as follows : - - Paul Daneman -

-

The global xml:id attribute may be used to specify a unique + Paul Daneman

+

The global xml:id attribute may be used to specify a unique identifier for the role element, where it is desired to link speeches within the text explicitly to the role, using the who attribute, as further discussed in section below.

-

The occasionally lengthy descriptions of a role sometimes found in +

The occasionally lengthy descriptions of a role sometimes found in written play scripts may be marked using the roleDesc element, as in the following example: - - Tom Thumb the Great - a little hero with a great soul, something violent in his - temper, which is a little abated by his love for Huncamunca - Young Verhuyk - +Tom Thumb the Greata little hero with a great soul, something violent in his + temper, which is a little abated by his love for HuncamuncaYoung Verhuyk For non-speaking or un-named roles, a castItem may contain a roleDesc without an accompanying role, for example - - Costermonger - +Costermonger

-

When a list of such minor roles is given together, the +

When a list of such minor roles is given together, the type attribute of the castItem should indicate that it contains more than one role, by taking a value such as list. The encoder may or may not elect to encode each separate constituent within such a composite castItem. Thus, either of the following is acceptable: -Constables, Drawer, Turnkey, etc. - - Constables, - Drawer, - Turnkey, +Constables, Drawer, Turnkey, etc.Constables,Drawer,Turnkey, etc.

-

A group of cast items forming a distinct subdivision of a cast list +

A group of cast items forming a distinct subdivision of a cast list may be marked as such by using the special purpose castGroup element. The rend attribute may be used to indicate whether this grouping is indicated in the text by layout alone (i.e. the @@ -482,77 +276,35 @@ use of whitespace), by long braces or by some other means. A castGroup may contain an optional heading (represented as usual by a head element) followed by a series of castItem elements: - - friends of Mathias - - Walter - Mr Frank Hall - - - Hans - Mr F.W. Irish - - +friends of MathiasWalterMr Frank HallHansMr F.W. Irish

-

Alternatively, the encoder may prefer to regard the phrase +

Alternatively, the encoder may prefer to regard the phrase friends of Mathias as a role description, and encode the above example as follows: - - friends of Mathias - - Walter - Mr Frank Hall - - - Hans - Mr F.W. Irish - - + friends of MathiasWalterMr Frank HallHansMr F.W. Irish

-

This version has the advantage that all role descriptions are treated +

This version has the advantage that all role descriptions are treated alike, rather than in some cases being treated as headings. On the other hand there are also cases, such as the following, where the role description does function more like a heading: - - - Mendicants - Aafaa Femi Johnson - Blindman Femi Osofisan - Goyi Wale Ogunyemi - Cripple Tunji Oyelana - - Si Bero - Sister to Dr Bero - Deolo Adedoyin - - Two old women - Iya Agba Nguba Agolia - Iya Mate Bopo George - - Dr Bero - Specialist - Nat Okoro - Priest Gbenga Sonuga - The old man - Bero's father - Dapo Adelugba - +MendicantsAafaaFemi JohnsonBlindmanFemi OsofisanGoyiWale OgunyemiCrippleTunji OyelanaSi BeroSister to Dr BeroDeolo AdedoyinTwo old womenIya AgbaNguba AgoliaIya MateBopo GeorgeDr BeroSpecialistNat OkoroPriestGbenga SonugaThe old manBero's fatherDapo Adelugba

- - - - - - - - -
-
-
The Body of a Performance Text -

The body of a performance text may be divided into structural + + + + + + + + +

+
+
+ The Body of a Performance Text +

The body of a performance text may be divided into structural units, variously called acts, scenes, stasima, entr'actes, etc. All such formal divisions should be encoded using an appropriate text-division element (div, div1, div2, @@ -567,58 +319,31 @@ preceding or following them and cannot therefore be treated as text-divisions. (see ). Speeches will generally consist of a sequence of chunk-level items: paragraphs, verse lines, stanzas, or (in case of uncertainty as to whether -something is verse or prose) ab elements (see ).

-

The boundaries of formal units such as verse lines or paragraphs do +something is verse or prose) ab elements (see ).

+

The boundaries of formal units such as verse lines or paragraphs do not always coincide with speech boundaries. Units such as songs may be discontinuous or shared among several speakers. As described below in section , such fragmentation may be encoded in a relatively simple fashion using the linkage and aggregation mechanisms defined in chapter .

-
Major Structural Divisions -

Large divisions in drama such as acts, scenes, stasima, or entr'actes +

+ Major Structural Divisions +

Large divisions in drama such as acts, scenes, stasima, or entr'actes are indicated by numbered or unnumbered div elements, as described in section . The type and n attributes may be used to define the type of division being marked, and to provide a name or number for it, as in the following example: - - - Night—Faust's Study (i) - - - Outside the City Gate - - +Night—Faust's Study (i)Outside the City Gate

-

Where the largest divisions of a performance text are themselves +

Where the largest divisions of a performance text are themselves subdivided, most obviously in the case of plays traditionally divided into acts and scenes, further nested text-division elements may be used, as in this example: - - - Act One - - Pa Ubu, Ma Ubu - Pa Ubu

Pschitt!

- - - A room in Pa Ubu's house, where a magnificent - collation is set out - - - - Act Two - - Scene One - - - Scene Two - - - +Act OnePa Ubu, Ma UbuPa Ubu

Pschitt!

A room in Pa Ubu's house, where a magnificent + collation is set outAct TwoScene OneScene Two

-

In the example above, the div2 element has been used to +

In the example above, the div2 element has been used to represent the French scene convention, (where the entrance of each new set of characters is marked as a distinct unit in the text) and the div1 element to represent the acts into which @@ -630,26 +355,20 @@ had no acts, but only scenes, then the scenes might be represented by element might be used to represent acts. The type should be used, as above, to make explicit the name associated with a particular category of subdivision.

-

As an alternative to the use of numbered +

As an alternative to the use of numbered divisions, the encoder may represent all subdivisions with the same element, the unnumbered div. The second act in the above example would then be represented as follows: -

- Act Two -
- Scene One -
-
- Scene Two -
-

-

For further discussion of the use of numbered and unnumbered -divisions, see section .

-
Speeches and Speakers -

The following elements are used to identify speeches and speakers in +

Act Two
Scene One
Scene Two

+

For further discussion of the use of numbered and unnumbered +divisions, see section .

+
+
+ Speeches and Speakers +

The following elements are used to identify speeches and speakers in a performance text:

-

As noted above, the structure of many performance texts may be +

As noted above, the structure of many performance texts may be analysed as multiply hierarchic: a scene of a verse play, for example, may be divided into speeches and, at the same time, into verse lines. The end of a line may or may not coincide with the end of a speech, and @@ -665,7 +384,7 @@ performance text in which individual speeches were entirely subordinate to the formal units of prose and verse. For more detailed discussion and examples of various treatments of this fundamental issue, refer to chapter .

-

The who attribute and the speaker element are +

The who attribute and the speaker element are both used to indicate the speaker or speakers of a speech, but in rather different ways. The speaker element is used to encode the word or phrase actually used within the source text to indicate @@ -674,83 +393,48 @@ of as a highly specialized form of stage direction. The who attribute however contains one or more pointer values, each of which indicates one or more other XML elements documenting the character to whom the speech is assigned. Typically, this attribute -might point to a person element in the TEI header , to a role element in the cast list , or even to some external source such as an online +might point to a person element in the TEI header , to a role element in the cast list , or even to some external source such as an online handbook of dramatic roles. The most usual case is that the pointer value supplied (prefixed by a sharp sign) corresponds with the value of an xml:id attribute, used elsewhere in the document to identify a particular element, as in the following examples: - - Menaechmus - Peniculus - - Menaechmus - Responde, adulescens, quaeso, quid nomen tibist? - Peniculus - Etiam derides, quasi nomen non noveris? - Menaechmus - Non edepol ego te, quot sciam, umquam ante hunc diem - Vidi neque novi; ... +MenaechmusPeniculusMenaechmusResponde, adulescens, quaeso, quid nomen tibist?PeniculusEtiam derides, quasi nomen non noveris?MenaechmusNon edepol ego te, quot sciam, umquam ante hunc diemVidi neque novi; ...

-

If present, a speaker element may only appear as the first +

If present, a speaker element may only appear as the first part of an sp element. The distinction between the speaker element and the who attribute makes it possible to encode uniformly characters whose names are not indicated in a uniform fashion throughout the play, or characters who appear in disguise, as in the following examples: - - Henry Higgins - - - The Notetaker -

...

- +Henry HigginsThe Notetaker

...

-

If the speaker attributions are completely regular (and may thus be +

If the speaker attributions are completely regular (and may thus be reconstructed mechanically from the values given for the who attribute), or are of no interest for the encoder of the text (as might be the case with editorially supplied attributions in older texts), then the speaker element need not be used; the former example above then might look like this: - - Menaechmus - Peniculus - -Responde, adulescens, quaeso, quid nomen tibist? -Etiam derides, quasi nomen non noveris? -Non edepol ego te, quot sciam, umquam ante hunc diem - Vidi neque novi; ... +MenaechmusPeniculusResponde, adulescens, quaeso, quid nomen tibist?Etiam derides, quasi nomen non noveris?Non edepol ego te, quot sciam, umquam ante hunc diemVidi neque novi; ...

-

More than one identifier may be listed as value for the who +

More than one identifier may be listed as value for the who attribute if the speech is spoken by more than one person, as in the following example: - - - Nano - Castrone - - Nano and Castrone sing - - Fools, they are the only nation - Worth men's envy or admiration - - +NanoCastroneNano and Castrone singFools, they are the only nationWorth men's envy or admiration

-

In the event there is a speech that is assigned to a +

In the event there is a speech that is assigned to a character that is not listed in the source cast list, a castList may be encoded inside the standOff element to provide an element to which the who of sp may point.

-

The sp and speaker elements are both declared -within the core module (see section ).

- -
Grouped Speeches -

This module makes available the following additional element for -handling groups of speeches:

-

The spGrp element is intended for cases where +

The sp and speaker elements are both declared +within the core module (see section ).

+
+
+ Grouped Speeches +

This module makes available the following additional element for +handling groups of speeches:

+

The spGrp element is intended for cases where the characters in a performance launch into something which might be regarded almost as a kind of separate structural division, typically associated with its own heading or numbering system, but which @@ -758,53 +442,17 @@ associated with its own heading or numbering system, but which as speeches preceding or following it. Such units are often numbered, titled, and visually presented as distinct objects within the text. Here is a typical example from a well-known American musical comedy: - -By Strauss : performed by Georges Guetary, Gene Kelly, and Oscar -Levant -HENRI BAUREL -The waltzes of Mittel Europa -They charm you and warm you within -While each day discloses -What Broadway composes -Is emptiness pounding on tin. - - -JERRY MULLIGAN: ADAM COOK: -Mein Herr! -Mein Herr! -Bitte, bitte! -Denke, danke! -Aufwiedersehen! Aufwiedersehen! - -HENRI BAUREL: -How can I be civil -When hearing this drivel? -It's only for night-clubbing souses. -Oh give me the free 'n easy -Waltz that is Viennes-y -And go tell the band -If they want a hand -The waltz must be Strauss's - -ALL -Ya ya ya -Give me oom pah pah... - - - -

-
-
Stage Directions -

Both between and within the speeches of a written performance text, +By Strauss : performed by Georges Guetary, Gene Kelly, and Oscar +LevantHENRI BAURELThe waltzes of Mittel Europa They charm you and warm you within While each day discloses What Broadway composes Is emptiness pounding on tin.JERRY MULLIGAN: ADAM COOK:Mein Herr! Mein Herr!Bitte, bitte!Denke, danke!Aufwiedersehen! Aufwiedersehen!HENRI BAUREL:How can I be civil When hearing this drivel? It's only for night-clubbing souses. Oh give me the free 'n easy Waltz that is Viennes-y And go tell the bandIf they want a handThe waltz must be Strauss'sALLYa ya ya Give me oom pah pah...

+
+
+ Stage Directions +

Both between and within the speeches of a written performance text, it is normal practice to include a wide variety of descriptive directions to indicate non-verbal action. The following elements are provided to represent these: - - - -

-

A satisfactory typology of stage directions is difficult to define. +

+

A satisfactory typology of stage directions is difficult to define. Certain basic types such as entrance, exit, setting, delivery, are easily identified. But the list is not a closed one, and it is not uncommon to mix types within a single @@ -812,90 +460,43 @@ direction. No closed set of values for the type attribute is therefore proposed at the present time, though some suggested values are indicated in the list below, which also indicates the range of possibilities. -The throne descends. -Music -Enter Husband as being thrown off his horse. -Exit pursued by a bear. -He quickly takes the stone out. -To Lussurioso. -Aside. -Not knowing what to say. -Disguised as Ansaldo. -At a window. -Having had enough, and embarrassed +The throne descends.MusicEnter Husband as being thrown off his horse.Exit pursued by a bear.He quickly takes the stone out.To Lussurioso.Aside.Not knowing what to say.Disguised as Ansaldo.At a window.Having had enough, and embarrassed for the family.

-

The meaning of the values used for the type attribute on +

The meaning of the values used for the type attribute on stage elements may be defined within the tagUsage element of the TEI header (described in section ). For example: This element is used for all stage directions, editorial or authorial. The type attribute on this element takes one or more of the following values: - - - describes the set - - describes movement across stage, position, etc. - - describes movement other than blocking - - describes how the line is said - - describes character's emotional state or through line - + describes the setdescribes movement across stage, position, etc.describes movement other than blockingdescribes how the line is saiddescribes character's emotional state or through line

-

This approach is purely documentary; in a real project it would generally be more effective to define the range of +

This approach is purely documentary; in a real project it would generally be more effective to define the range of permitted values explicitly within the project's schema specification, using the techniques described in chapter . For example, a specification like the following might be used to produce a schema in which the type attribute of the stage element is permitted to take only the values listed above: - - - - - - - - - - - -describes the set -describes movement across stage, position, etc. -describes movement other than blocking -describes how the line is said -describes character's emotional state or through line - - - +describes the setdescribes movement across stage, position, etc.describes movement other than blockingdescribes how the line is saiddescribes character's emotional state or through line

-

The stage element may appear both between and within +

The stage element may appear both between and within sp elements. It may contain a mixture of phrase level elements, possibly combined into paragraphs, as in the following example: - - -

Scene. — A room furnished comfortably and +

Scene. — A room furnished comfortably and tastefully but not extravagantly ... The floor is carpeted and a fire burns in the stove. -It is winter.

-

A bell rings in the hall; shortly afterwards the -door is heard to open. Enter NORA humming a tune ...

- -Nora -

Hide the Christmas Tree carefully, Helen. Be sure the +It is winter.

A bell rings in the hall; shortly afterwards the +door is heard to open. Enter NORA humming a tune ...

Nora

Hide the Christmas Tree carefully, Helen. Be sure the children do not see it till this evening, when it is dressed. To the PORTER taking -out her purse How much?

- - +out her purse How much?

-

The stage element may also be used in non-theatrical +

The stage element may also be used in non-theatrical texts, to mark sound effects or musical effects, etc., as further discussed in section .

-

The move element is intended to help overcome the fact that +

The move element is intended to help overcome the fact that the stage directions of a printed text may often not provide full information about either the intended or the actual movement of actors on stage. It may be used to keep track of entrances and exits in @@ -908,33 +509,25 @@ involved (where attribute). For stage-historical purposes, a perf attribute is also provided; this allows the recording of different move elements as taken in different performances of the same text.

-

The move element should be located at the position in the +

The move element should be located at the position in the text where the move is presumed to take place. This will often coincide with a stage direction, as in the following simple example: - -Bellafront - - +Bellafront Enter Bellafront mad.

-

The move element can however appear independently of a stage +

The move element can however appear independently of a stage direction, as in the following example: - -Lady Macbeth -First Gentleman - - Gent. -

Neither to you, nor any one; having no witness +Lady MacbethFirst GentlemanGent.

Neither to you, nor any one; having no witness to confirm my speech. Lo you! here she comes. This is her very guise; and, -upon my life, fast asleep.

-

- - - - -
-
Speech Contents -

The actual speeches of a dramatic text may be composed of running +upon my life, fast asleep.

+ + + + +
+
+ Speech Contents +

The actual speeches of a dramatic text may be composed of running text, which must be formally organized into paragraphs, in the case of prose (see section ), verse lines or line groups in that of verse (see section ), or seg @@ -942,33 +535,24 @@ elements, in case of doubt as to whether the material should be treated as verse or prose. The following elements, all of which are defined in the core, are particularly useful when marking units of prose or verse within speeches: -

-

Like other milestone elements, the element lb additionally bears the attributes +

+

Like other milestone elements, the element lb additionally bears the attributes ed and edRef, from its membership in the class att.edition: - - - +

-

As a member of the classes att.typed +

As a member of the classes att.typed and att.divLike, the lg element also bears the following attributes: - - - - -

- -

When the verse module is included in a +

+

When the verse module is included in a schema, the elements l and lg also gain additional attributes through their membership of the class att.metrical:

- - -

In many texts, prose and verse may be inextricably mingled; +

In many texts, prose and verse may be inextricably mingled; particularly in earlier printed texts, prose may be printed as verse or verse as prose, or it may be impossible to distinguish the two. In cases of doubt, an encoder may prefer to tag the dubious material @@ -977,40 +561,24 @@ of the source text, or to use the neutral ab element to contain the speech itself. When this question arises, the tagUsage element in the encodingDesc element of the header may be used to record explicitly what policy has been adopted.

-

Even where they can reliably be distinguished, a single speech may frequently +

Even where they can reliably be distinguished, a single speech may frequently contain a mixture of prose (marked as p) and verse (marked as l or—if stanzaic—lg).

- -

The part attribute which both l and lg -elements inherit from the att.fragmentable class provides one simple way of indicating where the boundaries of a +

The part attribute which both l and lg +elements inherit from the att.fragmentable class provides one simple way of indicating where the boundaries of a speech and of a verse line or line group do not coincide. The encoder may simply indicate that a line or line group is metrically incomplete by specifying the value Y or N, as in the following example: FaceYou most -notorious whelp, you insolent slave -Dare you do this? -SubtleYes faith, yes faith. -FaceWhy! Who -Am I, my mongrel? Who am I? -SubtleI'll tell you, - -

-

Alternatively, where the fragments of the line or line group are +notorious whelp, you insolent slaveDare you do this?SubtleYes faith, yes faith.FaceWhy! WhoAm I, my mongrel? Who am I?SubtleI'll tell you,

+

Alternatively, where the fragments of the line or line group are consecutive in the text (though possibly interrupted by stage directions), the values I (initial), M (medial), and F (final) may be used to indicate how metrical lines are constituted: FaceYou most -notorious whelp, you insolent slave -Dare you do this? -SubtleYes faith, yes faith. -FaceWhy! Who -Am I, my mongrel? Who am I? -SubtleI'll tell you, - - +notorious whelp, you insolent slaveDare you do this?SubtleYes faith, yes faith.FaceWhy! WhoAm I, my mongrel? Who am I?SubtleI'll tell you,

-

In dramatic texts, the lg or line group element is most +

In dramatic texts, the lg or line group element is most often of use for the encoding of songs and other stanzaic material. Line groups may be fragmented across speakers in the same way as individual lines, and the same set of attributes may be used to record this fact. The element @@ -1018,53 +586,18 @@ attributes may be used to record this fact. The element common in performances, where performance of a single entity, such as a song, is shared amongst several performers, as in the following example: - -Song — Sir Joseph - - I am the monarch of the sea, - The ruler of the Queen's Navee. - Whose praise Great Britain loudly chants. - - - Cousin Hebe - And we are his sisters and his cousins and his aunts! - - - Rel. - And we are his sisters and his cousins and his aunts! - - - - +Song — Sir JosephI am the monarch of the sea,The ruler of the Queen's Navee.Whose praise Great Britain loudly chants.Cousin HebeAnd we are his sisters and his cousins and his aunts!Rel.And we are his sisters and his cousins and his aunts!

-

This encoding however does not indicate that the three lines of +

This encoding however does not indicate that the three lines of Sir Joseph's song and the two lines following it together constitute a single verse stanza. This can be indicated by using the part attribute, as follows: - -Song — Sir Joseph - - I am the monarch of the sea, - The ruler of the Queen's Navee. - Whose praise Great Britain loudly chants. - - - Cousin Hebe - And we are his sisters and his cousins and his aunts! - - - Rel. - And we are his sisters and his cousins and his aunts! - - - - +Song — Sir JosephI am the monarch of the sea,The ruler of the Queen's Navee.Whose praise Great Britain loudly chants.Cousin HebeAnd we are his sisters and his cousins and his aunts!Rel.And we are his sisters and his cousins and his aunts!

-
-
Embedded Structures -

Although primarily composed of speeches, performance texts often +

+
+ Embedded Structures +

Although primarily composed of speeches, performance texts often contain other structural units such as songs or strophes which are shared among different speakers. More generally, complex nested structures of plays within plays, interpolated masques, or interludes @@ -1072,7 +605,7 @@ are far from uncommon. In more modern material, comparably complex structural devices such as flashback or nested playback are equally frequent. In all kinds of performance material, it may be necessary to indicate several actions which are happening simultaneously.

-

A number of different devices are available within the TEI scheme to +

A number of different devices are available within the TEI scheme to support these complexities in the general case. Texts may be composite or self-nesting (see section ) and multiple hierarchies may be defined (see chapter ). The TEI @@ -1080,222 +613,85 @@ encoding scheme provides a variety of linking mechanisms, which may be used to indicate temporal alignment and aggregation of fragmented structures. In this section we provide a few specific examples of the application of these techniques to performance texts: - -the use of the floatingText element -the use of the part attribute on fragmentary -lg elements -the use of the next and prev attributes on -fragments of embedded structures to join them into a larger whole -the use of the join element to define a +the use of the floatingText elementthe use of the part attribute on fragmentary +lg elementsthe use of the next and prev attributes on +fragments of embedded structures to join them into a larger wholethe use of the join element to define a virtual element composed of the fragments indicated

-

When the whole of a song appears within a single speech, it may +

When the whole of a song appears within a single speech, it may require no special treatment if it is considered to form a part -of the speech: Kelly - (calmly). -

Aha, so you've bad minds along with th' love of gain. +of the speech: Kelly(calmly).

Aha, so you've bad minds along with th' love of gain. You thry to pin on others th' dirty decorations that - may be hangin' on your own coats.

- (He points, one after the other at Conroy, Bull, - and Flagonson. Lilting) - - Who were you with last night? - Who were you with last night? - Will you tell your missus when you go home - Who you were with last night? - -Flagonson - (in anguished indignation). -

This is more than a hurt to us: this hits at the - decency of the whole nation!

- + may be hangin' on your own coats.

(He points, one after the other at Conroy, Bull, + and Flagonson. Lilting)Who were you with last night?Who were you with last night?Will you tell your missus when you go homeWho you were with last night?Flagonson(in anguished indignation).

This is more than a hurt to us: this hits at the + decency of the whole nation!

 If however, the song is to be regarded as forming a distinct item, perhaps with its own front and back matter, it may be better to regard it as a floating text: -Kelly - (calmly). -

Aha, so you've bad minds along with ...

 - (He points, one after the other at Conroy, Bull, - and Flagonson. Lilting): - - - Kelly's Song - - - Who were you with last night? - Who were you with last night? - Will you tell your missus when you go home - Who you were with last night? - - -

-

When an embedded structure extends across more than one sp +Kelly(calmly).

Aha, so you've bad minds along with ...

(He points, one after the other at Conroy, Bull, + and Flagonson. Lilting):Kelly's SongWho were you with last night?Who were you with last night?Will you tell your missus when you go homeWho you were with last night?

+

When an embedded structure extends across more than one sp element, each of its constituent parts must be regarded as a distinct fragment; the problem then facing the encoder is to reconstitute the interrupted whole in some way.

-

As already noted above, the spGrp element may be used to +

As already noted above, the spGrp element may be used to group together consecutive speeches which are grouped together in some way, for example constituting a single song. Alternatively the part attribute, typically used to indicate that an l element contains a partial, not a complete, verse line, may also be used on the lg element, to indicate that the line group is partial rather than complete, thus: -Kelly - (wheeling quietly in his semi-dance, - as he goes out): - - Goodbye to holy souls left here, - Goodbye to man an' fairy; - - -Widda Machree - (wheeling quietly in her semi-dance, - as she goes out): - - Goodbye to all of Leicester Square, - An' the long way to Tipperary. - -

-

When the fragments of a song are separated by other intervening +Kelly(wheeling quietly in his semi-dance, + as he goes out):Goodbye to holy souls left here,Goodbye to man an' fairy;Widda Machree(wheeling quietly in her semi-dance, + as she goes out):Goodbye to all of Leicester Square,An' the long way to Tipperary.

+

When the fragments of a song are separated by other intervening dialogue, or even when not, they may be linked together with the next and prev attributes defined in section . For example, the line groups making up Ophelia's song might be encoded as follows: - - - Elsinore. A room in the Castle. - Enter Ophelia, distracted. - Ophelia -

Where is the beauteous Majesty of Denmark?

- - Queen -

How now, Ophelia?

- - Ophelia - Singing - - How should I your true-love know - From another one? - By his cockle hat and staff - And his sandal shoon. - - - Queen -

Alas, sweet lady, what imports this song?

- - Ophelia -

Say you? Nay, pray you mark.

- Sings - - He is dead and gone, lady, - He is dead and gone; - At his head a grass-green turf, - At his heels a stone. - -

O, ho!

- - -

-

The next and prev attributes are discussed in +Elsinore. A room in the Castle.Enter Ophelia, distracted.Ophelia

Where is the beauteous Majesty of Denmark?

Queen

How now, Ophelia?

OpheliaSingingHow should I your true-love knowFrom another one?By his cockle hat and staffAnd his sandal shoon.Queen

Alas, sweet lady, what imports this song?

Ophelia

Say you? Nay, pray you mark.

SingsHe is dead and gone, lady,He is dead and gone;At his head a grass-green turf,At his heels a stone.

O, ho!

+

The next and prev attributes are discussed in section : they form part of the module for alignment and linking; this module must therefore be included in a schema if they are to be used, as further discussed in section .

-

The fragments of Ophelia's song might also be linked together using +

The fragments of Ophelia's song might also be linked together using the join mechanism described in section . The join element is specifically intended to encode the fact that several discontiguous elements of the text together form one virtual element. Using this mechanism, the example might be encoded as follows: - - - - - Elsinore. A room in the Castle. - Queen -

How now, Ophelia?

- - Ophelia - Singing - - How should I your true-love know - From another one? - By his cockle hat and staff - And his sandal shoon. - - - Queen -

Alas, sweet lady, what imports this song?

- - Ophelia -

Say you? Nay, pray you mark.

- Sings - - He is dead and gone, lady, - He is dead and gone; - At his head a grass-green turf, - At his heels a stone. - -

O, ho!

- - - - - - + Elsinore. A room in the Castle.Queen

How now, Ophelia?

OpheliaSingingHow should I your true-love knowFrom another one?By his cockle hat and staffAnd his sandal shoon.Queen

Alas, sweet lady, what imports this song?

Ophelia

Say you? Nay, pray you mark.

SingsHe is dead and gone, lady,He is dead and gone;At his head a grass-green turf,At his heels a stone.

O, ho!

 The location of the join element is not significant; here it has been placed shortly after the conclusion of the song, in order to have it close to the fragments it unifies.

-

Like the next and prev attributes, the +

Like the next and prev attributes, the join element requires the additional module for linking, which -is selected as shown above.

-
Simultaneous Action -

In printed or written versions of performance texts, a variety of +is selected as shown above.

+
+
+ Simultaneous Action +

In printed or written versions of performance texts, a variety of techniques may be used to indicate the temporal alignment of speeches or actions. Speeches may be printed vertically aligned on the page, or braced together; stage directions (e.g. Speaking at the same time) are also often used. In operatic or musical works in particular, the need to indicate timing and alignment of individual parts of a song may lead to very complex layout.

-

One simple method of indicating the temporal alignment of speeches or +

One simple method of indicating the temporal alignment of speeches or actions is to use the spGrp element discussed in section , with a type attribute to specify the reason for grouping, as in the following example: - Mangan - wildly -

Look here: I'm going to take off all my clothes.

- he begins tearing off his coat. - - - Lady Utterword -

Mr Mangan!

- - Captain Shotover -

Whats that?

- - Hector -

Ha! ha! Do. Do.

- - Ellie -

Please dont.

- -in consternation - - Mrs. Hushabye - catching his arm and stopping him -

Alfred: for shame! Are you mad?

-

- - - - -

In the original, the stage direction in consternation is +

In the original, the stage direction in consternation is printed opposite a brace grouping all four speeches, indicating that all four characters speak at once, and that the stage direction applies to all of them. Rather than attempting to represent the appearance of the @@ -1308,16 +704,19 @@ grouped by the brace in the copy text. Producing a readable version of the text which simulates the original printed effect may however require more complex markup and processing.

-

More powerful and more precise mechanisms for temporal alignment are +

More powerful and more precise mechanisms for temporal alignment are defined in chapter . These would be appropriate for encodings the focus of which is on the actual performance of a text rather than its structure or formal properties. The module described in that chapter includes a large number of other detailed proposals for the encoding of such features as voice quality, prosody, etc., which might be relevant to such a treatment of performance texts. -

-
Other Types of Performance Text -

Most of the elements and structures identified thus far are derived +

+
+
+
+ Other Types of Performance Text +

Most of the elements and structures identified thus far are derived from traditional theatrical texts. Although other performance texts, such as screenplays or radio scripts, have not been discussed specifically, they can be encoded using the elements and structures @@ -1327,7 +726,7 @@ scripts containing very detailed technical information, the tech element discussed in section may also be useful.

-

Like other texts, screenplays and television or radio scripts may +

Like other texts, screenplays and television or radio scripts may be divided into text divisions marked with div or div1, etc. Within units corresponding with the traditional act and scene, further subdivisions or sequences may be @@ -1340,7 +739,7 @@ un-numbered divisions are in use) specifying sequence or shot as the value of the type attribute, as appropriate.

-

It is normal practice in screenplays and radio scripts to distinguish +

It is normal practice in screenplays and radio scripts to distinguish directions concerning camera angles, sound effects, etc., from other forms of stage direction. Such texts also generally include far more detailed specifications of what the audience actually sees: @@ -1352,12 +751,11 @@ attribute. Alternatively, or in addition, the following more specific elements may be used, where clear distinctions can be made:

-

Some examples of the use of these elements follow: -Angle on Olivia. -Ryan's wife, standing nervously alone on the sidelines, +

Some examples of the use of these elements follow: +Angle on Olivia.Ryan's wife, standing nervously alone on the sidelines, biting her lip. She's scared and she shows it.

-

Where particular words or phrases within a direction are emphasized +

Where particular words or phrases within a direction are emphasized (by change of typeface or use of capital letters), an appropriate phrase-level element may be used to indicate the fact, as in the following examples, where certain words in the original are given in @@ -1371,53 +769,31 @@ George gasps. The train whistle screams. Ext. TV control van—Early morning. The T.V. announcer from the Ryan interview -stands near the Control Van, the lake in b.g. - T.V. Announcer -

Several years ago, Jack Ryan was a highly -successful hydroplane racer ...

- +stands near the Control Van, the lake in b.g.T.V. Announcer

Several years ago, Jack Ryan was a highly +successful hydroplane racer ...

-

All of these elements, like other stage directions, can appear both +

All of these elements, like other stage directions, can appear both within and between speeches. - - TV Announcer VO -

Working with Ryan are his two coworkers— +TV Announcer VO

Working with Ryan are his two coworkers— Strut Bowman, the mechanical engineer— Angle on Strut standing in the tow boat, walkie-talkie in hand, watching Ryan carefully. —and Roger Dalton, a rocket systems analyst, and one of the scientists -from the Jet Propulsion Lab ...

- - Benjy -

Now to business.

- - Ford and Zaphod -

To business.

 -Glasses clink. - Benjy -

I beg your pardon?

 - Ford -

I'm sorry, I thought you were proposing a toast.

 +from the Jet Propulsion Lab ...

+Benjy

Now to business.

Ford and Zaphod

To business.

Glasses clink.Benjy

I beg your pardon?

Ford

I'm sorry, I thought you were proposing a toast.

 Zoom in to overlay showing some stock film - of hansom cabs galloping past. -London, 1895. -The residence of Mr Oscar Wilde. -Suitably classy music starts. -Mix through to Wilde's drawing room. A crowd of suitably + of hansom cabs galloping past.London, 1895.The residence of Mr Oscar Wilde.Suitably classy music starts.Mix through to Wilde's drawing room. A crowd of suitably dressed folk are engaged in typically brilliant conversation, - laughing affectedly and drinking champagne. - - Prince of Wales -

My congratulations, Wilde. Your latest play is a great success.

- + laughing affectedly and drinking champagne.Prince of Wales

My congratulations, Wilde. Your latest play is a great success.

-
Technical Information -

Traditional stage scripts may contain additional technical +

+ Technical Information +

Traditional stage scripts may contain additional technical information about such production-related factors as lighting, blocking (that is, detailed notes on actors' movements), or props required at particular points. More technical @@ -1429,33 +805,25 @@ Alternatively, they may be formally distinguished from other stage directions by using the specialized tech element:

-

Like stage directions, tech elements can appear anywhere +

Like stage directions, tech elements can appear anywhere within a speech or between speeches.

- - - - - - - - -
-
- Module for Performance Texts -

The module described in this chapter makes available the + + + + + + + +

+
+
+ Module for Performance Texts +

The module described in this chapter makes available the following components: - - Performance Texts - Performance texts - Théâtre - 劇本 - Testi per performance - Textos de actuação - 舞台芸術モジュール - + Performance TextsPerformance textsThéâtre劇本Testi per performanceTextos de actuação舞台芸術モジュール The selection and combination of modules to form a TEI schema is described in .

-
+
diff --git a/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml b/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml index 025e17fe52..38d0539d70 100644 --- a/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml +++ b/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml @@ -1,56 +1,36 @@ - +
Default Text Structure -

This chapter describes the default high-level structure for TEI documents. A full TEI document combines metadata describing it, represented by a teiHeader element, with the document itself, represented by one or more text elements or other elements taken from the model.resource class. That is, the TEI element is used to group together metadata - about an encoded resource (in teiHeader, specified by the header module, which is fully described in + about an encoded resource (in teiHeader, specified by the header module, which is fully described in chapter ) with an encoded resource. Possible encoded resources are - - a logical transcription of a source document in a + a logical transcription of a source document in a text element; the text element is specified - along with its high-level constituents in the textstructure module and described in the - remainder of the current chapter - a diplomatic transcription of a source document in a - sourceDoc element, which is specified in the transcr module and described in - chapter - an encoded representation of a text-bearing object as images + along with its high-level constituents in the textstructure module and described in the + remainder of the current chaptera diplomatic transcription of a source document in a + sourceDoc element, which is specified in the transcr module and described in + chapter an encoded representation of a text-bearing object as images in a facsimile element, which is also specified in the transcr module and described in - chapter - a collection of contextual information or annotations that + chapter a collection of contextual information or annotations that provides more detail about another encoded resource (whether in the same or a different TEI document) in a standOff - element, which is specified in the linking module and described in section - a feature system declaration which can be used + element, which is specified in the linking module and described in section a feature system declaration which can be used to declare the use of fs elements in the rest of the - document, which is specified in the iso-fs module and described in section -

+ document, which is specified in the iso-fs module and described in section

In a case in which more than one resource related to the same source document share the same metadata, they may be grouped together in a TEI element following a single teiHeader.

-

Because the TEI can be a child of itself, a set or collection of +

Because the TEI can be a child of itself, a set or collection of documents may be represented by an outermost TEI element that contains a teiHeader with metadata that is applicable to the entire set or collection of transcriptions, and then a complete @@ -59,8 +39,7 @@ of these TEI elements contains a teiHeader with metadata that is applicable to the individual document, and one or more text or other elements taken from the model.resource class.

- -

A variant on this basic form, the teiCorpus, is also +

A variant on this basic form, the teiCorpus, is also defined for the representation of language corpora, or other collections of encoded texts. A teiCorpus consists of its own metadata in a teiHeader, followed by one or more complete @@ -70,22 +49,14 @@ permits the encoder to distinguish metadata applicable to the whole collection of encoded texts, which is represented by the outermost teiHeader, from that applicable to each of the individual TEI elements within the corpus. Further information about the -organization and encoding of language corpora is given in chapter .

- -

Alternatively, the corpus may be represented with a TEI +organization and encoding of language corpora is given in chapter .

+

Alternatively, the corpus may be represented with a TEI element (perhaps with a type of corpus) in the same manner as a teiCorpus.

- -

In summary, when the default structure module is included in a +

In summary, when the default structure module is included in a schema, the following elements are available for the representation of the outermost structure of a TEI document: - - - - - - + As noted above, the teiHeader element is formally declared in the header module (see chapter ). A TEI document may also contain elements from the @@ -98,14 +69,9 @@ as major parts of a TEI document. These three elements are provided by the textstructure module described by the present chapter. - - - - - +

- -

TEI texts may be regarded either as unitary, that is, +

TEI texts may be regarded either as unitary, that is, forming an organic whole, or as composite, that is, consisting of several components which are in some important sense independent of each other. The distinction is not always entirely @@ -114,8 +80,7 @@ single item in some circumstances, or as a number of distinct items in others. In such borderline cases, the encoder must choose whether to treat the text as unitary or composite; each may have advantages and disadvantages in a given situation.

- -

Whether unitary or composite, the text is marked with the +

Whether unitary or composite, the text is marked with the text tag and may contain front matter, a text body, and back matter. In unitary texts, the text body is tagged body; in composite texts, where the text body consists of a series of subordinate @@ -124,68 +89,20 @@ any text, unitary or composite, is thus defined by the following elements:

-

The overall structure of a unitary text is: - - - - - - - - - - - - - -

-

The overall structure of a composite text made up of two unitary +

The overall structure of a unitary text is: +

+

The overall structure of a composite text made up of two unitary texts is: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

-

Finally, a floatingText element is provided for the case +

Finally, a floatingText element is provided for the case where one text is embedded within another, but does not contribute to its hierarchical organization, for example because it interrupts it, or simply quoted within it. This is useful in such common literary contexts as the play within a play or the narrative interrupted by other (often -deeply nested) multiple narratives. - - - - - - - +deeply nested) multiple narratives.

-

Each of these elements is further described in the remainder of +

Each of these elements is further described in the remainder of this chapter. Elements front and back are further discussed in sections and . The group and floatingText elements, used for more complex or composite text structures, are @@ -195,9 +112,9 @@ these major structural elements, are discussed in chapter , i of document, or elsewhere in the case of elements specific to particular kinds of document.

-
Divisions of the Body - -

In some texts, the body consists simply of a sequence of low-level +

+ Divisions of the Body +

In some texts, the body consists simply of a sequence of low-level structural items, referred to here as components or component-level elements (see section ). Examples in prose texts include paragraphs or lists; in dramatic texts, speeches and stage directions; in @@ -220,8 +137,7 @@ book into entries; a newspaper into issues and sections, and so forth.

- -

Because of this variety, these Guidelines propose that all such +

Because of this variety, these Guidelines propose that all such textual divisions be regarded as occurrences of the same neutrally named elements, with an attribute type used to categorize elements independently of their hierarchic level. Two alternative styles are @@ -236,81 +152,39 @@ within it being div2, any further sub-sub-division being hierarchic depth. The two styles must not be combined within a single front, body, or back element.

-
Un-numbered Divisions -

The following element is used to identify textual subdivisions in +

+ Un-numbered Divisions +

The following element is used to identify textual subdivisions in the un-numbered style: As a member of the class att.typed, this element has the following additional attributes:

-

Using this style, the body of a text containing two parts, each +

Using this style, the body of a text containing two parts, each composed of two chapters, might be represented as follows: - -

-
- -
-
- -
-
-
-
- -
-
- -
-
- +

- - - - - - -
-
Numbered Divisions -

The following elements are used to identify textual subdivisions + + + + +

+
+ Numbered Divisions +

The following elements are used to identify textual subdivisions in the numbered style: - - - - - - - - - + As members of the class att.typed these elements all bear the following additional attributes:

-

The largest possible subdivision of the body is div1 +

The largest possible subdivision of the body is div1 element and the smallest possible div7. If numbered divisions are in use, a division at any one level (say, div3), may contain only numbered divisions at the next lowest level (in this case, div4).

-

Using this style, the body of a text containing two parts, each +

Using this style, the body of a text containing two parts, each composed of two chapters, might be represented as follows: - - - - - - - - - - - - - - - - - - + @@ -322,29 +196,27 @@ composed of two chapters, might be represented as follows:

- - - - - - - - - - - - - - -
-
Numbered or Un-numbered? -

Within the same front, body, or back + + + + + + + + + + + +

+
+ Numbered or Un-numbered? +

Within the same front, body, or back element, all hierarchic subdivisions must be marked using either nested div elements, or div1, div2 etc. elements nested as appropriate; the two styles must not be mixed.

-

The choice between numbered and un-numbered divisions will depend +

The choice between numbered and un-numbered divisions will depend to some extent on the complexity of the material: un-numbered divisions allow for an arbitrary depth of nesting, while numbered divisions limit the depth of the tree which can be constructed. Where @@ -363,15 +235,14 @@ ensure that the same numbered division always corresponds with the same type of textual feature: a chapter may be at level 1 in one work and level 3 in another.

-

Whichever style is used, the global n and xml:id +

Whichever style is used, the global n and xml:id attributes (section ) may be used to provide reference strings or labels for each division of a text, where appropriate. Such labels should be provided for each section which is regarded as significant for referencing purposes (on reference systems, see further section ).

- -

As indicated above, the type and subtype +

As indicated above, the type and subtype attributes provided by the att.typed class may be used to provide a name or description for the division. Typical values might be book, @@ -385,52 +256,25 @@ a novel, and illustrates the use of the attributes discussed above. It also uses some elements discussed in section and the p element discussed in section . - - Book I. - - Of writing lives in general, and particularly of Pamela, with a word - by the bye of Colley Cibber and others. -

It is a trite but true observation, that examples work more forcibly on - the mind than precepts: ...

- - - - Of Mr. Joseph Andrews, his birth, parentage, education, and great - endowments; with a word or two concerning ancestors. -

Mr. Joseph Andrews, the hero of our ensuing history, was esteemed to +Book I.Of writing lives in general, and particularly of Pamela, with a word + by the bye of Colley Cibber and others.

It is a trite but true observation, that examples work more forcibly on + the mind than precepts: ...

Of Mr. Joseph Andrews, his birth, parentage, education, and great + endowments; with a word or two concerning ancestors.

Mr. Joseph Andrews, the hero of our ensuing history, was esteemed to be the only son of Gaffar and Gammar Andrews, and brother to the - illustrious Pamela, whose virtue is at present so famous ...

- - - - The end of the first Book - - - Book II - - Of divisions in authors -

There are certain mysteries or secrets in all trades, from the highest + illustrious Pamela, whose virtue is at present so famous ...

The end of the first BookBook IIOf divisions in authors

There are certain mysteries or secrets in all trades, from the highest to the lowest, from that of prime-ministering, to this of authoring, which are seldom discovered unless to members of - the same calling ...

-

I will dismiss this chapter with the following observation: that it + the same calling ...

I will dismiss this chapter with the following observation: that it becomes an author generally to divide a book, as it does a butcher to joint his meat, for such assistance is of great help to both the reader and the carver. And now having indulged myself a little I will endeavour to indulge the curiosity of my reader, who is no doubt impatient to know - what he will find in the subsequent chapters of this book.

- - - A surprising instance of Mr. Adams's short memory, with the + what he will find in the subsequent chapters of this book.

A surprising instance of Mr. Adams's short memory, with the unfortunate consequences which it brought on Joseph. - -

Mr. Adams and Joseph were now ready to depart different ways ...

- - +

Mr. Adams and Joseph were now ready to depart different ways ...

- -

As an alternative (or complement) to this use of the +

As an alternative (or complement) to this use of the type attribute to characterize neutrally named division elements, the modification mechanisms discussed in section may be used to define new elements such as chapter, part, etc. To make this simpler, a single @@ -442,66 +286,24 @@ elements: model.divLike (containing consists of a series of diary entries, each of which is potentially divided into entries for the morning and the afternoon. This might be represented in any of the following ways. First, using the un-numbered -style: -

-

[...]

-

[...]

-
-
-

[...]

-

[...]

-
- - +style:

[...]

[...]

[...]

[...]

 Equivalently, using the numbered style: - - -

[...]

 -

[...]

 - - -

[...]

 -

[...]

 - - - +

[...]

[...]

[...]

[...]

 Now, assuming a customization in which a new element -diaryEntry has been added to the model.divLike class: - -

[...]

 -

[...]

 - - -

[...]

 -

[...]

 - - - +diaryEntry has been added to the model.divLike class:

[...]

[...]

[...]

[...]

 And finally, assuming a customization in which three new elements have been added: diaryEntry to the model.div1Like class, and amEntry and -pmEntry both to the model.div2Like class: -

- -

[...]

 -

[...]

 - - -

[...]

 -

[...]

 - - - +pmEntry both to the model.div2Like class:

[...]

[...]

[...]

[...]

-

More information about the customization techniques exemplified +

More information about the customization techniques exemplified here is provided in .

- - -
-
Partial and Composite Divisions -

In most situations, the textual subdivisions marked by div +

+
+ Partial and Composite Divisions +

In most situations, the textual subdivisions marked by div or div1 (etc.) elements will be both complete and identically organized with reference to the original source. For some purposes however, in particular where dealing with unusually large or unusually @@ -512,19 +314,15 @@ texts. Moreover, in some kinds of texts it is difficult or impossible to determine the order in which individual subdivisions should be combined to form the next higher level of subdivision, as noted below.

-

To overcome these problems, the following additional attributes are +

To overcome these problems, the following additional attributes are defined for all elements in the att.divLike class: - - - +

-

For example, an encoder might choose to transcribe only the first two +

For example, an encoder might choose to transcribe only the first two thousand words of each chapter from a novel. In such a case, each chapter might conveniently be regarded as a partial division, and tagged with a div element in the following form: -

-

...

-
+

...

where xx represents a number for the chapter, and the part attribute takes the value Y to indicate that this division is incomplete in some respect. Other possible @@ -533,43 +331,25 @@ initially (I), finally (F), or in the middle (M) of the division, while the gap element () may be used to indicate exactly where material has been omitted: -
-

...

- -

...

-
 +

...

...

The samplingDecl element in the TEI header should also be used to record the principles underlying the selection of incomplete samples, as further described in section .

-

The following example demonstrates how a newspaper column composed of +

The following example demonstrates how a newspaper column composed of very short unrelated snippets may be encoded using these attributes: - -News in brief - -Police deny losing bomb -

Scotland Yard yesterday denied claims in the Sunday +News in briefPolice deny losing bomb

Scotland Yard yesterday denied claims in the Sunday Express that anti-terrorist officers trailing an IRA van loaded with explosives in north London had lost track of -it 10 days ago.

- - -Hotel blaze -

Nearly 200 guests were evacuated before dawn +it 10 days ago.

Hotel blaze

Nearly 200 guests were evacuated before dawn yesterday after fire broke out at the Scandic -Crown hotel in the Royal Mile, Edinburgh.

- - -Test match split -

Test Match Special next summer will be split +Crown hotel in the Royal Mile, Edinburgh.

Test match split

Test Match Special next summer will be split between Radio 5 and Radio 3, after protests this -year that it disrupted Radio 3's music schedule.

- - +year that it disrupted Radio 3's music schedule.

-

The org attribute on the div1 element is used +

The org attribute on the div1 element is used here to indicate that individual stories in this group, marked here as div2, are really quite independent of each other, although they are all marked as subdivisions of the whole group. They can be read in @@ -579,44 +359,37 @@ impossible to determine the order in which they are intended to be read. Individual stories can be added or removed without affecting the existing components.

-

This method of encoding composite texts as composite divisions has +

This method of encoding composite texts as composite divisions has some limitations compared with the more general and powerful mechanisms discussed in section . However, it may be preferable in some circumstances, notably where the individual texts are very small. -

-
Elements Common to All Divisions -

The divisions of any kind of text may sometimes begin with a brief +

+
+
+
+ Elements Common to All Divisions +

The divisions of any kind of text may sometimes begin with a brief heading or descriptive title, with or without a byline, an epigraph or brief quotation, or a salutation such as one finds at the start of a letter. They may also conclude with a brief trailer, byline, postscript, or signature. Many of these (e.g. a byline) may appear either at the start or at the end of a text division proper.

-

To support this heterogeneity, the TEI architecture defines five +

To support this heterogeneity, the TEI architecture defines five classes, all of which are populated by this module: - - - - - - -

- -
Headings and Trailers - -

The head element is used to identify a heading prefixed to +

+
+ Headings and Trailers +

The head element is used to identify a heading prefixed to the start of any textual division, at any level. A given division may contain more than one such element, as in the following example: - -Etymology -(Supplied by a late consumptive usher to a -grammar school) -

The pale Usher — threadbare in coat, heart, +Etymology(Supplied by a late consumptive usher to a +grammar school)

The pale Usher — threadbare in coat, heart, body and brain; I see him now. He was ever dusting his old lexicons and grammars, ...

-

Unlike some other markup schemes, the TEI scheme does +

Unlike some other markup schemes, the TEI scheme does not require that headings attached to textual subdivisions at different hierarchic levels have different identifiers. All kinds of heading are marked identically using the @@ -626,7 +399,7 @@ example be a div1, div2, etc., an un-numbered div, or any member of the model.listLike class. However, as with div elements, the encoder may choose to extend the model.headLike class of which head is the sole member to include other such elements if required.

-

In certain kinds of text (notably newspapers), there may be a need +

In certain kinds of text (notably newspapers), there may be a need to categorize individual headings within the sequence at the start of a division, for example as main headings, or detail headings: this may readily be done using the @@ -637,21 +410,17 @@ attributes must be used to discriminate among other forms of heading. These attributes are provided, as elsewhere, by the att.typed attribute class of which the head element is a member.

-

In the following example, taken from a British newspaper, the lead +

In the following example, taken from a British newspaper, the lead story and its associated headlines have been encoded as a div element, with appropriate model.divTop elements attached: -

- +
President pledges safeguards for 2,400 British -troops in Bosnia - -Major agrees to enforced no-fly zone -By George Jones, Political Editor, in Washington -

Greater Western intervention in the conflict in +troops in Bosnia +Major agrees to enforced no-fly zoneBy George Jones, Political Editor, in Washington

Greater Western intervention in the conflict in former Yugoslavia was pledged by President Bush ...

-

In older writings, the headings or incipits may be +

In older writings, the headings or incipits may be longer than in modern works. When heading-like material appears in the middle of a text, the encoder must decide whether or not to treat it as the start of a new division. @@ -663,33 +432,20 @@ the kind of pull quotes often found in newspapers or magazines, then the quote, q, or cit element may be more appropriate.

-

The trailer element, which can appear at the end of a +

The trailer element, which can appear at the end of a division only, is used to mark any heading-like feature appearing in this position, as in this example:

In the name of Christ here begins the first book of the ecclesiastical history of Georgius Florentinus, - known as Gregory, Bishop of Tours. -
Chapter Headings - - - - -
-
In the name of Christ here begins Book I of the history. -

Proposing as I do ...

-

From the Passion of our Lord until the death of Saint Martin four - hundred and twelve years passed.

- Here ends the first Book, which covers five thousand, five + known as Gregory, Bishop of Tours.
Chapter Headings
In the name of Christ here begins Book I of the history.

Proposing as I do ...

From the Passion of our Lord until the death of Saint Martin four + hundred and twelve years passed.

Here ends the first Book, which covers five thousand, five hundred and ninety-six years from the beginning of the world down - to the death of Saint Martin. -
-
+ to the death of Saint Martin.

- - -
-
Openers and Closers -

In addition to headings of various kinds, divisions sometimes include +

+
+ Openers and Closers +

In addition to headings of various kinds, divisions sometimes include more or less formulaic opening or closing passages, typically conveying such information as the name and address of the person to whom the division is addressed, the place or time of its production, a salutation @@ -698,168 +454,89 @@ are particularly liable to include such features. Additional elements for the detailed encoding of personal names, dates, and places are provided in chapter . For simple cases, the following elements should be adequate: - - - - - - +

-

The byline and dateline elements are used to encode +

The byline and dateline elements are used to encode headings which identify the authorship and provenance of a division. Although the terminology derives from newspaper usage, there is no implication that dateline or byline elements apply only to newspaper texts. The following example illustrates use of the dateline and signed elements at the end of the preface to a novel: -

-To Henry Hope. -

It is not because this volume was conceived and partly +

To Henry Hope.

It is not because this volume was conceived and partly executed amid the glades and galleries of the Deepdene, that I have inscribed it with your name. ... I shall find a reflex to their efforts in your own generous spirit and enlightened mind. -

- -D. -Grosvenor Gate, May-Day, 1844 - -
- +

D.Grosvenor Gate, May-Day, 1844

-

Where a sequence of such elements appear together, either at the +

Where a sequence of such elements appear together, either at the beginning or end of an element, it may be convenient to group them together using one of the following elements: - - - + The following examples demonstrate the use of the opener and closer grouping elements: -

- Sixth Narrative - contributed by Sergeant Cuff -
- - - Dorking, Surrey, - July 30th, 1849 - - To Franklin Blake, Esq. Sir, — - -

I beg to apologize for the delay that has occurred in the +

Sixth Narrativecontributed by Sergeant Cuff
Dorking, Surrey,July 30th, 1849To Franklin Blake, Esq. Sir, —

I beg to apologize for the delay that has occurred in the production of the Report, with which I engaged to furnish you. - I have waited to make it a complete Report ...

- - I have the honour to remain, dear sir, your - obedient servant - RICHARD CUFF (late sergeant in the - Detective Force, Scotland Yard, London). - -
-
+ I have waited to make it a complete Report ...

I have the honour to remain, dear sir, your + obedient servant RICHARD CUFF (late sergeant in the + Detective Force, Scotland Yard, London).
-
-Letter XIV: Miss Clarissa Harlowe to Miss Howe - Thursday evening, March 2. -

On Hannah's depositing my long letter ...

-

An interruption obliges me to conclude myself -in some hurry, as well as fright, what I must ever be,

- -Yours more than my own, -Clarissa Harlowe - -
 +
Letter XIV: Miss Clarissa Harlowe to Miss HoweThursday evening, March 2.

On Hannah's depositing my long letter ...

An interruption obliges me to conclude myself +in some hurry, as well as fright, what I must ever be,

Yours more than my own,Clarissa Harlowe

-

For further discussion of the encoding of dates and of names of persons and places, see section and chapter . -

-
Arguments, Epigraphs, and Postscripts -

The argument element may be used to encode the prefatory +

For further discussion of the encoding of dates and of names of persons and places, see section and chapter . +

+
+
+ Arguments, Epigraphs, and Postscripts +

The argument element may be used to encode the prefatory list of topics sometimes found at the start of a chapter or other division. It is most conveniently encoded as a list, since this allows each item to be distinguished, but may also simply be presented as a paragraph. The following are thus both equally valid ways of encoding the same argument: -

- -

Kingston — Instructive remarks on early English history +

Kingston — Instructive remarks on early English history — Instructive observations on carved oak and life in general — Sad case of Stivvings, junior — Musings on antiquity — I forget that I am steering — Interesting result - — Hampton Court Maze — Harris as a guide.

- -

It was a glorious morning, late spring or early summer, as you - care to take it ...

-
+ — Hampton Court Maze — Harris as a guide.

It was a glorious morning, late spring or early summer, as you + care to take it ...

-
- - - Kingston - Instructive remarks on early English history - Instructive observations on carved oak and life in - general - Sad case of Stivvings, junior - Musings on antiquity - I forget that I am steering - Interesting result - Hampton Court Maze - Harris as a guide. - - -

It was a glorious morning, late spring or early summer, as you - care to take it ...

-
 +
KingstonInstructive remarks on early English historyInstructive observations on carved oak and life in + generalSad case of Stivvings, juniorMusings on antiquityI forget that I am steeringInteresting resultHampton Court MazeHarris as a guide.

It was a glorious morning, late spring or early summer, as you + care to take it ...

-

An epigraph is a quotation from some other work, a +

An epigraph is a quotation from some other work, a saying, or a motto, appearing on a title page, or at the start of a division. It may be encoded using the special-purpose epigraph element, as in the following example: - - -E. M. Forster -Howards End -Only connect... - - +E. M. ForsterHowards EndOnly connect... When an epigraph contains a quotation, this may often be associated with a bibliographic reference. In such cases, it is recommended additionally to group the quotation and its source together using the -cit element, as in the following example:

Chapter 19 - - I pity the man who can travel +cit element, as in the following example:
Chapter 19I pity the man who can travel from Dan to Beersheba, and say 'Tis all barren; and so is all the world to him who will not cultivate the fruits it offers. - - Sterne: Sentimental Journey. - -

To say that Deronda was romantic would be to + Sterne: Sentimental Journey.

To say that Deronda was romantic would be to misrepresent him: but under his calm and somewhat - self-repressed exterior ...

-
 + self-repressed exterior ...

-

For discussion of quotations appearing other than as epigraphs refer +

For discussion of quotations appearing other than as epigraphs refer to section . -

A postscript is a passage added after the signature of +

+

A postscript is a passage added after the signature of a letter or, less frequently, the main portion of the body of a book, article, or essay. In English a postscript is often abbreviated as P.S. or PS, and postscripts are often introduced by labels with one of these abbreviations, as in the following example. - -

- - - Newport - May ye 27th 1761 - - Gentlemen - -

Capt Stoddard's Business +

NewportMay ye 27th 1761Gentlemen

Capt Stoddard's Business calling him to Providence, have got him to look at Hopkins brigantine & if can agree to Purchase her, shall @@ -870,25 +547,16 @@ abbreviations, as in the following example. Line respecting the brigantine & Beg leave to Recommend the Bearer to you for your advice & Friendship - in this matter

- - I am your most humble servant - Joseph Wanton Jr - - - -

I have Mollases, Sugar, + in this matter

I am your most humble servantJoseph Wanton Jr

I have Mollases, Sugar, Coffee & Rum, which will Exchange with you - for Candles or Oyl

- -
- + for Candles or Oyl

-
-
Content of Textual Divisions -

Other than elements from the model.divWrapper, model.divTop, or model.divBottom classes, every textual division +

+
+ Content of Textual Divisions +

Other than elements from the model.divWrapper, model.divTop, or model.divBottom classes, every textual division (numbered or un-numbered) consists of a sequence of ungrouped model.common elements (see ). The actual elements available will depend on the modules in use; in all cases, at least the component-level structural elements defined in the core will be available (paragraphs, lists, @@ -902,28 +570,27 @@ defined in chapter ) will also be available; if the module for transcribed speech is in use, then utterances, pauses, vocals, kinesics, etc., as defined in chapter will be available; and so on.

-

Where a text contains low-level elements from more than one +

Where a text contains low-level elements from more than one module these may appear at any point; there is no requirement that elements from the same module be kept together.

- - - - - - - - - - - - - - - -
-
-
Grouped and Floating Texts -

The group element discussed in + + + + + + + + + + + + + +

+
+
+ Grouped and Floating Texts +

The group element discussed in should be used to represent a collection of independent texts which is to be regarded as a single unit for processing or other purposes. The floatingText element discussed in @@ -931,8 +598,9 @@ should be used to represent an independent text which interrupts the text containing it at any point but after which the surrounding text resumes.

-
Grouped Texts -

+

+ Grouped Texts +

Examples of composite texts which should be represented using the group element include anthologies and other collections. The presence of common front matter @@ -941,92 +609,41 @@ relating to each individual text, is a good indication that a given text might usefully be encoded in this way; this structure may be found useful in other circumstances too.

-

For example, the overall structure of a collection of +

For example, the overall structure of a collection of short stories might be encoded as follows: - - - - + The Adventures of Sherlock Holmes - - First published in The Strand - between July 1891 and December 1892 - - - - - - Adventures of Sherlock - Holmes - Adventure I. — - A Scandal in Bohemia - By A. Conan Doyle. - - -

To Sherlock Holmes she is always - the woman. ...

- - - - - - Adventures of Sherlock Holmes - Adventure II. — - The Red-Headed League - By A. Conan Doyle. - - -

I had called upon my friend, Mr. Sherlock Holmes, one day + First published in The Strand + between July 1891 and December 1892Adventures of Sherlock + HolmesAdventure I. —A Scandal in BohemiaBy A. Conan Doyle.

To Sherlock Holmes she is always + the woman. ...

Adventures of Sherlock HolmesAdventure II. —The Red-Headed LeagueBy A. Conan Doyle.

I had called upon my friend, Mr. Sherlock Holmes, one day in the autumn of last year and found him in deep conversation with a very stout, florid-faced, elderly gentleman with fiery red hair … -

- - - - - - Adventures of Sherlock Holmes - Adventure XII. — - The Adventure of the Copper Beeches - - By A. Conan Doyle. - - -

To the man who loves art for its +

Adventures of Sherlock HolmesAdventure XII. —The Adventure of the Copper BeechesBy A. Conan Doyle.

To the man who loves art for its own sake, remarked Sherlock Holmes ... ... she is now the head of a private school at Walsall, where I believe that she has - met with considerable success.

- - - - - + met with considerable success.

-

A text which is a member of a group may itself contain groups. This +

A text which is a member of a group may itself contain groups. This is quite common in collections of verse, but may happen in any kind of text. As an example, consider the overall structure of a typical collection, such as the Muses Library edition of Crashaw's poetry. Following a critical introduction and table of contents, this work contains the following major sections: - -Steps to the Temple (a collection of -verse as published in 1648) -Carmen deo Nostro (a second collection, -published in 1652) -The Delights of the Muses (a third -collection, published in 1648) -Posthumous Poems, I (a collection of -fragments all taken from a single manuscript) -Posthumous Poems, II (a further collection +Steps to the Temple (a collection of +verse as published in 1648)Carmen deo Nostro (a second collection, +published in 1652)The Delights of the Muses (a third +collection, published in 1648)Posthumous Poems, I (a collection of +fragments all taken from a single manuscript)Posthumous Poems, II (a further collection of fragments, taken from a different manuscript)

-

The first three of these collections each has a +

The first three of these collections each has a reasonable claim to be considered as a text in its own right, and may therefore be encoded as such. It is rather more arbitrary as to whether the two posthumous collections should be treated as two @@ -1034,7 +651,7 @@ groups, following the practice of the Muses Library edition. An encoder might elect to combine the two into a single group or simply to treat each fragment as an ungrouped unitary text.

-

The Muses Library edition reprints the whole of each +

The Muses Library edition reprints the whole of each of the three original collections, including their original front matter (title pages, dedications etc.). These should be encoded using the front element and its constituents (on which see further @@ -1044,80 +661,11 @@ poem within the collections should be encoded as a distinct text element. The beginning of the whole collection would thus appear as follows (for further discussion of the use of the elements div and lg for textual subdivision of -verse, see section and chapter ): - - - The poems of Richard Crashaw - Edited by J.R. Tutin - -

Editor's Note -

A few words are necessary ...

-
- - - - - - - Steps to the Temple, Sacred Poems - - -
The Preface to the Reader -

Learned Reader, The Author's friend will not usurp much - upon thy eye ...

-
- - - - - Sospetto D'Herode - - - - Libro Primo - - Casting the times with their strong signs - - - Muse! now the servant of soft loves no more - Hate is thy theme and Herod whose unblest - Hand (O, what dares not jealous greatness?) tore - A thousand sweet babes from their mothers' breast, - The blooms of martyrdom ... - - - The Tear - - - What bright soft thing is this - Sweet Mary, thy fair eyes' expense? - - - - - - - - - - - - - - - - - - - - - - - - +verse, see section and chapter ): The poems of Richard CrashawEdited by J.R. Tutin
Editor's Note

A few words are necessary ...

Steps to the Temple, Sacred Poems
The Preface to the Reader

Learned Reader, The Author's friend will not usurp much + upon thy eye ...

Sospetto D'HerodeLibro PrimoCasting the times with their strong signsMuse! now the servant of soft loves no moreHate is thy theme and Herod whose unblestHand (O, what dares not jealous greatness?) toreA thousand sweet babes from their mothers' breast,The blooms of martyrdom ...The TearWhat bright soft thing is thisSweet Mary, thy fair eyes' expense?

-

The group element may be used in this way to encode any kind +

The group element may be used in this way to encode any kind of collection of which the constituents are regarded by the encoder as texts in their own right. Examples include anthologies or collections of verse or @@ -1126,32 +674,19 @@ journals, day books, etc. As a fairly typical example, we consider The Norton Book of Travel, an anthology edited by Paul Fussell and published in 1987 by W. W. Norton. This work comprises the following major sections: - -Front matter (title page, acknowledgments, introductory essay) -The Beginnings -The Eighteenth Century and the Grand Tour -The Heyday -Touristic Tendencies -Post Tourism -Back matter (permissions list, index) +Front matter (title page, acknowledgments, introductory essay)The BeginningsThe Eighteenth Century and the Grand TourThe HeydayTouristic TendenciesPost TourismBack matter (permissions list, index) Each titled section listed above comprises a group of extracts or complete texts from writers of a given historical period, preceded by an introductory essay. For example, the second group listed above contains, inter alia, the following: - -Prefatory essay -Five letters by Lady Mary Wortley Montagu -An extract from Swift's Gulliver's Travels -Two poems by Alexander Pope -Two extracts from Boswell's Journal -A poem by William Blake +Prefatory essayFive letters by Lady Mary Wortley MontaguAn extract from Swift's Gulliver's TravelsTwo poems by Alexander PopeTwo extracts from Boswell's JournalA poem by William Blake Each group of writings by a single author is preceded by a brief biographical notice. Some of the extracts are quite lengthy, containing several chapters or other divisions; others are quite short. As the above list indicates, the texts included range across all kinds of material: verse, prose, journals and letters.

-

The easiest way of encoding such an anthology is to treat each +

The easiest way of encoding such an anthology is to treat each individual extract as a text in its own right. A sequence of texts by a single author, together with the biographical note preceding it, can then be treated as a single group element within the larger @@ -1159,43 +694,9 @@ then be treated as a single group element within the larger composite texts making up a single section of the work is likewise treated, together with its prefatory essay, as a single group within the work. Schematically: - - - - - - - The Beginnings - - - - - - - - - - - - - - - - - - - - - - The Heyday - - - - - - +The Beginnings The Heyday

-

Note that the editor's introductory essays on each author may be +

Note that the editor's introductory essays on each author may be treated as texts in their own right (as the essays on Lady Mary Wortley Montagu and Alexander Pope have been treated above), or as front matter to the embedded text, as the essay on Swift has been. @@ -1206,20 +707,14 @@ by Swift and one by the editor, or by treating the Montagu and Pope sections as text elements containing the editor's essays as front matter. Marked in the second way, the Pope section of the book would look like this: - - - - - - - +

-

The essays on The Eighteenth Century and the Grand Tour and +

The essays on The Eighteenth Century and the Grand Tour and other larger sections could also be tagged as front matter in the same way, by treating the larger sections as text elements rather than group elements.

-

Where, as in this case, an anthology contains different kinds of +

Where, as in this case, an anthology contains different kinds of text (for example, mixtures of prose and drama, or transcribed speech and dictionary entries, or letters and verse), the elements to be encoded will of course be drawn from more than one module. @@ -1228,7 +723,7 @@ described in chapter should however prove adequate for most simple purposes, where prose, drama, and verse are combined in a single collection.

-

For anthologies of short extracts such as commonplace books, it may +

For anthologies of short extracts such as commonplace books, it may often be preferable to regard each extract not as a text in its own right but simply as a quotation or cit element. The following component-level elements may be used to encode quotations of this kind: @@ -1236,45 +731,24 @@ component-level elements may be used to encode quotations of this kind: For example, the chapter of extracts which appears in the front matter of Melville's Moby Dick might be encoded as follows: -

- Extracts - (Supplied by a sub-sub-Librarian) -

It will be seen that this mere painstaking burrower and +

Extracts(Supplied by a sub-sub-Librarian)

It will be seen that this mere painstaking burrower and grubworm of a poor devil of a Sub-Sub appears to have gone through the long Vaticans and street-stalls of the earth, picking up whatever random allusions to whales he could anyways find ... Here ye strike but splintered hearts together — there, - ye shall strike unsplinterable glasses!

-

- - And God created great whales. - Genesis - - - - Leviathan maketh a path to shine after him; - One would think the deep to be hoary. - - Job - - - By art is created that great Leviathan, + ye shall strike unsplinterable glasses!

And God created great whales.GenesisLeviathan maketh a path to shine after him;One would think the deep to be hoary.JobBy art is created that great Leviathan, called a Commonwealth or State — (in Latin, civitas), which - is but an artificial man. - Opening sentence of Hobbes's Leviathan - -

-
+ is but an artificial man.Opening sentence of Hobbes's Leviathan

For more information on the use of the quote and bibl elements, see sections and respectively.

- -
-
Floating Texts -

An important characteristic of the unitary or composite text +

+
+ Floating Texts +

An important characteristic of the unitary or composite text structures discussed so far is that they can be regarded as forming what is mathematically known as a tesselation covering the whole of the available text (or text division) at each hierarchic @@ -1288,8 +762,7 @@ true of texts which are only partly tesselated at a given level. For example, if a text A is contained by text B in such a way that part of B precedes A and part follows it, we cannot tesselate the whole of B. In such a case, we say that text A is a floating text.

- -

The floatingText element is a member of the +

The floatingText element is a member of the model.divPart class, and can thus appear within any division level element in the same way as a paragraph. For example, texts such as the Decameron or the @@ -1298,81 +771,58 @@ floating texts embedded within another single text, the framing narrative, rather than as groups of discrete texts in which the fragments of framing narrative are regarded as front or back matter.

- -

As an example, we consider an 18th century text The Lining to + <p>As an example, we consider an 18th century text <title>The Lining to the <hi>Patch-Work Screen</hi>, by Jane Barker (1726). This lengthy narrative contains nearly a hundred distinct tales embedded (as the title suggests) in a single patchwork. The work begins by introducing the central character, Galecia, but within a few pages launches into a distinct narrative, the story of Captain Manly: - -

Galecia one Evening setting alone in her Chamber by a clear Fire, +

Galecia one Evening setting alone in her Chamber by a clear Fire, and a clean Hearth [...] reflected on the Providence of our -All-wise and Gracious Creator [...]

-

She was thus ruminating, when a Gentleman enter'd the Room, the +All-wise and Gracious Creator [...]

She was thus ruminating, when a Gentleman enter'd the Room, the Door being a jar [...] calling for a Candle, she beg'd a thousand Pardons, engaged him to sit down, and let her know, what had so long conceal'd him from her Correspondence. -

- -The Story of Captain Manly -

Dear Galecia, said he, though you partly know the loose, or rather +

The Story of Captain Manly

Dear Galecia, said he, though you partly know the loose, or rather lewd Life that I led in my Youth; yet I can't forbear relating part of it to you by way of Abhorrence... I had lost and spent all I had in the World; in which I verified the Old Proverb, That a Rolling Stone never gathers Moss, -

 - - +

-

Following the conclusion of Captain Manly's tale, we are +

Following the conclusion of Captain Manly's tale, we are returned to Galecia, and almost immediately after that into two further stories. However, the Galecia narrative returns between each of the texts, which is why we choose to represent them as floatingTexts: - -

The Gentleman having finish'd his Story, Galecia waited on him to +

The Gentleman having finish'd his Story, Galecia waited on him to the Stairs-head; and at her return, casting her Eyes on the Table, she saw lying there an old dirty rumpled Book, and found in it the -following story:

-

IN the time of the Holy War when +following story:

IN the time of the Holy War when Christians from all parts went into the Holy Land to oppose the Turks; -Amongst these there was a certain English Knight...

- -

The King graciously pardoned the Knight; Richard was kindly receiv'd +Amongst these there was a certain English Knight...

The King graciously pardoned the Knight; Richard was kindly receiv'd into his Convent, and all things went on in good order: But from hence came the Proverb, We must not strike Robert for -Richard.

 - -

By this time Galecia's Maid brought up her Supper; after which she +Richard.

By this time Galecia's Maid brought up her Supper; after which she cast her Eyes again on the foresaid little Book, where she found the following Story, which she read through before she went to bed. -

-The Cause of the Moors Overrunning -Spain -

King ———— of Spain at his Death, committed the Government of his +

The Cause of the Moors Overrunning +Spain

King ———— of Spain at his Death, committed the Government of his Kingdom to his Brother Don ——— till his little Son should come of -Age ...

-

Thus the little Story ended, without telling what Misery +Age ...

Thus the little Story ended, without telling what Misery befel the King and Kingdom, by the Moors, who over ran the Country for many Years after. To which, we may well apply the Proverb, - - Who drives the Devil's Stages, - Deserves the Devil's Wages -

- -

The reading this Trifle of a Story detained Galecia from her Rest +Who drives the Devil's Stages,Deserves the Devil's Wages

The reading this Trifle of a Story detained Galecia from her Rest beyond her usual Hour; for she slept so sound the next Morning, that she did not rise, till a Lady's Footman came to tell her, that his Lady and another or two were coming to breakfast with her... +

- -

-

In other multi-narrative texts, the individual nested tales may +

In other multi-narrative texts, the individual nested tales may have greater significance than the framing narratives, and it may therefore be preferable to treat the fragments of framing narrative as front or back matter associated with each nested tale. This is @@ -1380,15 +830,13 @@ commonly done, for example, in texts such as Chaucer's Canterbury Tales, where each tale is typically presented with front matter in which the teller of the tale is introduced, and back matter in which the pilgrims comment on it.

- -

It is important to distinguish between the uses of floatingText and quote. Whereas the semantics of quote suggest that its content derives from a source external to the current text, floatingText carries no such implication and is simply used whenever the richer content model that it provides is required to support the markup of a part of a text that is presented as a discrete inclusion. In some cases, such inclusions could be considered external (e.g., enclosures, attachments, etc.); often however, as in the examples above, the included text bears no signs of emanating from outside.

- -

floatingText and quote may be used in combination. For a text with rich internal structure that is quoted at length, floatingText might be used within quote. Also, like a unitary text, floatingText may include one or more quoted sections, each marked with a quote element.

- -
- -
Virtual Divisions -

Where the whole of a division can be automatically generated, for +

It is important to distinguish between the uses of floatingText and quote. Whereas the semantics of quote suggest that its content derives from a source external to the current text, floatingText carries no such implication and is simply used whenever the richer content model that it provides is required to support the markup of a part of a text that is presented as a discrete inclusion. In some cases, such inclusions could be considered external (e.g., enclosures, attachments, etc.); often however, as in the examples above, the included text bears no signs of emanating from outside.

+

floatingText and quote may be used in combination. For a text with rich internal structure that is quoted at length, floatingText might be used within quote. Also, like a unitary text, floatingText may include one or more quoted sections, each marked with a quote element.

+
+
+
+ Virtual Divisions +

Where the whole of a division can be automatically generated, for example because it is derived from another part of this or another document, an encoder may prefer not to represent it explicitly but instead simply mark its location by means of a @@ -1396,15 +844,12 @@ processing instruction, or by using the special purpose divGen element:

-

This element is made available by the model.divGenLike class of which it is the sole +

This element is made available by the model.divGenLike class of which it is the sole element. The divGen element is a member of the att.typed class, from which it inherits the type and subtype attributes. It may appear wherever a div or div1 (div2, etc.) element may appear.

- - - -

For example, if the table of contents (toc) for a given work is simply +

For example, if the table of contents (toc) for a given work is simply derived by copying the first head element from each div element in a text, it might be more easily encoded as follows: @@ -1414,9 +859,7 @@ of some text with a translated version of it, it may be desired to represent the transcript, the translation, and an aligned version of the two as three distinct divisions. This could be achieved by an encoding like the following: -

-
-
The processing to be carried out when a +
 The processing to be carried out when a divGen element is rendered will be determined by the application program or stylesheet in use: the function of the TEI markup is simply to identify the location at which the virtual @@ -1424,12 +867,10 @@ division is to be generated, and also to provide some information about the kind of division to be generated. As such it may be regarded as a special kind of processing instruction, and could equally well be represented by one.

- -
- - -
Front Matter -

By front matter we mean distinct sections of a text +

+
+ Front Matter +

By front matter we mean distinct sections of a text (usually, but not necessarily, a printed one), prefixed to it by way of introduction or identification as a part of its production. Features such as title pages or prefaces are clear examples; a less definite @@ -1438,7 +879,7 @@ encoded text should not be confused with the TEI header described in chapter , which serves as a kind of front matter for the computer file itself, not the text it encodes.

-

An encoder may choose simply to ignore the front matter in a text, +

An encoder may choose simply to ignore the front matter in a text, if the original presentation of the work is of no interest, or for other reasons; alternatively some or all components of the front matter may be thought worth including with the text as components of the @@ -1457,46 +898,30 @@ handle these values when they occur, without limiting the user to the values in this list. for the type attribute may be used to distinguish various kinds of division characteristic of front matter: - -A foreword or preface addressed to +A foreword or preface addressed to the reader in which the author or publisher explains the - content, purpose, or origin of the text. -A formal declaration of + content, purpose, or origin of the text.A formal declaration of acknowledgment by the author in which persons and institutions - are thanked for their part in the creation of a text. -A formal offering or dedication of - a text to one or more persons or institutions by the author. -A summary of the content of a text as - continuous prose. -A table of contents, specifying the + are thanked for their part in the creation of a text.A formal offering or dedication of + a text to one or more persons or institutions by the author.A summary of the content of a text as + continuous prose.A table of contents, specifying the structure of a work and listing its constituents. The list - element should be used to mark its structure. -A pictorial frontispiece, + element should be used to mark its structure.A pictorial frontispiece, possibly including some text.

-

The following extended example demonstrates how various parts of the +

The following extended example demonstrates how various parts of the front matter of a text may be encoded. The front part begins with a title page, which is presented in section below. This is followed by a dedication and a preface, each of which is encoded as a distinct div: -

-

To my parents, Ida and Max Fish

-
-
Preface -

The answer this book gives to its title question is there is - and there isn't.

-

Chapters 1–12 have been previously published in the +

To my parents, Ida and Max Fish

Preface

The answer this book gives to its title question is there is + and there isn't.

Chapters 1–12 have been previously published in the following journals and collections: - - chapters 1 and 3 in New literary History - chapter 10 in Boundary II (1980) - . - I am grateful for permission to reprint.

- S.F. -
+ chapters 1 and 3 in New literary Historychapter 10 in Boundary II (1980). + I am grateful for permission to reprint.

S.F.

-

The front matter concludes with another div element, shown +

The front matter concludes with another div element, shown in the next example, this time containing a table of contents, which contains a list element (as described in section ). Note the use of the ptr element to provide @@ -1504,99 +929,47 @@ page-references: the implication here is that the target identifiers supplied (fish1, fish2, etc.) will correspond with identifiers used for the div elements containing chapters of the text itself. (For the ptr element, see .) -

- Contents - - Introduction, or How I stopped Worrying and Learned to Love - Interpretation - - - Part One: Literature in the Reader - Literature in the Reader: Affective Stylistics - - What is Stylistics and Why Are They Saying Such - Terrible Things About It? - -
-
Introduction - -
-
Literature in the Reader - -
-
What is stylistics? - -
- +
ContentsIntroduction, or How I stopped Worrying and Learned to Love + Interpretation Part One: Literature in the ReaderLiterature in the Reader: Affective Stylistics + What is Stylistics and Why Are They Saying Such + Terrible Things About It?
Introduction
Literature in the Reader
What is stylistics?
 Alternatively, the pointers in the index might link to the page breaks at which a chapter begins, assuming that these have been included in the markup: - - Literature in the Reader: Affective Stylistics - 24 - -
Literature in the Reader - - -
- - +Literature in the Reader: Affective Stylistics + 24
Literature in the Reader

-

The following example uses numbered divisions to mark up the front +

The following example uses numbered divisions to mark up the front matter of a medieval text. Note that in this case no title page in the modern sense occurs; the title is simply given as a heading at the start of the front matter. Note also the use of the type attribute on the div elements to indicate document elements comparatively unusual in modern books such as the initial prayer: - - -

Here bygynniþ a book of contemplacyon, þe whiche +

Here bygynniþ a book of contemplacyon, þe whiche is clepyd þE CLOWDE OF VNKNOWYNG, - in þe whiche a soule is onyd wiþ GOD.

- - - Here biginneþ þe preyer on þe prologe. -

God, unto whom alle hertes ben open, & unto whome alle wille + in þe whiche a soule is onyd wiþ GOD.

Here biginneþ þe preyer on þe prologe.

God, unto whom alle hertes ben open, & unto whome alle wille spekiþ, & unto whom no priue þing is hid: I beseche þee so for to clense þe entent of myn hert wiþ þe unspekable 3ift of þi grace, þat I may parfiteliche - loue þee & worþilich preise þee. Amen.

- - - Here biginneþ þe prolog. -

In þe name of þe Fader & of þe Sone & - of þe Holy Goost.

-

I charge þee & I beseeche þee, wiþ as moche + loue þee & worþilich preise þee. Amen.

Here biginneþ þe prolog.

In þe name of þe Fader & of þe Sone & + of þe Holy Goost.

I charge þee & I beseeche þee, wiþ as moche power & vertewe as þe bonde of charite is sufficient to suffre, what-so-euer þou be þat þis book schalt - haue in possession ...

- - - Here biginneþ a table of þe chapitres. - - - Of foure degrees of Cristen mens leuing; & of þe - cours of his cleping þat þis book was maad vnto. - - A schort stering to meeknes & to þe werk of þis - book - - Of somme certein tokenes bi þe whiche a man may proue - wheþer he be clepid of God to worche in þis werk. - - & here eendeþ þe table of þe chapitres. - - + haue in possession ...

Here biginneþ a table of þe chapitres.Of foure degrees of Cristen mens leuing; & of þe + cours of his cleping þat þis book was maad vnto.A schort stering to meeknes & to þe werk of þis + bookOf somme certein tokenes bi þe whiche a man may proue + wheþer he be clepid of God to worche in þis werk.& here eendeþ þe table of þe chapitres.

-

If, however, the table of contents can be automatically generated +

If, however, the table of contents can be automatically generated from the remainder of the text, it may be preferable simply to mark its presence, either by means of an empty divGen element or by using an appropriate processing instruction.

-
-
Title Pages -

Detailed analysis of the title page and other +

+
+ Title Pages +

Detailed analysis of the title page and other preliminaries of older printed books and manuscripts is of major importance in descriptive bibliography and the cataloguing of printed books; such analysis may require a rather more detailed module @@ -1608,86 +981,55 @@ European Workgroup on SGML. See for example MAJOUR: Modular Application for Journals: DTD for Article Headers ([n.p.]: EWS, 1991). The following elements are suggested as a means of encoding the major features of most title pages: - - - - - - - - - - - - - - +

-

These elements constitute the model.titlepagePart class. Together with the figure +

These elements constitute the model.titlepagePart class. Together with the figure element described in chapter , any number of elements from this class can appear within a titlePage element. The figure element is included so as to enable encoders to record the presence of complex non-textual material on a title page. For simple cases such as printers' ornaments or illustrations the graphic element discussed in section should be adequate.

-

The elements listed above, together with the head element, +

The elements listed above, together with the head element, also constitute the class model.pLike.front. The elements in this class can appear within a minimal front element without any need to group them together and encode a complete title page.

-

Encoders wishing to add new elements to either class may do so +

Encoders wishing to add new elements to either class may do so using the methods described in section . Two examples of the use of these elements follow. First, the title page of -the work discussed earlier in this section: - - - Is There a Text in This Class? - The Authority of Interpretive Communities - - Stanley Fish - - Harvard University Press - Cambridge, Massachusetts - London, England - -

-

Second, a characteristically verbose 17th century example. Note the +the work discussed earlier in this section: Is There a Text in This Class?The Authority of Interpretive CommunitiesStanley FishHarvard University PressCambridge, MassachusettsLondon, England

+

Second, a characteristically verbose 17th century example. Note the use of the lb tag to mark the line breaks of the original where necessary: - - - THE +THE Pilgrim's Progress FROM THIS WORLD, TO - That which is to come: - Delivered under the Similitude of a - DREAM - Wherein is Discovered, + That which is to come:Delivered under the Similitude of a + DREAMWherein is Discovered, The manner of his setting out, His Dangerous Journey; And safe - Arrival at the Desired Countrey. - - - I have used Similitudes,Hos. 12.10 - - By John Bunyan. - Licensed and Entred according to Order. - - LONDON, + Arrival at the Desired Countrey.I have used Similitudes,Hos. 12.10By John Bunyan.Licensed and Entred according to Order.LONDON, Printed for Nath. Ponder at the Peacock in the Poultrey near Cornhil, 1678.

-

Where, as here, it is considered important to encode salient +

Where, as here, it is considered important to encode salient features of the way a title page was originally rendered, the techniques exemplified in may also be useful.

- - - - -

Where title pages are encoded, their physical rendition is + + + + + + + + + + +

Where title pages are encoded, their physical rendition is often of considerable importance. One approach to this requirement would be to use the seg tag, described in chapter , to segment the typographic content of each part of the title page, and then use the global rend attribute to specify @@ -1697,63 +1039,40 @@ bearing special-purpose attributes to describe line-height, leading, degree of kerning, font, etc. Further discussion of these problems is provided in chapter .

- - - - - - - -
-
Back Matter -

Conventions vary as to which elements are grouped as back matter and + + + + +

+
+ Back Matter +

Conventions vary as to which elements are grouped as back matter and which as front. For example, some books place the table of contents at the front, and others at the back. Even title pages may appear at the back of a book as well as at the front. The content model for back and front elements are therefore identical.

-

The following suggested values may be used for the type +

The following suggested values may be used for the type attribute on all division elements, in order to distinguish various kinds of division characteristic of back matter: - -An ancillary self-contained section of +An ancillary self-contained section of a work, often providing additional but in some sense extra-canonical -text. -A list of terms associated with definition texts +text.A list of terms associated with definition texts (glosses): this should be encoded as a list type="gloss" -(see section ). -A section in which textual or -other kinds of notes are gathered together. -A list of bibliographic citations: this should be encoded -as a listBibl (see section ). -Any form of index to the work. -A statement appearing at the end of a book describing the +(see section ).A section in which textual or +other kinds of notes are gathered together.A list of bibliographic citations: this should be encoded +as a listBibl (see section ).Any form of index to the work.A statement appearing at the end of a book describing the conditions of its physical production.

-

No additional elements are proposed for the encoding of back matter +

No additional elements are proposed for the encoding of back matter at present. Some characteristic examples follow; first, an index (for the case in which a printed index is of sufficient interest to merit transcription): - -

- Index - - Actors, public, paid for the contempt attending - their profession, 263 - Africa, cause assigned for the barbarous state of - the interior parts of that continent, 125 - Agriculture - - ancient policy of Europe unfavourable to, 371 - artificers necessary to carry it on, 481 - cattle and tillage mutually improve each other, 325 - wealth arising from more solid than that which proceeds - from commerce 520 - - Alehouses, the number of, not the efficient cause of drunkenness, 461 - -
- +
IndexActors, public, paid for the contempt attending + their profession, 263Africa, cause assigned for the barbarous state of + the interior parts of that continent, 125Agriculture + ancient policy of Europe unfavourable to, 371artificers necessary to carry it on, 481cattle and tillage mutually improve each other, 325wealth arising from more solid than that which proceeds + from commerce 520Alehouses, the number of, not the efficient cause of drunkenness, 461
 Note that if the page breaks in the original source have also been explicitly encoded, and given identifiers, the references to them in the @@ -1763,35 +1082,21 @@ like this: then the last item above might be encoded more usefully in either of the following forms: - Alehouses, the number of, not -the efficient cause of drunkenness, 461 - Alehouses, the number of, not the efficient cause of drunkenness, -

-

Next, a back-matter division in epistolary form: - -

- A letter written to his wife, founde with this booke - after his death. -

The remembrance of the many wrongs offred thee, and thy + Alehouses, the number of, not +the efficient cause of drunkenness, 461Alehouses, the number of, not the efficient cause of drunkenness,

+

Next, a back-matter division in epistolary form: +

A letter written to his wife, founde with this booke + after his death.

The remembrance of the many wrongs offred thee, and thy unreproued vertues, adde greater sorrow to my miserable state, than I can utter or thou conceiue. ... ... yet trust I in the world to come to find mercie, by the merites of my Saiuour to whom I commend thee, and commit - my soule.

- Thy repentant husband for his disloyaltie, - Robert Greene. -

Faelicem fuisse infaustum

 - FINIS -
- + my soule.

Thy repentant husband for his disloyaltie, + Robert Greene.

Faelicem fuisse infaustum

FINIS

-

And finally, a list of corrigenda and addenda with pseudo-epistolary +

And finally, a list of corrigenda and addenda with pseudo-epistolary features: - -

- Addenda - M. Scriblerus Lectori -

Once more, gentle reader I appeal unto thee, from the shameful +

AddendaM. Scriblerus Lectori

Once more, gentle reader I appeal unto thee, from the shameful ignorance of the Editor, by whom Our own Specimen of Virgil hath been mangled in such miserable manner, that scarce without tears can we behold it. At the very entrance, Instead @@ -1802,31 +1107,19 @@ In the next page thou findest leviter perlabere, which his ignorance took to be the infinitive mood of perlabor but ought to be perlabi ... Wipe away all these -monsters, Reader, with thy quill.

-
- +monsters, Reader, with thy quill.

- - - - - -
-
- Module for Default Text Structure -

The module described by the present chapter has the following + + + +

+
+ Module for Default Text Structure +

The module described by the present chapter has the following components: - - Default Text Structure - Default text structure - Structure textuelle par défaut - 預設文件結構 - Struttura standard del testo - Estrutura do texto por defeito - テキスト構造モジュール - + Default Text StructureDefault text structureStructure textuelle par défaut預設文件結構Struttura standard del testoEstrutura do texto por defeitoテキスト構造モジュール @@ -1835,5 +1128,5 @@ monsters, Reader, with thy quill.

The selection and combination of modules to form a TEI schema is described in .

-
+
diff --git a/P5/Source/Guidelines/en/Dedication.xml b/P5/Source/Guidelines/en/Dedication.xml index 7e994dc732..405f91636e 100644 --- a/P5/Source/Guidelines/en/Dedication.xml +++ b/P5/Source/Guidelines/en/Dedication.xml @@ -1,11 +1,5 @@ - +
Dedication diff --git a/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml b/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml index 07464a05bb..858920629f 100644 --- a/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml +++ b/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml @@ -1,16 +1,8 @@ - + -
Preface and Acknowledgments -

This publication constitutes the fifth distinct version of the Guidelines for Electronic Text Encoding and Interchange, and the first complete revision since the @@ -23,7 +15,6 @@ $Id$ editors are therefore particularly pleased to acknowledge with gratitude the hard work and dedication put into this project by the Council over the last five years.

-

The Chair of the TEI Board sits on the Technical Council, and the Board appoints the Chair of the Technical Council and one other member of the Council. Other Council members are all elected by the @@ -32,157 +23,26 @@ $Id$ during the production of this edition of the Guidelines are listed below. - - Board Chair - 2004–2005: Julia Flanders (Brown University) - 2006: Matthew Zimmerman (New York University) - 2007–2011: Daniel O'Donnell (University of Lethbridge) - 2011: Martin Mueller (Northwestern University) - 2011–2012: John Unsworth (University of Illinois at Urbana-Champaign / Brandeis University) - 2012–2015: Elena Pierazzo (King's College London / Université Stendhal-Grenoble 3) - 2016–2017: Michelle Dalmau (Indiana University) - 2018–2021: Kathryn Tomasek (Wheaton College) - 2022-2023: Diane K. Jakacki (Bucknell University) - + Board Chair2004–2005: Julia Flanders (Brown University)2006: Matthew Zimmerman (New York University)2007–2011: Daniel O'Donnell (University of Lethbridge)2011: Martin Mueller (Northwestern University)2011–2012: John Unsworth (University of Illinois at Urbana-Champaign / Brandeis University)2012–2015: Elena Pierazzo (King's College London / Université Stendhal-Grenoble 3)2016–2017: Michelle Dalmau (Indiana University)2018–2021: Kathryn Tomasek (Wheaton College)2022-2023: Diane K. Jakacki (Bucknell University) - - Technical Council Chair - 2002–2003: John Unsworth (University of Virginia) - 2003–2007: Christian Wittern (Kyoto University) - 2008–2011: Laurent Romary (Max Planck Digital Library / Inria & Humboldt-Universität zu Berlin) - 2012–2014: James Cummings (University of Oxford) - 2015–2017: Hugh Cayless (Duke University) - 2018–2022: Martina Scholger (University of Graz) - 2023: Elisa Beshero-Bondar (Penn State Erie, The Behrend College) - + Technical Council Chair2002–2003: John Unsworth (University of Virginia)2003–2007: Christian Wittern (Kyoto University)2008–2011: Laurent Romary (Max Planck Digital Library / Inria & Humboldt-Universität zu Berlin)2012–2014: James Cummings (University of Oxford)2015–2017: Hugh Cayless (Duke University)2018–2022: Martina Scholger (University of Graz)2023: Elisa Beshero-Bondar (Penn State Erie, The Behrend College) - - Members of the Technical Council Appointed by the TEI Board - 2001–2009: Sebastian Rahtz (University of Oxford) - 2010–2014: Lou Burnard (University of Oxford / TGE Adonis / Independent Consultant) - + Members of the Technical Council Appointed by the TEI Board2001–2009: Sebastian Rahtz (University of Oxford)2010–2014: Lou Burnard (University of Oxford / TGE Adonis / Independent Consultant) - - Appointed Editors - 2001–2007: Syd Bauman (Brown Univesity) - 2001–2007: Lou Burnard (University of Oxford) - + Appointed Editors2001–2007: Syd Bauman (Brown Univesity)2001–2007: Lou Burnard (University of Oxford) - - Elected Members of the Technical Council - 2011–2012: Piotr Bański (University of Warsaw) - 2010–2013: Brett Barney (University of Nebraska) - 2013–2023: Syd Bauman (Brown University / Northeastern University) - 2021–2025: Helena Bermúdez Sabel (Université de Neuchâtel / JinnTec) - 2016–2024: Elisa Beshero-Bondar (University of Pittsburgh at Greensburg / Penn State Erie, The Behrend College) - 2022: Elli Bleeker (Huygens Institute for the History of the Netherlands) - 2019–2020: Vanessa Bigot Juloux (Ecole Pratique des Hautes Etudes / Paris Sciences et Lettres / Andrews University, Michigan) - 2003–2006, 2017–2018: Alejandro Bia (University of Alicante) - 2004–2007: David Birnbaum (University of Pittsburgh) - 2008–2013: Gabriel Bodard (King's College London) - 2008–2009: Peter Boot (Huygens Institute for Netherlands History) - 2020–2021: Meaghan Brown (Papers of the Bibliographical Society of America) - 2007–2008: Tone Merete Bruvik (University of Bergen) - 2015–2016: Lou Burnard (Independent Consultant) - 2013–2023: Hugh Cayless (New York University / Duke University) - 2014–2015: Fabio Ciotti (University of Rome “Tor Vergata”) - 2007–2009: Arianna Ciula (King's College London / European Science Foundation) - 2005–2019: James Cummings (University of Oxford / Newcastle University) - 2020: Nicholas Cole (Pembroke College Oxford) - 2002–2007, 2010: Matthew Driscoll (University of Copenhagen) - 2002–2004: David Durand (Ingenta plc) - 2002–2004: Tomas Erjavec (Jozef Stefan Institute, Ljubljana) - 2014–2015: Stefanie Gehrke (Biblissima) - 2010–2013: Kevin Hawkins (University of Michigan) - 2010–2015: Martin Holmes (University of Victoria) - 2002: Fotis Jannidis (University of Munich) - 2021–2023: Janelle Jenstad (University of Victoria) - 2006: Amit Kumar (University of Illinois at Urbana-Champaign) - 2020–2021: Jessica H. Lu (University of Maryland) - 2015–2016: Stefan Majewski (Austrian National Library) - 2002: Martin Mueller (Northwestern University) - 2013–2014, 2016–2019: Elli Mylonas (Brown University) - 2010–2011: Julianne Nyhan (University of Trier / University College London) - 2023-2025: Patricia O Connor (Independent Researcher) - 2008–2011: Elena Pierazzo (King's College London) - 2006–2007, 2009–2010: Dot Porter (University of Kentucky / Digital Humanities Observatory / Indiana University) - 2002–2003: Merillee Proffitt (Research Libraries Group) - 2002: Peter Robinson (De Montfort University) - 2009–2014: Sebastian Rahtz (University of Oxford) - 2002: Geoffrey Rockwell (Macmaster University) - 2002–2007: Laurent Romary (Inria / CNRS / Max Planck Digital Library) - 2008–2009, 2012–2015: Paul Schaffner (University of Michigan) - 2016–2024: Martina Scholger (University of Graz) - 2003–2007: Susan Schreibman (University of Maryland) - 2022-2024: Sabine Seifert (University of Potsdam) - 2008–2009: David Sewell (University of Virginia) - 2004–2005: Natasha Smith (University of North Carolina at Chapel Hill) - 2014–2022: Peter Stadler (Carl-Maria-von-Weber-Gesamtausgabe / University of Paderborn) - 2017–2019: Sarah Stanley (Florida State University) - 2023: Joey Takeda (Digital Humanities Innovation Lab, Simon Fraser University) - 2008–2009: Manfred Thaller (University of Cologne) - 2006–2007: Conal Tuohy (Victoria University of Wellington) - 2016–2024: Magdalena Turska (eXist Solutions / University of Oxford) - 2004–2005: Edward Vanhoutte (Royal Academy of Dutch Language and Literature) - 2015–2023: Raffaele Viglianti (University of Maryland) - 2005–2008: John Walsh (Indiana University) - 2012–2013: Rebecca Welzenbach (University of Michigan) - 2002–2005: Perry Willett (Indiana University / University of Michigan) - 2011–2012: Stuart Yeates (New Zealand Electronic Text Centre) - + Elected Members of the Technical Council2011–2012: Piotr Bański (University of Warsaw)2010–2013: Brett Barney (University of Nebraska)2013–2023: Syd Bauman (Brown University / Northeastern University)2021–2025: Helena Bermúdez Sabel (Université de Neuchâtel / JinnTec)2016–2024: Elisa Beshero-Bondar (University of Pittsburgh at Greensburg / Penn State Erie, The Behrend College)2022: Elli Bleeker (Huygens Institute for the History of the Netherlands)2019–2020: Vanessa Bigot Juloux (Ecole Pratique des Hautes Etudes / Paris Sciences et Lettres / Andrews University, Michigan)2003–2006, 2017–2018: Alejandro Bia (University of Alicante) 2004–2007: David Birnbaum (University of Pittsburgh)2008–2013: Gabriel Bodard (King's College London)2008–2009: Peter Boot (Huygens Institute for Netherlands History)2020–2021: Meaghan Brown (Papers of the Bibliographical Society of America)2007–2008: Tone Merete Bruvik (University of Bergen)2015–2016: Lou Burnard (Independent Consultant)2013–2023: Hugh Cayless (New York University / Duke University)2014–2015: Fabio Ciotti (University of Rome “Tor Vergata”)2007–2009: Arianna Ciula (King's College London / European Science Foundation)2005–2019: James Cummings (University of Oxford / Newcastle University)2020: Nicholas Cole (Pembroke College Oxford)2002–2007, 2010: Matthew Driscoll (University of Copenhagen)2002–2004: David Durand (Ingenta plc)2002–2004: Tomas Erjavec (Jozef Stefan Institute, Ljubljana)2014–2015: Stefanie Gehrke (Biblissima)2010–2013: Kevin Hawkins (University of Michigan)2010–2015: Martin Holmes (University of Victoria)2002: Fotis Jannidis (University of Munich) 2021–2023: Janelle Jenstad (University of Victoria)2006: Amit Kumar (University of Illinois at Urbana-Champaign)2020–2021: Jessica H. Lu (University of Maryland)2015–2016: Stefan Majewski (Austrian National Library)2002: Martin Mueller (Northwestern University)2013–2014, 2016–2019: Elli Mylonas (Brown University)2010–2011: Julianne Nyhan (University of Trier / University College London)2023-2025: Patricia O Connor (Independent Researcher)2008–2011: Elena Pierazzo (King's College London)2006–2007, 2009–2010: Dot Porter (University of Kentucky / Digital Humanities Observatory / Indiana University)2002–2003: Merillee Proffitt (Research Libraries Group)2002: Peter Robinson (De Montfort University)2009–2014: Sebastian Rahtz (University of Oxford)2002: Geoffrey Rockwell (Macmaster University)2002–2007: Laurent Romary (Inria / CNRS / Max Planck Digital Library)2008–2009, 2012–2015: Paul Schaffner (University of Michigan)2016–2024: Martina Scholger (University of Graz)2003–2007: Susan Schreibman (University of Maryland)2022-2024: Sabine Seifert (University of Potsdam)2008–2009: David Sewell (University of Virginia)2004–2005: Natasha Smith (University of North Carolina at Chapel Hill)2014–2022: Peter Stadler (Carl-Maria-von-Weber-Gesamtausgabe / University of Paderborn)2017–2019: Sarah Stanley (Florida State University)2023: Joey Takeda (Digital Humanities Innovation Lab, Simon Fraser University)2008–2009: Manfred Thaller (University of Cologne)2006–2007: Conal Tuohy (Victoria University of Wellington)2016–2024: Magdalena Turska (eXist Solutions / University of Oxford)2004–2005: Edward Vanhoutte (Royal Academy of Dutch Language and Literature)2015–2023: Raffaele Viglianti (University of Maryland)2005–2008: John Walsh (Indiana University)2012–2013: Rebecca Welzenbach (University of Michigan)2002–2005: Perry Willett (Indiana University / University of Michigan)2011–2012: Stuart Yeates (New Zealand Electronic Text Centre)

- -

The bulk of the Council's work has been carried out by email and by +

The bulk of the Council's work has been carried out by email and by regular telephone conference. In addition, the Council has held many two-day face-to-face meetings. During production of P5, these meetings were generously hosted by the following institutions: - - King's College, London (2002) - Oxford University Computing Services (2003) - Royal Academy of Dutch Language and Literature, Ghent (2004) - AFNOR: Association française de normalisation, Paris (2005) - Institute for Research in Humanities, Kyoto University (2006) - Berlin-Brandenburgische Akademie der Wissenschaften, Berlin (2007) - National University of Ireland, Galway (2008) - Ecole Normale Supérieure, Lyon (2009) - Royal Irish Academy, Dublin (2010) - Big Ten Center, Chicago (2011) - Inria, Paris (2011) - University of Michigan, Ann Arbor (2012) - University of Oxford (2012) - Brown University (2013) - University of Oxford (2013) - University of Oxford (2014) - Duke University (2014) - University of Michigan, Ann Arbor (2015) - Lyon (2015) - Brown University (2016) - Austrian Academy of Sciences (2016) - Prague (2017) - Victoria (2017) - CCEH, Cologne University (2018) - University of Tokyo (2018) - Folger Shakespeare Library, Washington, D.C. (2019) - ZIM-ACDH, University of Graz (2019) - Virtual meeting (May 2020) - Virtual meeting (October 2020) - Short virtual meeting (January 2021) - Short virtual meeting (May 2021) - Short virtual meeting (October 2021) - Short virtual (April 2022) - Newcastle University (September 2022) - University of Guelph (May 2023) - Paderborn University (September 2023) -

- -

During the production of TEI P5, the Council chartered a number +King's College, London (2002)Oxford University Computing Services (2003)Royal Academy of Dutch Language and Literature, Ghent (2004)AFNOR: Association française de normalisation, Paris (2005)Institute for Research in Humanities, Kyoto University (2006)Berlin-Brandenburgische Akademie der Wissenschaften, Berlin (2007)National University of Ireland, Galway (2008)Ecole Normale Supérieure, Lyon (2009)Royal Irish Academy, Dublin (2010)Big Ten Center, Chicago (2011)Inria, Paris (2011)University of Michigan, Ann Arbor (2012)University of Oxford (2012)Brown University (2013)University of Oxford (2013)University of Oxford (2014)Duke University (2014)University of Michigan, Ann Arbor (2015)Lyon (2015)Brown University (2016)Austrian Academy of Sciences (2016)Prague (2017)Victoria (2017)CCEH, Cologne University (2018)University of Tokyo (2018)Folger Shakespeare Library, Washington, D.C. (2019)ZIM-ACDH, University of Graz (2019)Virtual meeting (May 2020)Virtual meeting (October 2020)Short virtual meeting (January 2021)Short virtual meeting (May 2021)Short virtual meeting (October 2021)Short virtual (April 2022)Newcastle University (September 2022)University of Guelph (May 2023)Paderborn University (September 2023)

+

During the production of TEI P5, the Council chartered a number of smaller workgroups and similar activities, each of which made significant contribution to the intellectual content of the work. Active members of these are listed below: - - - -

Active between July 2001 and January 2005, this group revised and +

Active between July 2001 and January 2005, this group revised and developed the recommendations now forming chapters and . It was chaired by Christian Wittern, and its membership included: Deborah Anderson (Berkeley); Michael Beddow @@ -190,24 +50,14 @@ membership included: Deborah Anderson (Berkeley); Michael Beddow Martin Duerst (W3C/Keio University); Patrick Durusau (Society of Biblical Literature); Tomohiko Morioka (Kyoto University); - and Espen Ore (National Library of Norway).

- - - - -

Active between February 2003 and February 2005, this group developed the + and Espen Ore (National Library of Norway).

Active between February 2003 and February 2005, this group developed the material now forming . It was chaired by Sebastian Rahtz, and its membership included: Alejandro Bia; David G. Durand; Laurent Romary; Norman Walsh (Sun Microsystems); -and Christian Wittern.

- - - - -

Active between February 2002 and January 2006, this +and Christian Wittern.

Active between February 2002 and January 2006, this group reviewed and expanded the material now largely forming part of . It was chaired by David G. Durand, and its membership included: @@ -216,18 +66,10 @@ Chris Caton (University of Oxford); Jessica P. Hekman (Ingenta plc); Nancy M. Ide (Vassar College); and -Fabio Vitali (University of Bologna).

 - - - -

Active between February 2003 and December 2005, this group reviewed +Fabio Vitali (University of Bologna).

Active between February 2003 and December 2005, this group reviewed and finalised the material now forming . It was chaired by Matthew Driscoll and comprised David Birnbaum and Merrilee -Proffitt, in addition to the TEI Editors.

- - - -

Active between January 2006 and May 2007, this group formulated the +Proffitt, in addition to the TEI Editors.

Active between January 2006 and May 2007, this group formulated the new material now forming part of . It was chaired by Matthew Driscoll. and its membership included Gabriel Bodard (King's College London); @@ -241,12 +83,7 @@ Tadeusz Piotrowski (Opole University); Sebastian Rahtz; and Tatiana Timcenko (Vilnius University). -

- - - - -

Active between January 2003 and August 2007, this group reviewed the +

Active between January 2003 and August 2007, this group reviewed the material now presented in and revised it for inclusion in ISO Standard 24610. It was chaired by Kiyong Lee (Korea University), and its active membership included the following: @@ -258,41 +95,27 @@ Patrick Drouin (University of Montréal); Lee Gillam (Surrey University); and Kōiti Hasida (ICOT). -

-

- -

From 2000 to 2008 the TEI had two appointed Editors, Lou Burnard +

+

From 2000 to 2008 the TEI had two appointed Editors, Lou Burnard (University of Oxford) and Syd Bauman (Brown University), who served ex officio on the Council and, as far as possible, on all Council workgroups.

- - -

The Council also oversees an Internationalization and Localization +

The Council also oversees an Internationalization and Localization project, led by Sebastian Rahtz and with funding from the ALLC. This activity, ongoing since October 2005, is engaged in translating key parts of the P5 source into a variety of languages.

- -

Production of the translations currently included in P5 has been +

Production of the translations currently included in P5 has been coordinated by the following: - - Marcus Bingenheimer (Chung-hwa Institute -of Buddhist Studies, Taipei / Temple University) and Weining Hwang (Würzburg University) -Pierre-Yves Duchemin (ENSSIB); Jean-Luc + Marcus Bingenheimer (Chung-hwa Institute +of Buddhist Studies, Taipei / Temple University) and Weining Hwang (Würzburg University)Pierre-Yves Duchemin (ENSSIB); Jean-Luc Benoit (ATILF); Anila Angjeli (BnF); Joëlle Bellec Martini (BnF); Marie-France Claerebout (Aldine); Magali Le Coënt (BIUSJ); Florence Clavaud (EnC); Cécile Pierre (BIUSJ). - - Werner Wegstein (Würzburg University), Franz Fischer (Cologne University), Martina Scholger (University of Graz) and Peter Stadler (Paderborn University) -Marco Venuti (University of Venice) and Letizia Cirillo -(University of Bologna) - Ohya Kazushi (Tsurumi University), Kiyonori Nagasaki (University of Tokyo) and Martin Holmes (University of Victoria) -Beom-mo Kang and Jungha Hong (Korea University) - Carmen Arronis Llopis (University of - Alicante), Alejandro Bia (Miguel Hernández University), Gimena del Rio Riande (Consejo Nacional de Investigaciones Científicas y Técnicas) and Susanna Allés-Torrent (University of Miami) - + Werner Wegstein (Würzburg University), Franz Fischer (Cologne University), Martina Scholger (University of Graz) and Peter Stadler (Paderborn University) Marco Venuti (University of Venice) and Letizia Cirillo +(University of Bologna) Ohya Kazushi (Tsurumi University), Kiyonori Nagasaki (University of Tokyo) and Martin Holmes (University of Victoria)Beom-mo Kang and Jungha Hong (Korea University) Carmen Arronis Llopis (University of + Alicante), Alejandro Bia (Miguel Hernández University), Gimena del Rio Riande (Consejo Nacional de Investigaciones Científicas y Técnicas) and Susanna Allés-Torrent (University of Miami)

- -

Any one who works closely with the TEI Guidelines, whether as +

Any one who works closely with the TEI Guidelines, whether as translator, editor, or reader is constantly reminded of the ambitious scope and exceptionally high editorial standards set by the original project, now approaching twenty years ago. It is appropriate therefore to retain @@ -301,6 +124,5 @@ first appearance in 1990, and to acknowledge with gratitude the contributions made to that evolution by very many individuals and institutions around the world. The original prefatory notes to each major edition of the Guidelines recording these names are therefore -preserved in an appendix to the current edition (see ).

+preserved in an appendix to the current edition (see ).

diff --git a/P5/Source/Guidelines/en/FS-FeatureStructures.xml b/P5/Source/Guidelines/en/FS-FeatureStructures.xml index df7354bad9..d19c42e833 100644 --- a/P5/Source/Guidelines/en/FS-FeatureStructures.xml +++ b/P5/Source/Guidelines/en/FS-FeatureStructures.xml @@ -1,15 +1,10 @@ - + -
Feature Structures - -

A feature structure is a general purpose data +

+ Feature Structures + +

A feature structure is a general purpose data structure which identifies and groups together individual features, each of which associates a name with one or more values. Because of the generality of feature structures, they @@ -27,8 +22,9 @@ declarations.The recommendations of this chapter hav been adopted as ISO Standard 24610-1 Language Resource Management — Feature Structures — Part One: Feature Structure Representation

-
Organization of this Chapter -

This chapter is organized as +

+ Organization of this Chapter +

This chapter is organized as follows. Following this introduction, section introduces the elements fs and f, used to represent feature structures and features respectively, together with the @@ -53,13 +49,13 @@ for the validation of typed feature structures. Formal definitions for all the elements introduced in this chapter are provided in section .

- - -
- -
Elementary Feature Structures and the Binary + + +
+
+ Elementary Feature Structures and the Binary Feature Value -

The fundamental elements used to represent a feature structure +

The fundamental elements used to represent a feature structure analysis are f (for feature), which represents a feature-value pair, and fs (for feature structure), which represents a structure made up of such @@ -76,27 +72,23 @@ a degree of recursion. Values may be under-specified or defaulted in various ways. These possibilities are all described in more detail in this and the following sections.

-

Feature and feature-value representations (including feature +

Feature and feature-value representations (including feature structure representations) may be embedded directly at any point in an XML document, or they may be collected together in special-purpose feature or feature-value libraries. The components of such libraries may then be referenced from other feature or feature-value representations, using the feats or fVal attribute as appropriate.

-

We begin by considering the simple case of a feature structure +

We begin by considering the simple case of a feature structure which contains binary-valued features only. The following three XML elements are needed to represent such a feature structure: - - - - - + The attributes feats and the fVal are not discussed in this section: they provide an alternative way of indicating the content of an element, as further discussed in section .

-

An fs element containing f elements with binary +

An fs element containing f elements with binary values can be straightforwardly used to encode the matrices of feature-value specifications for phonetic segments, such as the following for the English segment [s]. @@ -110,16 +102,8 @@ following for the English segment [s]. | strident + | +--- ---+

-

This representation may be encoded in XML as follows: - - - - - - - - - +

This representation may be encoded in XML as follows: + Note that fs elements may have an optional type attribute to indicate the kind of feature structure in question, whereas f elements must have a name attribute to @@ -131,7 +115,7 @@ Similarly, the fs element may be empty, but the f element must specify its value either directly as content, by means of the fVal attribute, or implicitly by reference to a feature system declaration.

-

The restriction of specific features to specific types of values +

The restriction of specific features to specific types of values (e.g. the restriction of the feature strident to a binary value) requires additional validation, as does any restriction on the features available within a feature structure of a @@ -142,18 +126,19 @@ out at the document level, using special purpose processing, at the schema level using additional validation rules, or at the declarative level, using an additional mechanism such as the feature-system declaration discussed in .

-

Although we have used the term binary for this kind +

Although we have used the term binary for this kind of value, and its representation in XML uses values such as true and false (or, equivalently, 1 and 0), it should be noted that such values are not restricted to propositional assertions. As this example shows, this kind of value is intended for use with any binary-valued feature.

- -
-
Other Atomic Feature Values -

Features may take other kinds of atomic value. In this section, we +

+
+ Other Atomic Feature Values +

Features may take other kinds of atomic value. In this section, we define elements which may be used to represent: symbolic values, numeric values, and string values. The module defined by this chapter allows for the @@ -161,24 +146,17 @@ specification of additional datatypes if necessary, by extending the underlying class model.featureVal.single. If this is done, it is recommended that only the basic W3C datatypes should be used; more complex datatyping should be represented as feature structures. - - - - +

-

The symbol element is used for the value of a feature when +

The symbol element is used for the value of a feature when that feature can have any of a small, finite set of possible values, representable as character strings. For example, the following might be used to represent the claim that the Latin noun form mensas (tables) has accusative case, feminine gender, and -plural number: - - - - +plural number:

-

More formally, this representation shows a structure in which three +

More formally, this representation shows a structure in which three features (case, gender, and number) are used to define morpho-syntactic properties of a word. Each of these features can take one of a small number of @@ -188,60 +166,43 @@ etc.) and it is therefore appropriate to represent the values taken in this instance as symbol elements. Note that, instead of using a symbolic value for grammatical number, one could have named the feature singular or plural and given it -an appropriate binary value, as in the following example: - - - - +an appropriate binary value, as in the following example: Whether one uses a binary or symbolic value in situations like this is largely a matter of taste.

-

The string element is used for the value of a +

The string element is used for the value of a feature when that value is a string drawn from a very large or potentially unbounded set of possible strings of characters, so that it would be impractical or impossible to use the symbol element. The string value is expressed as the content of the string element, rather than as an attribute value. For example, one might encode a street address as follows: - - 3418 East Third Street -

-

The numeric element is used when the value of a feature is a + 3418 East Third Street

+

The numeric element is used when the value of a feature is a numeric value, or a range of such values. For example, one might wish to regard the house number and the street name as different features, using an encoding like the following: - - - East Third Street -

-

If the numeric value to be represented falls within a specific + East Third Street

+

If the numeric value to be represented falls within a specific range (for example an address that spans several numbers), the max attribute may be used to supply an upper limit: - - - East Third Street -

-

It is also possible to specify that the numeric value (or values) + East Third Street

+

It is also possible to specify that the numeric value (or values) represented should (or should not) be truncated. For example, assuming that the daily rainfall in mm is a feature of interest for some address, one might represent this by an encoding like the following: - - - This represents any of the infinite + This represents any of the infinite number of numeric values falling between 0 and 1.3; by contrast - - - represents only two possible values: 0 and 1. + represents only two possible values: 0 and 1.

-

Some communities of practice, notably those with a strong computer-science +

Some communities of practice, notably those with a strong computer-science bias, prefer to dissociate the information on the value of the given feature from the specification of the data type that this value represents. In such cases, feature values can be provided directly as textual content of f, with the assumption that the data type is specified by the schema. The following is an example taken from ISO 24612, presenting the symbolic values for Active Voice and Simple Present Tense in the untyped -form:active -SimPre

-

As noted above, additional processing is necessary to ensure that +form:activeSimPre

+

As noted above, additional processing is necessary to ensure that appropriate values are supplied for particular features, for example to ensure that the feature singular is not given a value such as symbol value="feminine"/. There are two @@ -263,10 +224,10 @@ individual case, gender and number values in the preceding illustration. We discuss the use of such libraries and their representation in XML further in section below.

-

However, the most general method of attempting to ensure that only legal +

However, the most general method of attempting to ensure that only legal combinations of feature names and values are used is to provide a feature-system declaration discussed in .

-

Whether at the level of feature-system declarations, feature- and +

Whether at the level of feature-system declarations, feature- and feature-value libraries, or individual features, it is possible to align both feature names and their values with standardized external data category repositories. See @@ -276,31 +237,19 @@ standardized external taxonomies. In the following example, both the feature part_of_speech and its value NN (standing for common noun) are aligned with the respective definitions provided by the CLARIN Concept Registry (CCR). - - - - - - - -

-

Since the above representation takes up a lot of space and quickly becomes redundant and +

+

Since the above representation takes up a lot of space and quickly becomes redundant and error-prone, it is possible to delegate the task of aligning with external repositories to elements such as fLib, fvLib, fDecl, or fsDecl to reduce the feature representation at hand and to increase its readability at the same time, as shown in the example below. - - - - - - -

-

The value common_noun should best be listed (as an xml:id) either in a +

+

The value common_noun should best be listed (as an xml:id) either in a library of feature values (fvLib, see the following section) or in a taxonomy element.

-
-
Feature Libraries and Feature-Value Libraries -

As the examples in the preceding section suggest, the direct +

+
+ Feature Libraries and Feature-Value Libraries +

As the examples in the preceding section suggest, the direct encoding of feature structures can be verbose. Moreover, it is often the case that particular feature-value combinations, or feature structures composed of them, are re-used in different analyses. To reduce @@ -315,81 +264,47 @@ values of whatever type can be collected together in fvLib elements value a feature structure or other value which is predefined in this way, the fVal attribute may be used to point to it, as discussed in the next section. The following elements are used for representing feature libraries and feature-value libraries: - - - +

-

For example, suppose a feature library for phonological feature +

For example, suppose a feature library for phonological feature specifications is set up as follows. - - - - - - - - - - - - - - - - - +

-

Then the feature structures that represent the analysis of the +

Then the feature structures that represent the analysis of the phonological segments (phonemes) /t/, /d/, /s/, and /z/ may be defined as follows. - - - - +

-

The preceding are but four of the 128 logically possible fully +

The preceding are but four of the 128 logically possible fully specified phonological segments using the seven binary features listed in the feature library. Presumably not all combinations of features correspond to phonological segments (there are no strident vowels, for example). The legal combinations, however, can be collected together, each one represented as an identifiable fs element within a feature-value library, as in the following example: - - - - - - - - +

-

Once defined, these feature structure values can also be reused. +

Once defined, these feature structure values can also be reused. Other f elements may invoke them by reference, using the fVal attribute; for example, one might use them in a -feature value pair such as: rather than expanding the hierarchy of the +feature value pair such as: rather than expanding the hierarchy of the component phonological features explicitly.

-

The feature structure that concludes section above, identifying the +

The feature structure that concludes section above, identifying the value of some part of speech to be a common noun, may be used in tandem with a feature-value library, which offers a way to encode a grammatical tagset, in this case containing labels for parts of speech: - - - - - - - + Such a feature-value library combines the standard short symbolic label for a part of speech (e.g., NN) with a mnemonic identifier that can be referenced by means of fVal, and with a persistent identifier, maintained in a public reference taxonomy repository together with the basic definition of the given concept.

-

Feature structures stored in the way presented in this section may also be associated with +

Feature structures stored in the way presented in this section may also be associated with the text which they are intended to annotate, either by a link from the text (for example, using the TEI global ana attribute), or by means of stand-off annotation techniques (for example, using the TEI link element): see further section below.

-

Note that when features or feature structures are linked to in this +

Note that when features or feature structures are linked to in this way, the result is effectively a copy of the item linked to into the place from which it is linked. This form of linking should be distinguished from the phenomenon of structure-sharing, where it is desired @@ -397,9 +312,10 @@ to indicate that some part of an annotation structure appears simultaneously in two or more places within the structure. This kind of annotation should be represented using the vLabel element, as discussed in below.

-
-
Feature Structures as Complex Feature Values -

Features may have complex values as well as atomic ones; the +

+
+ Feature Structures as Complex Feature Values +

Features may have complex values as well as atomic ones; the simplest such complex value is represented by supplying an fs element as the content of an f element, or (equivalently) by supplying the identifier of an fs element as the value for @@ -409,7 +325,7 @@ mechanism. For example, an fs element may contain or point to an f element, which may contain or point to an fs element, which may contain or point to an f element, and so on.

-

To illustrate the use of complex values, consider the following +

To illustrate the use of complex values, consider the following simple model of a word, as a structure combining surface form information, a syntactic category, and semantic information. Each word analysis is represented as a fs type='word' element, @@ -418,37 +334,15 @@ containing three features named surface, has an atomic string value, but the other two have complex values, represented as nested feature structures of types category and act respectively: - - love - - - - - - - - - - - -

-

This analysis does not tell us much about the meaning of the +love

+

This analysis does not tell us much about the meaning of the symbols verb or transitive. It might be preferable to replace these atomic feature values by feature structures. Suppose therefore that we maintain a feature-value library for each of the major syntactic categories (N, V, ADJ, PREP): - - - - - - - - - - +

-

This library allows us to use shortcut codes (N, +

This library allows us to use shortcut codes (N, V, etc.) to reference a complete definition for the corresponding feature structure. Each definition may be explicitly contained within the fs element, as a number of f @@ -461,82 +355,41 @@ attribute, as in these examples: <!-- ... -->

-

This ability to re-use feature definitions within multiple feature +

This ability to re-use feature definitions within multiple feature structure definitions is an essential simplification in any realistic example. In this case, we assume the existence of a feature library containing specifications for the basic feature categories like the following: - - - - - - - - +

-

With such libraries in place, and assuming the availability of +

With such libraries in place, and assuming the availability of similarly predefined feature structures for transitivity and semantics, the preceding example could be considerably simplified: - -love - - - - - - - - - - - - -

-

Although in principle the fVal attribute could point to +love

+

Although in principle the fVal attribute could point to any kind of feature value, its use is not recommended for simple atomic values.

-
-
Re-entrant Feature Structures -

Sometimes the same feature value is required at multiple places +

+
+ Re-entrant Feature Structures +

Sometimes the same feature value is required at multiple places within a feature structure, in particular where the value is only partially specified at one or more places. The vLabel element is provided as a means of labelling each such re-entrancy point: - - - +

-

For example, suppose one wishes to represent noun-verb agreement as +

For example, suppose one wishes to represent noun-verb agreement as a single feature structure. Within the representation, the feature indicating (say) number appears more than once. To represent the fact that each occurrence is another appearance of the same feature (rather than a copy) one could use an encoding like the following: - - - - - - - - - - - - - - - - - - - - +

-

In the above encoding, the features named vb-num and +

In the above encoding, the features named vb-num and nm-num exhibit structure sharing. Their values, given as vLabel elements, are understood to be references to the same point in the feature structure, which is labelled by their name attribute.

-

The scope of the names used to label re-entrancy points is that of the +

The scope of the names used to label re-entrancy points is that of the outermost fs element in which they appear. When a feature structure is imported from a feature value library, or referenced from elsewhere (for example by using the fVal attribute) the @@ -547,17 +400,16 @@ some other feature structure were to reference the fs element given in the example above, for example in this way: then the labelled points in the example would be interpreted as if they had the name NVAL1.

-
-
Collections as Complex Feature Values -

Complex feature values need not always be represented as feature +

+
+ Collections as Complex Feature Values +

Complex feature values need not always be represented as feature structures. Multiple values may also be organized as sets, bags or multisets, or lists of atomic values of any type. The vColl element is provided to represent such cases: - - - +

-

A feature whose value is regarded as a set, bag, or list may have +

A feature whose value is regarded as a set, bag, or list may have any positive number of values as its content, or none at all, (thus allowing for representation of the empty set, bag, or list). The items in a list are ordered, and need not be distinct. The items @@ -568,39 +420,20 @@ not matter for the former, but does matter for the latter, while sets are distinguished from bags and lists in that repetitions of values do not count for the former but do count for the latter.

-

If no value is specified for the org attribute, the +

If no value is specified for the org attribute, the assumption is that the vColl defines a list of values. If the vColl element is empty, the assumption is that it represents the null list, set, or bag.

-

To illustrate the use of the org attribute, suppose that +

To illustrate the use of the org attribute, suppose that a feature structure analysis is used to represent a genealogical tree, with the information about each individual treated as a single feature structure, like this: - - - - Daniel - Edouard - - - - - - - - - - - - - - - +DanielEdouard

-

In this example, the vColl element is first used to supply +

In this example, the vColl element is first used to supply a list of name feature values, which together constitute the forenames feature. Other features are defined by reference to values which we assume are held in some @@ -610,7 +443,7 @@ persons's siblings should be regarded as constituting a set rather than a list. Each sibling is represented by a feature structure: in this example, each feature structure is a copy of one specified in the feature value library.

-

If a specific feature contains only a single feature structure as +

If a specific feature contains only a single feature structure as its value, the component features of which are organized as a set, bag, or list, it may be more convenient to represent the value as a vColl rather than as an fs. For example, consider the @@ -619,90 +452,53 @@ following encoding of the English verb form agreement feature whose value is a feature structure which contains person and number features with symbolic values. - - - - - - - - - - +

-

If the names of the features contained within +

If the names of the features contained within the agreement feature structure are of no particular significance, the following simpler representation may be used: - - - - - - - - - - +

-

The vColl element is also useful in cases where an analysis +

The vColl element is also useful in cases where an analysis has several components. In the following example, the French word auxquels has a two-part analysis, represented as a list of two values. The first specifies that the word contains a preposition; the second that it contains a masculine plural relative pronoun: - - - - - - - - - - - - - - - - - - +

-

The set, bag, or list which has no members is known as the null (or +

The set, bag, or list which has no members is known as the null (or empty) set, bag, or list. A vColl element with no content and with no value for its feats attribute is interpreted as referring to the null set, bag, or list, depending on the value of its org attribute.

-

If, for example, the individual described by the +

If, for example, the individual described by the feature structure with identifier p027 (above) had no siblings, we might specify the siblings feature as follows.

-

A vColl element may also collect together one or more other +

A vColl element may also collect together one or more other vColl elements, if, for example one of the members of a set is itself a set, or if two lists are concatenated together. Note that such collections pay no attention to the contents of the nested vColl elements: if it is desired to produce the union of two sets, the vMerge element discussed below should be used to make a new collection from the two sets.

-
-
Feature Value Expressions -

It is sometimes desirable to express the value of a feature as the +

+
+ Feature Value Expressions +

It is sometimes desirable to express the value of a feature as the result of an operation over some other value (for example, as not green, or as male or female, or as the concatenation of two collections). Three special purpose elements are provided to represent disjunctive alternation, negation, and collection of values: - - - - - +

-
Alternation -

The vAlt element can be used wherever a feature value can +

+ Alternation +

The vAlt element can be used wherever a feature value can appear. It contains two or more feature values, any one of which is to be understood as the value required. Suppose, for example, that we are using a feature system to describe residential property, using such @@ -712,42 +508,29 @@ a house has two or three bathrooms. As we have already shown, one simple way to represent this would be with a numeric maximum:

-

A more general way would be to represent the +

A more general way would be to represent the alternation explicitly, in this way: - +

-

The vAlt element represents alternation over feature +

The vAlt element represents alternation over feature values, not feature-value pairs. If therefore the uncertainty relates to two or more feature value specifications, each must be represented as a feature structure, since a feature structure can always appear where a value is required. For example, suppose that it is uncertain as to whether the house being described has two bathrooms or two bedrooms, a structure like the following may be used: - - - - - - +

-

Note that alternation is always regarded as exclusive: +

Note that alternation is always regarded as exclusive: in the case above, the implication is that having two bathrooms excludes the possibility of having two bedrooms and vice versa. If inclusive alternation is required, a vColl element may be included in the alternation as follows: - - - - - - - - - + This analysis indicates that the property may have two bathrooms, two bedrooms, or both two bathrooms and two bedrooms.

-

As the previous example shows, the vAlt element can also +

As the previous example shows, the vAlt element can also be used to indicate alternations among values of features organized as sets, bags or lists. Suppose we use a feature selling.points to describe items that are mentioned to @@ -756,54 +539,31 @@ good view. Now suppose for a particular listing, the selling points include an alarm system and a good view, and either a pool or a jacuzzi (but not both). This situation could be represented, using the vAlt element, as follows. - - - - alarm system - good view - - pool - jacuzzi - - - - +alarm systemgood viewpooljacuzzi

-

Now suppose the situation is like the preceding except that one is +

Now suppose the situation is like the preceding except that one is also uncertain whether the property has an alarm system or a good view. This can be represented as follows. - - - - - alarm system - good view - - - pool - jacuzzi - - - - +alarm systemgood viewpooljacuzzi

-

If a large number of ambiguities or uncertainties need to be +

If a large number of ambiguities or uncertainties need to be represented, involving a relatively small number of features and values, it is recommended that a stand-off technique, for example using the general-purpose alt element discussed in section be used, rather than the special-purpose vAlt element.

-
-
Negation -

The vNot element can be used wherever a feature value can +

+
+ Negation +

The vNot element can be used wherever a feature value can appear. It contains any feature value and returns the complement of its contents. For example, the feature number.of.bathrooms in the following example has any whole numeric value other than 2: - +

-

Strictly speaking, the effect of the vNot element is to +

Strictly speaking, the effect of the vNot element is to provide the complement of the feature values it contains, rather than their negation. If a feature system declaration is available which defines the possible values for the associated feature, then it is possible to say @@ -812,23 +572,16 @@ available values for the feature case are declared to be nominative, genitive, dative, or accusative, whether in a TEI feature system declaration or by some other means. Then the following two specifications are equivalent: - (i) - -(ii) - - - - - - + (i) +(ii)

-

If however no such system declaration is available, all that one +

If however no such system declaration is available, all that one can say about a feature specified via negation is that its value is something other than the negated value.

-

Negation is always applied to a feature value, rather than to a +

Negation is always applied to a feature value, rather than to a feature-value pair. The negation of an atomic value is the set of all other values which are possible for the feature.

-

Any kind of value can be negated, including collections +

Any kind of value can be negated, including collections (represented by a vColl elements) or feature structures (represented by fs elements). The negation of any complex value is understood to be the set of values which @@ -843,51 +596,34 @@ the same as that of the original value, for example that a negated set is understood to mean the set which is a complement of the set, but such a requirement cannot be enforced in the absence of a constraint mechanism.

-
-
Collection of Values -

The vMerge element can be used wherever a feature value can +

+
+ Collection of Values +

The vMerge element can be used wherever a feature value can appear. It contains two or more feature values, all of which are to be collected together. The organization of the resulting collection is specified by the value of the org attribute, which need not necessarily be the same as that of its constituent values if these are collections. For example, one can change a list to a set, or vice versa.

-

As an example, suppose that we wish to represent the range of +

As an example, suppose that we wish to represent the range of possible values for a feature genders used to describe some language. It would be natural to represent the possible values as a set, using the vColl element as in the following example: - - - - - - - - - +

-

Suppose however that we discover for some language it is necessary +

Suppose however that we discover for some language it is necessary to add a new possible value, and to treat the value of the feature as a list rather than as a set. The vMerge element can be used to achieve this: - - - - - - - - - - - - -

- -
-
-
Default Values -

The value of a feature may be underspecified in a number of + +

+ +
+
+
+ Default Values +

The value of a feature may be underspecified in a number of different ways. It may be null, unknown, or uncertain with respect to a range of known possibilities, as well as being defined as a negation or an alternation. As previously noted, the specification of the range @@ -900,178 +636,84 @@ and that the default value is neuter. With such definitions available to us, it becomes possible to say that some feature takes the default value, or some unspecified value from the list. The following special element is provided for this purpose: - - - -

-

The value of an empty f element which also lacks an fVal + +

+

The value of an empty f element which also lacks an fVal attribute is understood to be the most general case, i.e. any of the available values. Thus, assuming the feature system defined above, the following two representations are equivalent. - - - - - - - - +

-

If, however, the value is explicitly stated to be the default one, +

If, however, the value is explicitly stated to be the default one, using the default element, then the following two representations are equivalent: - - + +

-

Similarly, if the value is stated to be the negation of the +

Similarly, if the value is stated to be the negation of the default, then the following two representations are equivalent: - - - - - + +

-
- - -
Linking Text and Analysis -

Text elements can be linked with feature structures using any of + +

+ Linking Text and Analysis +

Text elements can be linked with feature structures using any of the linking methods discussed elsewhere in these Guidelines (see for example sections and ). In the simplest case, the ana attribute may be used to point from any element to an annotation of it, as in the following example: - - The - closest - he - came - to - exercise - was - to - open - one - eye - - every - so - often - - , - if - someone - entered - the - room - - +Theclosesthecametoexercisewastoopenoneeyeeverysooften,ifsomeoneenteredtheroom

-

The values specified for the ana attribute reference +

The values specified for the ana attribute reference components of a feature-structure library, which represents all of the grammatical structures used by this encoding scheme. (For illustrative purposes, we cite here only the structures needed for the first six words of the sample sentence): - - - - - - - - - - + The components of each feature structure in the library are referenced in much the same way, using the feats attribute to identify one or more f elements in the following feature library (again, only a few of the available features are quoted here): - - - - - - - - - - - - - - - - - +

-

Alternatively, a stand-off technique may be used, as in the following +

Alternatively, a stand-off technique may be used, as in the following example, where a linkGrp element is used to link selected characters in the text Caesar seized control with their phonological representations. - - - Caesar - seized - control. - - - - - - - - - - - - +Caesarseizedcontrol. +

-

As this example shows, a stand-off solution requires that every +

As this example shows, a stand-off solution requires that every component to be linked to must be addressable in some way, by means of an XPointer. To handle the POS tagging example above, for example, each annotated element might be given an identifier of some sort, as follows: - - The - closest - he - came - to - exercise - +Theclosesthecametoexercise It would then be possible to link each word to its intended annotation in the feature library quoted above, as follows: - - - - - - - - +

-
- - -
-Feature System Declaration -

The Feature System Declaration (FSD) is intended for use in conjunction with a +

+
+ Feature System Declaration +

The Feature System Declaration (FSD) is intended for use in conjunction with a TEI-conforming text that makes use of fs (that is, feature structure) elements. - The FSD serves three purposes: - the encoder can list all of the feature names and feature values and give a prose - description as to what each represents. - the encoder can define what it means to be a well-formed feature structure, and + The FSD serves three purposes: the encoder can list all of the feature names and feature values and give a prose + description as to what each represents.the encoder can define what it means to be a well-formed feature structure, and define constraints which may be used to determine whether a particular feature structure is valid relative to a given theory stated in typed feature logic. These may involve constraints on the range of a feature value, constraints on what features are valid within certain types of feature structures, or - constraints that prevent the co-occurrence of certain feature-value pairs. - the encoder can define the intended interpretation of underspecified feature + constraints that prevent the co-occurrence of certain feature-value pairs.the encoder can define the intended interpretation of underspecified feature structures. This involves defining default values (whether literal or computed) for missing features.

-

The scheme described in this chapter may be used to document any +

The scheme described in this chapter may be used to document any feature structure system, but is primarily intended for use with the feature structure representation defined by the ISO 24610-1:2006 standard, which corresponds with the recommendations presented in @@ -1079,15 +721,13 @@ these Guidelines, . This chapter relies upon, but does not reproduce, formal definitions and descriptions presented more thoroughly in the ISO standard, which should be consulted in case of ambiguity or uncertainty.

- -

The FSD serves an important function in documenting precisely what +

The FSD serves an important function in documenting precisely what the encoder intended by the system of feature structure markup used in an XML-encoded text. The FSD is also an important resource which standardizes the rules of inference used by software to validate the feature structure markup in a text, and to infer the full interpretation of underspecified feature structures.

- -

The reader should be aware the terminology used in this document +

The reader should be aware the terminology used in this document does not always closely follow conventional practice in formal logic, and may also diverge from practice in some linguistic applications of typed feature structures. In particular, the term @@ -1109,26 +749,24 @@ distinct from and in addition to the well-formedness that pertains at the level of this encoding standard. No appeal to any notion from formal semantics should be inferred.

- -

We begin by describing how an encoded text is associated with one +

We begin by describing how an encoded text is associated with one or more feature system declarations. The second, third, and fourth sections describe the overall structure of a feature system declaration and give details of how to encode its components. The final section offers a full example; fuller discussion of the reasoning behind FSDs and another complete example are provided in .

-
-Linking a TEI Text to Feature System Declarations -

In order for application software to use feature system +

+ Linking a TEI Text to Feature System Declarations +

In order for application software to use feature system declarations to aid in the automatic interpretation of encoded texts, or even for human readers to find the appropriate declarations which document the feature system used in markup, there must be a formal link from the encoded texts to the declarations. However, the schema which declares the syntax of the Feature System itself should be kept distinct from the feature structure schema, which is an -application of that system.

- -

A document containing typed feature structures may simply include a +application of that system.

+

A document containing typed feature structures may simply include a feature system declaration documenting those feature structures. A more usual scenario, however, is that the same feature system declaration (or parts of it) will be shared by many documents. In @@ -1136,129 +774,65 @@ either case, an fsDecl element for each distinct type of feature structure used must be provided and associated with the type, which is the value used within each feature structure for its type attribute.

- -

When the module defined in this chapter is included in an XML +

When the module defined in this chapter is included in an XML schema, the following elements become available via the model.fsdDeclPart class: - - - - + The fsdDecl element serves as a wrapper for declaring feature systems and may be supplied either within the header of a standard TEI document, or as a standalone document in its own right. It contains one or more fsdLink or fsDecl elements and may hold several fLib or fvLib as well.

- - - -

For example, suppose that a document doc.xml +

For example, suppose that a document doc.xml contains feature structures of two types: gpsg and lex. We might simply embed an fsDecl element for each within the header attached to the document as follows: - - - - - - - - - - - - - - - - - - - - - - - - - +

-

In this case there is an implicit link between the fs +

In this case there is an implicit link between the fs element and the corresponding fsDecl element because they share the same value for their type attribute and appear within the same document. This is a short cut for the more general case which requires a more explicit link provided by means of the fsdLink element, as demonstrated below.

- -

Now suppose that we wish to create a second document which includes +

Now suppose that we wish to create a second document which includes feature structures of the same type. Rather than duplicate the corresponding declarations, we will need to provide a means of pointing to them from this second document. The easiestWays of pointing to components of a TEI document without using an XML identifier are discussed in way of accomplishing this is to add an XML identifier to each fsDecl element in example.xml: - - - - - - - - - - + (Although in this case the XML identifier is simply an uppercase version of the type name, there is no necessary connection between the two names. The only requirement is that the XML identifier conform to the standards required for identifiers, and that it be unique within the document containing it.)

-

In the fsdDecl for the second document, we can now include +

In the fsdDecl for the second document, we can now include pointers to the fsDecl elements in the first: - - - - - - - - - - - - - - - - - - - - - + Note that in doc2.xml there is no requirement for the local name for a given type of feature structures to be the same as that used by example.xml. We assume in this encoding that the type called lexx in doc2.xml is declared as having identical constraints and other properties to those declared for the type called lex in example.xml.

- -

An fsdDecl may be given, as above, within the encoding +

An fsdDecl may be given, as above, within the encoding description of the teiHeader element of a TEI document containing typed feature structures. Alternatively, it may appear independently of any feature structures, as a document in its own right with its own teiHeader. These options are both possible -because the element is a member of both the model.encodingDescPart class and the model.resource class.

- -

The current recommendations provide no way of enforcing uniqueness +because the element is a member of both the model.encodingDescPart class and the model.resource class.

+

The current recommendations provide no way of enforcing uniqueness of the type values among fsdDecl elements, nor of requiring that every type value specified on an fs element be also declared on an fsdDecl element. Encoders @@ -1266,21 +840,18 @@ requiring such constraints (which might have some obvious utility in assisting the consistency and accuracy of tagging) are recommended to develop tools to enforce them, using such mechanisms as Schematron assertions.

- -
-
The Overall Structure of a Feature System Declaration -

A feature system declaration contains one or more feature +

+
+ The Overall Structure of a Feature System Declaration +

A feature system declaration contains one or more feature structure declarations, each of which has up to three parts: an optional description (which gives a prose comment on what that type of feature structure encodes), an obligatory set of feature declarations (which specify range constraints and default values for the features in that type of structure), and optional feature structure constraints (which specify co-occurrence restrictions on feature values). - - - -

-

Feature declarations and feature structure constraints are +

+

Feature declarations and feature structure constraints are described in the next two sections. Note that the specification of similar fsDecl elements can be simplified by devising an inheritance hierarchy for the feature structure types. Each @@ -1296,24 +867,10 @@ three features. This is because fsDecl type="Derived" inherits the two feature declarations from fsDecl type="Basic" when it specifies a base type of Basic.

-

The following sample shows the overall structure of a complete +

The following sample shows the overall structure of a complete feature structure declaration: - - - Describes what this type of fs represents - - - - - - - - - - -

- -

The attribute baseTypes gives the name of one or more + Describes what this type of fs represents

+

The attribute baseTypes gives the name of one or more types from which this type inherits feature specifications and constraints; if this type includes a feature specification with the same name as one inherited from any of the types specified by this @@ -1323,84 +880,30 @@ unification. Similarly, the set of constraints applicable is derived by conjoining those specified explicitly within this element with those implied by the baseTypes attribute. When no base type is specified, no feature specification or constraint is inherited.

-

Although the present standard does provide for default feature values, +

Although the present standard does provide for default feature values, feature inheritance is defined to be monotonic. -

+

+

The process of combining constraints may result in a contradiction, for example if two specifications for the same feature specify disjoint ranges of values, and at least one such specification is mandatory. In such a case, there is no valid feature structure of the type being defined.

-

+

Every type specified by baseTypes must be a single word which is a legal XML name; for example, they cannot include whitespace or begin with digits. Multiple base types are separated with spaces, e.g. fsDecl type="Sub" baseTypes="Super1 Super2".

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
Feature Declarations -

Each feature is declared in an fDecl element whose + + + + + + +

+
+ Feature Declarations +

Each feature is declared in an fDecl element whose name attribute identifies the feature being declared; this matches the name attribute of the f elements it declares. @@ -1423,47 +926,35 @@ specification (which declares what default value should be supplied when the named feature does not appear in an fs). If, in a feature structure, a feature: - is not optional (i.e., is obligatory), - has no value provided, or the value default is -provided (see ISO 24610-1, Subclause 5.10, Default Values, and - either has no default specified, or has conditional defaults, -none of the conditions on which is met, - + is not optional (i.e., is obligatory), has no value provided, or the value default is +provided (see ISO 24610-1, Subclause 5.10, Default Values, and either has no default specified, or has conditional defaults, +none of the conditions on which is met, then the value of this feature in the feature structure's most general valid extension is the most general value provided in its vRange, in the case of a unit organization, or the singleton set, bag, or list containing that element, in the case of a complex organization. If the feature: - is optional, - has no value provided, or the value default is -provided, and - either has a default specified, or has conditional defaults, -one of the conditions on which is met, - + is optional, has no value provided, or the value default is +provided, and either has a default specified, or has conditional defaults, +one of the conditions on which is met, then this feature does have a value in the feature structure's most general valid extension when it exists, namely the default value that pertains.

-

It is possible that a feature structure will not have a valid +

It is possible that a feature structure will not have a valid extension because the default value that pertains to a feature is not consistent with that feature's declared range. Additional tools are required for the enforcement of such criteria.

- -

The following elements are used in feature system declarations: - - - - - - -

-

The logic for validating feature values and for matching the +

The following elements are used in feature system declarations: +

+

The logic for validating feature values and for matching the conditions for supplying default values is based on the operation of subsumption. Subsumption is a standard operation in feature-structure-based formalisms. Informally, a feature structure @@ -1475,8 +966,7 @@ re-entrancies (see ) that FS does. ( and ) A more formal definition is provided in ISO 24610-1:2006 .

- - -

Following the spirit of the informal definition above, we can extend +

Following the spirit of the informal definition above, we can extend subsumption in a straightforward way to cover alternation, negation, special primitive values, and the use of attributes in the markup. For instance, a vAlt containing the value v subsumes v. The negation @@ -1503,8 +993,8 @@ subsumes any value that is not. --> The value fs type="X"/ subsumes any feature structure of type X, even if it is not valid.

- -

As an example of feature declarations, consider the following extract + +

As an example of feature declarations, consider the following extract from Gazdar et al.'s Generalized Phrase Structure Grammar. In the appendix to their book, they propose a feature system for English of which this is just a sampling: @@ -1518,24 +1008,17 @@ PFORM {to, by, for, ...} FSD 1: [-INV] FSD 2: ~[CONJ] FSD 9: [INF, +SUBJ] --> [COMP for]

-

The INV feature, which encodes whether or not a sentence is inverted, +

The INV feature, which encodes whether or not a sentence is inverted, allows only the values plus (+) and minus (-). If the feature is not specified, then the default rule (FSD 1 above) says that a value of minus is always assumed. The feature declaration for this feature would be encoded as follows: - - inverted sentence - - - - - -

-

The value range is specified as an alternation (more precisely, an +inverted sentence

+

The value range is specified as an alternation (more precisely, an exclusive disjunction), which can be represented by the binary feature value. That is, the value must be either true or false, but cannot be both or neither.

-

The CONJ feature indicates the surface form of the conjunction used +

The CONJ feature indicates the surface form of the conjunction used in a construction. The ~ in the default rule (see FSD 2 above) represents negation. This means that by default the feature is not applicable, in other words, no conjunction is taking place. Note that @@ -1544,29 +1027,13 @@ the value range. In their analysis, NIL means that the phenomenon of conjunction is taking place but there is no explicit conjunction in the surface form of the sentence. The feature declaration for this feature would be encoded as follows: - - surface form of the conjunction - - - - - - - - - - - - - - +surface form of the conjunction Note that the vDefault is not strictly necessary in this case, since the binary value of false only serves to convey the information that the feature has no other legitimate value.

- -

The COMP feature indicates the surface form of the complementizer +

The COMP feature indicates the surface form of the complementizer used in a construction. In value range, it is analogous to CONJ. However, its default rule (see FSD 9 above) is conditional. It says that if the verb form is infinitival (the VFORM feature is not @@ -1578,23 +1045,8 @@ to go, a for complement must be used; that is, It is necessary for John to go. The feature declaration for this feature would be encoded as follows: - - surface form of the complementizer - - - - - - - - - - - - - -

-

The AGR feature stores the features relevant to subject-verb +surface form of the complementizer

+

The AGR feature stores the features relevant to subject-verb agreement. Gazdar et al. specify the range of this feature as CAT. This means that the value is a category, which is their term for a feature structure. This is actually too weak a @@ -1603,144 +1055,48 @@ a feature structure for agreement (which is defined in the complete example at the end of the chapter to contain the features of person and number). The following feature declaration encodes this constraint on the value range: - - agreement for person and number - - +agreement for person and number That is, the value must be a feature structure of type Agreement. The complete example at the end of this chapter includes the fsDecl type="Agreement" which includes fDecl name="PERS" and fDecl name="NUM".

-

The PFORM feature indicates the surface form of the preposition used +

The PFORM feature indicates the surface form of the preposition used in a construction. Since PFORM is specified above as an open set, string is used in the range specification below rather than symbol. - - word form of a preposition - - +word form of a preposition This example makes use of a negated value: <vNot><string/></vNot> subsumes any string that is not the empty string.

-

For the reduced feature structure that concludes section above and +

For the reduced feature structure that concludes section above and identifies the value of some part of speech to be a common noun, it is possible to align the concept of part of speech with its definition and persistent identifier using the targetDatcat attribute, which connects the modeled XML object with the appropriate locus in a reference taxonomy, as shown below: - - -part of speech (morphosyntactic category) - - - - - - - - - +part of speech (morphosyntactic category) The above example declares the feature POS as instantiating the corresponding concept defined in a reference taxonomy or ontology, and defines the range of values of the feature at hand by listing the appropriate alternatives, together with their external persistent identifiers.

-

Note that +

Note that the class model.featureVal includes all possible single feature values, including feature structures, alternations (vAlt) and complex collections (vColl).

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
Feature Structure Constraints -

Ensuring the validity of feature structures may require much more + + + + + + + + +

+
+ Feature Structure Constraints +

Ensuring the validity of feature structures may require much more than simply specifying the range of allowed values for each feature. There may be constraints on the co-occurrence of one feature value with the value of another feature in the same feature structure or in an embedded feature structure.

-

Such constraints on valid feature structures are expressed as a +

Such constraints on valid feature structures are expressed as a series of conditional and biconditional tests in the fsConstraints part of an fsDecl. A particular feature structure is valid only if it meets all the constraints. The @@ -1766,265 +1122,73 @@ feature structure is simply not known; in this case, the constraint must be persistently monitored as the feature structure becomes more informative until either its truth value is determined or computation fails for some other reason.

-

The +

The following elements make up the fsConstraints part of an FSD:

-

For an example of feature structure constraints, consider the +

For an example of feature structure constraints, consider the following feature co-occurrence restrictions extracted from the feature system for English proposed by Gazdar, et al. (1985:246–247): [FCR 1: [+INV] → [+AUX, FIN] FCR 7: [BAR 0] ≡ [N] & [V] & [SUBCAT] FCR 8: [BAR 1] → ~[SUBCAT]]

-

The first constraint says that if a construction is inverted, it must +

The first constraint says that if a construction is inverted, it must also have an auxiliary and a finite verb form. That is, - - - - - - -

-

The second constraint says that if a construction has a BAR value of +

+

The second constraint says that if a construction has a BAR value of zero (i.e., it is a sentence), then it must have a value for the features N, V, and SUBCAT. By the same token, because it is a biconditional, if it has values for N, V, and SUBCAT, it must have BAR='0'. That is, - - - - - - - - -

- -

The final constraint says that if a construction has a BAR value of 1 +

+ +

The final constraint says that if a construction has a BAR value of 1 (i.e., it is a phrase), then the SUBCAT feature should be absent (~). This is not biconditional, since there are other instances under which the SUBCAT feature is inappropriate. That is, - - - - -

- -

+

+ +

Note that cond and bicond use the empty tags then and iff, respectively, to separate the antecedent and consequent. These are primarily for the sake of enhancing human readability.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
A Complete Example -

To summarize this chapter, the complete FSD for the example that has + + + + + + +

+
+ A Complete Example +

To summarize this chapter, the complete FSD for the example that has run through the chapter is reproduced below: - - - - - A sample FSD based on an extract from Gazdar - et al.'s GPSG feature system for English - - encoded by - Gary F. Simons - - - -

This sample was first encoded by Gary F. Simons (Summer +A sample FSD based on an extract from Gazdar + et al.'s GPSG feature system for Englishencoded byGary F. Simons

This sample was first encoded by Gary F. Simons (Summer Institute of Linguistics, Dallas, TX) on January 28, 1991. Revised April 8, 1993 to match the specification of FSDs in version P2 of the TEI Guidelines. Revised again December 2004 to be consistent with the feature structure representation standard jointly developed with ISO TC37/SC4. -

- -

This sample FSD does not describe a complete feature +

This sample FSD does not describe a complete feature system. It is based on extracts from the feature system for English presented in the appendix (pages 245–247) of Generalized Phrase Structure Grammar, by Gazdar, Klein, -Pullum, and Sag (Harvard University Press, 1985).

- - - - - - Encodes a feature structure for the GPSG analysis - of English (after Gazdar, Klein, Pullum, and Sag) - - inverted sentence - - - - - - - - - - surface form of the conjunction - - - - - - - - - surface form of the complementizer - - - - - - - - - - - - agreement for person and number - - - - word form of a preposition - - - - - - - - - - - - - - - - - - - - - - - This type of feature structure encodes the features - for subject-verb agreement in English - - person (first, second, or third) - - - - - - number (singular or plural) - - - - -

- -
- - - -
- Formal Definition and Implementation -

This elements discussed in this chapter constitute a module of the +Pullum, and Sag (Harvard University Press, 1985).

Encodes a feature structure for the GPSG analysis + of English (after Gazdar, Klein, Pullum, and Sag)inverted sentencesurface form of the conjunctionsurface form of the complementizeragreement for person and numberword form of a prepositionThis type of feature structure encodes the features + for subject-verb agreement in Englishperson (first, second, or third)number (singular or plural)

+
+
+
+ Formal Definition and Implementation +

This elements discussed in this chapter constitute a module of the TEI scheme which is formally defined as follows: - - Feature Structures - Feature structures - Structures de traits - 功能結構 (Feature Structures) - Strutture di configurazione (feature structures) - Estrutura das características - 素性構造モジュール - + Feature StructuresFeature structuresStructures de traits功能結構 (Feature Structures)Strutture di configurazione (feature structures)Estrutura das características素性構造モジュール The selection and combination of modules to form a TEI schema is described in . - - - - - - - - - - - - - - - - - +

-
+
diff --git a/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml b/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml index 4d9341e3a2..4406c05e8b 100644 --- a/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml +++ b/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml @@ -1,11 +1,5 @@ - +
Tables, Formulæ, Graphics, and Notated Music @@ -88,11 +82,7 @@ this is rarely if ever done in practice.
TEI Tables

For encoding tables of low to moderate complexity, these Guidelines - provide the following special purpose elements: - - - - + provide the following special purpose elements:

The table element is defined as a member of the class model.inter; it may therefore appear both within other components (such as paragraphs), or between them, provided that @@ -129,31 +119,9 @@ this is rarely if ever done in practice.

The following simple example demonstrates how the data presented as a labelled list in section might be represented by an encoder wishing to preserve its original appearance as a table: - - Report of the conduct and progress of Ernest - Pontifex. Upper Vth form — half term ending Midsummer 1851 - - Classics - Idle listless and unimproving - - - Mathematics - ditto - - - Divinity - ditto - - - Conduct in house - Orderly - - - General conduct - Not satisfactory, on account of his great unpunctuality and - inattention to duties - -
+ Report of the conduct and progress of Ernest + Pontifex. Upper Vth form — half term ending Midsummer 1851ClassicsIdle listless and unimprovingMathematicsdittoDivinitydittoConduct in houseOrderlyGeneral conductNot satisfactory, on account of his great unpunctuality and + inattention to duties

Note that this encoding makes no attempt to represent the full @@ -163,39 +131,7 @@ this is rarely if ever done in practice. interpretation, see chapter .

The following example demonstrates how a simple statistical table may be represented using this scheme: - - Poor Man's Lodgings in Norfolk (Mayhew, 1843) - - - Dossing Cribs or Lodging Houses - Beds - Needys or Nightly Lodgers - - - Bury St Edmund's - 5 - 8 - 128 - - - Thetford - 3 - 6 - 36 - - - Attleboro' - 3 - 5 - 20 - - - Wymondham - 1 - 11 - 22 - -
+ Poor Man's Lodgings in Norfolk (Mayhew, 1843) Dossing Cribs or Lodging HousesBedsNeedys or Nightly LodgersBury St Edmund's58128Thetford3636Attleboro'3520Wymondham11122

Note the use of a blank cell in the first row to ensure that the column labels are correctly aligned with the data. Again, this encoding does @@ -213,33 +149,7 @@ this is rarely if ever done in practice. potentially more useful semantic information, as in the following example, where the fact that one cell contains a number and the other contains a place name has been explicitly recorded: - - US State populations, 1990 - - Wyoming - - - 453,588 - - - Alaska - - - 550,043 - - - Montana - - - 799,065 - - - Rhode Island - - - 1,003,464 - -
+ US State populations, 1990Wyoming453,588Alaska550,043Montana799,065Rhode Island1,003,464

The use of semantically marked elements within a cell enables the encoder to convey something about the nature and significance of the @@ -247,17 +157,7 @@ this is rarely if ever done in practice. columns.

Alternatively, the role attribute might be used to convey such information: - - US State populations, 1990 - Wyoming - 453,588 - Alaska - 550,043 - Montana - 799,065 - Rhode Island - 1,003,464 -
+ US State populations, 1990Wyoming 453,588 Alaska 550,043 Montana 799,065 Rhode Island1,003,464

The content of table elements is not limited to head and row. Milestone elements such as cb and lb @@ -267,26 +167,10 @@ this is rarely if ever done in practice. trailer provide options for including text which is clearly part of the table, but outside the actual tabular layout. This example shows the use of trailer: - - The Table of Battallions, reduced out of the grand square of - men. - - 1 - 2 - 3 - 4 - - - - 841 - 3 - 289 289 256 - 7 - - The end of the Table of Battallions reduced out of the +
The Table of Battallions, reduced out of the grand square of + men.12348413289 289 2567The end of the Table of Battallions reduced out of the battels of g. and squares of men: vpon the right side of euery - leafe. -
+ leafe.

@@ -388,9 +272,7 @@ Basic document type ().

--> clearly simply representing superscripts and subscripts will be inadequate.

The formula element provided by these Guidelines makes no - attempt to represent the internal structure of formulæ. - - + attempt to represent the internal structure of formulæ.

By default, a formula is assumed to contain character data which is not validated in any way. The notation used may however be named, using @@ -446,45 +328,7 @@ which became a W3C recommendation on February 21, 2001.

elements correspond with the range of operators, relations, and named functions typically found at the high-school level of mathematics. The tortoise example given above in TeX can be re-expressed in MathML as - - - - 1 - - - 10 - - - + - - - 1 - - - 100 - - - + - - - 1 - - - 1000 - - - + - - - 1 - - - 10000 - - - + - … - + 110+1100+11000+110000+…

MathML 2.0 provides support for a Semantic Math-Web, XML namespaces, and other current XML standards, such as XML DOM, OMG IDL, @@ -497,11 +341,7 @@ which became a W3C recommendation on February 21, 2001.

semantically rich representations of mathematical objects both on and off the Web in a platform-independent manner.

The OpenMath Standard () consists - of specifications for - OpenMath objects, representing the structure of formulæ (); - Content Dictionaries, providing semantic context (); - Encodings, both binary () and XML (). -

+ of specifications for OpenMath objects, representing the structure of formulæ ();Content Dictionaries, providing semantic context ();Encodings, both binary () and XML ().

OpenMath and MathML have certain common aspects. They both use prefix operators, both are XML-based and they both construct their objects by applying certain rules recursively. Such similarities facilitate mapping @@ -524,30 +364,7 @@ which became a W3C recommendation on February 21, 2001.

MathML namespace may be included in a TEI document; see further discussion at .

The volume of a sphere - is given by the formula: - - V - = - - - 4 - - - 3 - - - π - - - r - - - 3 - - - - which is readily calculated.

-

As we have seen in equation , ...

+ is given by the formula: V=43πr3 which is readily calculated.

As we have seen in equation , ...

@@ -574,33 +391,20 @@ discussion at . notatedMusic is not the same as musicNotation, a metadata element, which is used to describe musical notation that appears in a manuscript. See .)

-

The following elements can be used for encoding music notation in text: - - - - - - +

The following elements can be used for encoding music notation in text:

- - groups elements representing or + groups elements representing or containing music notation. - - can be used to indicate the location of a - representation of the music notation. - mimeType supplies the MIME type of the data format, - when available. - + can be used to indicate the location of a + representation of the music notation. mimeType supplies the MIME type of the data format, + when available. - - can be used to give a prose description of + can be used to give a prose description of the notated music. - - can be used to indicate the location of + can be used to indicate the location of a graphical representation of the music notation. - - provides encoded binary data which + provides encoded binary data which constitutes another representation of the music notation (e.g. audio). @@ -610,37 +414,47 @@ discussion at . the ptr element, whose target attribute provides its electronically-accessible location. The attribute mimeType supplies the MIME type of the data format when available. For example:

- + + - + +

A textual description of the notation can be provided within the desc element; alternatively, a label may be supplied. For example:

- + + First bar of Chopin's Scherzo No.3 Op.39 - + +

It is possible to link to any kind of music notation data format. However, when a MIME type is not available, it is recommended that the format be specified in the description. See the following examples.

MIME type available:

- + + First bar of Chopin's Scherzo No.3 Op.39. Encoded in MusicXML. - + +

MIME type not available:

- + + First bar of Chopin's Scherzo No.3 Op.39. Encoded in Lilypond. - + +

Application format:

- + + First bar of Chopin's Scherzo No.3 Op.39. MuseScore Notation Software format. - + +

It is possible to specify the location of digital objects representing the notated music in other media such as images or audio-visual files. The interpretation of the correspondence between the notated music and these @@ -650,29 +464,29 @@ discussion at . application using the encoding. The alignment of encoded notated music, images carrying the notation, and audio files is a complex matter for which we refer the reader to other formats and specifications such as MPEG-SMR.

- + + First bar of Chopin's Scherzo No.3 Op.39 - - + +

It is also recommended, when useful, to embed XML-based music notation formats, such as the Music Encoding Initiative format as content of notatedMusic. This must be done by means of customization.

-

In modern printing, music notation positioned between blocks of text for illustrative purposes is usually referred to as a figure or example. In this cases, we recommend the inclusion of notatedMusic in figure in order to encode possible captions and headers. For example:

- Example from: - Prout, E. (1899). The + <figDesc>Example from: <bibl><author>Prout, E.</author> (<date when="1899">1899</date>). <title>The orchestra.
-
+ +

We now give some examples, from the works of the great masters, of some of the most frequently used bowings.

@@ -690,12 +504,7 @@ discussion at .
Specific Elements for Graphic Images

The following special purpose elements are used to indicate the presence - of graphic images within a document: - - - - - + of graphic images within a document:

The graphic and binaryObject elements form part of the common core module, and are discussed in section .

@@ -703,35 +512,25 @@ discussion at . textual descriptions of the pictures. The images themselves are specified using the graphic element, whose url attribute provides the location of an image. For example: -
- -
+

Three kinds of content may be supplied inside a figure element: the element head may be used to transcribe (or supply) a descriptive heading or title for the graphic itself as in this example: -

- - The View from the Bridge -
+
The View from the Bridge

Figures are often accompanied not only by a title or heading (a caption), but by a paragraph or so of commentary (a legend) following the caption. One or more p or ab elements may be used to transcribe any commentary on the figure in the source: -

- - Above: -

The drawing room of the Pullman house, the white and gold saloon +

Above:

The drawing room of the Pullman house, the white and gold saloon where the magnate delighted in giving receptions for several hundred - people.

- The figure shows an elaborately decorated room, at least + people.

The figure shows an elaborately decorated room, at least twenty-five feet side to side and fifty feet long, with ornate mouldings and Corinthian columns on the walls, overstuffed armchairs and loveseats arranged in several conversational groupings, and two - large chandeliers. -
+ large chandeliers.
Here, the figure contains a heading Above which is complemented by a @@ -742,13 +541,9 @@ discussion at . form with the needs of print-handicapped readers in mind, the figDesc element may be provided by the author rather than a subsequent encoder. -
- - Figure One: The View from the Bridge - A Whistleresque view showing four or five sailing boats in +
Figure One: The View from the BridgeA Whistleresque view showing four or five sailing boats in the foreground, and a series of buoys strung out between - them. -
+ them.

Where the graphic itself contains large amounts of text, perhaps with a complex structure, and perhaps difficult to distinguish from the graphic, @@ -763,21 +558,9 @@ discussion at . relationship between the graphic and the surrounding text.

A figure which is internally divided, or contains sub-figures, may be encoded with nested figure elements, as in the following example. - -

-
- - Parallel -
-
- - Perspective -
- The two canonical view volumes, for the (a) +
Parallel
Perspective
The two canonical view volumes, for the (a) parallel and (b) perspective projections. Note that -z is to the - right. -
- + right.

Like any other element in the TEI scheme, figures may be given @@ -793,11 +576,7 @@ discussion at . version of the figure discussed above is available as fig1th.png, we might embed a reference to the image using the simple ref element discussed in section : Click - here for enlightenment -

- -
- + here for enlightenment

Another common requirement is to associate part or the whole of an image with a textual element not necessarily contiguous to it in the text; this @@ -815,38 +594,20 @@ discussion at .

The first requirement is some way of identifying and hence pointing to sub-parts of a graphic image. This may be done by pointing into an XML graphic representation, for example an SVG file. Thus - - +

These ptr elements identify two areas within the image Fig1 by pointing at elements inside the XML file Fig1.svg, which contains the following. - - - - - - - - - - +

The next requirement is some way of identifying the parts of the document to which a link is to be made. The most obvious way of doing this is to use the global xml:id attribute: - - - - - - +

Now, all that is needed to linking these areas to the relevant chapters is a linkGrp element, as described in section : - - - - +

In this example, the SVG representation of the graphic is stored externally to the TEI document and linked by means of a pointer. It is @@ -942,21 +703,7 @@ discussion at . extent and cannot therefore be regarded as standards in any meaningful sense. They are however widely used by many different vendors.

The following formats are widely used at the present time, and likely to - remain supported by more than one vendor's software: - BMP: Microsoft bitmap format - CGM: Computer Graphics Metafile - GIF: Graphics Interchange Format - JPEG: Joint Photographic Expert Group - PBM: Portable Bit Map - PCX: IBM PC raster format - PICT: Macintosh drawing format - PNG: Portable Network Graphics format - Photo-CD: Kodak Photo Compact Disk format - QuickTime: Apple real-time image system - SMIL: Synchronized Multimedia Integration Language format - SVG: Scalable Vector Graphics format - TIFF: Tagged Image File Format -

+ remain supported by more than one vendor's software: BMP: Microsoft bitmap formatCGM: Computer Graphics MetafileGIF: Graphics Interchange FormatJPEG: Joint Photographic Expert GroupPBM: Portable Bit MapPCX: IBM PC raster formatPICT: Macintosh drawing formatPNG: Portable Network Graphics formatPhoto-CD: Kodak Photo Compact Disk formatQuickTime: Apple real-time image systemSMIL: Synchronized Multimedia Integration Language formatSVG: Scalable Vector Graphics formatTIFF: Tagged Image File Format

Brief descriptions of all the above are given below. Where possible, current addresses or other contact information are shown for the originator of each format. Many formal standards, especially those @@ -1090,15 +837,7 @@ discussion at .

Module for Tables, Formulæ, Notated Music, and Graphics

The module described in this chapter provides the following features: - - Tables, Formulæ, Notated Music, Figures - Tables, formulæ, notated music, and figures - Tableaux, formules et graphiques - 表格、方程式與圖表 - Tabelle, formule e figure - Tabelas, fórmulas, e figuras - 図表式モジュール - + Tables, Formulæ, Notated Music, FiguresTables, formulæ, notated music, and figuresTableaux, formules et graphiques表格、方程式與圖表Tabelle, formule e figureTabelas, fórmulas, e figuras図表式モジュール The selection and combination of modules to form a TEI schema is described in . @@ -1107,4 +846,4 @@ discussion at .

-
\ No newline at end of file +
diff --git a/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml b/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml index f7e1642626..bd1d5eafd7 100644 --- a/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml +++ b/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml @@ -1,19 +1,13 @@ - + -
Graphs, Networks, and Trees -

Graphical representations are widely used for displaying relations +

+ Graphs, Networks, and Trees +

Graphical representations are widely used for displaying relations among informational units because they help readers to visualize those relations and hence to understand them better. Two general types of graphical representations may be distinguished. - - Graphs, in the strictly mathematical sense, consist +Graphs, in the strictly mathematical sense, consist of points, often called nodes or vertices, and connections among them, called arcs, or under certain conditions, @@ -23,15 +17,13 @@ generally and networks in particular are dealt with directly below. Trees are dealt with separately in sections and .The treatment here is largely based on the -characterizations of graph types in -Charts, which typically plot data in two or more +characterizations of graph types in Charts, which typically plot data in two or more dimensions, including plots with orthogonal or radial axes, bar charts, pie charts, and the like. These can be described using the elements defined in the module for figures and graphics; see chapter .

- -

Among the types of qualitative relations often represented by graphs +

Among the types of qualitative relations often represented by graphs are organizational hierarchies, flow charts, genealogies, semantic networks, transition networks, grammatical relations, tournament schedules, seating plans, and directions to people's houses. In @@ -41,8 +33,9 @@ common conventions for representing them visually. However, it must be emphasized that these recommendations do not provide for the full range of possible graphical representations, and deal only partially with questions of design, layout, and placement.

-
Graphs and Digraphs -

Broadly speaking, graphs can be divided into two types: +

+ Graphs and Digraphs +

Broadly speaking, graphs can be divided into two types: undirected and directed. An undirected graph is a set of nodes (or vertices) together with a set of pairs of those vertices, called arcs or @@ -59,11 +52,8 @@ whole, node to encode nodes or vertices, and arc to encode arcs or edges; arcs can also be encoded by attributes on the node element. These elements have the following descriptions and attributes: - - - -

-

Before proceeding, some additional terminology may be helpful. We +

+

Before proceeding, some additional terminology may be helpful. We define a path in a graph as a sequence of nodes n1, ..., nk such that there is an arc from each ni to ni+1 in the sequence. A cyclic path, or cycle is a path leading from a @@ -73,43 +63,23 @@ cycle is said to be cyclic; otherwise it is connected if there is a path from some node to every other node in the graph; any graph that is not connected is said to be disconnected.

-

Here is an example of an undirected, cyclic disconnected graph, in +

Here is an example of an undirected, cyclic disconnected graph, in which the nodes are annotated with three-letter codes for airports, and the arcs connecting the nodes are represented by horizontal and vertical lines, with 90 degree bends used simply to avoid having to draw diagonal lines.

- - - - - -

- -

Next is a markup of the graph, using arc elements to encode + + + + + +

+ +

+

Next is a markup of the graph, using arc elements to encode the arcs. - - - - - - - - - - - - - - - - - - - - - -

-

+

+

The first child element of graph may be a label to record a label for the graph; similarly, the label child of each node element records the labels of that node. The @@ -129,7 +99,7 @@ to the nodes connected by those arcs. Since the graph is undirected, no directionality is implied by the use of the from and to attributes; the values of these attributes could be interchanged in each arc without changing the graph.

-

The adj, adjFrom, and adjTo +

The adj, adjFrom, and adjTo attributes of the node element provide an alternative method of representing unlabeled arcs, their values being pointers to the nodes which are adjacent to or from that node. The adj attribute @@ -138,198 +108,50 @@ is to be used for undirected graphs, and the adjFrom and for the directed adjacency attributes to be used in an undirected graph, and vice versa. Here is a markup of the preceding graph, using the adj attribute to represent the arcs. - - - - - - - - - - - - - - - - - -

-

Note that each arc is represented twice in this encoding of the +

+

Note that each arc is represented twice in this encoding of the graph. For example, the existence of the arc from LAX to LVG can be inferred from each of the first two node elements in the graph. This redundancy, however, is not required: it suffices to describe an arc in any one of the three places it can be described (either adjacent node, or in a separate arc element). Here is a less redundant representation of the same graph. - - - - - - - - - - - - - - - - - -

-

Although in many cases the arc element is redundant (since +

+

Although in many cases the arc element is redundant (since arcs can be described using the adjacency attributes of their adjacent nodes), it has nevertheless been included in this module, in order to allow the convenient specification of identifiers, display or rendition information, and labels for each arc (using the attributes xml:id, rend, and a child label element).

-

Next, let us modify the preceding graph by adding directionality to +

Next, let us modify the preceding graph by adding directionality to the arcs. Specifically, we now think of the arcs as specifying selected routes from one airport to another, as indicated by the direction of the arrowheads in the following diagram.

-

-

Here is an encoding of this graph, using the arc element to +

+ +

+

Here is an encoding of this graph, using the arc element to designate the arcs. - - - - - - - - - - - - - - - - - - - - - - - + The attributes inDegree and outDegree indicate the number of nodes which are adjacent to and from the node concerned respectively.

- -

Here is another encoding of the graph, using the adjTo and +

Here is another encoding of the graph, using the adjTo and adjFrom attributes on nodes to designate the arcs. - - - - - - - - - - - - - - - - - -

-

If we wish to label the arcs, say with flight numbers, then +

+

If we wish to label the arcs, say with flight numbers, then arc elements must be used to hold the label elements, as in the following example. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Transition Networks -

For encoding transition networks and other kinds of directed graphs + + + + + +

+ Transition Networks +

For encoding transition networks and other kinds of directed graphs in which distinctions among types of nodes must be made, the type attribute is provided for node elements. In the following example, the initial and final @@ -337,106 +159,115 @@ nodes (or states) of the network are distinguished. It can be understood as accepting the set of strings obtained by traversing it from its initial node to its final node, and concatenating the labels.

-

- - - - - - - - - - - - - - - - - - - - - - - - - - -

-

A finite state transducer has two labels on each arc, and can be +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+

A finite state transducer has two labels on each arc, and can be thought of as representing a mapping from one sequence of labels to the other. The following example represents a transducer for translating the English strings accepted by the network in the preceding example into French. The nodes have been annotated with numbers, for convenience.

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-
Family Trees -

The next example provides an encoding a portion of a +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+
+
+ Family Trees +

The next example provides an encoding a portion of a family treeThe family tree is that of the mathematician and philosopher Bertrand Russell, whose third wife was commonly known as Peter. The information presented here is taken from @@ -452,130 +283,122 @@ the graph, nodes representing females are framed by ovals, nodes representing males are framed by boxes, and nodes representing parents are framed by diamonds.

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-
Historical Interpretation -

For our final example, we represent graphically the relationships +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+
+
+ Historical Interpretation +

For our final example, we represent graphically the relationships among various geographic areas mentioned in a seventeenth-century Scottish document. The document itself is a sasine, which records a grant of land from the earl of Argyll to one Donald McNeill, and reads in part as follows (abbreviations have been expanded silently, and [...] marks illegible passages): - -

Item instrument of Sasine given the said Hector +

Item instrument of Sasine given the said Hector Mcneil confirmed and dated 28 May 1632 -[...] at Edinburgh upon the 15 June 1632

-

Item ane charter granted by Archibald late earl +[...] at Edinburgh upon the 15 June 1632

Item ane charter granted by Archibald late earl of Argyle and Donald McNeill of Gallachalzie wh makes mention that ... the said late Earl yields and grants -to the said Donald MacNeill ...

-

All and hail the two merk land of old extent +to the said Donald MacNeill ...

All and hail the two merk land of old extent of Gallachalzie with the pertinents by and in the lordship of Knapdale within the sherrifdome -of Argyll

-

[description of other lands granted follows ...]

-

This Charter is dated at Inverary the 15th May 1669

-

In this example, we are concerned with the land and pertinents (i.e. +of Argyll

[description of other lands granted follows ...]

This Charter is dated at Inverary the 15th May 1669

+

In this example, we are concerned with the land and pertinents (i.e. accompanying sources of revenue) described as the two merk land of old extent of Gallachalzie with the pertinents by and in the lordship of Knapdale within the sherrifdom of Argyll.

-

The passage concerns the following pieces of land: - -the Earl of Argyll's land (i.e. the lands granted by this clause -of the sasine) -two mark of land in Gallachalzie -the pertinents for this land -the Lordship of Knapdale -the sherrifdom of Argyll +

The passage concerns the following pieces of land: +the Earl of Argyll's land (i.e. the lands granted by this clause +of the sasine)two mark of land in Gallachalziethe pertinents for this landthe Lordship of Knapdalethe sherrifdom of Argyll We will represent these geographic entities as nodes in a graph. Arcs in the graph will represent the following relationships among them: - -containment (INCLUDE) -location within (IN) -contiguity (BY) -constituency (PART OF) +containment (INCLUDE)location within (IN)contiguity (BY)constituency (PART OF) Note that these relationships are logically related: include and in, for example, are inverses of each other: the Earl of Argyll's land includes the parcel in Gallachalzie, and the parcel is @@ -583,7 +406,7 @@ therefore in the Earl of Argyll's land. Given an explicit set of inference rules, an appropriate application could use the graph we are constructing to infer the logical consequences of the relationships we identify.

-

Let us assume that feature-structure analyses are available which +

Let us assume that feature-structure analyses are available which describe Gallachalzie, Knapdale, and Argyll. We will link to those feature structures using the value attribute on the nodes representing those places. However, there may be some uncertainty as to @@ -602,74 +425,25 @@ The graph given here describes the possible interpretations of the clause itself, not the sets of inferences derivable from each syntactic interpretation, for which it would be convenient to use the facilities described in chapter .

-

We represent the graph and its encoding as follows, where +

We represent the graph and its encoding as follows, where the dotted lines in the graph indicate the mutually exclusive arcs; in the encoding, we use the exclude attribute to indicate those arcs.

-

-

The graph formalizes the following relationships: - -the Earl of Argyll's land includes (the parcel of -land in) Gallachalzie -the Earl of Argyll's land includes the pertinents of that parcel -the pertinents are (in part) by the Lordship of Knapdale -the pertinents are (in part) part of the Lordship of Knapdale -the Earl of Argyll's land, or the pertinents, or +

+ +

+

The graph formalizes the following relationships: +the Earl of Argyll's land includes (the parcel of +land in) Gallachalziethe Earl of Argyll's land includes the pertinents of that parcelthe pertinents are (in part) by the Lordship of Knapdalethe pertinents are (in part) part of the Lordship of Knapdalethe Earl of Argyll's land, or the pertinents, or the Lordship of Knapdale, is in the Sherrifdom of Argyll We encode the graph thus: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-
Trees -

A tree is a connected acyclic graph. That is, it is +

+
+
+
+ Trees +

A tree is a connected acyclic graph. That is, it is possible in a tree graph to follow a path from any vertex to any other vertex, but there are no paths that lead from any vertex to itself. A rooted tree is a directed graph based on a tree; that is, the arcs in @@ -696,12 +470,8 @@ nodes, which (when its parent is ordered) it would be assumed to precede, giving rise to crossing arcs. The elements used for the encoding of trees have the following descriptions and attributes. - - - - -

-

Here is an example of a tree. It represents the order in which the +

+

Here is an example of a tree. It represents the order in which the operators of addition (symbolized by +), exponentiation (symbolized by **) and division (symbolized by /) are applied in evaluating the arithmetic formula @@ -709,55 +479,58 @@ applied in evaluating the arithmetic formula In drawing the graph, the root is placed on the far right, and directionality is presumed to be to the left.

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-

In this encoding, the arity attribute represents the +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+

In this encoding, the arity attribute represents the arity of the tree, which is the greatest value of the outDegree attribute for any of the nodes in the tree. If, as in this case, arity is 2, we say that the tree is a binary tree.

-

Since the left-to-right (or top-to-bottom!) order of the children of +

Since the left-to-right (or top-to-bottom!) order of the children of the two + nodes does not affect the arithmetic result in this case, we could represent in this tree all of the arithmetically equivalent formulas involving its leaves, by specifying the attribute @@ -765,188 +538,91 @@ equivalent formulas involving its leaves, by specifying the attribute ord as true on the root and other iNode elements, and the attribute ord as partial on the tree element, as follows. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-

This encoding represents all of the following: - - ((a**2)+(b**2))/((a+b)**2) - ((b**2)+(a**2))/((a+b)**2) - ((a**2)+(b**2))/((b+a)**2) - ((b**2)+(a**2))/((a+b)**2) - +

+

This encoding represents all of the following: +((a**2)+(b**2))/((a+b)**2)((b**2)+(a**2))/((a+b)**2)((a**2)+(b**2))/((b+a)**2)((b**2)+(a**2))/((a+b)**2)

-

Linguistic phrase structure is very commonly represented by trees. +

Linguistic phrase structure is very commonly represented by trees. Here is an example of phrase structure represented by an ordered tree with its root at the top, and a possible encoding.

-

- - - - - - - - - - - - - - - - - - - - - - - - - - -

-

Finally, here is an example of an ordered tree, in which a particular +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+

Finally, here is an example of an ordered tree, in which a particular node which ordinarily would precede another is specified as following it. In the drawing, the xxx symbol indicates that the arc from VB to PT crosses the arc from VP to PN.

-

- - - - - - - - - - - - - - - - - - - - - - - - - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
Another Tree Notation -

In this section, we present an alternative to the method of +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+ + + + + + +
+
+ Another Tree Notation +

In this section, we present an alternative to the method of representing the structure of ordered rooted trees given in section , which is based on the observation that any node of such a tree can be thought of as the root of the @@ -970,67 +646,68 @@ which consists of one or more tree, eTree, or consists of one or more forest elements. The elements used for the encoding of embedding trees and the units containing them have the following descriptions and attributes. - - - - - - -

-

Like the root, iNode, and leaf of a +

+

Like the root, iNode, and leaf of a tree, the eTree, triangle and eLeaf elements may also have value attributes and label children.

-

To illustrate the use of the eTree and eLeaf +

To illustrate the use of the eTree and eLeaf elements, here is an encoding of the second example in section , repeated here for convenience.

-

- - - - - - - - - - - - - - - - - - - - - - - -

-

Next, we provide an encoding, using the triangle element, in +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + +

+

Next, we provide an encoding, using the triangle element, in which the internal structure of the eTree labeled NP is omitted.

-

- - - - - - - - - - - - - - - -

-

Ambiguity involving alternative tree structures associated with the +

+ + + + + + + + + + + + + + + + + + +

+

Ambiguity involving alternative tree structures associated with the same terminal sequence can be encoded relatively conveniently using a combination of the exclude and copyOf attributes described in sections and . In @@ -1051,63 +728,67 @@ ambiguous tree by means of the dotted-line arcs. The markup using the copyOf and exclude attributes follows the sketch.

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-

To indicate that one of the alternatives is selected, one may specify +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+

To indicate that one of the alternatives is selected, one may specify the select attribute on the highest eTree as either #GD-PPA or #GD-PPB; see section -.

-

Depending on the grammar one uses to associate structures with +.

+

Depending on the grammar one uses to associate structures with examples like see the man with the periscope, the representations may be more complicated than this. For example, adopting a version of the X-bar theory of phrase structure @@ -1117,77 +798,97 @@ node which is not required when the attachment is not made, as shown in the following diagram. A possible encoding of this ambiguous structure immediately follows the diagram.

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- -

A derivation in a generative grammar is often thought +

A derivation in a generative grammar is often thought of as a set of trees. To encode such a derivation, one may use the forest element, in which the trees may be marked up using the tree, the eTree, or the triangle element. @@ -1201,160 +902,99 @@ what.The symbols special theoretical constructs (empty category and trace respectively), which need not concern us here.

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-

In this markup, we have used copyOf attributes to provide +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+

In this markup, we have used copyOf attributes to provide virtual copies of elements in the tree representing the second stage of the derivation that also occur in the first stage, and the corresp attribute (see section ) to link those elements in the second stage with corresponding elements in the first stage that are not copies of them.

-

If a group of forests (e.g. a full grammatical derivation including +

If a group of forests (e.g. a full grammatical derivation including syntactic, semantic, and phonological subderivations) is to be articulated, the grouping element listForest may be used.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
Representing Textual Transmission - -

A stemma codicum (sometimes called just + + + + + + + +

+
+ Representing Textual Transmission +

A stemma codicum (sometimes called just stemma) is a tree-like graphic structure that has become traditional in manuscript studies for representing textual transmission. Consider the following hypothetical stemma: -

Example stemma -
+
Example stemma

- -

The nodes in this stemma represent manuscripts; each has a label (a +

The nodes in this stemma represent manuscripts; each has a label (a letter) which identifies it and also distinguishes whether the manuscript is extant, lost, or hypothetical. Extant manuscripts are identified by uppercase Latin letters or words beginning with @@ -1371,8 +1011,7 @@ and t share textual material that is not shared with other manuscripts (represented in this case by δ) even though no physical manuscript attesting this stage in the textual transmission has ever been identified.

- -

Manuscripts are copied from other manuscripts. The preceding +

Manuscripts are copied from other manuscripts. The preceding stemma represents the hypothesis that all manuscripts go back to a common ancestor (α), that the tradition split after that stage into two (β and γ), etc. Descent by copying is indicated with a solid line. @@ -1380,8 +1019,7 @@ According to this model, α is the earliest common hypothetical stage that can be reconstructed, and all nodes below α have a single parent, that is, were copied from a single other stage in the tradition.

- -

This familiar tree model is complicated because manuscripts +

This familiar tree model is complicated because manuscripts sometimes show the influence of more than one ancestor. They may have been produced by a scribe who checked the text in one manuscript of the same work whilst copying from another, or perhaps @@ -1398,8 +1036,7 @@ called contamination, and it is reflected in a stemma by a dotted line. Thus, the example above asserts that A is copied within the ε tradition, but is also contaminated from the γ tradition.

- -

The utility of a stemma as a visualization tool is inversely +

The utility of a stemma as a visualization tool is inversely proportional to the degree of contamination in the manuscript tradition. A tradition completely without contamination (called a closed tradition) yields a classic tree, easily @@ -1407,8 +1044,7 @@ represented graphically by a stemma. An open tradition, with substantial contamination, yields a spaghetti-like stemma characterized by crossing dotted lines, which is both difficult to read and not very informative.

- -

The eTree element introduced in this chapter can be used +

The eTree element introduced in this chapter can be used to represent a closed tradition in a straightforward manner. Each non-terminal node is represented by a typed eTree element and each terminal node by an eLeaf. A label element @@ -1416,17 +1052,7 @@ provides a way of identifying each node, complementary to the global attributes n and xml:id attributes. For example, the closed part of the tradition headed by the label δ may be encoded as follows: - - - - - - - - - - - + To complete this representation, we need to show that the node labelled A is not derived solely from its parent node (labelled ε) but also demonstrates contamination from the node labelled γ. The @@ -1435,64 +1061,19 @@ easiest way to accomplish this is to include an appropriately-typed target of which points to the node labelled γ. This requires that this latter node be supplied with a value for its xml:id attribute. The complete representation is thus: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

-

In any substantial codicological project, it is likely that +

In any substantial codicological project, it is likely that significantly more data will be required about the individual witnesses than indicated in the simple structures above. These Guidelines provide a rich variety of additional elements for representing such information: see in particular chapters , , and .

- -
- -
- Module for Graphs, Networks, and Trees -

The module described in this chapter makes available the +

+
+ Module for Graphs, Networks, and Trees +

The module described in this chapter makes available the following components: - - Graphs, networks, and trees - Graphs, networks, and trees - Graphes, réseaux et arbres - 圖形、網絡與樹狀結構 - Grafici, reti e alberi - Grafos, redes, e árvores - グラフモジュール - + Graphs, networks, and treesGraphs, networks, and treesGraphes, réseaux et arbres圖形、網絡與樹狀結構Grafici, reti e alberiGrafos, redes, e árvoresグラフモジュール The selection and combination of modules to form a TEI schema is described in . @@ -1500,5 +1081,5 @@ representing such information: see in particular chapters , <

+
-
\ No newline at end of file diff --git a/P5/Source/Guidelines/en/HD-Header.xml b/P5/Source/Guidelines/en/HD-Header.xml index 0eebacb3ba..2a33521413 100644 --- a/P5/Source/Guidelines/en/HD-Header.xml +++ b/P5/Source/Guidelines/en/HD-Header.xml @@ -1,15 +1,9 @@ - +
-The TEI Header -

This chapter addresses the problems of describing an encoded work + The TEI Header +

This chapter addresses the problems of describing an encoded work so that the text itself, its source, its encoding, and its revisions are all thoroughly documented. Such documentation is equally necessary for scholars using the texts, for software processing them, and for @@ -18,12 +12,11 @@ declarations provide an electronic analogue to the title page attached to a printed work. They also constitute an equivalent for the content of the code books or introductory manuals customarily accompanying electronic data sets.

-

Every TEI-conformant text must carry such a set of descriptions, +

Every TEI-conformant text must carry such a set of descriptions, prefixed to it and encoded as described in this chapter. The set is known as the TEI header, tagged teiHeader, and has five major parts: - -a file description, tagged fileDesc, +a file description, tagged fileDesc, containing a full bibliographical description of the computer file itself, from which a user of the text could derive a proper bibliographic citation, or which a librarian or archivist could use in @@ -34,15 +27,13 @@ even when this is stored in several distinct operating system files. The file description also includes information about the source or sources from which the electronic document was derived. The TEI elements used to encode the file description are described in section - below. -an encoding description, tagged encodingDesc, + below.an encoding description, tagged encodingDesc, which describes the relationship between an electronic text and its source or sources. It allows for detailed description of whether (or how) the text was normalized during transcription, how the encoder resolved ambiguities in the source, what levels of encoding or analysis were applied, and similar matters. The TEI elements used to encode the -encoding description are described in section below. -a text profile, tagged profileDesc, +encoding description are described in section below.a text profile, tagged profileDesc, containing classificatory and contextual information about the text, such as its subject matter, the situation in which it was produced, the individuals described by or participating in producing it, and so forth. @@ -52,21 +43,19 @@ desirable to enforce a controlled descriptive vocabulary or to perform retrievals from a body of text in terms of text type or origin. The text profile may however be of use in any form of automatic text processing. The TEI elements used to encode the profile description -are described in section below. -a container element, tagged xenoData, which allows easy +are described in section below.a container element, tagged xenoData, which allows easy inclusion of metadata from non-TEI schemes (i.e., other than elements in the TEI namespace). For example, the MARC record for the encoded document might be included using MARCXML or MODS. A simple set of metadata for harvesting might be included encoded in Dublin -Core. -a revision history, tagged revisionDesc, +Core.a revision history, tagged revisionDesc, which allows the encoder to provide a history of changes made during the development of the electronic text. The revision history is important for version control and for resolving questions about the history of a file. The TEI elements used to encode the revision description are described in section below.

-

A TEI header can be a very large and complex object, or it may be a +

A TEI header can be a very large and complex object, or it may be a very simple one. Some application areas (for example, the construction of language corpora and the transcription of spoken texts) may require more specialized and detailed information than others. The present @@ -85,11 +74,11 @@ elements are available, as further detailed in that chapter. , at the end of the present chapter, discusses the recommended content of a minimal TEI header and its relation to standard library cataloguing practices.

- -
Organization of the TEI Header - -
The TEI Header and Its Components -

The teiHeader element should be clearly distinguished +

+ Organization of the TEI Header +
+ The TEI Header and Its Components +

The teiHeader element should be clearly distinguished from the front matter of the text itself (for which see section ). A composite text, such as a corpus or collection, may contain several headers, as further discussed below. In @@ -97,103 +86,57 @@ the general case, however, a TEI-conformant text will contain a single teiHeader element, followed by a single text or facsimile element, or both.

-

The header element has the following description: +

The header element has the following description:

-

As discussed above, the teiHeader element has five principal +

As discussed above, the teiHeader element has five principal components: - - - - - - - -

-

Of these, only the fileDesc element is required in all TEI + +

+

Of these, only the fileDesc element is required in all TEI headers; the others are optional. That is, only one of the five components of the TEI header (the fileDesc) is mandatory, and it also has some mandatory components, as further discussed in below. The smallest possible valid TEI header thus looks like this: - - - - <!-- title of the resource --> - - -

- - -

- - -

-

The content of the elements making up a TEI header may be given in + <!-- title of the resource -->

+

The content of the elements making up a TEI header may be given in any language, not necessarily that of the text to which the header applies, and not necessarily English. As elsewhere, the xml:lang attribute should be used at an appropriate level to specify the language. For example, in the following schematic example, an English text has been given a French header: - - - - - - - - - -

-

In the case of language corpora or collections, it may be + +

+

In the case of language corpora or collections, it may be desirable to record header information either at the level of the individual components in the corpus or collection, or at the level of the corpus or collection itself (more details concerning the tagging of composite texts are given in section , which should be read in conjunction with the current chapter). A corpus may thus take the form: - - - - - - - - - - - - - - - - - - - +

- - - - - - - - - - -
- -
Types of Content in the TEI Header -

The elements occurring within the TEI header may contain several + + + + + + + + + + +

+
+ Types of Content in the TEI Header +

The elements occurring within the TEI header may contain several types of content; the following list indicates how these types of content are described in the following sections: - - - Most elements contain simple running prose at some level. Many +Most elements contain simple running prose at some level. Many elements may contain either prose (possibly organized into paragraphs) or more specific elements, which themselves contain prose. In this chapter's descriptions of element content, the phrase @@ -203,9 +146,7 @@ content are described in the following sections: understood to imply character data, interspersed as need be with phrase-level elements, but not organized into paragraphs. For more information on paragraphs, highlighted phrases, lists, etc., see - section . - - Elements whose names end with the suffix + section .Elements whose names end with the suffix Stmt (e.g. editionStmt, titleStmt) and the xenoData element enclose a group of specialized elements recording some structured information. @@ -223,9 +164,7 @@ content are described in the following sections: elements may contain prose descriptions as an alternative to the set of specialized elements, thus allowing the encoder to choose whether or not the information concerned should be presented in a structured - form or in prose. - - Elements whose names end with the suffix + form or in prose.Elements whose names end with the suffix Decl (e.g. tagsDecl, refsDecl) enclose information about specific encoding practices applied in the electronic text; often these practices are @@ -236,17 +175,15 @@ content are described in the following sections: header of each such text or subdivision. Instead, the decls attribute of each text (or subdivision of the text) to which the declaration applies may be used to supply a - cross-reference to it, as further described in section . - - Elements whose names end with the suffix + cross-reference to it, as further described in section .Elements whose names end with the suffix Desc (e.g. settingDesc, projectDesc) contain a prose description, possibly, but not necessarily, organized under some specific headings by suggested - sub-elements. -

- -
Model Classes in the TEI Header -

The TEI header provides a very rich collection of metadata + sub-elements.

+
+
+ Model Classes in the TEI Header +

The TEI header provides a very rich collection of metadata categories, but makes no claim to be exhaustive. It is certainly the case that individual projects may wish to record specialized metadata which either does not fit within one of the predefined categories @@ -256,25 +193,16 @@ may elect to define additional elements using the customization methods discussed in . The TEI class system makes such customizations simpler to effect and easier to use in interchange.

-

These classes are specific to parts of the header: - - - - - - - - - - - -

-
- -
The File Description -

This section describes the fileDesc element, which is the +

These classes are specific to parts of the header: + +

+
+
+
+ The File Description +

This section describes the fileDesc element, which is the first component of the teiHeader element.

-

The bibliographic description of a machine-readable or digital text +

The bibliographic description of a machine-readable or digital text resembles in structure that of a book, an article, or any other kind of textual object. The file description element of the TEI header has therefore been closely modelled on existing standards in library @@ -284,50 +212,40 @@ to allow cataloguers to catalogue it. Bibliographic citations occurring elsewhere in the header, and also in the text itself, are derived from the same model (on bibliographic citations in general, see further section ). See further section .

-

The bibliographic description of an electronic text should be +

The bibliographic description of an electronic text should be supplied by the mandatory fileDesc element: - - - +

-

The fileDesc element contains three mandatory elements and +

The fileDesc element contains three mandatory elements and four optional elements, each of which is described in more detail in sections to below. These elements are listed below in the order in which they must be given within the fileDesc element.

-

A complete file description containing all possible sub-elements +

A complete file description containing all possible sub-elements might look like this: - - - <!-- title of the resource --> -

- -

-

- -

- - + <!-- title of the resource -->

 Of these elements, only the titleStmt, publicationStmt, and sourceDesc are required; the others may be omitted unless considered useful.

- - - - - - - - -
The Title Statement -

The titleStmt element is the first component of the + + + + + + + + + +

+ The Title Statement +

The titleStmt element is the first component of the fileDesc element, and is mandatory: It contains the title given to the electronic work, together with @@ -336,7 +254,7 @@ identify the encoder, editor, author, compiler, or other parties responsible for it:

-

The title element contains the chief name of the +

The title element contains the chief name of the electronic work, including any alternative title or subtitles it may have. It may be repeated, if the work has more than one title (perhaps in different languages) and takes whatever form is @@ -361,7 +279,7 @@ This will distinguish the electronic work from the source text in citations and in catalogues which contain descriptions of both types of material.

-

The electronic work will also have an external name (its +

The electronic work will also have an external name (its filename or data set name) or reference number on the computer system where it resides at any time. This name is likely to change frequently, as new copies of the file are made on the computer @@ -372,18 +290,18 @@ files. For these reasons, these Guidelines strongly recommend that such names should not be used as the title for any electronic work.

-

Helpful guidance on the formulation of useful descriptive titles in +

Helpful guidance on the formulation of useful descriptive titles in difficult cases may be found in chapter 25 of ) or another national cataloguing code.

-

The elements author, editor, sponsor, funder, +

The elements author, editor, sponsor, funder, and principal, are specializations of the more general respStmt element. These elements are used to provide the statements of responsibility which identify the person(s) responsible for the intellectual or artistic content of an item and any corporate bodies from which it emanates.

-

Any number of such statements may occur within the title +

Any number of such statements may occur within the title statement. At a minimum, identify the author of the text and (where appropriate) the creator of the file. If the bibliographic description @@ -395,7 +313,7 @@ agencies. The name of the person responsible for physical data input need not normally be recorded, unless that person is also intellectually responsible for some aspect of the creation of the file.

-

Where the person whose responsibility is to be documented is not an +

Where the person whose responsibility is to be documented is not an author, sponsor, funding body, or principal researcher, the respStmt element should be used. This has two subcomponents: a name element identifying a responsible individual or organization, and a @@ -404,7 +322,7 @@ specific recommendations are made at this time as to appropriate content for the resp: it should make clear the nature of the responsibility concerned, as in the examples below.

-

Names given may be personal names or corporate names. Give all names +

Names given may be personal names or corporate names. Give all names in the form in which the persons or bodies wish to be publicly cited. This would usually be the fullest form of the name, including first names.Agencies compiling catalogues of @@ -412,53 +330,39 @@ machine-readable files are recommended to use available authority lists, such as the Library of Congress Name Authority List, for all common personal names.

-

Examples: - - Capgrave's Life of St. John Norbert: a - machine-readable transcription - compiled by P.J. Lucas - - - Two stories by Edgar Allen Poe: electronic version - Poe, Edgar Allen (1809-1849) - - compiled by James D. Benson - - - - Yogadarśanam (arthāt + <p>Examples: +<egXML xmlns="http://www.tei-c.org/ns/Examples"><titleStmt><title>Capgrave's Life of St. John Norbert: a + machine-readable transcriptioncompiled byP.J. Lucas +Two stories by Edgar Allen Poe: electronic versionPoe, Edgar Allen (1809-1849)compiled byJames D. Benson +Yogadarśanam (arthāt yogasūtrapūṭhaḥ): - a digital edition. - The Yogasūtras of Patañjali: - a digital edition. - Wellcome Institute for the History of Medicine - Dominik Wujastyk - Wieslaw Mical - data entry and proof correction - - Jan Hajic - conversion to TEI-conformant markup - -

- -
- -
The Edition Statement -

The editionStmt element is the second component of the + a digital edition.The Yogasūtras of Patañjali: + a digital edition.Wellcome Institute for the History of MedicineDominik WujastykWieslaw Micaldata entry and proof correctionJan Hajicconversion to TEI-conformant markup +

+ + + + + + +
+
+ The Edition Statement +

The editionStmt element is the second component of the fileDesc element. It is optional but recommended. It contains either phrases or more specialized elements identifying the edition and those responsible for it:

-

For printed texts, the word edition applies +

For printed texts, the word edition applies to the set of all the identical copies of an item produced from one master copy and issued by a particular publishing agency or a group of such agencies. A change in the identity of the distributing body or bodies does not normally constitute a change of edition, while a change in the master copy does.

-

For electronic texts, the notion of a master +

For electronic texts, the notion of a master copy is not entirely appropriate, since they are far more easily copied and modified than printed ones; nonetheless the term edition may be used for a particular state of a @@ -469,7 +373,8 @@ Synonymous terms used in these Guidelines are revision and update, by contrast, are used for minor changes to a file which do not amount to a new edition. -

No simple rule can specify how substantive +

+

No simple rule can specify how substantive changes have to be before they are regarded as producing a new edition, rather than a simple update. The general principle proposed here is that the production of a new edition entails a significant @@ -484,19 +389,19 @@ whereas the addition of new information (e.g. a linguistic analysis expressed in part-of-speech tagging, sound or graphics, referential links to external data sets) almost always does.

-

Clearly, there will always be borderline cases and the matter is +

Clearly, there will always be borderline cases and the matter is somewhat arbitrary. The simplest rule is: if you think that your file is a new edition, then call it such. An edition statement is optional for the first release of a computer file; it is mandatory for each later release, though this requirement cannot be enforced by the parser.

-

Note that all changes in a file considered significant, whether or not they are +

Note that all changes in a file considered significant, whether or not they are regarded as constituting a new edition or simply a new revision, should be independently noted in the revision description section of the file header (see section ).

-

The edition element should contain phrases describing the +

The edition element should contain phrases describing the edition or version, including the word edition, version, or equivalent, together with a number or date, or terms indicating difference from other editions such as new @@ -506,36 +411,30 @@ occur within the edition statement should be marked with the edition element may be used as elsewhere to supply any formal identification (such as a version number) for the edition.

-

One or more respStmt elements may also be used to supply +

One or more respStmt elements may also be used to supply statements of responsibility for the edition in question. These may refer to individuals or corporate bodies and can indicate functions such as that of a reviser, or can name the person or body responsible for the provision of supplementary matter, of appendices, etc., in a new edition. For further detail on the respStmt element, see section .

-

Some examples follow: - - Second draft, substantially - extended, revised, and corrected. - - -Student's edition, June 1987 - - New annotations by - George Brown - - -

- - -
- -
Type and Extent of File -

The extent element is the third component of the +

Some examples follow: +Second draft, substantially + extended, revised, and corrected. +Student's edition, June 1987New annotations byGeorge Brown +

+ + + + +
+
+ Type and Extent of File +

The extent element is the third component of the fileDesc element. It is optional.

-

For printed books, information about the carrier, such as the kind of +

For printed books, information about the carrier, such as the kind of medium used and its size, are of great importance in cataloguing procedures. The print-oriented rules for bibliographic description of an item's medium and extent need some re-interpretation when applied to @@ -547,70 +446,55 @@ are specifically aimed at facilitating transparent document storage and interchange, any purely machine-dependent information should be irrelevant as far as the file header is concerned.

-

This is particularly true of information about file-type +

This is particularly true of information about file-type although library-oriented rules for cataloguing often distinguish two types of computer file: data and programs. This distinction is quite difficult to draw in some cases, for example, hypermedia or texts with built in search and retrieval software.

-

Although it is equally system-dependent, some measure of the size of +

Although it is equally system-dependent, some measure of the size of the computer file may be of use for cataloguing and other practical purposes. Because the measurement and expression of file size is fraught with difficulties, only very general recommendations are possible; the element extent is provided for this purpose. It contains a phrase indicating the size or approximate size of the computer file in one of the following ways: - -in bytes of a specified length (e.g. 4000 16-bit bytes) -as falling within a range of categories, for example: - -less than 1 Mb -between 1 Mb and 5 Mb -between 6 Mb and 10 Mb -over 10 Mb -in terms of any convenient logical units (for example, -words or sentences, citations, paragraphs) -in terms of any convenient physical units (for example, +in bytes of a specified length (e.g. 4000 16-bit bytes)as falling within a range of categories, for example: +less than 1 Mbbetween 1 Mb and 5 Mbbetween 6 Mb and 10 Mbover 10 Mbin terms of any convenient logical units (for example, +words or sentences, citations, paragraphs)in terms of any convenient physical units (for example, blocks, disks, tapes)

-

The use of standard abbreviations for units of quantity is +

The use of standard abbreviations for units of quantity is recommended where applicable, here as elsewhere (see ).

-

Examples: +

Examples: between 1 and -2 Mb -4.2 MiB -4532 bytes -3200 sentences -Five 90 mm High Density Diskettes +2 Mb4.2 MiB4532 bytes3200 sentencesFive 90 mm High Density Diskettes

-

The measure element and its attributes may be used to supply +

The measure element and its attributes may be used to supply machine-tractable or normalized versions of the size or sizes given, as in the following example: - -About four megabytes -245 pages of source -material - +About four megabytes245 pages of source +material Note that when more than one measure is supplied in a single extent, the implication is that all the measurements apply to the whole resource.

- - -
- -
Publication, Distribution, Licensing, etc. -

The publicationStmt element is the fourth component of the + + + +

+
+ Publication, Distribution, Licensing, etc. +

The publicationStmt element is the fourth component of the fileDesc element and is mandatory. Its function is to name the agency by which a resource is made available (for example, a publisher or distributor) and to supply any additional information about the way in which it is made available such as licensing conditions, identifying numbers, etc. It may contain either a simple prose description organized as one or more paragraphs, or the more specialised elements described below.

-

A structured publication statement must begin with one of the following elements: +

A structured publication statement must begin with one of the following elements: These elements form the model.publicationStmtPart.agency class; if the agency making the resource available is unknown, but other structured information about it is available, an explicit statement such as publisher unknown should be used.

- -

The publisher is the person or institution by whose +

The publisher is the person or institution by whose authority a given edition of the file is made public. The distributor is the person or institution from whom copies of the text may be obtained. Where a text is not considered formally @@ -618,85 +502,59 @@ published, but is nevertheless made available for circulation by some individual or organization, this person or institution is termed the release authority.

-

Whichever of these elements is chosen, it may be followed by one or more of the following elements, which together form the model.publicationStmtPart.detail class +

Whichever of these elements is chosen, it may be followed by one or more of the following elements, which together form the model.publicationStmtPart.detail class

-

Here is a simple example: - - Oxford University Press - Oxford 1989 - 0-19-254705-4 -

Copyright 1989, Oxford University Press

+

Here is a simple example: +Oxford University PressOxford19890-19-254705-4

Copyright 1989, Oxford University Press

- -

The model.publicationStmtPart.detail elements all supply additional information relating to the +

The model.publicationStmtPart.detail elements all supply additional information relating to the the publisher, distributor, or release authority immediately preceding them. In the following example, Benson is identified as responsible for distribution of some resource at the date and place cited: - - James D. Benson - London 1994 + James D. BensonLondon1994

-

+

A resource may have (for example) both a publisher and a distributor, or more than one publisher each using different identifiers for the same resource, and so on. For this reason, the sequence of at least one model.publicationStmtPart.agency element followed by zero or more model.publicationStmtPart.detail elements may be repeated as often as necessary.

-

The following example shows a resource published by one agency (Sigma Press) at one address and date, which is also distributed by another (Oxford Text Archive), with a specified identifier and a different date: - - Sigma Press -

- 21 High Street, - Wilmslow, - Cheshire M24 3DF -
- 1991 - - Oxford Text Archive - 1256 - -

Available with prior consent of depositor for - purposes of academic research and teaching only.

- -1994 - - +

The following example shows a resource published by one agency (Sigma Press) at one address and date, which is also distributed by another (Oxford Text Archive), with a specified identifier and a different date: Sigma Press

21 High Street,Wilmslow,Cheshire M24 3DF
1991Oxford Text Archive1256

Available with prior consent of depositor for + purposes of academic research and teaching only.

1994

-

The date element used within publicationStmt always refers to the date of publication, first distribution, or initial release. +

The date element used within publicationStmt always refers to the date of publication, first distribution, or initial release. If the text was created at some other date, this may be recorded using the creation element within the profileDesc element. Other useful dates (such as dates of collection of data) may be given using a note in the notesStmt element.

- -

The availability element may be used, as above, to provide a simple prose statement of any restrictions concerning the distribution of the resource. Alternatively, a more formal statement of the licensing conditions applicable may be provided using the licence element: - - University of Victoria Humanities Computing and Media Centre - Victoria, BC 2011 +

The availability element may be used, as above, to provide a simple prose statement of any restrictions concerning the distribution of the resource. Alternatively, a more formal statement of the licensing conditions applicable may be provided using the licence element: + University of Victoria Humanities Computing and Media CentreVictoria, BC2011 Distributed under a Creative Commons Attribution-ShareAlike 3.0 Unported License Note here the use of the target attribute to point to a location from which the licence document itself may be obtained. Alternatively, the licence document may simply be contained within the licence element.

- - - - -
- -
The Series Statement -

The seriesStmt element is the fifth component of the + + + + + + + + +

+
+ The Series Statement +

The seriesStmt element is the fifth component of the fileDesc element and is optional.

-

In bibliographic parlance, a series may be defined in +

In bibliographic parlance, a series may be defined in one of the following ways: - -A group of separate items related to one another by the fact +A group of separate items related to one another by the fact that each item bears, in addition to its own title proper, a collective title applying to the group as a whole. The -individual items may or may not be numbered. -Each of two or more volumes of essays, lectures, articles, -or other items, similar in character and issued in sequence. -A separately numbered sequence of volumes within a series or +individual items may or may not be numbered.Each of two or more volumes of essays, lectures, articles, +or other items, similar in character and issued in sequence.A separately numbered sequence of volumes within a series or serial. A seriesStmt element may contain a prose description or one or more of the following more specific elements:

-

The idno may be used to supply any identifying number +

The idno may be used to supply any identifying number associated with the item, including both standard numbers such as an ISSN and particular issue numbers. (Arabic numerals separated by punctuation are recommended for this purpose: 6.19.33, @@ -704,55 +562,44 @@ for example, rather than VI/xix:33). Its type attribute is the number further, taking the value ISSN for an ISSN for example. Multiple seriesStmt elements may be supplied if the TEI document is associated with more than one series.

-

Examples: - - Machine-Readable Texts for the Study of - Indian Literature - ed. by Jan Gonda - 1.2 - 0 345 6789 - - -

- -
The Notes Statement -

The notesStmt element is the sixth component of the +

Examples: +Machine-Readable Texts for the Study of + Indian Literatureed. byJan Gonda1.20 345 6789 +

+
+
+ The Notes Statement +

The notesStmt element is the sixth component of the fileDesc element and is optional. If used, it contains one or more note elements, each containing a single piece of descriptive information of the kind treated as general notes in traditional bibliographic descriptions.

-

Some information found in the notes area in conventional bibliography +

Some information found in the notes area in conventional bibliography has been assigned specific elements in these Guidelines; in particular the following items should be tagged as indicated, rather than as general notes: - -the nature, scope, artistic form, or purpose of the file; also +the nature, scope, artistic form, or purpose of the file; also the genre or other intellectual category to which it may belong: e.g. Text types: newspaper editorials and reportage, science fiction, westerns, and detective stories. These should be formally described within the profileDesc element -(section ). -an abstract or summary of the content of a document which has been supplied by the encoder because no such abstract forms part of the content of the source. This should be supplied in the abstract element within the profileDesc element (section ). -summary description providing a factual, non-evaluative +(section ).an abstract or summary of the content of a document which has been supplied by the encoder because no such abstract forms part of the content of the source. This should be supplied in the abstract element within the profileDesc element (section ).summary description providing a factual, non-evaluative account of the subject content of the file: e.g. Transcribes interviews on general topics with native speakers of English in 17 cities during the spring and summer of 1963. These should also be formally described within the profileDesc element -(section ). -bibliographic details relating to the source or sources of +(section ).bibliographic details relating to the source or sources of an electronic text: e.g. Transcribed from the Norton facsimile of the 1623 Folio. These should be formally described in the sourceDesc element -(section ). -further information relating to publication, distribution, +(section ).further information relating to publication, distribution, or release of the text, including sources from which the text may be obtained, any restrictions on its use or formal terms on its availability. These should be placed in the appropriate division of the publicationStmt element -(section ). -publicly documented numbers associated with the file: e.g. +(section ).publicly documented numbers associated with the file: e.g. ICPSR study number 1803 or Oxford Text Archive text number 1243. These should be placed in an idno element within the appropriate division of the @@ -762,59 +609,37 @@ Serial Numbers (ISSN), International Standard Book Numbers that uniquely identify an item, should be treated in the same way, rather than as specialized bibliographic notes.

-

Nevertheless, the notesStmt element may be used to record +

Nevertheless, the notesStmt element may be used to record potentially significant details about the file and its features, e.g.: - -dates, when they are relevant to the content or condition of the +dates, when they are relevant to the content or condition of the computer file: e.g. manual dated 1983, Interview wave I: -Apr. 1989; wave II: Jan. 1990 -names of persons or bodies connected with the technical production, +Apr. 1989; wave II: Jan. 1990names of persons or bodies connected with the technical production, administration, or consulting functions of the effort which produced the file, if these are not named in statements of responsibility in the title or edition statements of the file description: -e.g. Historical commentary provided by Mark Cohen -availability of the file in an additional medium or information not +e.g. Historical commentary provided by Mark Cohenavailability of the file in an additional medium or information not already recorded about the availability of documentation: -e.g. User manual is loose-leaf in eleven paginated sections -language of work and abstract, if not encoded in the langUsage +e.g. User manual is loose-leaf in eleven paginated sectionslanguage of work and abstract, if not encoded in the langUsage element, e.g. Text in English with -summaries in French and German -The unique name assigned to a serial by the International Serials -Data System (ISDS), if not encoded in an idno -lists of related publications, either describing the source itself, +summaries in French and GermanThe unique name assigned to a serial by the International Serials +Data System (ISDS), if not encoded in an idnolists of related publications, either describing the source itself, or concerned with the creation or use of the electronic work, e.g. -Texts used in -

-

Each such item of information may be tagged using the +Texts used in

+

Each such item of information may be tagged using the general-purpose note element, which is described in section . Groups of notes are contained within the notesStmt element, as in the following example: - - Historical commentary provided by Mark Cohen. - OCR scanning done at University of Toronto. - +Historical commentary provided by Mark Cohen.OCR scanning done at University of Toronto. There are advantages, however, to encoding such information with more precise elements elsewhere in the TEI header, when such elements are available. For example, the notes above might be encoded as follows: - - - … - - Mark Cohen - historical commentary - - - University of Toronto - OCR scanning - - - - +…Mark Cohenhistorical commentaryUniversity of TorontoOCR scanning +

-
- -
The Source Description -

The sourceDesc element is the seventh and final component of +

+
+ The Source Description +

The sourceDesc element is the seventh and final component of the fileDesc element. It is a mandatory element and is used to record details of the source or sources from which a computer file is derived. This might be a printed text or manuscript, another computer @@ -823,70 +648,41 @@ these. An electronic file may also have no source, if what is being catalogued is an original text created in electronic form.

-

The sourceDesc element may contain little more than a +

The sourceDesc element may contain little more than a simple prose description, or a brief note stating that the document has no source: - -

Born digital.

-

-

Alternatively, it may contain elements drawn from the following +

Born digital.

+

Alternatively, it may contain elements drawn from the following three classes: - - - - - +

-

These classes make available by default a range of ways of +

These classes make available by default a range of ways of providing bibliographic citations which specify the provenance of the text. For written or printed sources, the source may be described in the same way as any other bibliographic citation, using one of the following elements: - - - - - - + These elements are described in more detail in section . Using them, a source might be described in very simple terms: - - The first folio of Shakespeare, prepared by - Charlton Hinman (The Norton Facsimile, 1968) - +The first folio of Shakespeare, prepared by + Charlton Hinman (The Norton Facsimile, 1968) or with more elaboration: - - - - Eugène Sue - Martin, l'enfant trouvé - Mémoires d'un valet de chambre - - Bruxelles et Leipzig - C. Muquardt - 1846 - - - +Eugène SueMartin, l'enfant trouvéMémoires d'un valet de chambreBruxelles et LeipzigC. Muquardt1846

-

When the header describes a text derived from some pre-existing +

When the header describes a text derived from some pre-existing TEI-conformant or other digital document, it may be simpler to use the following element, which is designed specifically for documents derived from texts which were born digital: - - - + For further discussion see section .

-

When the module for manuscript description is included in a schema, +

When the module for manuscript description is included in a schema, this class also makes available the following element: - - - + This element enables the encoder to record very detailed information about one or more manuscript or analogous sources, as further discussed in .

-

The model.sourceDescPart class also makes +

The model.sourceDescPart class also makes available additional elements when additional modules are included. For example, when the spoken module is included, the @@ -896,8 +692,7 @@ is derived from a spoken text rather than a written one: Full descriptions of these elements and their contents are given in section .

- -

A single electronic text may be derived from multiple source +

A single electronic text may be derived from multiple source documents, in whole or in part. The sourceDesc may therefore contain a listBibl element grouping together bibl, biblStruct, or msDesc elements for each of the @@ -906,236 +701,163 @@ sources concerned. It is also possible to repeat the attribute described in section may be used to associate parts of the encoded text with the bibliographic element from which it derives in either case.

- -

The source description may also include lists of names, persons, +

The source description may also include lists of names, persons, places, etc. when these are considered to form part of the source for an encoded document. When such information is recorded using the specialized elements discussed in the namesdates module (), the class model.listLike makes available the following elements to hold such information: - - - - - - -

- - - -
- -
TEI documents derived from other TEI documents -

When a TEI document (call it B) is derived not from a + +

+ + + + + + +
+
+ TEI documents derived from other TEI documents +

When a TEI document (call it B) is derived not from a printed source but from another TEI file (call it A), then the five sections of A's file header will need to be incorporated into the new header for B as indicated below: - - - A's file description should be copied into the +A's file description should be copied into the sourceDesc section of B's file description, enclosed within - a biblFull element - - A's profileDesc should be copied into B's, in + a biblFull elementA's profileDesc should be copied into B's, in principle unchanged; it may however be expanded by project-specific - information relating to B. - - A's encoding practice may or (more likely) may not be the same + information relating to B.A's encoding practice may or (more likely) may not be the same as B's. Since the object of the encoding description is to define the relationship between the current file and its source, in principle only changes in encoding practice between A and B need be documented in B. The relationship between A and its source(s) is then only recoverable from the original header of A. In practice it may be more convenient to create a new complete - encodingDesc for B based on A's. - - B is a new computer file, with a different source than A's + encodingDesc for B based on A's.B is a new computer file, with a different source than A's source (namely, A). Thus it is unlikely that metadata from other schemes about A or its source can be copied wholesale to B, although - there may be similarities. - - B is a new computer file, and should therefore have a new + there may be similarities.B is a new computer file, and should therefore have a new revision description. If, however, it is felt useful to include some information from A's revisionDesc, for example dates of major updates or versions, such information must be clearly marked - as relating to A rather than to B. - + as relating to A rather than to B. This concludes the discussion of the fileDesc element and its contents. -

-
- -
The Encoding Description -

The encodingDesc element is the second major subdivision of +

+
+
+
+ The Encoding Description +

The encodingDesc element is the second major subdivision of the TEI header. It specifies the methods and editorial principles which governed the transcription or encoding of the text in hand and may also include sets of coded definitions used by other components of the header. Though not formally required, its use is highly recommended. - - - + The encoding description may contain any combination of paragraphs of text, marked up using the p element, along with more specialized elements taken from the model.encodingDescPart class. By default, this class makes available the following elements: - - - - - - - - - - - - -Each of these elements is further described +Each of these elements is further described in the appropriate section below. Other modules have the ability to extend this class; examples are noted in section

- - - - - - - - - - - - - -
The Project Description -

The projectDesc element may be used to describe, in prose, + + + + + + + + + + + + +

+ The Project Description +

The projectDesc element may be used to describe, in prose, the purpose for which a digital resource was created, together with any other relevant information concerning the process by which it was assembled or collected. This is of particular importance for corpora or miscellaneous collections, but may be of use for any text, for example to explain why one kind of encoding practice has been followed rather than another. - - -

-

For example: - - -

Texts collected for use in the - Claremont Shakespeare Clinic, June 1990.

- -

- - -
- -
The Sampling Declaration -

The samplingDecl element may be used to describe, in +

+

For example: +

Texts collected for use in the + Claremont Shakespeare Clinic, June 1990.

+ + + +
+
+ The Sampling Declaration +

The samplingDecl element may be used to describe, in prose, the rationale and methods used in selecting texts, or parts of text, for inclusion in the resource. - - - + It should include information about such matters as - -the size of individual samples -the method or methods by which they were selected -the underlying population being sampled -the object of the sampling procedure used +the size of individual samplesthe method or methods by which they were selectedthe underlying population being sampledthe object of the sampling procedure used but is not restricted to these. - -

Samples of 2000 words taken from the beginning of the text.

-

-

It may also include a simple +

Samples of 2000 words taken from the beginning of the text.

+

It may also include a simple description of any parts of the source text included or excluded. - -

Text of stories only has been transcribed. Pull quotes, captions, +

Text of stories only has been transcribed. Pull quotes, captions, and advertisements have been silently omitted. Any mathematical expressions requiring symbols not present in the ISOnum or ISOpub entity sets have been omitted, and their place marked with a GAP - element.

-

-

A sampling declaration which applies to more than one text or + element.

+

A sampling declaration which applies to more than one text or division of a text need not be repeated in the header of each such text. Instead, the decls attribute of each text (or subdivision of the text) to which the sampling declaration applies may be used to supply a cross-reference to it, as further described in section .

- - -
- -
-The Editorial Practices Declaration -

The editorialDecl element is used to + + + +

+
+ The Editorial Practices Declaration +

The editorialDecl element is used to provide details of the editorial practices applied during the encoding of a text. - - -It may contain a prose description only, or one or more of a set of +It may contain a prose description only, or one or more of a set of specialized elements, members of the TEI model.editorialDeclPart class. Where an encoder wishes to record an editorial policy not specified above, this may be done by adding a new element to this class, using the mechanisms -discussed in chapter .

Some of these policy elements carry attributes to support automated +discussed in chapter .

+

Some of these policy elements carry attributes to support automated processing of certain well-defined editorial decisions; all of them contain a prose description of the editorial principles adopted with respect to the particular feature concerned. Examples of the kinds of questions which these descriptions are intended to answer are given in -the list below. - - - - - -

+the list below.

Was the text corrected during or after data capture? If so, were corrections made silently or are they marked using the tags described in section ? What principles have been adopted with respect to omissions, truncations, dubious corrections, alternate readings, false starts, repetitions, -etc.?

- - - - - -

+etc.?

Was the text normalized, for example by regularizing any non-standard spellings, dialect forms, etc.? If so, were normalizations performed silently or are they marked using the tags described in section ? What authority was used for the regularization? Also, what principles were used when normalizing numbers to provide the standard values for the value attribute described in section and what format used for -them?

 - - - - - -

Are punctuation marks present in the original source retained? Are they identified with the element pc, or implied by markup? If retained, how are they placed with respect to related elements? For example, do commas and periods appear inside or outside elements marking phrases and sentences?

 - - - - - -

+them?

Are punctuation marks present in the original source retained? Are they identified with the element pc, or implied by markup? If retained, how are they placed with respect to related elements? For example, do commas and periods appear inside or outside elements marking phrases and sentences?

How were quotation marks processed? Are apostrophes and quotation marks distinguished? How? Are quotation marks retained as content in the text or replaced by markup? Are there any special conventions regarding for example the use of single or double quotation marks when nested? Is the file consistent in its practice or has this not been checked? See section for discussion of ways in which -quotation marks may be encoded.

 - - - - - -

+quotation marks may be encoded.

Does the encoding distinguish soft and hard hyphens? What principle has been adopted with respect to end-of-line hyphenation @@ -1143,23 +865,11 @@ where source lineation has not been retained? Have soft hyphens been silently removed, and if so what is the effect on lineation and pagination? See section for discussion of ways in which hyphenation may be encoded. -

 - - - - - -

+

How is the text segmented? If s or seg segmentation units have been used to divide up the text for analysis, how are they marked and how was the -segmentation arrived at?

 - - - - - -

In most cases, attributes bearing standardized values (such as the +segmentation arrived at?

In most cases, attributes bearing standardized values (such as the when or when-iso attribute on dates) should conform to a defined W3C or ISO datatype. In cases where this is not appropriate, this element may be @@ -1171,86 +881,68 @@ format are its values presented? If the when, when-iso, or similar attributes described in sections and has been used, are the values given supposed to match a subset of the formats -available?-->

 - - - - - -

+available?-->

Has any analytic or interpretive information been provided—that is, information which is felt to be non-obvious, or potentially contentious? If so, how was it generated? How was it encoded? If feature-structure analysis has been used, are fsdDecl elements (section ) -present?

 -

Any information about the editorial principles applied not falling +present?

+

Any information about the editorial principles applied not falling under one of the above headings should be recorded in a distinct list of items. Experience shows that a full record should be kept of decisions relating to editorial principles and encoding practice, both for future users of the text and for the project which produced the text in the first instance. Some simple examples follow: - -

s elements mark orthographic sentences and +

s elements mark orthographic sentences and are numbered sequentially within their parent div element -

- -

The part of speech analysis applied throughout section 4 was - added by hand and has not been checked.

- - -

Errors in transcription controlled by using the - WordPerfect spelling checker.

- - -

All words converted to Modern American spelling following - Websters 9th Collegiate dictionary.

- - -

All opening quotation marks represented by entity reference +

The part of speech analysis applied throughout section 4 was + added by hand and has not been checked.

Errors in transcription controlled by using the + WordPerfect spelling checker.

All words converted to Modern American spelling following + Websters 9th Collegiate dictionary.

All opening quotation marks represented by entity reference odq; all closing quotation marks - represented by entity reference cdq.

- - -

- - - -

An editorial practices declaration which applies to more than one text + represented by entity reference cdq.

 +

+ + + + + + + + + + + + +

An editorial practices declaration which applies to more than one text or division of a text need not be repeated in the header of each such text. Instead, the decls attribute of each text (or subdivision of the text) to which it applies may be used to supply a cross-reference to it, as further described in section . -

- -
The Tagging Declaration -

The tagsDecl element is used to record +

+
+
+ The Tagging Declaration +

The tagsDecl element is used to record the following information about the tagging used within a particular document: - -the namespace to which elements appearing within the transcribed -text belong. -how often particular elements appear within the text, so that -a recipient can validate the integrity of a text during interchange. -any comment relating to the usage of particular elements not -specified elsewhere in the header. -a default rendition applicable to all instances +the namespace to which elements appearing within the transcribed +text belong.how often particular elements appear within the text, so that +a recipient can validate the integrity of a text during interchange.any comment relating to the usage of particular elements not +specified elsewhere in the header.a default rendition applicable to all instances of an element.

-

This information is conveyed by the following elements: - - - - - -

The tagsDecl element is descriptive, rather than prescriptive: if used, it simply documents +

This information is conveyed by the following elements: +

+

The tagsDecl element is descriptive, rather than prescriptive: if used, it simply documents practice in the TEI document containing it. The elements constituting a TEI customization file (discussed in chapter ) by contrast document expected practice in a number of documents, and may thus be used prescriptively. If there is an inconsistency between the actual state of a document and what is documented by its tagsDecl, then the latter should be corrected. If there is an inconsistency between a document and what is required by the customization file, or a schema derived from it, then it will usually be the document that requires correction.

-

The tagsDecl element consists of an optional sequence of +

The tagsDecl element consists of an optional sequence of rendition elements, each of which must bear a unique identifier, followed by an optional sequence of one or more namespace elements, each of which contains a series of @@ -1259,29 +951,22 @@ namespace occurring within the associated text element. Note that these tagUsage elements must be nested within a namespace element, and cannot appear directly within the tagsDecl element.

- -
Rendition -

The rendition element allows the encoder to specify how +

+ Rendition +

The rendition element allows the encoder to specify how one or more elements are rendered in the original source in any of the following ways: - -using an informal prose description -using a standard stylesheet language such as CSS or -XSL-FO -using a project-defined formal language -

-

One or more such specifications may be associated with elements of +using an informal prose descriptionusing a standard stylesheet language such as CSS or +XSL-FOusing a project-defined formal language

+

One or more such specifications may be associated with elements of a document in two ways: - -the selector attribute on any rendition element may be used to select a collection of elements to which it applies -the global rendition attribute may be used on any +the selector attribute on any rendition element may be used to select a collection of elements to which it appliesthe global rendition attribute may be used on any element to -indicate its rendition, overriding or complementing any supplied default value - +indicate its rendition, overriding or complementing any supplied default value The global rend and style attributes may also be used to describe the rendering of an element. See further .

-

The content of a rendition element may +

The content of a rendition element may describe the appearance of the source material using prose, a project-defined formal language, or any standard languages such as the Cascading Stylesheet Language () or the XML @@ -1292,76 +977,42 @@ supplied within the encodingDesc to specify which of these applies by default, and it may be overridden for one or more specific rendition elements using the scheme attribute.

- -

The recommended way to indicate a default rendition on one or more elements is to use the selector attribute together with the scheme attribute on rendition. For example, suppose that all paragraphs in the front of a text appear in a large font, with significant top and bottom margins, while paragraphs in the main body are in regular font size and have no top and bottom margins. The use of selector together with scheme provides an efficient way to specify the distinct styling for distinct contexts of the paragraph by means of CSS selectors: - - +

The recommended way to indicate a default rendition on one or more elements is to use the selector attribute together with the scheme attribute on rendition. For example, suppose that all paragraphs in the front of a text appear in a large font, with significant top and bottom margins, while paragraphs in the main body are in regular font size and have no top and bottom margins. The use of selector together with scheme provides an efficient way to specify the distinct styling for distinct contexts of the paragraph by means of CSS selectors: + font-size: 110%; margin-top: 0.5em; margin-bottom: 0.5em; - - - - + + font-size: 100%; margin-top: 0; margin-bottom: 0; - - +

- -

In the following extended example we consider how to capture the +

In the following extended example we consider how to capture the appearance of a typical early 20th century titlepage, such as that in the following figure:

Elements for the encoding of the information on a titlepage are presented in ; here we consider how we might go about encoding some of the visual information as well, using the rendition element and its corresponding attributes.

-

First we define a rendition element for each aspect of the source +

First we define a rendition element for each aspect of the source page rendition that we wish to retain. Details of CSS are given in ; we use it here simply to provide a vocabulary with which to describe such aspects as font size and style, letter and line spacing, colour, etc. Note that the purpose of this encoding is to describe the original, rather than specify how it should be reproduced, although the two are obviously closely linked. - - - - text-align: center; - font-size: small; - font-size: large; - font-size: x-large; - font-size: xx-large - letter-spacing: +3pt; - line-height: 150%; - line-height: 200%; - color: red; - -

-

The global rendition attribute can now be used to + text-align: center;font-size: small;font-size: large;font-size: x-large;font-size: xx-largeletter-spacing: +3pt;line-height: 150%;line-height: 200%;color: red; +

+

The global rendition attribute can now be used to specify on any element which of the above rendition features apply to it. For example, a title page might be encoded as follows: - - - - THE POEMS - OF - ALGERNON CHARLES SWINBURNE - IN SIX VOLUMES - - VOLUME I. +THE POEMSOFALGERNON CHARLES SWINBURNEIN SIX VOLUMES VOLUME I. POEMS AND BALLADS FIRST SERIES - - - - LONDON - CHATTO & WINDUS - 1904 - - -

-

When CSS is used as the style definition language, the scope + LONDONCHATTO & WINDUS1904

+

When CSS is used as the style definition language, the scope attribute may be used to specify CSS pseudo-elements. These pseudo-elements are used to specify styling applicable to only a portion of the given text. For example, the first-letter @@ -1371,29 +1022,24 @@ element, while the before and "content" property to add additional characters which need to be added before or after the element content to make it more closely resemble the appearance of the source.

-

For example, assuming that a text has been encoded using the q +

For example, assuming that a text has been encoded using the q element to enclose passages in quotation marks, but the quotation marks themselves have been routinely omitted from the encoding, a set of renditions such as the following: - -content: -'“'; -content: -'”'; - + content: +'“';content: +'”'; might be used to predefine pseudo-elements quoteBefore and quoteAfter. Where a q element is actually rendered in the source with initial and final quotation marks, it may then be encoded as follows: - -Four score and seven years -ago... - +Four score and seven years +ago...

-
- -
Tag Usage -

As noted above, each namespace element, if present, +

+
+ Tag Usage +

As noted above, each namespace element, if present, should contain up to one occurrence of a tagUsage element for each element type from the given namespace that occurs within the outermost text element associated with the @@ -1406,22 +1052,21 @@ a count of the number of occurrences of this element within the text, which is given as the value of its occurs attribute. It may also be used to hold any additional usage information, which is supplied as running prose within the element itself.

-

For example: +

For example: Used only to mark English words italicised in the copy text. This indicates that the hi element appears a total of 28 times in the text element in question, and that the encoder has used it to mark italicised English words only.

-

The withId attribute may optionally be used to specify +

The withId attribute may optionally be used to specify how many of the occurrences of the element in question bear a value for the global xml:id attribute, as in the following example: Marks page breaks in the York (1734) edition only This indicates that the pb element occurs 321 times, on each of which an identifier is provided.

- -

The content of the tagUsage element is not susceptible of +

The content of the tagUsage element is not susceptible of automatic processing. It should not therefore be used to hold information for which provision is already made by other components of the encoding description. A TEI-conformant document is not required to @@ -1430,61 +1075,43 @@ attributes, but if it does, then the counts provided must correspond with the number of such elements present in the associated text. - - - - - - - -

-
- -
The Default Style Definition Language Declaration -

The content of the rendition element, the value of its +

+
+
+
+ The Default Style Definition Language Declaration +

The content of the rendition element, the value of its selector attribute, and the value of the style attribute are expressed using one of a small number of formally defined style definition languages. For ease of processing, it is strongly recommended to use a single such language throughout an encoding project, although the TEI system permits a mixture.

-

The element styleDefDecl, a sibling of the +

The element styleDefDecl, a sibling of the tagsDecl element, is used to supply the name of the default style definition language. The name is supplied as the value of the scheme attribute and may take any of the following values: - -Informal free text description -Cascading Stylesheet Language -Extensible Stylesheet Language Formatting Objects -A user-defined formal description -language . The schemeVersion attribute may be +Informal free text descriptionCascading Stylesheet LanguageExtensible Stylesheet Language Formatting ObjectsA user-defined formal description +language. The schemeVersion attribute may be used to supply the precise version of the style definition language used, and the content of this element, if any, may supply additional information.

-

When the style attribute is used, its value must always +

When the style attribute is used, its value must always be expressed using whichever default style definition language is in force. If more than one occurrence of the styleDefDecl is provided, there will be more than one default available, and the decls attribute must be used to select which is applicable in a given context, as discussed in section .

-
- -
The Reference System Declaration -

The refsDecl element is used to +

+
+ The Reference System Declaration +

The refsDecl element is used to document the way in which any standard referencing scheme built into the encoding works. - - - + It may contain either a series of prose paragraphs or the following specialized elements: - - - - - - - + Note that not all possible referencing schemes are equally easily supported by current software systems. A choice must be made between the convenience of the encoder and the likely efficiency of the @@ -1492,23 +1119,19 @@ particular software applications envisaged, in this context as in many others. For a more detailed discussion of referencing systems supported by these Guidelines, see section below.

-

A referencing scheme may be described in one of four ways using this +

A referencing scheme may be described in one of four ways using this element: - -as a prose description -as nested set of citation structure declarations -as a series of pairs of regular expressions and XPaths -as a concatenation of sequentially organized +as a prose descriptionas nested set of citation structure declarationsas a series of pairs of regular expressions and XPathsas a concatenation of sequentially organized milestones Each method is described in more detail below. Only one method can be used within a single refsDecl element.

-

More than one refsDecl element can be included in the +

More than one refsDecl element can be included in the header if more than one canonical reference scheme is to be used in the same document, but the current proposals do not check for mutual inconsistency.

- -
Prose Method -

The referencing scheme may be specified within the refsDecl +

+ Prose Method +

The referencing scheme may be specified within the refsDecl by a simple prose description. Such a description should indicate which elements carry identifying information, and whether this information is represented as attribute values or as content. Any special rules about @@ -1517,9 +1140,8 @@ reference string should also be specified here. Such a prose description cannot be processed automatically, and this method of specifying the structure of a canonical reference system is therefore not recommended for automatic processing.

-

For example: - -

The n attribute of each text in this corpus carries a +

For example: +

The n attribute of each text in this corpus carries a unique identifying code for the whole text. The title of the text is held as the content of the first head element within each text. The n attribute on each div1 and @@ -1528,42 +1150,36 @@ not recommended for automatic processing.

numerals, and yyy the section number in arabic. Line breaks are marked by empty lb elements, each of which includes the through line number in Casaubon's edition as the value of its - n attribute.

-

The through line number and the text identifier uniquely identify + n attribute.

The through line number and the text identifier uniquely identify any line. A canonical reference may be made up by concatenating the n values from the text, div1, or - div2 and calculating the line number within each part.

-

- -
-Search-and-Replace Method -

This method often requires a significant investment of effort + div2 and calculating the line number within each part.

+
+
+ Search-and-Replace Method +

This method often requires a significant investment of effort initially, but permits extremely flexible addressing. For details, see section . - - - -

- -
Milestone Method -

This method is appropriate when only milestone + +

+
+
+ Milestone Method +

This method is appropriate when only milestone tags (see section ) are available to provide the required referencing information. It does not provide any abilities which cannot be mimicked by the search-and-replace referencing method discussed in the previous section, but in the cases where it applies, it provides a somewhat simpler notation.

-

A reference based on milestone tags concatenates the values specified +

A reference based on milestone tags concatenates the values specified by one or more such tags. Since each tag marks the point at which a value changes, it may be regarded as specifying the refState of a variable. A reference declaration using this method therefore specifies the individual components of the canonical reference as a sequence of refState elements: - - - -

-

For example, the reference Matthew 12:34 might be thought of +

+

For example, the reference Matthew 12:34 might be thought of as representing the state of three variables: the book variable is in state Matthew; the chapter variable is in state 12, and the verse variable is @@ -1578,7 +1194,7 @@ right through the text, monitoring changes in the state of each of these three variables as it does so. When all three are simultaneously in the required state, the desired point will have been reached. There may of course be several such points.

-

The delim and length attributes are used to +

The delim and length attributes are used to specify components of a canonical reference using this method in exactly the same way as for the stepwise method described in the preceding section. The other attributes are used to determine which instances of @@ -1589,17 +1205,13 @@ identical to those of the refState element in question. The value for the new state may be given explicitly by the n attribute on the milestone element, or it may be implied, if the n attribute is not specified.

-

For example, for canonical references in the form xx.yyy where +

For example, for canonical references in the form xx.yyy where the xx represents the page number in the first edition, and yyy the line number within this page, a reference system declaration such as the following would be appropriate: - - - - + This implies that milestone tags of the form - - + will be found throughout the text, marking the positions at which page and line numbers change. Note that no value has been specified for the n attribute on the second milestone tag above; this implies @@ -1608,57 +1220,44 @@ For more detail on the use of milestone tags, see section .

-

The milestone referencing scheme, though conceptually simple, is not +

The milestone referencing scheme, though conceptually simple, is not supported by a generic XML parser. Its use places a correspondingly greater burden of verification and accuracy on the encoder.

- - - - - - - - - - - - - - -

A reference system declaration which applies to more than one text or + + + + + + + + + + + +

A reference system declaration which applies to more than one text or division of a text need not be repeated in the header of each such text. Instead, the decls attribute of each text (or subdivision of the text) to which the declaration applies may be used to supply a cross-reference to it, as further described in section .

-
- -
The Classification Declaration -

The classDecl element is used to group +

+
+
+ The Classification Declaration +

The classDecl element is used to group together definitions or sources for any descriptive classification schemes used by other parts of the header or elsewhere in the document. Each such scheme is represented by a taxonomy element, which may contain either a simple bibliographic citation, or a definition of the descriptive typology concerned; the following elements are used in defining a descriptive classification scheme: - - - - - - + The taxonomy element has two slightly different, but related, functions. For well-recognized and documented public classification schemes, such as Dewey or other published descriptive thesauri, it contains simply a bibliographic citation indicating where a full description of a particular taxonomy may be found. - - - - Dewey Decimal Classification - Abridged Edition 12 - - +Dewey Decimal ClassificationAbridged Edition 12 For less easily accessible schemes, the taxonomy element contains a description of the taxonomy itself as well as an optional bibliographic citation. The description consists of a number of @@ -1672,111 +1271,42 @@ of a set of situational parameters (see further section ; if the corpus module is not included in a schema, this class is empty and the catDesc element may contain only plain text.

-

If the category is subdivided, each subdivision is represented by a +

If the category is subdivided, each subdivision is represented by a nested category element, having the same structure. Categories may be nested to an arbitrary depth in order to reflect the hierarchical structure of the taxonomy. Each category element bears a unique xml:id attribute, which is used as the target for catRef elements referring to it. - - Brown Corpus - - Press Reportage - Daily - Sunday - National - Provincial - Political - Sports - - Religion - Books - Periodicals and tracts - -

-

Linkage between a particular text and a category within such a +Brown CorpusPress ReportageDailySundayNationalProvincialPoliticalSportsReligionBooksPeriodicals and tracts

+

Linkage between a particular text and a category within such a taxonomy is made by means of the catRef element within the textClass element, as described in section . Where finer-grained analysis is desired, the ana attribute on an element in the text could point to a category, as in the following abbreviated example: - - - - Poetry - - Sonnet - - Shakespearean Sonnet - - - Petrarchan Sonnet - - - - Metrical Categories - - Metrical Feet - - Iambic - - - trochaic - - - - Number of feet - - >Pentameter - - - >Tetrameter - - - - - - - - Shall I compare thee to a summer's day - - - -

-

Where the taxonomy permits of classification along more + PoetrySonnetShakespearean SonnetPetrarchan SonnetMetrical CategoriesMetrical FeetIambictrochaicNumber of feet>Pentameter>TetrameterShall I compare thee to a summer's day +

+

Where the taxonomy permits of classification along more than one dimension, more than one category will be referenced by a particular catRef, as in the following example, which identifies a text with the sub-categories Daily, National, and Political within the category Press Reportage as defined above.

-

A single category may contain more than one +

A single category may contain more than one catDesc child, when for example the category is described in more than one language, as in the following example: - - -literatura piękna -fiction - -proza -prose - - -poezja -poetry - - -dramat -drama - - - -

- - -
- -
The Geographic Coordinates Declaration -

The following element is provided to indicate (within the + literatura pięknafictionprozaprosepoezjapoetrydramatdrama +

+ + + + + + +
+
+ The Geographic Coordinates Declaration +

The following element is provided to indicate (within the header of a document, or in an external location) that a particular coordinate notation, or a particular datum, has been employed in a text. The default notation @@ -1785,22 +1315,15 @@ more than one language, as in the following example: longitude according to the 1984 World Geodetic System (WGS84).

- -
-
The Unit Declaration -

When documents feature units of measurement that are not listed in the International System of Units, the unitDecl element may be used in the encoding description to provide definitions and information about their origins and equivalents. - - - + +

+
+ The Unit Declaration +

When documents feature units of measurement that are not listed in the International System of Units, the unitDecl element may be used in the encoding description to provide definitions and information about their origins and equivalents. +

-

The unitDecl contains one or more unitDef child elements that serve to describe units of measure which may be marked in unit elements within the text. - - - - - - - +

The unitDecl contains one or more unitDef child elements that serve to describe units of measure which may be marked in unit elements within the text. + Within the unitDef, a conversion element may be used to store information relating to conversion between units. The conversion element holds a special pair of attributes, fromUnit and toUnit, which serve to indicate the direction of a calculation from one unit of measure (stored in fromUnit) to another (stored in toUnit). A mathematical calculation to define the relation between these units may be stored in formula, as shown in the following examples. @@ -1808,43 +1331,43 @@ Within the unitDef, a conversion element may be used to store Among other things, this means that division must be expressed with div as opposed to the more common forward slash (/, U+002F), so as not to be confused with path navigation. The conversion element may also use attributes to store dates and date ranges as well as location(s) that specify when and where a conversion formula was applied.

- - - - - - - - - Keel was a unit measuring weight of coal. It had been equal to 20 chalders from 1421 to 1676, and it was made to be equivalent to 16 chalders from 1676 to 1824. - - - - - - - Chalder was a unit measuring weight of coal. It had been equal to 32 bushels from 1421 to 1676, and it was made to be equivalent to 36 bushels from 1676 to 1824. - - - - - Bushel was a unit measuring weight of coal. - - - - - - - - - - - To convert from the Fahrenheit to the Celsius scale, subtract 32 from the Celsius temperature and multiply by 5/9. - - - - - + + + + + + + + + Keel was a unit measuring weight of coal. It had been equal to 20 chalders from 1421 to 1676, and it was made to be equivalent to 16 chalders from 1676 to 1824. + + + + + + + Chalder was a unit measuring weight of coal. It had been equal to 32 bushels from 1421 to 1676, and it was made to be equivalent to 36 bushels from 1676 to 1824. + + + + + Bushel was a unit measuring weight of coal. + + + + + + + + + + + To convert from the Fahrenheit to the Celsius scale, subtract 32 from the Celsius temperature and multiply by 5/9. + + + + + @@ -1856,73 +1379,52 @@ Within the unitDef, a conversion element may be used to store The shunbul was the main unit to measure grain in the Northern parts of Greater Syria. - - - - - - - - -
-
The Schema Specification -

The schemaSpec element contains a schema specification. When this element appears inside encodingDesc, it allows embedding of a TEI ODD customization file inside a TEI header; alternatively, this element may be used in the body of an ODD document. The use of ODD files, and their relationship to schemas, is described in detail in .

- -

A schemaSpec element contains all the information needed to generate schemas for a particular TEI customization, and the ODD documentation elements, by reference to the TEI, are more succinct than the schemas derived from them. Therefore you may find it + + + + + + + +

+
+ The Schema Specification +

The schemaSpec element contains a schema specification. When this element appears inside encodingDesc, it allows embedding of a TEI ODD customization file inside a TEI header; alternatively, this element may be used in the body of an ODD document. The use of ODD files, and their relationship to schemas, is described in detail in .

+

A schemaSpec element contains all the information needed to generate schemas for a particular TEI customization, and the ODD documentation elements, by reference to the TEI, are more succinct than the schemas derived from them. Therefore you may find it convenient to make a copy of the schemaSpec from your project's ODD document inside the teiHeader itself, in addition to supplying an external schema and/or ODD file; if the XML file becomes separated from its schema, the schema can be regenerated at any time using the information in the schemaSpec element. For example: - - - - - - - - - - +

-

Alternatively, it is possible to point to an external ODD customization file or schema through use of the schemaRef element. More than one schemaRef element may be provided for different sources, stages in a workflow, or formats. +

Alternatively, it is possible to point to an external ODD customization file or schema through use of the schemaRef element. More than one schemaRef element may be provided for different sources, stages in a workflow, or formats. - - - - - + The url attribute may be any form of URI pointer including a private URI syntax documented by a prefixDef.

-
- -
-The Application Information Element -

It is sometimes convenient to store information relating to the +

+
+ The Application Information Element +

It is sometimes convenient to store information relating to the processing of an encoded resource within its header. Typical uses for such information might be: - - to allow an + to allow an application to discover that it has previously opened or edited a file, and what version of itself was used - to do that; - to show (through a date) which + to do that; to show (through a date) which application last edited the file to allow for diagnosis of any problems that might have been caused by that - application; - to allow users to discover information - about an application used to edit the file -to allow + application; to allow users to discover information + about an application used to edit the fileto allow the application to declare an interest in elements of the file which it has edited, so that other applications or human editors may be more wary of making changes to - those sections of the file. -

The class model.applicationLike + those sections of the file.

+

The class model.applicationLike provides an element, application, which may be used to record -such information within the appInfo element. - - - -

Each application element identifies the current state of +such information within the appInfo element. +

+

Each application element identifies the current state of one software application with regard to the current file. This element is a member of the att.datable class, which provides a variety of attributes for associating this @@ -1932,52 +1434,50 @@ the application and its major version number (for example, ImageMarkupTool 1.5). It is not intended that an application should add a new application each time it touches the file.

-

The following example shows how these elements might be used to +

The following example shows how these elements might be used to document the fact that version 1.5 of an application called Image Markup Tool has an interest in two parts of a document which was last saved on June 6 2006. The parts concerned are accessible at the URLs given as target for the two ptr -elements. - - - - - - - - -

-
- -
Module-Specific Declarations -

The elements discussed so far are available to any +elements. +

+ + + + + +
+
+ Module-Specific Declarations +

The elements discussed so far are available to any schema. When the schema in use includes some of the more specialized TEI modules, these make available other more module-specific components of the encoding description. These are discussed fully in the documentation for the module in question, but are also noted briefly here for convenience. -

The fsdDecl element is available only when the iso-fs module is included in a schema. Its +

+

The fsdDecl element is available only when the iso-fs module is included in a schema. Its purpose is to document the feature system declaration (as defined in chapter ) underlying any analytic -feature structures (as defined in chapter ) present in the text documented by this header.

The metDecl element is available only when the verse module is included in a schema. Its +feature structures (as defined in chapter ) present in the text documented by this header.

+

The metDecl element is available only when the verse module is included in a schema. Its purpose is to document any metrical notation scheme used in the text, as further discussed in section . It consists either of a prose description or a series of metSym -elements.

The variantEncoding element is available only when the +elements.

+

The variantEncoding element is available only when the textcrit module is included in a schema. Its purpose is to document the method used to encode textual variants in the text, as discussed in section .

-
-
- -
The Profile Description -

The profileDesc element is the third major subdivision of +

+
+
+ The Profile Description +

The profileDesc element is the third major subdivision of the TEI header. It is an optional element, the purpose of which is to enable information characterizing various descriptive aspects of a text or a corpus to be recorded within a single unified framework. - - - + In principle, almost any component of the header might be of importance as a means of characterizing a text. The author of a written text, its title or its date of publication, may all be regarded as @@ -1988,35 +1488,21 @@ forms part of a standard bibliographic style description, if only because such information has already been included elsewhere in the TEI header.

-

The profileDesc element contains +

The profileDesc element contains elements taken from the model.profileDescPart class. The default members of this class are the following : - - - - - - - - + These elements are further described in the remainder of this section.

-

When the corpus +

When the corpus module described in chapter is included in a schema, three further elements become available within the profileDesc element: - - - - - + For descriptions of these elements, see section .

-

When the transcr module for the +

When the transcr module for the transcription of primary sources described in chapter is included in a schema, the following elements become available within the profileDesc element: - - - - + For a description of the handNotes element, see section . Its purpose is to group together a number of handNote elements, each of which describes a different hand or equivalent identified within a manuscript. The @@ -2027,39 +1513,35 @@ schema. For this reason, the handNote element is actually declared within the header module, but is only accessible to a schema when one or other of the transcr or msdescription modules is included in a schema. See further the discussion at .

-

The listTranspose element is discussed in detail in section .

- - - - - - - - - - -
Creation -

The creation element contains phrases describing the +

The listTranspose element is discussed in detail in section .

+ + + + + + + + + + +
+ Creation +

The creation element contains phrases describing the origin of the text, e.g. the date and place of its composition. - - - + The date and place of composition are often of particular importance for studies of linguistic variation; since such information cannot be inferred with confidence from the bibliographic description of the copy text, the creation element may be used to provide a consistent location for this information: - - August 1992 - Taos, New Mexico -

- - - -
- -
Language Usage -

The langUsage element is used within the +August 1992Taos, New Mexico

+ + + +
+
+ Language Usage +

The langUsage element is used within the profileDesc element to describe the languages, sublanguages, registers, dialects, etc. represented within a text. It contains one or more language elements, each of which provides information @@ -2069,44 +1551,35 @@ element should not be used to supply information about any non-standard characters or glyphs used by this language; such information should be recorded in the charDecl element in the encoding description (see further ). - - - -

-

A language element may be supplied for each different +

+

A language element may be supplied for each different language used in a document. If used, its ident attribute should specify an appropriate language identifier, as further discussed in section . This is particularly important if extended language identifiers have been used as the value of xml:lang attributes elsewhere in the document.

-

Here is an example of the use of this element: - - Québecois - Canadian business English - British English - -

- -
- -
The Text Classification -

The +

Here is an example of the use of this element: +QuébecoisCanadian business EnglishBritish English +

+ + + + +
+
+ The Text Classification +

The textClass element is used to classify a text in some way. - - -

-

+

+

Text classification may be carried out according to one or more of the following methods: - -by reference to a recognized international classification such as +by reference to a recognized international classification such as the Dewey Decimal Classification, the Universal Decimal Classification, the Colon Classification, the Library of Congress Classification, or any -other system widely used in library and documentation work -by providing a set of keywords, as provided for example by British -Library or Library of Congress Cataloguing in Publication data -by referencing any other taxonomy of text categories recognized in +other system widely used in library and documentation workby providing a set of keywords, as provided for example by British +Library or Library of Congress Cataloguing in Publication databy referencing any other taxonomy of text categories recognized in the field concerned, or peculiar to the material in hand; this may include one based on recurring sets of values for the situational parameters defined in section , or the demographic @@ -2115,13 +1588,9 @@ The last of these may be particularly important for dealing with existing corpora or collections, both as a means of avoiding the expense or inconvenience of reclassification and as a means of documenting the organizing principles of such materials.

-

The following elements are provided for this purpose: - - - - -

-

The keywords element simply categorizes an individual text +

The following elements are provided for this purpose: +

+

The keywords element simply categorizes an individual text by supplying a list of keywords which may describe its topic or subject matter, its form, date, etc. In some schemes, the order of items in the list is significant, for example, from major topic to minor; in others, @@ -2131,50 +1600,27 @@ such keywords should be taken from a recognized source, such as the British Library/Library of Congress Cataloguing in Publication data in the case of printed books, or a published thesaurus appropriate to the field.

-

The scheme attribute is used to indicate the source of +

The scheme attribute is used to indicate the source of the keywords used, in the case where such a source exists. If the keywords are taken from an externally defined authority which is available online, this attribute should point directly to it, as in the following examples: - - - Babbage, Charles - Mathematicians - Great Britain - Biography - - - - English literature -- History and criticism -- Data processing. - English literature -- History and criticism -- Theory, etc. - English language -- Style -- Data processing. - Style, Literary -- Data processing. - -

-

If the authority file is not available online, but is generally + Babbage, CharlesMathematicians - Great Britain - Biography +English literature -- History and criticism -- Data processing.English literature -- History and criticism -- Theory, etc.English language -- Style -- Data processing.Style, Literary -- Data processing. +

+

If the authority file is not available online, but is generally recognized and commonly cited, a bibliographic description for it should be supplied within the taxonomy element described in section ; the scheme attribute may then reference that taxonomy element by means of its identifier in the usual way: - -ceremonials -fairs -street life - - - - - Notes on London Municipal Literature, and a Suggested - Scheme for Its Classification -Charles Welch -1895 - - - -

-

If no authority file exists, perhaps because the keywords used were +ceremonialsfairsstreet lifeNotes on London Municipal Literature, and a Suggested + Scheme for Its ClassificationCharles Welch1895 +

+

If no authority file exists, perhaps because the keywords used were assigned directly by an author, the scheme attribute should be omitted.

-

Alternatively, if the keyword vocabulary itself is locally defined, +

Alternatively, if the keyword vocabulary itself is locally defined, the scheme attribute will point to the local definition, which will typically be held in a taxonomy element within the classDecl part of the encoding description (see section ). @@ -2183,7 +1629,7 @@ typically be held in a taxonomy element within the

-

The classCode element also categorizes an individual text, +

The classCode element also categorizes an individual text, by supplying a numerical or other code rather than descriptive terms. Such codes constitute a recognized classification scheme, such as the Dewey Decimal Classification. On this element, the @@ -2191,10 +1637,9 @@ as the Dewey Decimal Classification. On this element, the classification scheme in the same way as for keywords: this may be a pointer of any kind, either to a TEI element, possibly in the current document, as in the keywords examples above, or to some -canonical source for the scheme, as in the following example: 005.756 - +canonical source for the scheme, as in the following example: 005.756

-

The catRef element categorizes an individual text by +

The catRef element categorizes an individual text by pointing to one or more category elements using the target attribute, which it inherits from the att.pointing class. The category element (which is fully described in section ) holds information about a particular classification or @@ -2202,40 +1647,42 @@ category within a given taxonomy. Each such category must have a unique identifier, which may be supplied as the value of the target attribute for catRef elements which are regarded as falling within the category indicated.

-

A text may, of course, fall into more than one category, in which +

A text may, of course, fall into more than one category, in which case more than one identifier may be supplied as the value for the target attribute on the catRef element, as in the following example: -

The scheme attribute +

+

The scheme attribute may be supplied to specify the taxonomy to which the categories identified by the target attribute belong, if this is not adequately conveyed by the resource pointed to. For example, - - + Here the same text has been classified as of categories b.a4 and b.d2 within the Brown classification scheme (presumed to be available from http://www.example.com/browncorpus), and as of category A45 within the SUC classification scheme documented at the URL given.

-

In general, it is a matter of style whether to use a single catRef with multiple +

In general, it is a matter of style whether to use a single catRef with multiple identifiers in the value of target or multiple catRef elements, each with a single identifier in the value of target. However, note that maintenance of a TEI document with a large number of values within a single target can be cumbersome.

-

The distinction between the catRef and classCode +

The distinction between the catRef and classCode elements is that the values used as identifying codes are exhaustively enumerated for the former, typically within the TEI header. In the latter case, however, the values use any externally-defined scheme, and therefore may be taken from a more open-ended descriptive classification system.

- - -
- -
Abstracts -

The main purpose of the abstract element is to supply a brief resume or abstract for an article which was originally published without such a component. An abstract or summary forming part of the document at its creation should usually appear in the front matter (front) of the document. - - -

This paper is a draft studying + + + + + + +

+
+ Abstracts +

The main purpose of the abstract element is to supply a brief resume or abstract for an article which was originally published without such a component. An abstract or summary forming part of the document at its creation should usually appear in the front matter (front) of the document. +

This paper is a draft studying various aspects of using the TEI as a reference serialization framework for LMF. Comments are welcome to bring @@ -2243,10 +1690,8 @@ classification system.

community.

-

Abstracts may be provided in multiple languages, distinguished by the xml:lang attribute: - - -

The recent archaeological emphasis +

Abstracts may be provided in multiple languages, distinguished by the xml:lang attribute: +

The recent archaeological emphasis on the study of settlement patterns, landscape and palaeoenvironments has shaped and re-shaped our understanding @@ -2260,9 +1705,7 @@ classification system.

some of the key studies of the ecological consequences of the Norse landnám - are presented.

- -

L’accent récent des + are presented.

L’accent récent des recherches archéologiques sur l’étude des configurations spatiales des colonies, de la géographie des sites ainsi que des éléments @@ -2280,62 +1723,45 @@ classification system.

études principales qui traitent des conséquences écologiques du landnám - islandais.

- + islandais.

- -

The same element may be used to provide other summary information supplied by the encoder, perhaps grouped together into a list of discrete items: - - - -An annual HBC supply ship is - set to the North West Coast for mid-September. - Pelly writes +

The same element may be used to provide other summary information supplied by the encoder, perhaps grouped together into a list of discrete items: + An annual HBC supply ship is + set to the North West Coast for mid-September.Pelly writes to ascertain the British Government's plans for the lands associated with the Oregon Treaty; he wants to know what will happen to the HBC's establishment on the southern Vancouver Island. He adds that a former Crown grant, an 1838 exclusive trade-grant for the lands in question, has yet to - expire. - The minutes discuss the nature of the HBC's + expire.The minutes discuss the nature of the HBC's original entitlements and question whether or not, and in what capacity, the Oregon Treaty affects the HBC's position. The majority council further investigation, and to reply cautiously and judiciously to the HBC inquiry.A summary of a meeting with Pelly is offered in - order to elucidate the HBC's intentions. - Lord Grey calls + order to elucidate the HBC's intentions.Lord Grey calls for greater consideration on the issue of colonization; he asks that Stephen write the Company, asking them to detail their intentions, and to state their legal opinion for entitlement. - - - - - +

-
- -
Calendar Description -

The calendarDesc element is used within the +

+
+ Calendar Description +

The calendarDesc element is used within the profileDesc element to document objects referenced by means of either the calendar attribute on date or the - datingMethod attribute on any member of the att.datable class. - - - + datingMethod attribute on any member of the att.datable class. +

-

This element may contain one or more calendar elements: - - - +

This element may contain one or more calendar elements: +

-

Each such element contains one or more paragraphs of description +

Each such element contains one or more paragraphs of description for the calendar system concerned, and also supplies an identifying code for it as the value of its xml:id attribute. A calendar element may also have a type (and @@ -2343,28 +1769,23 @@ classification system.

any convenient way. In the following example, type is used to differentiate real calendar systems in actual use from those used in a fictional environment. - - -

Gregorian calendar

 -

Fictional Stardate (from Star Trek series)

 -

Calendar years before present (measured from 1950)

 - - +

Gregorian calendar

Fictional Stardate (from Star Trek series)

Calendar years before present (measured from 1950)

-

This identifying code may then be referenced from any element +

This identifying code may then be referenced from any element supplying a date expressed using that calendar system: - -

Captain's log stardate 23.9 rounded off +

Captain's log stardate 23.9 rounded off to the nearest decimal point...

See for details of the usage of dating attributes in conjunction with calendar elements in the teiHeader.

- - -
- -
Correspondence Description + + + + +
+
+ Correspondence Description

The correspDesc element is used within the profileDesc element to provide detailed correspondence-specific metadata, concerning in particular the communicative aspects (sending, receiving, forwarding etc.) associated with an act @@ -2372,81 +1793,37 @@ classification system.

This information is complementary to the detailed descriptions of physical objects (such as letters) associated with correspondence acts, which are typically provided by - the sourceDesc element. - - + the sourceDesc element.

The correspDesc element contains the elements correspAction and correspContext, describing the actions identified and the context in - which the correspondence occurs respectively. - - - + which the correspondence occurs respectively.

Acts of correspondence typically do not occur in isolation from each other. The correspContext element is used to group references relevant to the item of correspondence being described, typically to other items such as the item to which - it is a reply, or the item which replies to it: - - Previous letter of Chamisso to de La - Foye: 16 January 1807 - Next letter of Chamisso to de La Foye: - 07 May 1810 - - + it is a reply, or the item which replies to it: Previous letter of Chamisso to de La + Foye: 16 January 1807Next letter of Chamisso to de La Foye: + 07 May 1810

- - - +

Many types of correspondence actions may be distinguished. The type attribute should be used to indicate the type of action being documented, using values such as those suggested above.

The following simple example uses correspAction to describe the sending of a letter by Adelbert von Chamisso from Vertus on 29 January 1807 to Louis de La Foye at - Caen. The date of reception is unknown: - - Adelbert von Chamisso - Vertus - - - - Louis de La Foye - Caen - unknown - - + Caen. The date of reception is unknown: Adelbert von ChamissoVertusLouis de La FoyeCaenunknown Note the use of the when attribute described in to provide a normalized form of the date. The content of the date element may be omitted, since no underlying source is being transcribed.

-

Several senders, recipients, etc. can be specified for a single correspAction if the action is considered to apply to them all acting as a single group. In the following example, two people are considered to have received - the piece of correspondence. - - Hermann Hesse - Ninon Hesse - Montagnola - - + the piece of correspondence. Hermann HesseNinon HesseMontagnola

The subtype attribute may be used to further distinguish types of action. In the following example, an e-mail is sent to two people directly and to a third by - carbon copy (cc). - - PN0001 - - - - PN0002 - - - PN0003 - - - PN0004 - - + carbon copy (cc). PN0001PN0002PN0003PN0004

The same person may be associated with several actions. For example, it will often be the case that the author and sender of a message are identical, and that many @@ -2454,11 +1831,7 @@ Note the use of the when attribute described in sameAs attribute defined in section may be used to indicate that the same name applies to many actions. Its value will usually be the identifier of an element defining the person or name concerned, which is supplied - elsewhere in the document. - - - - + elsewhere in the document.

It is assumed that each correspondence action applies to a single act of @@ -2469,32 +1842,9 @@ Note the use of the when attribute described in correspDesc elements should be supplied, one for each communication. In the following example, the same document contains distinct messages, sent by two different people to the same destination: correspDesc is used for each - separately: - - - John Gneisenau Neihardt - Branson (Montgomery) - - - - Julius Temple House - New York - - - - - Enid Neihardt - Branson (Montgomery) - - - - - New York - - - + separately: John Gneisenau NeihardtBranson (Montgomery)Julius Temple HouseNew YorkEnid NeihardtBranson (Montgomery)New York

- + @@ -2505,9 +1855,9 @@ Note the use of the when attribute described in
- -
Non-TEI Metadata -

Projects often maintain metadata about their TEI documents in more +

+ Non-TEI Metadata +

Projects often maintain metadata about their TEI documents in more than one form or system. For example, a project may have a database of bibliographic information on the set of documents they intend to encode. From this database, both a MARC record and a @@ -2517,7 +1867,7 @@ which process additional information is added to the the web, a Dublin Core record is generated for discoverability of the resource. It is sometimes advantageous to store some or all of the non-TEI metadata in the TEI file.

-

Such non-TEI data may be placed anywhere within a TEI file +

Such non-TEI data may be placed anywhere within a TEI file (other than as the root element), as it does not affect TEI conformance. However, it is easier for humans to manage these kinds of data if they are grouped together in a single location. In addition, such @@ -2526,10 +1876,8 @@ during validation of the file against a TEI schema. The xenoData element, which may appear in the TEI header after the fileDesc but before the optional revisionDesc, is provided for this purpose. - - -

-

The xenoData element may contain anything except TEI +

+

The xenoData element may contain anything except TEI elements. It may contain one or more elements from outside the TEIAs is always the case when mixing elements from different namespaces in an XML document, the namespace of these @@ -2542,34 +1890,18 @@ of these are LESS-THAN SIGN (<, U+003C) and AMPERSAND (&, U+0026), which may be escaped with &lt; and &amp; respectively. See .

- - - -

In the following example, the prefix + + + +

In the following example, the prefix rdf is bound to the namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#, the prefix dc is bound to the namespace http://purl.org/dc/elements/1.1/, and the prefix cc is bound to the namespace http://web.resource.org/cc/. - - - - Applied Software Project Management - review - - - - - - - - - - - - -

-
- -
The Revision Description -

The final sub-element of the TEI header, the revisionDesc + Applied Software Project Management - review

+
+
+ The Revision Description +

The final sub-element of the TEI header, the revisionDesc element, provides a detailed change log in which each change made to a text may be recorded. Its use is optional but highly recommended. It provides essential information for the administration of large @@ -2580,19 +1912,15 @@ change logs, it is easy to confuse different versions of a file, or to remain unaware of small but important changes made in the file by some earlier link in the chain of distribution. No significant change should be made in any TEI-conformant file without corresponding entries being made in the -change log. - - - - +change log.

-

The main purpose of the revision description is to record changes +

The main purpose of the revision description is to record changes in the text to which a header is prefixed. However, it is recommended TEI practice to include entries also for significant changes in the header itself (other than the revision description itself, of course). At the very least, an entry should be supplied indicating the date of creation of the header.

-

The log consists of a list of entries, one for each change. Changes +

The log consists of a list of entries, one for each change. Changes may be grouped and organised using either the listChange element described in section or the simple list element described in section . Alternatively, a simple sequence of @@ -2604,60 +1932,36 @@ description of the change itself can range from a simple phrase to a series of paragraphs. If a number is to be associated with one or more changes (for example, a revision number), the global n attribute may be used to indicate it.

-

It is recommended to give changes in reverse chronological order, +

It is recommended to give changes in reverse chronological order, most recent first.

-

For example: - - - - Changed drama.verse +

For example: +Changed drama.verse lgs to ps. we have opened a discussion about the need for a new value for type of lg, drama.free.verse, in order to address the verse of Behn which is not in regular iambic pentameter. For the time being these instances are marked with a comment note until we are able to fully consider the best way to encode these instances. - - Added key and reg - to names. - Completed renovation. Validated. - - + Added key and reg + to names.Completed renovation. Validated. In the above example, the who attributes point to respStmt elements which have been included earlier in the titleStmt of the same header: - - - The Amorous Prince, or, the Curious Husband, 1671 - Behn, Aphra - - Caton, Paul - electronic publication editor - - - Gui, Weihsin - encoder - - - Wernimont, Jacqueline - encoder - - - +The Amorous Prince, or, the Curious Husband, 1671Behn, AphraCaton, Paulelectronic publication editorGui, WeihsinencoderWernimont, Jacquelineencoder There is however no requirement that the respStmt be used for this person, or that the elements indicated be contained within the same document. A project might for example maintain a separate document listing all of its personnel in which they were represented using the person element described in .

- - - - -
- -
Minimal and Recommended Headers -

The TEI header allows for the provision of a very large amount of + + + + +

+
+ Minimal and Recommended Headers +

The TEI header allows for the provision of a very large amount of information concerning the text itself, its source, its encodings, and revisions of it, as well as a wealth of descriptive information such as the languages it uses and the situation(s) in which it was @@ -2667,7 +1971,7 @@ to which it is envisaged that electronic texts conforming to these Guidelines will be put. It is emphatically not intended that all of the elements described above should be present in every TEI header.

-

The amount of encoding in a header will depend both on the nature +

The amount of encoding in a header will depend both on the nature and the intended use of the text. At one extreme, an encoder may expect that the header will be needed only to provide a bibliographic identification of the text adequate to local needs. At the other, @@ -2684,28 +1988,13 @@ In the remainder of this section we demonstrate first the minimal, and next a commonly recommended, level of encoding for the bibliographic information held by the TEI header.

-

Supplying only the minimal level of encoding required, the +

Supplying only the minimal level of encoding required, the TEI header of a single text might look like the following example: - - - - Thomas Paine: Common sense, a - machine-readable transcript - - compiled by - Jon K Adams - - - - Oxford Text Archive - - - The complete writings of Thomas Paine, collected and edited - by Phillip S. Foner (New York, Citadel Press, 1945) - - -

The only mandatory component of the TEI header is the +Thomas Paine: Common sense, a + machine-readable transcriptcompiled byJon K AdamsOxford Text ArchiveThe complete writings of Thomas Paine, collected and edited + by Phillip S. Foner (New York, Citadel Press, 1945)

+

The only mandatory component of the TEI header is the fileDesc element. Within this, titleStmt, publicationStmt, and sourceDesc are all required constituents. Within the title statement, a title is required, and an @@ -2717,7 +2006,7 @@ specified. Finally, the source description should contain at the least a loosely structured bibliographic citation identifying the source of the electronic text if (as is usually the case) there is one.

-

We now present the same example header, expanded to include +

We now present the same example header, expanded to include additionally recommended information, adequate to most bibliographic purposes, in particular to allow for the creation of an AACR2-conformant bibliographic record. We have also added information about the @@ -2728,127 +2017,21 @@ and about the revision of the file. - - - - Common sense, a machine-readable transcript - Paine, Thomas (1737-1809) - - compiled by - Jon K Adams - - - - - 1986 - - - - Oxford Text Archive. -

- Oxford University Computing Services, - 13 Banbury Road, - Oxford OX2 6RB, - UK -
- - - Brief notes on the text are in a - supplementary file. - - - - - Foner, Philip S. - The collected writings of Thomas Paine - - New York - Citadel Press - 1945 - - - - - - - -

Editorial notes in the Foner edition have not - been reproduced.

-

Blank lines and multiple blank spaces, including paragraph - indents, have not been preserved.

- - - -

The following errors +Common sense, a machine-readable transcriptPaine, Thomas (1737-1809)compiled byJon K Adams1986Oxford Text Archive.

Oxford University Computing Services,13 Banbury Road,Oxford OX2 6RB,UK
Brief notes on the text are in a + supplementary file.Foner, Philip S.The collected writings of Thomas PaineNew YorkCitadel Press1945

Editorial notes in the Foner edition have not + been reproduced.

Blank lines and multiple blank spaces, including paragraph + indents, have not been preserved.

The following errors in the Foner edition have been corrected: - - p. 13 l. 7 cotemporaries contemporaries - p. 28 l. 26 [comma] [period] - p. 84 l. 4 kin kind - p. 95 l. 1 stuggle struggle - p. 101 l. 4 certainy certainty - p. 167 l. 6 than that - p. 209 l. 24 publshed published - -

- - -

No normalization beyond that performed - by Foner, if any.

- - -

All double quotation marks + p. 13 l. 7 cotemporaries contemporariesp. 28 l. 26 [comma] [period]p. 84 l. 4 kin kindp. 95 l. 1 stuggle strugglep. 101 l. 4 certainy certaintyp. 167 l. 6 than thatp. 209 l. 24 publshed published +

No normalization beyond that performed + by Foner, if any.

All double quotation marks rendered with ", all single quotation marks with - apostrophe.

- - -

Hyphenated words that appear at the - end of the line in the Foner edition have been reformed.

- - -

The values of when-iso on the time + apostrophe.

Hyphenated words that appear at the + end of the line in the Foner edition have been reformed.

The values of when-iso on the time element always end in the format HH:MM or HH; i.e., seconds, fractions thereof, and time - zone designators are not present.

- - -

Compound proper names are marked.

-

Dates are marked.

-

Italics are recorded without interpretation.

- - - - - Library of Congress Subject Headings - - - Library of Congress Classification - - - - - - 1774 - - - English. - - - - Political science - United States -- Politics and government — - Revolution, 1775-1783 - - JC 177 - - - - finished proofreading - finished proofreading - finished data entry at end of term - began data entry before New Year 1995 - - + zone designators are not present.

Compound proper names are marked.

Dates are marked.

Italics are recorded without interpretation.

Library of Congress Subject HeadingsLibrary of Congress Classification1774English.Political scienceUnited States -- Politics and government — + Revolution, 1775-1783JC 177 finished proofreading finished proofreading finished data entry at end of term began data entry before New Year 1995 @@ -2858,13 +2041,14 @@ and about the revision of the file.

-

Many other examples of recommended usage for the elements discussed +

Many other examples of recommended usage for the elements discussed in this chapter are provided here, in the reference index and in the associated tutorials.

-
- -
Note for Library Cataloguers

A strong motivation in preparing the material in this chapter was to +

+
+ Note for Library Cataloguers +

A strong motivation in preparing the material in this chapter was to provide in the TEI header a viable chief source of information for cataloguing computer files. The TEI header is not a library catalogue record, and so will not make all of the distinctions @@ -2876,17 +2060,14 @@ header, and moreover that the mapping from the one to the other be as simple and straightforward as possible. Where the correspondence is not obvious, it may prove useful to consult one of the works which were influential in developing the content of the TEI header. These -include: - ISBD: International Standard Bibliographic Description +include:ISBD: International Standard Bibliographic Description is an international standard setting out what information should be recorded in a description of a bibliographical item. Until a consolidated edition published in 2011, there was a general standard called ISBD(G) and separate ISBDs covering different types of material, e.g. ISBD(M) for monographs, ISBD(ER) for electronic resources. These separate ISBDs follow the same general scheme as the main ISBD(G), but provide appropriate interpretations for the specific materials under -consideration. - -The Anglo-American Cataloguing Rules (second edition) were published +consideration.The Anglo-American Cataloguing Rules (second edition) were published in 1978, with revisions appearing periodically through 2005. AACR2 provides guidelines for the construction of catalogues in general libraries in the English-speaking world. AACR2 is explicitly based on the general framework @@ -2898,56 +2079,38 @@ française de normalisation (AFNOR), Regeln für die alphabetis in wissenschaftlichen Bibliotheken (RAK-WB), Regole italiane di catalogazione per autore (RICA), and Система стандартов по информации, библиотечному и издательскому делу. Библиографическая запись. Библиографическое -описание. Общие требования и правила составления (ГОСТ 7.1). - -The American National Standard for Bibliographic References +описание. Общие требования и правила составления (ГОСТ 7.1).The American National Standard for Bibliographic References was an American national standard governing bibliographic references for use in bibliographies, end-of-work lists, references in abstracting and indexing publications, and outputs from computerized bibliographic data bases. A revised version is maintained by the National Information Standards Organization (NISO). The related ISO standard is ISO 690. Other relevant national standards include BS 5605:1990, BS 6371:1983, DIN 1505-2, and ГОСТ 7.0.5.

- -

Since the TEI file description elements are based on the ISBD +

Since the TEI file description elements are based on the ISBD areas, it should be possible to use the content of file description as the basis for a catalog record for a TEI document. However, cataloguers should be aware that the permissive nature of the TEI Guidelines may lead to divergences between practice in using the TEI file description and the comparatively strict recommendations of AACR2 and other national cataloguing codes. Such divergences as the following may preclude automatic -generation of catalogue records from TEI headers: -The TEI Guidelines do not require that text be transcribed from the chief source of information using normalized capitalization and punctuation . -The TEI title statement may not categorize constituent titles in -the same way as prescribed by a national cataloguing code. -The TEI title statement contains authors, editors, and other +generation of catalogue records from TEI headers: The TEI Guidelines do not require that text be transcribed from the chief source of information using normalized capitalization and punctuation .The TEI title statement may not categorize constituent titles in +the same way as prescribed by a national cataloguing code.The TEI title statement contains authors, editors, and other responsible parties in separate elements, with names which may not have been normalized; it does not necessarily contain a single statement of responsibility . -There is no specific place in a TEI header to +information-->.There is no specific place in a TEI header to specify the main entry or added entries (name or title headings under which a catalogue record is - filed) for the catalogue record. -The TEI header does not require use of a particular vocabulary -for subject headings nor require the use of subject headings. -

-
- -
- The TEI Header Module -

The module described in this chapter makes available the + filed) for the catalogue record.The TEI header does not require use of a particular vocabulary +for subject headings nor require the use of subject headings.

+
+
+ The TEI Header Module +

The module described in this chapter makes available the following components: - - Common Metadata - The TEI header - En-tête TEI - TEI標頭 - L'intestazione TEI (TEI header) - O cabeçalho TEI - ヘダーモジュール - + Common MetadataThe TEI headerEn-tête TEITEI標頭L'intestazione TEI (TEI header)O cabeçalho TEIヘダーモジュール The selection and combination of modules to form a TEI schema is described in .

-
+
diff --git a/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml b/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml index b0514d371e..637f3b5498 100644 --- a/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml +++ b/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml @@ -1,17 +1,11 @@ - +
-Manuscript Description -
-Overview -

The msdescription module + Manuscript Description +

+ Overview +

The msdescription module This chapter is based on the work of the European MASTER (Manuscript Access through Standards for Electronic Records) project, funded by the European Union from January 1999 to June 2001, and led by Peter Robinson, then at the Centre @@ -27,7 +21,7 @@ enough that it can also be extended to other traditions and materials, and is potentially useful for any kind of text-bearing artefact. Where the textuality of an object is not the primary concern, encoders may wish to use the object element which provides a very similar system of description (see .

-

The scheme described here is also intended to accommodate the needs of many +

The scheme described here is also intended to accommodate the needs of many different classes of encoders. On the one hand, encoders may be engaged in retrospective conversion of existing detailed descriptions and catalogues into machine tractable form; on the other, they may be engaged in @@ -42,14 +36,14 @@ dates; at the other, a project may wish to create, in highly structured and encoded form, a detailed database of information about the physical characteristics, history, interpretation, etc. of the material, able to support practitioners of quantitative codicology as well as librarians.

-

To cater for this diversity, here as elsewhere, these Guidelines propose a +

To cater for this diversity, here as elsewhere, these Guidelines propose a flexible strategy, in which encoders must choose for themselves the approach appropriate to their needs, and are provided with a choice of encoding mechanisms to support those differing degrees.

-
-
-The Manuscript Description Element -

The msDesc element will normally appear within the +

+
+ The Manuscript Description Element +

The msDesc element will normally appear within the sourceDesc element of the header of a TEI-conformant document, where the document being encoded is a digital representation of some manuscript original, whether as an encoded transcription, as a collection of digital images @@ -59,22 +53,11 @@ of manuscript descriptions, the msDesc element may be used in the same way as the bibliographic elements (bibl, biblFull, and biblStruct) making up the TEI element class model.biblLike. These typically appear within the listBibl -element. - -

-

The msDesc element has the following components, which provide more +element.

+

The msDesc element has the following components, which provide more detailed information under a number of headings. Each of these component -elements is further described in the remainder of this chapter. - - - - - - - - -

-

The first of these components, msIdentifier, is the only one which +elements is further described in the remainder of this chapter.

+

The first of these components, msIdentifier, is the only one which is mandatory; it is described in more detail in below. It is followed optionally by one or more head elements, each holding a brief heading (see ), and then either one or more @@ -89,177 +72,71 @@ codicological units) or a fragmented manuscript (a manuscript whose parts are no dispersed and kept at different places), a full description may also contain one or more msPart () elements and msFrag () elements, respectively.

-

To demonstrate the use of this module, consider the following sample +

To demonstrate the use of this module, consider the following sample manuscript description, chosen more or less at random from the Bodleian -Library's Summary catalogue ()

- -Entry for Bodleian MS. Add. A. 61 in Madan et al. 1895-1953 -
+Library's Summary catalogue ()
Entry for Bodleian MS. Add. A. 61 in Madan et al. 1895-1953

-

The simplest way of digitizing this catalogue entry would simply be to key in +

The simplest way of digitizing this catalogue entry would simply be to key in the text, tagging the relevant parts of it which make up the mandatory msIdentifier element, as follows: - - - -Oxford -Bodleian Library -MS. Add. A. 61 -28843 - -

In Latin, on parchment: written in more than one hand of the 13th cent. in +OxfordBodleian LibraryMS. Add. A. 6128843

In Latin, on parchment: written in more than one hand of the 13th cent. in England: 7¼ x 5⅜ in., i + 55 leaves, in double columns: with a few coloured -capitals.

-

'Hic incipit Bruitus Anglie,' the De origine et gestis Regum Angliae of +capitals.

'Hic incipit Bruitus Anglie,' the De origine et gestis Regum Angliae of Geoffrey of Monmouth (Galfridus Monumetensis: beg. 'Cum mecum multa & de -multis.'

-

On fol. 54v very faint is 'Iste liber est fratris guillelmi de buria de ... +multis.'

On fol. 54v very faint is 'Iste liber est fratris guillelmi de buria de ... Roberti ordinis fratrum Pred[icatorum],' 14th cent. (?): 'hanauilla' is written at the foot of the page (15th cent.). Bought from the rev. W. D. Macray on March -17, 1863, for £1 10s.

- +17, 1863, for £1 10s.

With a suitable stylesheet, this encoding would be as readable as the original; it would not, however, be very useful for search purposes since only shelfmarks and other identifiers are distinguished. To improve on this, one might wrap the paragraphs in the appropriate special-purpose first-child-level elements of msDesc and add some of the additional phrase-level elements available when this module is in use: - - - -Oxford -Bodleian Library -MS. Add. A. 61 - -28843 - - - -

Hic incipit Bruitus Anglie, the De origine et gestis +<egXML xmlns="http://www.tei-c.org/ns/Examples" source="#MS-eg-001"><msDesc><msIdentifier><settlement>Oxford</settlement><repository>Bodleian Library</repository><idno>MS. Add. A. 61</idno><altIdentifier type="SC"><idno>28843</idno></altIdentifier></msIdentifier><msContents><p><quote>Hic incipit Bruitus Anglie,</quote> the <title>De origine et gestis Regum Angliae of Geoffrey of Monmouth (Galfridus Monumetensis): beg. -Cum mecum multa & de multis. In Latin.

- - -

Parchment: written in +Cum mecum multa & de multis. In Latin.

Parchment: written in more than one hand: 7¼ x 5⅜ in., i + 55 leaves, in double columns: -with a few coloured capitals.

- - -

Written in England in the 13th +with a few coloured capitals.

Written in England in the 13th cent. On fol. 54v very faint is Iste liber est fratris guillelmi de buria de ... Roberti ordinis fratrum Pred[icatorum], 14th cent. (?): hanauilla is written at the foot of the page (15th -cent.). Bought from the rev. W. D. Macray on March 17, 1863, for £1 10s.

- - - +cent.). Bought from the rev. W. D. Macray on March 17, 1863, for £1 10s.

Note that in this version the text has been slightly reorganized, but no actual rewriting has been necessary. The encoding now allows the user to search for such features as title, material, and date and place of origin; it is also possible to distinguish quoted material from descriptive passages and to search within descriptions relating to a particular topic (for example, history as distinct from material).

-

This process could be continued further, restructuring the whole entry so as +

This process could be continued further, restructuring the whole entry so as to take full advantage of many more of the encoding possibilities provided by the module described in this chapter: - - - -Oxford -Bodleian Library -MS. Add. A. 61 - -28843 - - - - -Geoffrey of Monmouth -Galfridus Monumetensis -De origine et gestis Regum Angliae -Hic incipit Bruitus Anglie -Cum mecum multa & de multis -Latin - - - - - - -

Parchment.

- -i + 55 leaves -7¼ -5⅜ - - - - - -

In double columns.

- - - - -

Written in more than one hand.

- - -

With a few coloured capitals.

- - - - -

Written in England in the 13th cent.

- - -

On fol. 54v very faint is Iste liber est fratris +OxfordBodleian LibraryMS. Add. A. 6128843Geoffrey of MonmouthGalfridus MonumetensisDe origine et gestis Regum AngliaeHic incipit Bruitus AnglieCum mecum multa & de multisLatin

Parchment.

i + 55 leaves 7¼5⅜ +

In double columns.

Written in more than one hand.

With a few coloured capitals.

Written in England in the 13th cent.

On fol. 54v very faint is Iste liber est fratris guillelmi de buria de Roberti ordinis fratrum Predicatorum, 14th cent. (?): hanauilla is -written at the foot of the page (15th cent.).

- - -

Bought from the rev. W. D. Macray on March 17, 1863, for £1 10s.

- - - - +written at the foot of the page (15th cent.).

Bought from the rev. W. D. Macray on March 17, 1863, for £1 10s.

 In the remainder of this chapter we discuss all of the encoding features demonstrated above, together with many other related matters.

- - - -
-
-Phrase-level Elements -

When the msdescription module is in use, several + + + +

+
+ Phrase-level Elements +

When the msdescription module is in use, several extra elements are added to the phrase level class, and thus become available within paragraphs and elsewhere in the document. These elements are listed below -in alphabetical order: - - - - - - - - - - - - -

-

Within a manuscript description, many other standard TEI phrase level +in alphabetical order:

+

Within a manuscript description, many other standard TEI phrase level elements are available, notably those described in the Core module (). Additional elements of particular relevance to manuscript description, such as those for names and dates, may also be made available by including the relevant module in one's schema.

-
-Origination -

The following elements may be used to provide information about the origins -of any aspect of a manuscript: - - -

-

The origDate and origPlace elements are specialized forms +

+ Origination +

The following elements may be used to provide information about the origins +of any aspect of a manuscript:

+

The origDate and origPlace elements are specialized forms of the existing date and name elements respectively, used to indicate specifically the date and place of origin of a manuscript or manuscript part. Such information would normally be encoded within the history @@ -270,100 +147,71 @@ not of the same date or from the same location as rest of the manuscript. Both these elements are members of the att.editLike class, from which they inherit many attributes.

-

The origDate element is a member of the att.datable class, and may thus also carry additional attributes giving +

The origDate element is a member of the att.datable class, and may thus also carry additional attributes giving normalized values for the associated dating.

-
-
-Material and Object Type -

The material element can be used to tag any specific term used for +

+
+ Material and Object Type +

The material element can be used to tag any specific term used for the physical material of which a manuscript (or binding, seal, etc.) is composed. The objectType element may be used to tag any term specifying -the type of object or manuscript upon with the text is written. - - -

-

These elements may appear wherever a term regarded as significant by the +the type of object or manuscript upon with the text is written.

+

These elements may appear wherever a term regarded as significant by the encoder occurs, as in the following examples: - - -

Brown calfskin, previously with two clasps.

- - - - -

Parchment -codex with half goat-leather -binding.

- - -

-
-
-Watermarks and Stamps -

Two further elements are provided to mark up other decorative features -characteristic of manuscript leaves and bindings: - - -

-

These elements may appear wherever a term regarded as significant by the +

Brown calfskin, previously with two clasps.

+

Parchmentcodex with half goat-leather +binding.

 +

+
+
+ Watermarks and Stamps +

Two further elements are provided to mark up other decorative features +characteristic of manuscript leaves and bindings:

+

These elements may appear wherever a term regarded as significant by the encoder occurs. The watermark element is most likely to be of use within the support element discussed in below. We give a simple example here: Rag paper with anchor watermark

-

The stamp element will typically appear when text from the source is +

The stamp element will typically appear when text from the source is being transcribed, for example within a rubric in the following case: - -Apologyticu TTVLLIANI AC IGNORATIA IN XPO IHV +Apologyticu TTVLLIANI AC IGNORATIA IN XPO IHV SI NON LICET NOBIS RO -manii imperii Bodleian stamp - +manii imperii Bodleian stamp

-

It may also appear as part of the detailed description of a binding: - -

Modern calf recasing with original armorial stamp with legend +

It may also appear as part of the detailed description of a binding: +

Modern calf recasing with original armorial stamp with legend Ex Bibliotheca J. Richard -D.M.

- +D.M.

-

If, as here, any text contained by a stamp is included in its description it +

If, as here, any text contained by a stamp is included in its description it should be clearly distinguished from that description. The element mentioned may be used for this purpose, as shown above.

-
-
-Dimensions -

The dimensions element can be used to specify the size of some +

+
+ Dimensions +

The dimensions element can be used to specify the size of some aspect of the manuscript, and thus may be thought of as a specialized form of -the existing TEI measure element. - -

-

The dimensions element will normally occur within the element +the existing TEI measure element.

+

The dimensions element will normally occur within the element describing the particular feature or aspect of a manuscript whose dimensions are being given; thus the size of the leaves would be specified within the support or extent element (part of the physDesc element discussed in ), while the dimensions of other specific parts of a manuscript, such as accompanying materials, binding, etc., would be given in other parts of the description, as appropriate.

-

The following elements are available within the dimensions element: - - - - - -

-

These elements, as well as dimensions itself, are all members of the +

The following elements are available within the dimensions element: +

+

These elements, as well as dimensions itself, are all members of the att.dimensions class, which also inherits attributes from the att.ranging class. They all thus carry the -following attributes: - - -

-

Attributes scope, min, and max are used only +following attributes:

+

Attributes scope, min, and max are used only when the measurement applies to several items, for example the size of all leaves in a manuscript; attributes atLeast and atMost are used when the measurement applies to a single item, for example the size of a @@ -377,7 +225,7 @@ project, using standard units of measurement wherever possible, such as If however the only data available for the measurement uses some other unit, or it is preferred to normalize it in some other way, then it may be supplied as a string value by means of the extent attribute.

-

In the simplest case, only the extent attribute may be supplied: +

In the simplest case, only the extent attribute may be supplied: six cubits More usually, the measurement will be normalized into a value and an @@ -388,241 +236,144 @@ appropriate SI unit: estimated value: six cubits

-

It is often convenient to supply a measurement which applies to a number of +

It is often convenient to supply a measurement which applies to a number of discrete observations: for example, the number of ruled lines on the pages of a manuscript (which may not all be the same), or the diameter of an object like a bell, which will differ depending where it is measured. In such cases, the scope attribute may be used to specify the observations for which this measurement is applicable: - - + This indicates that most pages have at least 20 lines. The attributes min and max can also be used to specify the possible range of values: for example, to show that all pages have between 12 and 30 lines: - - +

-

The dimensions element may be repeated as often as necessary, with +

The dimensions element may be repeated as often as necessary, with appropriate attribute values to indicate the nature and scope of the measurement concerned. For example, in the following case the leaf size and ruled space of the leaves of the manuscript are specified: - - - - - - - - - - + This indicates that for most leaves of the manuscript being described the ruled space is 90 mm high and 48 mm wide, while the leaves throughout are between 157 and 160 mm in height and 105 mm in width.

-

The dim element is provided for cases where some measurement other +

The dim element is provided for cases where some measurement other than height, width, or depth is required. Its type attribute is used to indicate the type of measurement involved: - - - - - - -

-

The order in which components of the dimensions element may be + +

+

The order in which components of the dimensions element may be supplied is not constrained.

-
-
-References to Locations within a Manuscript -

The locus and its grouping element locusGrp element are +

+
+ References to Locations within a Manuscript +

The locus and its grouping element locusGrp element are specialized forms of the ref element, used to indicate a location, or -sequence of locations, within a manuscript. - - -

-

The locus element is used to reference a single location within a +sequence of locations, within a manuscript.

+

The locus element is used to reference a single location within a manuscript, typically to specify the location occupied by the element within which it appears. If, for example, it is used as the first component of an msItem or msItemStruct element, or of any of the more specific elements appearing within one (see further section below) then it is understood to specify the location (or locations) of that item within the manuscript being described.

-
-Identifying a Location -

A locus element can be used to identify any reference to one or more +

+ Identifying a Location +

A locus element can be used to identify any reference to one or more folios within a manuscript, wherever such a reference is appropriate. Locations are conventionally specified as a sequence of folio or page numbers, but may also be a discontinuous list, or a combination of the two. This specification should be given as the content of the locus element, using the conventions appropriate to the individual scholar or holding institution, as in the following example: - -ff. 1-24r -Apocalypsis beati Ioannis Apostoli - - +ff. 1-24rApocalypsis beati Ioannis Apostoli

-

A normalized form of the location can also be supplied, using special purpose +

A normalized form of the location can also be supplied, using special purpose attributes on the locus element, as in the following revision of the above example: - -ff. 1-24r -Apocalypsis beati Ioannis Apostoli - - +ff. 1-24rApocalypsis beati Ioannis Apostoli

-

When the item concerned occupies a discontinuous sequence of pages, this may +

When the item concerned occupies a discontinuous sequence of pages, this may simply be indicated in the body of the locus element: - -ff. 1-12v, 18-24r -Apocalypsis beati Ioannis Apostoli - - +ff. 1-12v, 18-24rApocalypsis beati Ioannis Apostoli Alternatively, if it is desired to indicate normalized values for each part of the sequence, a sequence of locus elements can be supplied, grouped within the locusGrp element: - - -ff. 1-12v -ff. 18-24r - -Apocalypsis beati Ioannis Apostoli - - +ff. 1-12vff. 18-24rApocalypsis beati Ioannis Apostoli If an existing catalogue is being transcribed and it is desirable to retain formatting of the reference (e.g. superscript or italic text) then the hi element may be used. If encoding multiple semantic divisions in a single location reference then a nested locus may be used to separate or annotate these.

-

Finally, the content of the locus element may be omitted if a +

Finally, the content of the locus element may be omitted if a formatting application can construct it automatically from the values of the from and to attributes: - - - - - -Apocalypsis beati Ioannis Apostoli - - +Apocalypsis beati Ioannis Apostoli

-
-
-Linking a Location to a Transcription or an Image -

The locus attribute can also be used to associate a location within +

+
+ Linking a Location to a Transcription or an Image +

The locus attribute can also be used to associate a location within a manuscript with facsimile images of that location, using the facs attribute, or with a transcription of the text occurring at that location. The former association is effected by means of the facs attribute; the latter by means of the target attribute.

-

The facs is available only when the transcr module described in chapter is included in +

The facs is available only when the transcr module described in chapter is included in a schema. It associates a locus element with one or more digitized images, as in the following example: - - -fols. 8v-10v -Birds Praise of Love - -IMEV -1506 - - - +fols. 8v-10vBirds Praise of LoveIMEV1506 Here, the facs attribute uses a URI reference to point directly to images of the relevant pages. This method may be found cumbersome when many images are to be associated with a single location. It is of most use when specific pages are referenced within a description, as in the following example: - - -

Several of the miniatures in this section have been damaged and overpainted +

Several of the miniatures in this section have been damaged and overpainted at a later date (e.g. the figure of Christ on fol. 33r; the face of the Shepherdess on fol. -59v, etc.).

- - +59v, etc.).

For further discussion of the facs attribute, see section .

-

Where a transcription of the relevant pages is available, this may be +

Where a transcription of the relevant pages is available, this may be associated with the locus element using its target attribute, as in the following example: - - -ff. 1r-2r -Ben Jonson -Ode to himself - - An Ode - to him selfe. -Com leaue the loathed stage -And see his chariot triumph ore his wayne. -Beal, Index 1450-1625, JnB 380 - - - - - - - - - +ff. 1r-2rBen JonsonOde to himself An Ode + to him selfe.Com leaue the loathed stageAnd see his chariot triumph ore his wayne.Beal, Index 1450-1625, JnB 380

-

When (as in this example) a sequence of elements is to be supplied as target +

When (as in this example) a sequence of elements is to be supplied as target value, it may be given explicitly as above, or using the xPointer range() syntax defined at . Note however that support for this pointer mechanism is not widespread in current XML processing systems.

-

The target attribute should only be used to point to elements that +

The target attribute should only be used to point to elements that contain or indicate a transcription of the locus being described. To associate a locus element with a page image or other comparable representation, the global facs attribute should be used instead.

-
-
-Using Multiple Location Schemes -

Where a manuscript contains more than one foliation, the scheme +

+
+ Using Multiple Location Schemes +

Where a manuscript contains more than one foliation, the scheme attribute may be used to distinguish them. For example, MS 65 Corpus Christi College, Cambridge contains two fly leaves bearing music. These leaves have modern foliation 135 and 136 respectively, but are also marked with an older foliation. This may be preserved in an encoding such as the following: - -XCIII -135 - +XCIII135 Here the scheme attribute points to a foliation element providing more details about the scheme used, as further discussed in below.

-

Where discontinuous sequences are identified within two different foliations, +

Where discontinuous sequences are identified within two different foliations, the scheme attribute should be supplied on the locusGrp element in preference, as in the following: - - -XCIII -CC-CCII - - -135 -197-204 - - -

-
-
-
-Names of Persons, Places, and Organizations -

The standard TEI element name may be used to identify names of any -kind occurring within a description: - - As further discussed in , this element is a +XCIIICC-CCII135197-204 +

+
+
+
+ Names of Persons, Places, and Organizations +

The standard TEI element name may be used to identify names of any +kind occurring within a description: As further discussed in , this element is a member of the class att.canonical, from which it -inherits the following attributes: - - -

-

Here are some examples of the use of the name element: - -Thomas Hoccleve -Villingaholt -Vetus Latina Institut -Occleve - -

-

Note that the name element is defined as providing information about +inherits the following attributes: +

+

Here are some examples of the use of the name element: +Thomas HoccleveVillingaholtVetus Latina InstitutOccleve +

+

Note that the name element is defined as providing information about a name, not the person, place, or organization to which that name refers. In the last example above, the ref attribute is used to associate the name with a more detailed description of the person named. This is @@ -630,15 +381,7 @@ provided by means of the person element, which becomes available when the namesdates module described in chapter is included in a schema. An element such as the following might then be used to provide detailed information about the person indicated by the name: - - -Hoccleve -Thomas - - -poet - - +HoccleveThomaspoet Note that an instance of @@ -648,7 +391,7 @@ must be found as the xml:id attribute of some person element; the same value will be used as the ref attribute of every reference to Hoccleve in the document (however spelled), but there will only be one person element with this identifier.

-

Alternatively, the key attribute may be used to supply a unique +

Alternatively, the key attribute may be used to supply a unique identifying code for the person referenced by the name independently of both the existence of a person element and the use of the standard URI reference mechanism. If, for example, a project maintains as its authority file some @@ -659,44 +402,40 @@ other digital resources for this purpose, the unique codes used by such interchangeability of the resulting encoded texts, they may be judged more convenient or practical in certain situations. As explained in , interchange is improved by use of tag URIs in ref instead of key.

-

All the person elements referenced by a particular +

All the person elements referenced by a particular document set should be collected together within a listPerson element, located in a standOff element. This functions as a kind of prosopography for all the people referenced by the set of manuscripts being described, in much the same way as a listBibl element may be used to hold bibliographic information for all the works referenced.

-

When the namesdates module described in chapter +

When the namesdates module described in chapter is included in a schema, similar mechanisms are used to maintain and reference canonical lists of places or organizations, as further discussed in sections and respectively.

-
-
-Catchwords, Signatures, Secundo Folio -

The catchwords element is used to describe one method by which +

+
+ Catchwords, Signatures, Secundo Folio +

The catchwords element is used to describe one method by which correct ordering of the quires of a codex is ensured. Typically, this takes the form of a word or phrase written in the lower margin of the last leaf verso of a gathering, which provides a preview of the first recto leaf of the successive gathering. This may be a simple phrase such as the following: Quires signed on the -last leaf verso in roman numerals. - +last leaf verso in roman numerals. Alternatively, it may contain more details: - -Vertical catchwords in the hand of the scribe placed along the inner -bounding line, reading from top to bottom. - +Vertical catchwords in the hand of the scribe placed along the inner +bounding line, reading from top to bottom.

-

The Signatures element is used, in a similar way, to +

The Signatures element is used, in a similar way, to describe a similar system in which quires or leaves are marked progressively in order to facilitate arrangement during binding. For example: At the bottom of the first four leaves of quires 1-14 are the remains of a series of quire signatures -a-o plus roman figures in a cursive hand of the fourteenth century. - +a-o plus roman figures in a cursive hand of the fourteenth century.

-

The signatures element can be used for either leaf signatures, or a +

The signatures element can be used for either leaf signatures, or a combination of quire and leaf signatures, whether the marking is alphabetic, alphanumeric, or some ad hoc system, as in the following more complex example: Quire and leaf @@ -705,25 +444,22 @@ signatures in letters, [b]-v, and roman numerals; those in quires 10 (1) and 17 crayon in arabic numerals in the centre lower margin of the first leaf recto: "2" for quire 4 (f. 19), "3" for quire 7 (f. 43); "4", barely visible, for quire 10 (f. 65), "5", in a later hand, for quire 13 (f. 89), "6", in a later hand, -for quire 16 (f. 113). - +for quire 16 (f. 113).

-

The secFol element (for secundo folio) is used +

The secFol element (for secundo folio) is used to record an identifying phrase (also called dictio probatoria) taken from a specific known point in a codex (for example the first few words on the second leaf). Since these words will differ from one copy of a text to another, the practice originated in the middle ages of using them when cataloguing a manuscript in order to distinguish individual copies of a work in a way which its opening words could not. - -(ando-)ssene in una villa - +(ando-)ssene in una villa

-
-
-Heraldry - -

Descriptions of heraldic arms, supporters, devices, and mottos may appear at +

+
+ Heraldry + +

Descriptions of heraldic arms, supporters, devices, and mottos may appear at various points in the description of a manuscript, usually in the context of ownership information, binding descriptions, or detailed accounts of illustrations. A full description may also contain a detailed account of the @@ -731,81 +467,64 @@ heraldic components of a manuscript independently considered. Frequently, however, heraldic descriptions will be cited as short phrases within other parts of the record. The phrase level element heraldry is provided to allow such phrases to be marked for further analysis, as in the following examples: - -

Ownership stamp (xvii cent.) on i recto with the arms A bull +

Ownership stamp (xvii cent.) on i recto with the arms A bull passant within a bordure bezanty, in chief a crescent for difference -[Cole], crest, and the legend Cole Deum.

- -

A c. 8r fregio su due lati, stemma e imprese medicee -racchiudono l'inizio dell'epistolario di Paolino.

- -

- - - - - - - - - - - - - - - - - - - - -
-
-
-The Manuscript Identifier -

The msIdentifier element is intended to provide an unambiguous means +[Cole], crest, and the legend Cole Deum.

A c. 8r fregio su due lati, stemma e imprese medicee +racchiudono l'inizio dell'epistolario di Paolino.

+

+ + + + + + + + + + + + + + + + + + + + +
+
+
+ The Manuscript Identifier +

The msIdentifier element is intended to provide an unambiguous means of uniquely identifying a particular manuscript. This may be done in a structured way, by providing information about the holding institution and the call number, shelfmark, or other identifier used to indicate its location within that institution. Alternatively, or in addition, a manuscript may be identified -simply by a commonly used name. - -

-

A manuscript's actual physical location may occasionally be different from +simply by a commonly used name.

+

A manuscript's actual physical location may occasionally be different from its place of ownership; at Cambridge University, for example, manuscripts owned by various colleges are kept in the central University Library. Normally, it is the ownership of the manuscript which should be specified in the manuscript identifier, while additional or more precise information on the physical location of the manuscript can be given within the adminInfo element, discussed in section below.

-

The following elements are available within msIdentifier to identify -the holding institution: - - - - - -

-

These elements are all structurally equivalent to the standard TEI +

The following elements are available within msIdentifier to identify +the holding institution:

+

These elements are all structurally equivalent to the standard TEI name element with an appropriate value for its type attribute; however the use of this syntactic sugar enables the model for msIdentifier to be constrained rather more tightly than would otherwise be possible. Specifically, only one of each of the elements listed above may appear within the msIdentifier and they must, if present, appear in the order given.

-

Like name, these elements are all also members of the attribute +

Like name, these elements are all also members of the attribute class att.canonical, and thus can use the attributes key or ref to reference a single standardized source of information about the entity named.

-

The following elements are used within msIdentifier to provide -different ways of identifying the manuscript within its holding institution: - - - - -

-

Major manuscript repositories will usually have a preferred form of citation +

The following elements are used within msIdentifier to provide +different ways of identifying the manuscript within its holding institution:

+

Major manuscript repositories will usually have a preferred form of citation for manuscript shelfmarks, including rules about punctuation, spacing, abbreviation, etc., which should be adhered to. Where such a format also contains information which might additionally be supplied as a distinct @@ -814,88 +533,45 @@ decision must be taken as to whether to use the more specific element, or to include such information within the idno element. For example, the manuscript formally identified as El 26 C 9 forms a part of the Ellesmere (El) collection. Either of the following encodings is therefore feasible: - - -USA -California -San Marino -Huntington Library -El -26 C 9 -The Ellesmere Chaucer - - - - -USA -California -San Marino -Huntington Library -El 26 C 9 -The Ellesmere Chaucer - - +USACaliforniaSan MarinoHuntington LibraryEl26 C 9The Ellesmere Chaucer +USACaliforniaSan MarinoHuntington LibraryEl 26 C 9The Ellesmere Chaucer

-

In the former example, the preferred form of the identifier can be retrieved +

In the former example, the preferred form of the identifier can be retrieved by prefixing the content of the idno element with that of the collection element, while in the latter it is given explicitly. The advantage of the former is that it simplifies accurate retrieval of all manuscripts from a given collection; the disadvantage is that encoded abbreviations of this kind may not be as immediately comprehensible. Care should be taken to avoid redundancy: for example - -El -El 26 C 9 - +ElEl 26 C 9 would clearly be inappropriate. Equally clearly, - -Ellesmere -El 26 C 9 - +EllesmereEl 26 C 9 might be considered helpful in some circumstances (if, for example, some of the items in the Ellesmere collection had shelfmarks which did not begin El).

-

In some cases the shelfmark may contain no information about the collection; +

In some cases the shelfmark may contain no information about the collection; in other cases, the item may be regarded as belonging to more than one collection. The collection element may be added, and repeated as often as necessary to cater for such situations: - - -Hungary -Budapest - Bibliothèque de l'Académie des Sciences de Hongrie -Oriental Collection -Sandor Kégl Bequest -MS 1265 - - -

-

- - -USA -New Jersey -Princeton -Princeton University Library -Scheide Library -MS 71 -Blickling Homiliary - - -

-

Note in the latter case the use of the msName element to provide a +HungaryBudapest Bibliothèque de l'Académie des Sciences de Hongrie Oriental CollectionSandor Kégl BequestMS 1265 +

+

+ + + USA + New Jersey + Princeton + Princeton University Library + Scheide Library + MS 71 + Blickling Homiliary + + +

+

Note in the latter case the use of the msName element to provide a common name other than the shelfmark by which a manuscript is known. Where a manuscript has several such names, more than one of these elements may be used, as in the following example: - - -Danmark -København -Det Arnamagnæanske Institut -AM 45 fol. -Codex Frisianus -Fríssbók - - +DanmarkKøbenhavnDet Arnamagnæanske InstitutAM 45 fol.Codex FrisianusFríssbók Here the globally available xml:lang attribute has been used to specify the language of the alternative names.

-

In very rare cases a repository may have only one manuscript (or only one of +

In very rare cases a repository may have only one manuscript (or only one of any significance), which will have no shelfmark as such but will be known by a particular name or names. In such circumstances, the idno element may be omitted, and the manuscript identified by the name or names used for it, using one or more msName elements, as in the following example: - - -Rossano -Biblioteca arcivescovile -Codex Rossanensis -Codex purpureus -The Rossano Gospels - - +RossanoBiblioteca arcivescovileCodex RossanensisCodex purpureusThe Rossano Gospels If a manuscript name contains a name or referencing string that it is useful to annotate (e.g. by referring to an authority list) then name or rs may be used for this purpose.

-

Where manuscripts have moved from one institution to another, or even within +

Where manuscripts have moved from one institution to another, or even within the same institution, they may have identifiers additional to the ones currently used, such as former shelfmarks, which are sometimes retained even after they have been officially superseded. In such cases it may be useful to supply an @@ -929,71 +597,44 @@ alternative identifier, with a detailed structure similar to that of the msIdentifier itself. The following example shows a manuscript which had shelfmark II-M-5 in the collection of the Duque de Osuna, but which now has the shelfmark MS 10237 in the National Library in Madrid: - - -Madrid -Biblioteca Nacional -MS 10237 - -Andalucia -Osuna -Duque de Osuna -II-M-5 - - - +MadridBiblioteca NacionalMS 10237AndaluciaOsunaDuque de OsunaII-M-5 Normally, such information would be dealt with under history, except in cases where a manuscript is likely still to be referred to or known by its former identifier. For example, an institution may have changed its call number system but still wish to retain a record of the earlier number, perhaps because the manuscript concerned is frequently cited in print under its previous number: - - -Berkeley -University of California -Bancroft Library -UCB 16 -2MS BS1145 I8 - - +BerkeleyUniversity of CaliforniaBancroft LibraryUCB 162MS BS1145 I8 Where (as in this example) no repository is specified for the altIdentifier, it is assumed to be the same as that of the parent msIdentifier. Where the holding institution has only one preferred form of citation but wishes to retain the other for internal administrative purposes, the secondary could be given within altIdentifier with an appropriate value on the type attribute: - - -Oxford -Bodleian Library -MS. Bodley 406 -2297 - - +OxfordBodleian LibraryMS. Bodley 4062297 It might, however, be preferable to include such information within the adminInfo element discussed in section below.

-

Cases of such changed or alternative identifiers should be clearly +

Cases of such changed or alternative identifiers should be clearly distinguished from cases of fragmented () manuscripts, that is to say manuscripts which although physically disjoint are nevertheless generally treated as single units.

-

As mentioned above, the smallest possible description is one that contains +

As mentioned above, the smallest possible description is one that contains only the element msIdentifier; good practice in all but exceptional circumstances requires the presence within it of the three sub-elements settlement, repository, and idno, since they provide what is, by common consent, the minimum amount of information necessary to identify a manuscript.

- - - - - - - - -
-
-The Manuscript Heading -

Historically, the briefest possible meaningful description of a manuscript + + + + + + + + +

+
+ The Manuscript Heading +

Historically, the briefest possible meaningful description of a manuscript consists of no more than a title, e.g. Polychronicon. This will often have been enough to identify a manuscript in a small collection because the identity of the author is implicit. Where a title does not imply the @@ -1006,15 +647,11 @@ folio reference (e.g. Arch. B. 3. 2: Evangelium Matthei cum glossa, 126. Isidori Originum libri octo, Biblia Hieronimi, 2o fo. opus est); information on date and place of writing will sometimes also be included. The standard TEI element -head element can be used to provide a brief description of this kind. - - In this way the cataloguer or scholar can supply in one place a +head element can be used to provide a brief description of this kind. In this way the cataloguer or scholar can supply in one place a minimum of essential information, such as might be displayed or printed as the heading of a full description. For example: - -Marsilius de Inghen, Abbreviata phisicorum Aristotelis; Italy, -1463. - +Marsilius de Inghen, Abbreviata phisicorum Aristotelis; Italy, +1463. Any phrase-level elements, such as title, name, date, or the specialized elements origPlace and origDate, can also be used within a head element, but it @@ -1025,10 +662,10 @@ elements described below, msContents, physDesc, history, etc. However, in simple cases, the p element may also be used to supply an unstructured collection of such information, as in the example given above ().

-
-
-Intellectual Content -

The msContents element is used to describe the intellectual content +

+
+ Intellectual Content +

The msContents element is used to describe the intellectual content of a manuscript or manuscript part. It comprises either a series of informal prose paragraphs or a series of msItem or msItemStruct elements, each of which provides a more detailed @@ -1036,164 +673,93 @@ description of a single item contained within the manuscript. These may be prefaced, if desired, by a summary element, which is especially useful where one wishes to provide an overview of a manuscript's contents and describe only some of the items in detail. - - - - - - -

-

In the simplest case, only a brief description may be provided, as in the + +

+

In the simplest case, only a brief description may be provided, as in the following examples: - - -

A collection of Lollard sermons

- - - - -

Atlas of the world from Western Europe and Africa to Indochina, containing 27 - maps and 26 tables

- - - - -

Biblia sacra: Antiguo y Nuevo Testamento, con prefacios, prólogos y +

A collection of Lollard sermons

 +

Atlas of the world from Western Europe and Africa to Indochina, containing 27 + maps and 26 tables

 +

Biblia sacra: Antiguo y Nuevo Testamento, con prefacios, prólogos y argumentos de san Jerónimo y de otros. Interpretaciones de los nombres - hebreos.

- - + hebreos.

-

This description may of course be expanded to include any of the TEI elements +

This description may of course be expanded to include any of the TEI elements generally available within a p element, such as title, bibl, or list. More usually, however, each individual work within a manuscript will be given its own description, using the msItem or msItemStruct element described in the next section, as in the following example: - - -fols. 5r -7v -An ABC -IMEV -239 -fols. 7v -8v -Lenvoy de Chaucer a Scogan -IMEV -3747 -fol. 8vTruth -IMEV -809 -fols. 8v-10v -Birds Praise of Love -IMEV -1506 -fols. 10v -11v -De amico ad amicam -Responcio -IMEV -16 & 19 -fols. 14r-126v -Troilus and Criseyde -Bk. 1:71-Bk. 5:1701, with additional losses due to mutilation -throughout - - - -

-

The summary element may be used in conjunction with one or more +fols. 5r -7vAn ABCIMEV239fols. 7v -8vLenvoy de Chaucer a ScoganIMEV3747fol. 8vTruthIMEV809fols. 8v-10vBirds Praise of LoveIMEV1506fols. 10v -11vDe amico ad amicamResponcioIMEV16 & 19fols. 14r-126vTroilus and CriseydeBk. 1:71-Bk. 5:1701, with additional losses due to mutilation +throughout +

+

The summary element may be used in conjunction with one or more msItem elements if it is desired to provide both a general summary of the contents of a manuscript and more detail about some or all of the individual items within it. It may not however be used within an individual msItem element.

- - -A collection of Lollard sermons -fol. 4r-8r -3rd Sunday Before Lent -fol. 9r-16v -Sexagesima - - - -
-The msItem and msItemStruct Elements -

Each discrete item in a manuscript or manuscript part can be described within + + +

A collection of Lollard sermons + + fol. 4r-8r + 3rd Sunday Before Lent + + + fol. 9r-16v + Sexagesima + + + +
+ The msItem and msItemStruct Elements +

Each discrete item in a manuscript or manuscript part can be described within a distinct msItem or msItemStruct element, and may be classified using the class attribute.

-

These are the possible component elements of msItem and -msItemStruct. - - - - - - - - - - - - - - - - -

-

In addition, an msItemStruct may contain nested msItemStruct +

These are the possible component elements of msItem and +msItemStruct.

+

In addition, an msItemStruct may contain nested msItemStruct elements, just as an msItem may contain nested msItem elements.

-

The main difference between msItem and msItemStruct is that +

The main difference between msItem and msItemStruct is that in the former, the order and number of child elements is not constrained; any element, in other words, may be given in any order, and repeated as often as is judged necessary. In the latter, however, the sub-elements, if used, must be given in the order specified above and only some of them may be repeated; specifically, rubric, finalRubric. incipit, textLang and explicit can appear only once.

-

While neither msItem nor msItemStruct may contain untagged +

While neither msItem nor msItemStruct may contain untagged running text, both permit an unstructured description to be provided in the form of one or more paragraphs of text. They differ in this respect also: if paragraphs are supplied as the content of an msItem, then none of the other component elements listed above is permitted; in the msItemStruct case, however, paragraphs may appear anywhere as an alternative to any of the component elements listed above.

-

As noted above, both msItem and msItemStruct elements may +

As noted above, both msItem and msItemStruct elements may also nest, where a number of separate items in a manuscript are grouped under a single title or rubric, as is the case, for example, with a work like The Canterbury Tales.

-

The elements msContents, msItem, msItemStruct, +

The elements msContents, msItem, msItemStruct, incipit, and explicit are all members of the class att.msExcerpt from which they inherit the -defective attribute. - - This attribute can be used for example with collections of +defective attribute. This attribute can be used for example with collections of fragments, where each fragment is given as a separate msItem and the first and last words of each fragment are transcribed as defective incipits and explicits, as in the following example, a manuscript containing four fragments of a single work: - - -1r-9v -Knýtlinga saga -1r:1-2v:30 -danna a englandi -en meðan haraldr hein hafði +1r-9vKnýtlinga saga1r:1-2v:30danna a englandien meðan haraldr hein hafði konungr vit -yfir danmork - - - - - -

-

The elements ex, am, and expan used in the above +yfir danmork +

+

The elements ex, am, and expan used in the above example are further discussed in section ; they are available only when the transcr module defined by that chapter is selected. Similarly, the g element used in this example to represent the abbreviation mark is defined by the gaiji module documented in chapter .

-
-
-Authors and Titles -

When used within a manuscript description, the title element should +

+
+ Authors and Titles +

When used within a manuscript description, the title element should be used to supply a regularized form of the item's title, as distinct from any rubric quoted from the manuscript. If the item concerned has a standardized distinctive title, e.g. Roman de la Rose, then this @@ -1204,46 +770,34 @@ wishes to provide a general designation of the contents, then a supplied title can be given, e.g. missal, in which case the type attribute on the title should be given the value supplied.

-

Similarly, if used within a manuscript description, the author +

Similarly, if used within a manuscript description, the author element should always contain the normalized form of an author's name, irrespective of how (or whether) this form of the name is cited in the manuscript. If it is desired to retain the form of the author's name as given in the manuscript, this may be tagged as a distinct name element, within the text at the point where it occurs.

- -

Note that the key attribute can also be used, as on names in + +

Note that the key attribute can also be used, as on names in general, to specify the identifier of a person element carrying full details of the person concerned (see further ).

-

The respStmt element can be used to supply the name and role of a +

The respStmt element can be used to supply the name and role of a person other than the author who is responsible for some aspect of the intellectual content of the manuscript: - -Diogenes Laertius - -in the translation of -Ambrogio Traversari - - -

-

The respStmt element can also be used where there is a discrepancy +Diogenes Laertiusin the translation ofAmbrogio Traversari +

+

The respStmt element can also be used where there is a discrepancy between the author of an item as given in the manuscript and the accepted scholarly view, as in the following example: - -Sermons on the Epistles and the Gospels - -here erroneously attributed to -St. Bonaventura - - +Sermons on the Epistles and the Gospelshere erroneously attributed toSt. Bonaventura Note that such attributions of authorship, both correct and incorrect, are frequently found in the rubric or final rubric (and occasionally also elsewhere in the text), and can therefore be transcribed and included in the description, if desired, using the rubric, finalRubric, or quote elements, as appropriate.

-
-
-Rubrics, Incipits, Explicits, and Other Quotations from the Text -

It is customary in a manuscript description to record the opening and closing +

+
+ Rubrics, Incipits, Explicits, and Other Quotations from the Text +

It is customary in a manuscript description to record the opening and closing words of a text as well as any headings or colophons it might have, and the specialized elements rubric, incipit, explicit, finalRubric, and colophon are available within msItem @@ -1252,145 +806,88 @@ bits of the text not covered by these elements. Each of these elements has the same substructure, containing a mixture of phrase-level elements and plain text. A locus element can be included within each, in order to specify the location of the component, as in the following example: - - -f. 1-223 -Radulphus Flaviacensis -Expositio super Leviticum -f. 1r Forte Hervei monachi -f. 223v Benedictio salis et aquae - - - -

-

In the following example, standard TEI elements for the transcription of +f. 1-223Radulphus FlaviacensisExpositio super Leviticum f. 1r Forte Hervei monachif. 223v Benedictio salis et aquae +

+

In the following example, standard TEI elements for the transcription of primary sources have been used to mark the expansion of abbreviations and other features present in the original: - - -ff. 1r-24v -Ágrip af Noregs konunga sǫgum - -regi oc hann seti ho -sc heim sem þio -hon hever +ff. 1r-24vÁgrip af Noregs konunga sǫgumregi oc hann seti ho +sc heim sem þiohon hever oc þa buit hesta .ij. annan viþ fé en honom annan til -reiþar - - +reiþar Note here also the use of the defective attribute on incipit and explicit to indicate that the text begins and ends defectively.

-

The xml:lang attribute for colophon, explicit, +

The xml:lang attribute for colophon, explicit, incipit, quote, and rubric may always be used to identify the language of the text quoted, if this is different from the default language specified by the mainLang attribute on textLang.

-
- -
-Filiation -

The filiation element can be used to provide information on the +

+ +
+ Filiation +

The filiation element can be used to provide information on the relationship between the manuscript and other surviving manuscripts of the same text, either specifically or in a general way, as in the following example: - - -118rb -Ecce morior cum nichil horum ... [Dn 13, 43]. Verba ista -dixit Susanna de illis -ut bonum comune conservatur. -Schneyer 3, 436 (Johannes Contractus OFM) -weitere Überl. Uppsala C 181, 35r. - - +118rbEcce morior cum nichil horum ... [Dn 13, 43]. Verba ista +dixit Susanna de illisut bonum comune conservatur.Schneyer 3, 436 (Johannes Contractus OFM)weitere Überl. Uppsala C 181, 35r.

-
-
-Text Classification -

One or more text classification or text-type codes may be specified, either +

+
+ Text Classification +

One or more text classification or text-type codes may be specified, either for the whole of the msContents element, or for one or more of its constituent msItem elements, using the class attribute as specified above: - - - -1v-71v -Jónsbók -Magnus med guds miskun Noregs konungur -enn uirda þo til fullra aura - - +1v-71vJónsbókMagnus med guds miskun Noregs konungurenn uirda þo til fullra aura The value used for the class attribute in this example points to a category element with the identifier law, which defines the classification concerned. Such category elements will typically appear within a taxonomy element, within the classDecl element of the TEI header () as in the following example: - - - - -Legislation - - -Military topics - - - - +LegislationMilitary topics More than one classification may apply to a single item. Another text, concerned with legislation about military topics might thus be specified as follows: - - -

A treatise on Clausewitz

- - - +

A treatise on Clausewitz

-
-
-Languages and Writing Systems -

The textLang element should be used to provide information about the +

+
+ Languages and Writing Systems +

The textLang element should be used to provide information about the languages used within a manuscript item. It may take the form of a simple note, as in the following example: - -Old Church Slavonic, written in Cyrillic script. - +Old Church Slavonic, written in Cyrillic script.

-

Where, for validation and indexing purposes, it is thought convenient to add +

Where, for validation and indexing purposes, it is thought convenient to add keywords identifying the particular languages used, the mainLang attribute may be used. This attribute takes the same range of values as the global xml:lang attribute, on which see further . In the following example a manuscript written chiefly in Old Church Slavonic is described: - -Old Church Slavonic - +Old Church Slavonic

- -

A manuscript item will sometimes contain material in more than one language. + +

A manuscript item will sometimes contain material in more than one language. The mainLang attribute should be used only for the chief language. Other languages used may be specified using the otherLangs attribute as in the following example: - -Mostly Old Church Slavonic, with -some Russian and Greek material - +Mostly Old Church Slavonic, with +some Russian and Greek material

-

Since Old Church Slavonic may be written in either Cyrillic or Glagolitic +

Since Old Church Slavonic may be written in either Cyrillic or Glagolitic scripts, and even occasionally in both within the same manuscript, it might be preferable to use a more explicit identifier: - -Old Church Slavonic in Cyrillic script - +Old Church Slavonic in Cyrillic script

-

The form and scope of language identifiers recommended by these Guidelines is +

The form and scope of language identifiers recommended by these Guidelines is based on the IANA standard described at and should be followed throughout. Where additional detail is needed correctly to describe a language, or to discuss its deployment in a given text, this should be done using the langUsage element in the TEI header, within which individual language elements document the languages used: see .

-

Note that the language element defines a particular combination of +

Note that the language element defines a particular combination of human language and writing system. Only one language element may be supplied for each such combination. Standard TEI practice also allows this element to be referenced by any element using the global xml:lang @@ -1401,43 +898,37 @@ Latin), and de (for German), a manuscript description written in French which specifies that a particular manuscript contains predominantly German but also some Latin material, might have a textLang element like the following: - -allemand et -latin - -

- - - - - - - - - - - - - - - - - -
-
-
-Physical Description -

Under the general heading physical description we +allemand et +latin +

+ + + + + + + + + + + + + + + + + +
+
+
+ Physical Description +

Under the general heading physical description we subsume a large number of different aspects generally regarded as useful in the -description of a given manuscript. These include: -aspects of the form, support, extent, and quire structure of the -manuscript object and of the way in which the text is laid out on the page (); -the styles of writing, such as the way it is laid out on the page, the +description of a given manuscript. These include: aspects of the form, support, extent, and quire structure of the +manuscript object and of the way in which the text is laid out on the page ();the styles of writing, such as the way it is laid out on the page, the styles of writing, decorative features, any musical notation employed and any -annotations or marginalia (); - and discussion of its binding, seals, and any accompanying material (). -

-

Most manuscript descriptions touch on several of these categories of +annotations or marginalia (); and discussion of its binding, seals, and any accompanying material ().

+

Most manuscript descriptions touch on several of these categories of information though few include them all, and not all distinguish them as clearly as we propose here. In particular, it is often the case that an existing description will include information for which we propose distinct elements @@ -1445,7 +936,7 @@ within a single paragraph, or even sentence. The encoder must then decide whether to rewrite the description using the structure proposed here, or to retain the existing prose, marked up simply as a series of p elements, directly within the physDesc element.

-

The physDesc element may thus be used in either of two distinct +

The physDesc element may thus be used in either of two distinct ways. It may contain a series of paragraphs addressing topics listed above and similar ones. Alternatively, it may act as a container for any choice of the more specialized elements described in the remainder of this section, each of @@ -1454,32 +945,21 @@ attributes.

-

In general, it is not recommended to combine unstructured prose description +

In general, it is not recommended to combine unstructured prose description with usage of the more specialized elements, as such an approach complicates processing, and may lead to inconsistency within a single manuscript description. A single physDesc element will normally contain either a series of model.pLike elements, or a sequence of specialized elements from the model.physDescPart class. There are however circumstances in which this is not feasible, for -example: -the description already exists in a prose form where some of the +example: the description already exists in a prose form where some of the specialized topics are treated together in paragraphs of prose, but others are -treated distinctly; -although all parts of the description are clearly distinguished, some of -them cannot be mapped to a pre-existing specialized element. -

-

In such situations, both specialized and generic (model.pLike) elements may be combined in a single physDesc. +treated distinctly;although all parts of the description are clearly distinguished, some of +them cannot be mapped to a pre-existing specialized element.

+

In such situations, both specialized and generic (model.pLike) elements may be combined in a single physDesc. Note however that all generic elements given must precede the first specialized element in the description. Thus the following is valid: - - -

Generic descriptive prose...

- - - - - - +

Generic descriptive prose...

 but neither of the following is valid: @@ -1500,16 +980,16 @@ element in the description. Thus the following is valid: content model; again this is for simplicity of processing. They may of course be processed or displayed in any desired order, but for ease of validation, they must be given in the order specified below.

-
-Object Description -

The objectDesc element is used to group together those parts of the +

+ Object Description +

The objectDesc element is used to group together those parts of the physical description which relate specifically to the text-bearing object, its format, constitution, layout, etc. The objectDesc element is used for grouping elements relating to the physicality of a text-bearing object as part of a manuscript description. If a full description of an object (text-bearing or not) is desired, the more general object element may be preferred.

-

The form attribute is used to +

The form attribute is used to indicate the specific type of writing vehicle being described, for example, as a codex, roll, tablet, etc. If used it must appear first in the sequence of specialized elements. The objectDesc element has two parts: a @@ -1517,148 +997,98 @@ description of the support, i.e. the physical carrier on which the text is inscribed; and a description of the layout, i.e. the way text is organized on the carrier.

-

Taking these in turn, the description of the support is tagged using the -following elements, each of which is discussed in more detail below: - - - - - - -

-

Each of these elements contains paragraphs relating to the topic concerned. +

Taking these in turn, the description of the support is tagged using the +following elements, each of which is discussed in more detail below:

+

Each of these elements contains paragraphs relating to the topic concerned. Within these paragraphs, phrase-level elements (in particular those discussed above at ), may be used to tag specific terms of interest if so desired. - - - -

Mostly paper, with watermarks +

Mostly paper, with watermarks unicorn (Briquet 9993) and ox (close to Briquet 2785). The first and last leaf of each quire, with the exception of quires xvi and xviii, are constituted by bifolia of parchment, and all seven miniatures have been painted on inserted -singletons of parchment.

- - - +singletons of parchment.

-

This example combines information which might alternatively be more precisely +

This example combines information which might alternatively be more precisely tagged using the more specific elements described in the following subsections.

-
-Support -

The support element groups together information about the physical +

+ Support +

The support element groups together information about the physical carrier. Typically, for western manuscripts, this will entail discussion of the material (parchment, paper, or a combination of the two) written on. For paper, a discussion of any watermarks present may also be useful. If this discussion makes reference to standard catalogues of such items, these may be tagged using the standard ref element as in the following example: - -

-Paper with watermark: anchor in a circle with +

Paper with watermark: anchor in a circle with star on top, countermark B-B with trefoil similar to Mošin, Anchor N 1680 -1570-1585.

- +1570-1585.

-
-
-Extent -

The extent element, defined in the TEI header, may also be used in a +

+
+ Extent +

The extent element, defined in the TEI header, may also be used in a manuscript description to specify the number of leaves a manuscript contains, as in the following example: - -ii + 97 + ii - +ii + 97 + ii Information regarding the size of the leaves may be specifically marked using the phrase level dimensions element, as in the following example, or left as plain prose. - -ii + 321 leaves -35 -27 - - - -

-

Alternatively, the generic measure element might be used within +ii + 321 leaves 3527 + +

+

Alternatively, the generic measure element might be used within extent, as in the following example: - - -10 Bl. -37 x 29 cm - +10 Bl.37 x 29 cm

-
-
-Collation -

The collation element should be used to provide a description of a +

+
+ Collation +

The collation element should be used to provide a description of a book's current and original structure, that is, the arrangement of its leaves and quires. This information may be conveyed using informal prose, or any appropriate notational convention. Although no specific notation is defined here, an appropriate element to enclose such an expression would be the formula element, which is provided when the figures module is included in a schema. Here are some examples of different ways of treating collation: - -

1-3:8, 4:6, 5-13:8

- -

There are now four gatherings, the first, second and fourth originally +

1-3:8, 4:6, 5-13:8

There are now four gatherings, the first, second and fourth originally consisting of eight leaves, the third of seven. A fifth gathering thought to -have followed has left no trace. -Gathering I consists of 7 leaves, a first leaf, originally conjoint with +have followed has left no trace. Gathering I consists of 7 leaves, a first leaf, originally conjoint with fol. 7, having been cut away leaving only a narrow strip along the gutter; the others, fols 1 and 6, 2 and 5, and 3 and -4, are bifolia. -Gathering II consists of 8 leaves, 4 bifolia. -Gathering III consists of 7 leaves; fols 16 and -22 are conjoint, the others singletons. -Gathering IV consists of 2 leaves, a bifolium. -

- -

I (1, 2+9, 3+8, 4+7, 5+6, 10); II (11, 12+17, 13, 14, 15, 16, 18, -19).

 - -

1-5.8 6.6 (catchword, f. 46, does not match following text) 7-8.8 -9.10, 11.2 (through f. 82) 12-14.8 15.8(-7) -

- - -

-
-
-Foliation -

The foliation element may be used to indicate the scheme, medium or +4, are bifolia.Gathering II consists of 8 leaves, 4 bifolia.Gathering III consists of 7 leaves; fols 16 and +22 are conjoint, the others singletons.Gathering IV consists of 2 leaves, a bifolium.

I (1, 2+9, 3+8, 4+7, 5+6, 10); II (11, 12+17, 13, 14, 15, 16, 18, +19).

1-5.8 6.6 (catchword, f. 46, does not match following text) 7-8.8 +9.10, 11.2 (through f. 82) 12-14.8 15.8(-7)

 +

+
+
+ Foliation +

The foliation element may be used to indicate the scheme, medium or location of folio, page, column, or line numbers written in the manuscript, frequently including a statement about when and, if known, by whom, the numbering was done. - -

Neuere Foliierung, die auch das Vorsatzblatt mitgezählt -hat.

-

Folio numbers were added in brown ink by Árni Magnússon ca. -1720-1730 in the upper right corner of all recto-pages.

 - -

-

Where a manuscript contains traces of more than one foliation, each should be +

Neuere Foliierung, die auch das Vorsatzblatt mitgezählt +hat.

Folio numbers were added in brown ink by Árni Magnússon ca. +1720-1730 in the upper right corner of all recto-pages.

 +

+

Where a manuscript contains traces of more than one foliation, each should be recorded as a distinct foliation element and optionally given a distinct value for its xml:id attribute. The locus element discussed in can then indicate which foliation scheme is being cited by means of its scheme attribute, which points to this identifier: - -

Original foliation in red roman numerals in the -middle of the outer margin of each recto

-

Foliated in pencil in the top right corner of each -recto page.

 - -ff 1-20 - -

-
-
-Condition -

The condition element is used to summarize the overall physical +

Original foliation in red roman numerals in the +middle of the outer margin of each recto

Foliated in pencil in the top right corner of each +recto page.

ff 1-20 +

+
+
+ Condition +

The condition element is used to summarize the overall physical state of a manuscript, in particular where such information is not recorded elsewhere in the description. It should not, however, be used to describe changes or repairs to a manuscript, as these are more appropriately described as @@ -1669,36 +1099,37 @@ of the physical support of the manuscript; within the bindingDesc or condition of the binding or bindings concerned; or within the sealDesc element if it discusses the condition of any seal attached to the manuscript.

- - -

The manuscript shows signs of damage from water and mould on its -outermost leaves.

 - - - -

Despite tears on many of the leaves the codex is reasonably well + + + +

The manuscript shows signs of damage from water and mould on its +outermost leaves.

+ + + + + +

Despite tears on many of the leaves the codex is reasonably well preserved. The top and the bottom of f. 1 is damaged, and only a thin slip is left of the original second leaf (now foliated as 1bis). The lower margin of f. 92 has been cut away. There is a lacuna of one leaf between ff. 193 and 194. The manuscript ends defectively (there are approximately six leaves -missing).

 - - -
-
-Layout Description -

The second part of the objectDesc element is the layoutDesc +missing).

+ + + +
+
+ Layout Description +

The second part of the objectDesc element is the layoutDesc element, which is used to describe and document the mise-en-page of the manuscript, that is the way in which text and illumination are arranged on the page, specifying for example the number of written, ruled, or pricked lines and columns per page, size of margins, distinct textual streams such as glosses, commentaries, etc. This may be given as a simple series of paragraphs. Alternatively, one or more different layouts may be identified -within a single manuscript, each described by its own layout element. - - -

-

Where the layout element is used, the layout will often be +within a single manuscript, each described by its own layout element.

+

Where the layout element is used, the layout will often be sufficiently regular for the attributes on this element to convey all that is necessary; more usually however a more detailed treatment will be required. The attributes are provided as a convenient shorthand for commonly occurring cases, @@ -1707,148 +1138,89 @@ and should not be used except where the layout is regular. The value either very irregular, or where it cannot be characterized simply in terms of lines and columns, for example, where blocks of commentary and text are arranged in a regular but complex pattern on each page

-

The following examples indicate the range of possibilities: - - -

Most pages have between 25 and 32 long lines ruled in lead.

- - -

Written in one column throughout; 24 lines per page.

- -

Written in 3 columns, with 8 lines of text and interlinear glosses in +

The following examples indicate the range of possibilities: +

Most pages have between 25 and 32 long lines ruled in lead.

Written in one column throughout; 24 lines per page.

Written in 3 columns, with 8 lines of text and interlinear glosses in the centre, and up to 26 lines of gloss in the outer two columns. Double vertical bounding lines ruled in hard point on hair side. Text lines ruled faintly in lead. Remains of prickings in upper, lower, and outer (for 8 lines of -text only) margins.

 - +text only) margins.

-

Where multiple layout elements are supplied, the scope for each +

Where multiple layout elements are supplied, the scope for each specification can be indicated by means of locus elements within the content of the element, as in the following example: - - - -

On fols 1r-200v and fols 210r-212v there are between 25 and 32 ruled lines.

- - -

On fols 203r-209v there are between 34 -and 50 ruled lines.

- - -

-
-
-
-Writing, Decoration, and Other Notations -

The second group of elements within a structured physical description +

On fols 1r-200v and fols 210r-212v there are between 25 and 32 ruled lines.

On fols 203r-209v there are between 34 +and 50 ruled lines.

 +

+
+
+
+ Writing, Decoration, and Other Notations +

The second group of elements within a structured physical description concerns aspects of the writing, illumination, or other notation (notably, music) found in a manuscript, including additions made in later hands—the -text, as it were, as opposed to the carrier. - - - - - - - - - - -

-
-Writing -

The handDesc element can contain a short description of the general +text, as it were, as opposed to the carrier.

+
+ Writing +

The handDesc element can contain a short description of the general characteristics of the writing observed in a manuscript, as in the following example: - - -

Written in a late Caroline minuscule; versals in a form of +

Written in a late Caroline minuscule; versals in a form of rustic capitals; although the marginal and interlinear gloss is written in varying shades of ink that are not those of the main text, text and -gloss appear to have been copied during approximately the same time span.

- - +gloss appear to have been copied during approximately the same time span.

-

Note the use of the term element to mark specific technical terms +

Note the use of the term element to mark specific technical terms within the context of the handDesc element.

-

Where several distinct hands have been identified, this fact can be +

Where several distinct hands have been identified, this fact can be registered by using the hands attribute, as in the following example: - - -

The manuscript is written in two contemporary hands, otherwise unknown, but +

The manuscript is written in two contemporary hands, otherwise unknown, but clearly those of practised scribes. Hand I writes ff. 1r-22v and hand II ff. 23 and 24. Some scholars, notably Verner Dahlerup and Hreinn Benediktsson, have argued for a third hand on f. 24, but the evidence for this is -insubstantial.

- - +insubstantial.

-

Alternatively, or in addition, where more specific information about one or +

Alternatively, or in addition, where more specific information about one or more of the hands identified is to be recorded, the handNote element should be used, as in the following example: - - - -

The first part of the manuscript, fols +

The first part of the manuscript, fols 1v-72v:4, is written in a practised Icelandic Gothic bookhand. This hand -is not found elsewhere.

- -

The second part of the manuscript, fols +is not found elsewhere.

The second part of the manuscript, fols 72v:4-194, is written in a hand contemporary with the first; it can also be found in a fragment of Knýtlinga saga, AM 20b II -fol..

 - -

The third hand has written the majority of the chapter headings. This hand +fol..

The third hand has written the majority of the chapter headings. This hand has been identified as the one also found in AM 221 -fol..

 - - +fol..

Note here the use of the locus element, discussed in section , to specify exactly which parts of a manuscript are written by a given hand.

-

When a full or partial transcription of a manuscript is available in addition +

When a full or partial transcription of a manuscript is available in addition to the manuscript description, the handShift element described in can be used to link the relevant parts of the transcription to the appropriate handNote element in the description: for example, at the point in the transcript where the second hand listed above starts (i.e. at folio 72v:4), we might insert handShift new="#Eirsp-2"/.

-

Additions, notes, drawings etc. (e.g. add, note and figure) made by other hands +

Additions, notes, drawings etc. (e.g. add, note and figure) made by other hands in the text, can be linked to the corresponding handNote element using the hand attribute.

-

The elements typeDesc, and typeNote are used to provide +

The elements typeDesc, and typeNote are used to provide information about the printing of a source, in exactly the same way as the handDesc or handNote elements provide information about its writing. They are provided for the convenience of those using this module to provide information about early printed sources and incunables. The typeDesc element can simply provide a summary description: - -

Uses a mixture of Roman and Black Letter types.

- +

Uses a mixture of Roman and Black Letter types.

-

Where detailed information about individual typefaces is to be recorded, this +

Where detailed information about individual typefaces is to be recorded, this may be done using the typeNote element: - -

Uses a mixture of Roman and Black Letter types. -Antiqua typeface, showing influence of Jenson's Venetian -fonts. -The black letter face is a variant of Schwabacher. - - -

-

Where information is required about both typography and written script, for +

Uses a mixture of Roman and Black Letter types.Antiqua typeface, showing influence of Jenson's Venetian +fonts.The black letter face is a variant of Schwabacher. +

+

Where information is required about both typography and written script, for example where a printed book contains extensive handwritten annotation, both handDesc and typeDesc elements should be supplied. Similarly, in the following example, the source text is a typescript with extensive handwritten annotation: - - -Authorial typescript, probably produced on Eliot's own -Remington. - - -Ezra Pound's annotations. -Commentary in Eliot's hand. - - -

-

The elements scriptNote and scriptDesc may be used in +Authorial typescript, probably produced on Eliot's own +Remington. Ezra Pound's annotations.Commentary in Eliot's hand. +

+

The elements scriptNote and scriptDesc may be used in exactly the same way to document a script used in this and other manuscripts, for example to record that this script was used mainly for the production of books or for charters; or that it is characteristic of some geographical area or @@ -1857,12 +1229,12 @@ script may also be recorded. By contrast, the handNote element would be used to document the way that a particular scribe uses a script, for example with long or short descenders, or using a pen which is cut in a different way, or an ink of a given colour, and so forth.

-

As with typeNote, the scriptNote element can be used in +

As with typeNote, the scriptNote element can be used in combination with handNote.

-
-
-Decoration -

It can be difficult to draw a clear distinction between aspects of a +

+
+ Decoration +

It can be difficult to draw a clear distinction between aspects of a manuscript which are purely physical and those which form part of its intellectual content. This is particularly true of illuminations and other forms of decoration in a manuscript. We propose the following elements for the purpose @@ -1870,91 +1242,51 @@ of delimiting discussion of these aspects within a manuscript description, and for convenience locate them all within the physical description, despite the fact that the illustrative features of a manuscript will in many cases also be seen as constituting part of its intellectual content.

-

The decoDesc element may contain simply one or more paragraphs +

The decoDesc element may contain simply one or more paragraphs summarizing the overall nature of the decorative features of the manuscript, as in the following example: - - -

The decoration comprises two full page miniatures, perhaps added by the +

The decoration comprises two full page miniatures, perhaps added by the original owner, or slightly later; the original major decoration consists of twenty-three large miniatures, illustrating the divisions of the Passion narrative and the start of the major texts, and the major divisions of the Hours; seventeen smaller miniatures, illustrating the suffrages to saints; and -seven historiated initials, illustrating the pericopes and major prayers.

- - +seven historiated initials, illustrating the pericopes and major prayers.

Alternatively, it may contain a series of more specific typed decoNote elements, each summarizing a particular aspect or individual instance of the decoration present, for example the use of miniatures, initials (historiated or otherwise), borders, diagrams, etc., as in the following example: - - - -

One full-page miniature, facing the beginning of the first Penitential -Psalm.

- - -

One seven-line historiated initial, commencing the first Penitential -Psalm.

- - -

Six four-line decorated initials, commencing the second through the seventh -Penitential Psalm.

- - -

Some three hundred two-line versal initials with pen-flourishes, commencing -the psalm verses.

- - -

Four-sided border decoration surrounding the miniatures and three-sided -border decoration accompanying the historiated and decorated initials.

- - - -

-

Where more exact indexing of the decorative content of a manuscript is +

One full-page miniature, facing the beginning of the first Penitential +Psalm.

One seven-line historiated initial, commencing the first Penitential +Psalm.

Six four-line decorated initials, commencing the second through the seventh +Penitential Psalm.

Some three hundred two-line versal initials with pen-flourishes, commencing +the psalm verses.

Four-sided border decoration surrounding the miniatures and three-sided +border decoration accompanying the historiated and decorated initials.

 +

+

Where more exact indexing of the decorative content of a manuscript is required, the standard TEI elements term or index may be used within the prose description to supply or delimit appropriate iconographic terms, as in the following example: - - - -

Fourteen large miniatures with arched tops, above five lines of text: -fol. 14rPericopes. St. John writing on Patmos, +

Fourteen large miniatures with arched tops, above five lines of text: fol. 14rPericopes. St. John writing on Patmos, with the Eagle holding his ink-pot and pen-case; some flaking of pigment, -especially in the sky -fol. 26rHours of the Virgin, Matins. -Annunciation; Gabriel and the Dove to the right -fol. 60rPrime. Nativity; the Virgin and -Joseph adoring the Child -fol. 66rTerce. Annunciation to the Shepherds, -one with bagpipes - -

- - - -

-
-
-Musical Notation -

Where a manuscript contains music, the musicNotation element may be +especially in the skyfol. 26rHours of the Virgin, Matins. +Annunciation; Gabriel and the Dove to the rightfol. 60rPrime. Nativity; the Virgin and +Joseph adoring the Childfol. 66rTerce. Annunciation to the Shepherds, +one with bagpipes

+

+
+
+ Musical Notation +

Where a manuscript contains music, the musicNotation element may be used to describe the form of notation employed, as in the following examples: - - -

Square notation on 4-line red staves.

- - - -

Neumes in campo aperto of the St. Gall type.

- - -

If a manuscript employs more than one notation, they must both be described within the +

Square notation on 4-line red staves.

+

Neumes in campo aperto of the St. Gall type.

 +

+

If a manuscript employs more than one notation, they must both be described within the same musicNotation element, for example as different list items.

-
-
-Additions and Marginalia -

The additions element can be used to list or describe any additions +

+
+ Additions and Marginalia +

The additions element can be used to list or describe any additions to the manuscript, such as marginalia, scribblings, doodles, etc., which are considered to be of interest or importance. Such topics may also be discussed or referenced elsewhere in a description, for example in the history @@ -1962,24 +1294,16 @@ element, in cases where the marginalia provide evidence of ownership. Note that this element may not be repeated within a single manuscript description. If several different kinds of additional matter are discussed, the content may be structured as a labelled list or a series of paragraphs. Some examples follow: - -

Doodles on most leaves, possibly by children, and often quite -amusing.

- -

Quelques annotations marginales des XVIe et XVIIe s.

 - - -

The text of this manuscript is not interpolated with sentences from Royal +

Doodles on most leaves, possibly by children, and often quite +amusing.

 +

Quelques annotations marginales des XVIe et XVIIe s.

 +

The text of this manuscript is not interpolated with sentences from Royal decrees promulgated in 1294, 1305 and 1314. In the margins, however, another somewhat later scribe has added the relevant paragraphs of these decrees, see -pp. 8, 24, 44, 47 etc.

-

As a humorous gesture the scribe in one opening of the manuscript, pp. 36 and +pp. 8, 24, 44, 47 etc.

As a humorous gesture the scribe in one opening of the manuscript, pp. 36 and 37, has prolonged the lower stems of one letter f and five letters þ and has -them drizzle down the margin.

- - - -

Spaces for initials and chapter headings were left by the scribe but not +them drizzle down the margin.

 +

Spaces for initials and chapter headings were left by the scribe but not filled in. A later, probably fifteenth-century, hand has added initials and chapter headings in greenish-coloured ink on fols 8r, 8v, 9r, 10r and 11r. @@ -1990,176 +1314,130 @@ can be made out, e.g. fol. 8rb vm olaf conung, and fol. 10ra Gipting olafs -konungs.

-

The manuscript contains the following marginalia: -Fol. 4v, left margin: hialmadr +konungs.

The manuscript contains the following marginalia: Fol. 4v, left margin: hialmadr ok brynjadr, in a fifteenth-century hand, imitating an addition made -to the text by the scribe at this point. -Fol. 5r, lower margin: þetta +to the text by the scribe at this point.Fol. 5r, lower margin: þetta þiki mer vera gott blek ennda kann ek icki betr sia, in a fifteenth-century hand, probably the same as that on the -previous page. -Fol. 9v, bottom margin: þessa bok +previous page.Fol. 9v, bottom margin: þessa bok uilda eg gæt lært med an Gud gefe myer Gott ad -læra; seventeenth-century hand. -

-

There are in addition a number of illegible scribbles in a later hand (or +læra; seventeenth-century hand.

There are in addition a number of illegible scribbles in a later hand (or hands) on fols 2r, 3r, 5v and -19r.

- - +19r.

-
-
-
-Bindings, Seals, and Additional Material -

The third major component of the physical description relates to supporting +

+
+
+ Bindings, Seals, and Additional Material +

The third major component of the physical description relates to supporting but distinct physical components, such as bindings, seals and accompanying -material. These may be described using the following specialist elements: - - - - - -

-
-Binding Descriptions -

The bindingDesc element contains a description of the state of the +material. These may be described using the following specialist elements:

+
+ Binding Descriptions +

The bindingDesc element contains a description of the state of the present and former bindings of a manuscript, including information about its material, any distinctive marks, and provenance information. This may be given as a series of paragraphs if only one binding is being described, or as a series of distinct binding elements, each describing a distinct binding where these are separately described. For example: - - -

Sewing not visible; tightly rebound over 19th-century pasteboards, reusing +

Sewing not visible; tightly rebound over 19th-century pasteboards, reusing panels of 16th-century brown leather with gilt tooling à la fanfare, Paris c. 1580-90, the centre of each cover inlaid with a 17th-century oval medallion of red morocco tooled in gilt (perhaps replacing the identifying mark of a previous owner); the spine similarly tooled, without raised bands or title-piece; -coloured endbands; the edges of the leaves and boards gilt. Boxed.

- - +coloured endbands; the edges of the leaves and boards gilt. Boxed.

-

Within a binding description, the elements decoNote and +

Within a binding description, the elements decoNote and condition are available, as alternatives to p, for paragraphs dealing exclusively with information about decorative features of a binding, or about its condition, respectively. - -

Bound, s. XVIII (?), in diced russia leather +

Bound, s. XVIII (?), in diced russia leather retaining most of the original 15th century metal ornaments (but with some -replacements) as well as the heavy wooden boards.

-

On each cover: alternating circular stamps of the Holy Monogram, a -sunburst, and a flower.

 -

On the cornerpieces, one of which is missing, a rectangular stamp -of the Agnus Dei.

 -Front and back leather inlaid panels very badly worn. -

Rebacked during the 19th century.

- - -

-

As noted above, () the element condition may +replacements) as well as the heavy wooden boards.

On each cover: alternating circular stamps of the Holy Monogram, a +sunburst, and a flower.

On the cornerpieces, one of which is missing, a rectangular stamp +of the Agnus Dei.

Front and back leather inlaid panels very badly worn.

Rebacked during the 19th century.

+

+

As noted above, () the element condition may also be used as an alternative to p for paragraphs concerned exclusively with the condition of a binding, where this has not been supplied as part of the physical description.

-
-
-Seals -

The sealDesc element supplies information about the seal(s) attached +

+
+ Seals +

The sealDesc element supplies information about the seal(s) attached to documents to guarantee their integrity, or to show authentication of the issuer or consent of the participants. It may contain one or more paragraphs summarizing the overall nature of the seals, or may contain one or more seal elements. - - - -

Round seal of Anders Olufsen in black wax: DAS +

Round seal of Anders Olufsen in black wax: DAS 930. Parchment tag, on which is written: pertinere nos -predictorum placiti nostri iusticarii precessorum dif.

- -

The seal of Jens Olufsen in black wax: DAS +predictorum placiti nostri iusticarii precessorum dif.

The seal of Jens Olufsen in black wax: DAS 1061. Legend: S IOHANNES OLAVI. Parchment tag on -which is written: Woldorp Iohanne G.

- - - +which is written: Woldorp Iohanne G.

-
-
-Accompanying Material -

The circumstance may arise where material not originally part of a manuscript +

+
+ Accompanying Material +

The circumstance may arise where material not originally part of a manuscript is bound into or otherwise kept with a manuscript. In some cases this material would best be treated in a separate msPart element (see below). There are, however, cases where the additional matter is not self-evidently a distinct manuscript: it might, for example, be a set of notes by a later scholar, or a file of correspondence relating to the manuscript. The accMat element is provided as a holder for this kind of -information. - -

-

Here is an example of the use of this element, describing a note by the +information.

+

Here is an example of the use of this element, describing a note by the Icelandic manuscript collector Árni Magnússon which has been bound with the manuscript: - - -

A slip in Árni Magnússon's hand has been stuck to the pastedown on the inside +

A slip in Árni Magnússon's hand has been stuck to the pastedown on the inside front cover; the text reads: Þidreks Søgu þessa hefi eg feiged af Sekreterer Wielandt Anno 1715 i Kaupmanna høfn. Hun er, sem eg sie, Copia af Austfirda bókinni (Eidagás) enn ecki progenies Brædratungu bokarinnar. Og er þar fyrer eigi i allann máta samhlioda þeirre er Sr Jon Erlendz son hefer ritad fyrer Mag. Bryniolf. Þesse -Þidreks Saga mun vera komin fra Sr Vigfuse á Helgafelle.

- - -

- - - - - - - - - - - - - + - - - - - - - - - - - - - - -
-
-
-
-History -

The following elements are used to record information about the history of a -manuscript: - - - - -

-

The three components of the history element all have the same + + + + + + + + + + + + + + +

+
+
+
+ History +

The following elements are used to record information about the history of a +manuscript:

+

The three components of the history element all have the same substructure, consisting of one or more paragraphs marked as p elements. Each of these three elements is also a member of the att.datable attribute class, itself a member of the att.datable.w3c class, and thus also carries the following -optional attributes: - -

-

Information about the origins of the manuscript, its place and date of +optional attributes:

+

Information about the origins of the manuscript, its place and date of writing, should be given as one or more paragraphs contained by a single origin element; following this, any available information on distinct stages in the history of the manuscript before its acquisition by its current @@ -2167,215 +1445,143 @@ holding institution should be included as paragraphs within one or more provenance elements. Finally, any information specific to the means by which the manuscript was acquired by its present owners should be given as paragraphs within the acquisition element.

-

Here is a fairly simple example of the use of this element: - - -

Written in Durham during the mid-twelfth -century.

-

Recorded in two medieval catalogues of the books belonging to +

Here is a fairly simple example of the use of this element: +

Written in Durham during the mid-twelfth +century.

Recorded in two medieval catalogues of the books belonging to Durham Priory, made in 1391 and -1405.

 -

Given to W. Olleyf by William Ebchester, Prior (1446-56) and later belonged to -Henry Dalton, Prior of Holy Island (Lindisfarne) according to inscriptions on ff. 4v and 5.

- -

Presented to Trinity College in -1738 by Thomas Gale and his son Roger.

 - - -

-

Here is a fuller example, demonstrating the use of multiple +1405.

Given to W. Olleyf by William Ebchester, Prior (1446-56) and later belonged to +Henry Dalton, Prior of Holy Island (Lindisfarne) according to inscriptions on ff. 4v and 5.

Presented to Trinity College in +1738 by Thomas Gale and his son Roger.

 +

+

Here is a fuller example, demonstrating the use of multiple provenance elements where distinct periods of ownership for the manuscript have been identified: - - - Written in Spain or Portugal in the + Written in Spain or Portugal in the middle of the 13th century (the date 1042, given in a marginal note on f. 97v, -cannot be correct.) -The Spanish scholar Benito Arias Montano +cannot be correct.)The Spanish scholar Benito Arias Montano (1527-1598) has written his name on f. 97r, and may be presumed to have owned -the manuscript. -It came somehow into the possession of etatsråd +the manuscript. It came somehow into the possession of etatsråd Holger Parsberg (1636-1692), who has written his name twice, once on the front pastedown and once on f. 1r, the former dated -1680 and the latter 1682. -Following Parsberg's death the manuscript was bought by +1680 and the latter 1682.Following Parsberg's death the manuscript was bought by etatsråd Jens Rosenkrantz (1640-1695) when Parsberg's library -was auctioned off (23 October 1693). -The manuscript was acquired by +was auctioned off (23 October 1693).The manuscript was acquired by Árni Magnússon from the estate of Jens Rosenkrantz, presumably at auction (the auction lot number 468 is written in red chalk on the flyleaf), either in 1696 -or 97. - - -

- - - - - - -
-
- Additional Information -

Three categories of additional information are provided for by +or 97. +

+ + + + + + +
+
+ Additional Information +

Three categories of additional information are provided for by the scheme described here, grouped together within the additional element described in this section. - - - - - +

-

None of these specialized constituent elements of +

None of these specialized constituent elements of additional is required. If any is supplied, it may appear once only; furthermore, the order in which elements are supplied should be as specified above. Alternatively, additional information may be provided as either one or more paragraphs or anonymous blocks, marked up as a series of p or ab elements.

- - - -
-Administrative Information -

The adminInfo element is used to hold information relating to the + + + +

+ Administrative Information +

The adminInfo element is used to hold information relating to the curation and management of a manuscript. This may be supplied as a note using the global note element. Alternatively, different aspects of this information may be presented grouped within one of the following -specialized elements: - - - -

-
-Record History -

The recordHist element may contain simply a series of paragraphs. +specialized elements:

+
+ Record History +

The recordHist element may contain simply a series of paragraphs. Alternatively it may contain a source element, followed by an optional -series of change elements. - - -

-

The source element is used to document the primary source of +series of change elements.

+

The source element is used to document the primary source of information for the record containing it, in a similar way to the standard TEI sourceDesc element within a TEI Header. If the record is a new one, made without reference to anything other than the manuscript itself, then it may simply contain a p element, as in the following example: - -

Directly catalogued from the original manuscript.

- +

Directly catalogued from the original manuscript.

-

Frequently, however, the record will be derived from some previously existing +

Frequently, however, the record will be derived from some previously existing description, which may be specified using the standard TEI bibl element, as in the following example: - - -

Information transcribed from The index of Middle English -verse123.

- - -

-

If, as is likely, a full bibliographic description of the source from which +

Information transcribed from The index of Middle English +verse123.

+

+

If, as is likely, a full bibliographic description of the source from which cataloguing information was taken is included within the listBibl element contained by the current additional element, or elsewhere in the current document, then it need not be repeated here. Instead, it should be referenced using the standard TEI ref element, as in the following example: - - - - -

Information transcribed from IMEV -123.

- - - - - -Carleton Brown and Rossell Hope Robbins +

Information transcribed from IMEV +123.

Carleton Brown and Rossell Hope Robbins The index of Middle English verse New York 1943 - - - - - +

-

The change element may also appear within the revisionDesc +

The change element may also appear within the revisionDesc element of the standard TEI header; its use here is intended to signal the similarity of function between the two container elements. Where the TEI header should be used to document the revision history of the whole electronic file to which it is prefixed, the recordHist element may be used to document changes at a lower level, relating to the individual description, as in the following example: - -On 10 March 2005 MJD added provenance -information - +On 10 March 2005 MJD added provenance +information

-
-
-Availability and Custodial History -

The availability element is another element also available in the +

+
+ Availability and Custodial History +

The availability element is another element also available in the TEI header, which should be used here to supply any information concerning access to the current manuscript, such as its physical location (where this is not implicit in its identifier), any restrictions on access, information about copyright, etc. - - -

Viewed by appointment only, to be arranged with curator.

- - -

In conservation, Jan. - Mar., 2002. On loan to the Bayerische -Staatsbibliothek, April - July, 2002.

- - -

The manuscript is in poor condition, due to many of the leaves being brittle +

Viewed by appointment only, to be arranged with curator.

In conservation, Jan. - Mar., 2002. On loan to the Bayerische +Staatsbibliothek, April - July, 2002.

The manuscript is in poor condition, due to many of the leaves being brittle and fragile and the poor quality of a number of earlier repairs; it should -therefore not be used or lent out until it has been conserved.

- - +therefore not be used or lent out until it has been conserved.

-

The custodialHist record is used to describe the custodial history +

The custodialHist record is used to describe the custodial history of a manuscript, recording any significant events noted during the period that it has been located within its holding institution. It may contain either a series of p elements, or a series of custEvent elements, each describing a distinct incident or event, further specified by a type attribute, and carrying dating information by virtue of its membership in the -att.datable class, as noted above. - -

-

Here is an example of the use of this element: - - - -

Conserved between March 1961 and February 1963 at Birgitte Dalls -Konserveringsværksted.

- -

Photographed in May 1988 by AMI/FA.

 - -

Dispatched to Iceland 13 November 1989.

 - - -

- - - - - - - - -
-
-
-Surrogates -

The surrogates element is used to provide information about +att.datable class, as noted above.

+

Here is an example of the use of this element: +

Conserved between March 1961 and February 1963 at Birgitte Dalls +Konserveringsværksted.

Photographed in May 1988 by AMI/FA.

Dispatched to Iceland 13 November 1989.

 +

+ + + + + + + + +
+
+
+ Surrogates +

The surrogates element is used to provide information about representations such as photographs or other representations of the manuscript -which may exist within the holding institution or elsewhere. - -

-

The surrogates element should not be used to repeat information +which may exist within the holding institution or elsewhere.

+

The surrogates element should not be used to repeat information about representations of the manuscript available within published works; this should normally be documented within the listBibl element within the additional element. However, it is often also convenient to record @@ -2385,41 +1591,28 @@ well as to provide more detailed descriptive information about the surrogate itself. Such information may be provided as prose paragraphs, within which identifying information about particular surrogates may be presented using the standard TEI bibl element, as in the following example: - - -microfilm (master)G.neg. 160 -n.d. -microfilm (archive)G.pos. 186 -n.d. -b/w printsAM 795 4to -27 January 1999copy of G.pos. -186 -b/w printsreg.nr. 75 -25 January 1999 -photographs of the spine, outside covers, stitching etc. - - - +microfilm (master)G.neg. 160 +n.d.microfilm (archive)G.pos. 186 +n.d.b/w printsAM 795 4to27 January 1999copy of G.pos. +186b/w printsreg.nr. 7525 January 1999photographs of the spine, outside covers, stitching etc. Note the use of the specialized form of title (general material designation) to specify the kind of surrogate being documented.

-

At a later revision, the content of the surrogates element is likely +

At a later revision, the content of the surrogates element is likely to be expanded to include elements more specifically intended to provide detailed information such as technical details of the process by which a digital or photographic image was made. For information about the inclusion of digital facsimile images within a TEI document, refer also to .

- - - -
-
-
-Manuscript Parts -

The msPart element may be used in cases where manuscripts or parts + + + +

+
+
+ Manuscript Parts +

The msPart element may be used in cases where manuscripts or parts of manuscripts that were originally physically separate have been bound together -and/or share the same call number. - -

-

Since each component of such a composite manuscript will in all likelihood +and/or share the same call number.

+

Since each component of such a composite manuscript will in all likelihood have its own content, physical description, history, and so on, the structure of msPart is in the main identical to that of msDesc, allowing one to retain the top level of identity (msIdentifier), but to branch @@ -2450,46 +1643,17 @@ element, --> --> - - - -Brussels -Koninklijke Bibliotheek van België / Bibliothèque royale de -Belgique -ms. 10066-77 - -

Miscellany of various texts; Prudentius, -Psychomachia; Physiologus de natura animantium -Latin - - - - - -ms. 10066-77 ff. 140r-156v - -Physiologus -Latin - - - -ms. 10066-77 ff. 112r-139r - - -Prudentius, Psychomachia -Latin - - - - -

- - - -
-
-Manuscript Fragments -

The msFrag element may be used inside msDesc when encoding +BrusselsKoninklijke Bibliotheek van België / Bibliothèque royale de +Belgiquems. 10066-77

Miscellany of various texts; Prudentius, +Psychomachia; Physiologus de natura animantiumLatinms. 10066-77 ff. 140r-156vPhysiologusLatinms. 10066-77 ff. 112r-139rPrudentius, PsychomachiaLatin +

+ + + +
+
+ Manuscript Fragments +

The msFrag element may be used inside msDesc when encoding one or more fragments of a scattered or fragmented manuscript. The fragment(s) described in a single msDesc element may be held either at several institutions or at a single institution, so different call numbers may be @@ -2497,10 +1661,8 @@ attached to the fragments. Inside the msFrag element, information about the single fragment or each dispersed part is provided: e.g. the current shelfmark or call number, the labels of the range of folios concerned if the fragment currently forms part of a larger manuscript, dimensions, extent, title, -author, annotations, illuminations and so on. - -

-

One well-known example of fragmentation is the Old Church Slavonic manuscript +author, annotations, illuminations and so on.

+

One well-known example of fragmentation is the Old Church Slavonic manuscript known as Codex Suprasliensis, substantial parts of which are to be found in three separate repositories, in Ljubljana, Warsaw, and St. Petersburg. This manuscript should be represented using one single @@ -2508,69 +1670,31 @@ Petersburg. This manuscript should be represented using one single fragmented manuscript, along with three distinct msFrag elements, each of which contains the current identifier of one of the fragments, a physical description, and other related information: - - - -Codex Suprasliensis - - - -Ljubljana -Narodna in univerzitetna knjiznica -MS Kopitar 2 - - -

Contains ff. 10 to 42 only - - - - -Warszawa -Biblioteka Narodowa -BO 3.201 - - - - -Sankt-Peterburg -Rossiiskaia natsional'naia biblioteka -Q.p.I.72 - - - - -

- - - -
-
- Module for Manuscript Description -

The module described in this chapter makes available the following +Codex SuprasliensisLjubljanaNarodna in univerzitetna knjiznicaMS Kopitar 2

Contains ff. 10 to 42 onlyWarszawaBiblioteka NarodowaBO 3.201Sankt-PeterburgRossiiskaia natsional'naia bibliotekaQ.p.I.72 +

+ + + +
+
+ Module for Manuscript Description +

The module described in this chapter makes available the following components: - - Manuscript Description - Manuscript Description - Description de manuscrits - 寫本描述 - Descrizione di manoscritti - Descrição do manuscrito - 手書きモジュール - + Manuscript DescriptionManuscript DescriptionDescription de manuscrits寫本描述Descrizione di manoscrittiDescrição do manuscrito手書きモジュール The selection and combination of modules to form a TEI schema is described in .

- - - - - - - - - - - - - -
+ + + + + + + + + + + + + +
diff --git a/P5/Source/Guidelines/en/ND-NamesDates.xml b/P5/Source/Guidelines/en/ND-NamesDates.xml index 080753c925..62514c7df2 100644 --- a/P5/Source/Guidelines/en/ND-NamesDates.xml +++ b/P5/Source/Guidelines/en/ND-NamesDates.xml @@ -1,16 +1,8 @@ - +
- Names, Dates, People, and Places -

This chapter describes a module which may be used for the encoding of names and other phrases descriptive of persons, places, or organizations, in a manner more detailed than that possible using the elements already provided for these purposes in the Core module. In section it was noted that the elements provided in the core module allow an encoder to @@ -18,7 +10,6 @@ $Id$ named or referred to only by supplying a value for the type attribute. The elements provided by the present module allow the encoder to supply a detailed sub-structure for such referring strings, and to distinguish explicitly between names of persons, places, and organizations.

-

This module also provides elements for the representation of information about the person, place, or organization to which a given name is understood to refer and to represent the name itself, independently of its application. In simple terms, where the core module allows one simply to represent that a given piece of text is a name, this module allows one @@ -26,17 +17,12 @@ $Id$ canonical name being used. A similar range is provided for names of places and organizations. The main intended applications for this module are in biographical, historical, or geographical data systems such as gazetteers and biographical databases, where these are to be integrated with encoded texts.

-

The chapter begins by discussing attributes common to many of the elements discussed in the remaining parts of the chapter () before discussing specifically the elements provided for the encoding of component parts of personal names (section ), place names (section ) and organizational names - (section ). Elements for encoding personal and organizational data are discussed in section . Elements for the encoding of geographical data are discussed in section . + (section ). Elements for encoding personal and organizational data are discussed in section . Elements for the encoding of geographical data are discussed in section . Finally, elements for encoding onomastic data are discussed in , and the detailed encoding of dates and times is described in section .

- - -
Attribute Classes Defined by This Module

Most of the elements made available by this chapter share some important characteristics which are expressed by their @@ -44,36 +30,24 @@ $Id$ attributes which support linkage of a naming element with the entity (person, place, organization) being named; members of the class att.datable have specialized attributes which support a number of ways of normalizing the date or time of the data encoded by the element concerned.

-
Linking Names and Their Referents -

The class att.naming is a subclass of the class att.canonical, - from which it inherits the following attributes: - - As discussed in , these attributes provide two different ways of associating any sort + from which it inherits the following attributes: As discussed in , these attributes provide two different ways of associating any sort of name with its referent. For cases where all that is required is to provide some minimal information about the person name, for example their occupation or status, the att.naming class also provides a simple role attribute. It also provides an additional attribute, which allows the name itself to be associated with - a base or canonical form: - - The encoder may use these attributes in combination as appropriate. For example: That silly man David Paul Brown + a base or canonical form: The encoder may use these attributes in combination as appropriate. For example: That silly man David Paul Brown has suffered ... The ref attribute should be used wherever it is possible to supply a direct link - such as a URI to indicate the location of canonical information about the referent. That silly man David Paul Brown has + such as a URI to indicate the location of canonical information about the referent. That silly man David Paul Brown has suffered ... This encoding requires that there exist somewhere a person element with the identifier DPB1, which will contain canonical information about this particular person, marked up using the elements discussed in below. The same element might alternatively be provided by some other document, of - course, which the same attribute could refer to by means of a URI, as explained in : That silly man David Paul Brown has suffered ...More than one URI may be supplied if the name refers to + course, which the same attribute could refer to by means of a URI, as explained in : That silly man David Paul Brown has suffered ...More than one URI may be supplied if the name refers to more than one person. For example, assuming the existence of another person element for Mrs Brown, with - identifier EBB1, a reference to the Browns might be encoded That wretched pair the Browns came + identifier EBB1, a reference to the Browns might be encoded That wretched pair the Browns came to dine ...

-

The key attribute is provided for cases where no such direct link is required: for example because resolution of the reference is carried out by some local convention, or because the encoder judges that no such resolution is necessary. As an example of the first case, a project might maintain its own local database system containing canonical @@ -81,35 +55,21 @@ $Id$ constructed in a project-specific way from the value supplied for the key attribute.In the module described by chapter a similar method is used to link element descriptions to the modules or classes to which they belong, for example. As an example of the second case, consider the use of well-established - codifications such as country or airport codes, which it is probably unnecessary for an encoder to expand further: I never fly from Heathrow Airport to France + codifications such as country or airport codes, which it is probably unnecessary for an encoder to expand further: I never fly from Heathrow Airport to France

-

However, as explained in , interchange is improved by use of tag URIs in ref instead of key.

-

The nymRef attribute has a more specialized use, where it is the name itself which is of interest rather than the person, place, or organization being named. See section for further discussion.

- -

All members of the att.naming class inherit the following attributes from the att.global.responsibility class: - - This enables an encoder to record the agency responsible for a given assertion (for example, the name) and the +

All members of the att.naming class inherit the following attributes from the att.global.responsibility class: This enables an encoder to record the agency responsible for a given assertion (for example, the name) and the confidence placed in that assertion by the encoder. Examples are given below.

-
Dating Attributes - -

Members of the att.datable class share the following attributes: - - - +

Members of the att.datable class share the following attributes:

The when attribute is used to specify a normalized form for any temporal expression, independently of how it - is represented in the text, as in the following example: June 9th The period is approaching which will terminate my present + is represented in the text, as in the following example: June 9th The period is approaching which will terminate my present copartnership. On the 1st Jany. next, it expires by its own limitation.

The period attribute provides a convenient way of associating an event or date with a named period. Its value @@ -118,76 +78,28 @@ $Id$ the encodingDesc of a TEI header. A taxonomy may contain simply a bibliographic reference to an external definition for it. More usefully, it may also contain a series of category elements, each with an identifier and a description. The identifier can then be used as the target for a period attribute. For example, a taxonomy of - named periods might be defined as follows: - - - Before 510 BC - - Between 510 and 323 BC - - - Hellenistic. Commonly treated as from the death of Alexander to the Roman conquest. - - - - - Roman - - - - The Christian period technically starts at the birth of Jesus, but in practice is considered to date from - the conversion of Constantine in 312 AD. - - - + named periods might be defined as follows: Before 510 BCBetween 510 and 323 BCHellenistic. Commonly treated as from the death of Alexander to the Roman conquest.Roman The Christian period technically starts at the birth of Jesus, but in practice is considered to date from + the conversion of Constantine in 312 AD.

-

With these definitions in place, any datable element may be associated with a specific period: - Stauropolis

+

With these definitions in place, any datable element may be associated with a specific period: Stauropolis

The other dating attributes provided by this class support a wide range of methods of specifying temporal information in a normalized form. The from and to attributes may be used to express the begining and ending of a - period of time, for example: - - - A political and social protest campaign against the policy of racial segregation on the public transit system of - the city of Montgomery. - -

+ period of time, for example: A political and social protest campaign against the policy of racial segregation on the public transit system of + the city of Montgomery.

The notBefore and notAfter attributes may be used to express a range of possibilities for a particular date (or time). For example the following element, extracted from an imaginary prosopographic entry for Anne Calthorpe, indicates that although the exact date of her death is not known, it can be narrowed down to a particular range: from 22 August 1579 to 28 March 1582, inclusive. Ostensibly the encoder has evidence that Anne Calthorpe was alive - on the 22nd of August 1579 and evidence that she was already dead on the 28th of March 1582. - -

+ on the 22nd of August 1579 and evidence that she was already dead on the 28th of March 1582.

Since when is used for a particular date or time, from and to for a duration, and notBefore and notAfter for a date or time within a range, it makes no sense to use when in combination with one or more of the others. Thus these Guidelines at present recommend against the use of when in combination with any of from, to, notBefore, or notAfter.

The from or to attributes imply that the temporal expression to which they are attached signifies a - duration, so the use of either with notBefore or notAfter means a duration is indicated. - - - notBefore - from - - - notAfter - range of possibilities, inclusive - duration from from to sometime before - notAfter, inclusive - - - to - duration from sometime after notBefore to - to, inclusive - duration from from to to, inclusive - -
+ duration, so the use of either with notBefore or notAfter means a duration is indicated. notBeforefromnotAfterrange of possibilities, inclusiveduration from from to sometime before + notAfter, inclusivetoduration from sometime after notBefore to + to, inclusiveduration from from to to, inclusive

-

Some further self-explanatory examples follow: - 15 March 1857. - - - Some time in March or April of 1857. - - - Lived in Amsterdam during March and April of 1857. - - - From the 1st of March to some time later in March or April of 1857. - - - From the 1st of March or sometime later to the end of April, - 1857. - - - From sometime in March of 1856 to sometime in April of 1858. - +

Some further self-explanatory examples follow: 15 March 1857. + Some time in March or April of 1857. + Lived in Amsterdam during March and April of 1857. + From the 1st of March to some time later in March or April of 1857. + From the 1st of March or sometime later to the end of April, + 1857. + From sometime in March of 1856 to sometime in April of 1858.

Normalization of date and time values permits the efficient processing of data (for example, to determine whether one event precedes or follows another). These examples all use the W3C standard format for representation of dates and times. - Further examples, and discussion of some alternative approaches to normalization are given in section below.

+ Further examples, and discussion of some alternative approaches to normalization are given in section below.

-
-
Names -
Personal Names -

The core rs and name elements can distinguish names in a text but are insufficiently powerful to mark their internal components or structure. To conduct nominal record linkage or even to create an alphabetically sorted list of personal names, it is important to distinguish between a family name, a forename and an honorary title. Similarly, when confronted with a string such as John, by the grace of God, king of England, lord of Ireland, duke of Normandy and Aquitaine, and count of Anjou, the analyst will often wish to distinguish amongst the various constituent elements present, since they provide additional information about the status, occupation, or residence of the person to whom the - name belongs. The following elements are provided for these and related purposes: - - - - - - - - + name belongs. The following elements are provided for these and related purposes:

-

In addition to the att.naming attributes mentioned above, all of the above elements are - members of the class att.personal, and thus share the following attributes: - - + members of the class att.personal, and thus share the following attributes:

The persName element may be used in preference to the general name element irrespective of whether or not the components of the personal name are also to be marked. @@ -274,14 +158,10 @@ target="#CONA"/>). The tag -->The element persName is synonymous with the element name type="person", except that its type attribute allows for further subcategorization of the personal name itself, for example as a married, birth, pen, pseudo, or religious name. Consequently the following examples - are equivalent: That silly man David Paul Brown has suffered the furniture of his office to be seized the third time for + are equivalent: That silly man David Paul Brown has suffered the furniture of his office to be seized the third time for rent. - That silly man - David Paul Brown - has suffered ... - That silly man David Paul Brown has suffered ... + That silly man David Paul Brown has suffered ... + That silly man David Paul Brown has suffered ... That silly man David Paul Brown has suffered ...

@@ -289,205 +169,73 @@ target="#CONA"/>). The tag -->The components occurring within it can be marked as such.

Many cultures distinguish between a family or inherited surname and additional personal names, often known as given names. These should be tagged using the surname and forename elements respectively - and may occur in any order: - Roosevelt, Franklin - Delano - - - Franklin - Delano - Roosevelt - + and may occur in any order: Roosevelt, FranklinDelanoFranklinDelanoRoosevelt

The type attribute may be used with both forename and surname elements to provide further - culture- or project-specific detail about the name component, for example: - Franklin - Delano - Roosevelt - - - Margaret - Hilda - Roberts - Thatcher - - Muhammad Ali - - Norman - St John Stevas - - Values for the type attribute are not constrained, and may be chosen as appropriate to the encoding + culture- or project-specific detail about the name component, for example: FranklinDelanoRooseveltMargaretHildaRobertsThatcherMuhammad AliNormanSt John Stevas Values for the type attribute are not constrained, and may be chosen as appropriate to the encoding needs of the project. They may be used to distinguish different kinds of forename or surname, as well as to indicate the function a name component fills within the whole. In this example, we indicate that a surname is toponymic, and also point - to the specific place name from which it is derived: - - Johan - Dystvold - - - Dystvold - + to the specific place name from which it is derived: JohanDystvoldDystvold

-

The value complex was suggested above for the not uncommon case where the whole of a surname is composed of several other surname elements. These nested surnames may be individually tagged as well, together with appropriate type - values: - Kara - - Hattersley- Smith - - + values: KaraHattersley- Smith

The full attribute may be used to indicate whether a name is an abbreviation, initials, or given in full: - - Maggie - Thatcher - + MaggieThatcher

-

These elements may be applied as the encoder considers appropriate, including cases where phrases or expressions are used - to stand for surnames or forenames, as in the following: - Peter - son of Herbert gives the king 40 m. for having custody of the land and heir of - John - son of Hugh... + to stand for surnames or forenames, as in the following: Peterson of Herbert gives the king 40 m. for having custody of the land and heir of + Johnson of Hugh...

- -

Similarly, patronymics may be treated as forenames, thus: ... but it remained for - Snorri - Sturluson - to combine the two traditions in cyclic form. When a patronymic is used as a surname, however (e.g. +

Similarly, patronymics may be treated as forenames, thus: ... but it remained for SnorriSturluson to combine the two traditions in cyclic form. When a patronymic is used as a surname, however (e.g. by an individual who otherwise would have no surname, but lives in a culture which requires surnames), it may be tagged as - such: Even Finnur - Jonsson acknowledged the artificiality of the procedure... Alternatively, it may + such: Even FinnurJonsson acknowledged the artificiality of the procedure... Alternatively, it may be felt more appropriate to mark a patronymic as a distinct kind of name, neither a forename nor a surname, using the - addName element: - - Egill - Skallagrmsson - - In the following example, the type attribute is used to distinguish a patronymic from other forenames: - - Sergei - Mikhailovic - Uspensky - + addName element: EgillSkallagrmsson In the following example, the type attribute is used to distinguish a patronymic from other forenames: + SergeiMikhailovicUspensky

- - -

This example also demonstrates the use of the sort attribute common to all members of the model.persNamePart class; its effect is to state the sequence in which forename and surname +

This example also demonstrates the use of the sort attribute common to all members of the model.persNamePart class; its effect is to state the sequence in which forename and surname elements should be combined when constructing a sort key for the name.

Some names include generational or dynastic information, such as a number, or phrases such as Junior, or the Elder; these qualifications may also be used to distinguish similarly named but unrelated people. In either case, the genName element may be used to distinguish such labels from other parts of the name, as in the following - examples: - Marques - Junior, Henrique - - - Charles - II - - - Rudolf - II - von Habsburg - - - Smith - Minor - + examples: MarquesJunior, Henrique + CharlesII + RudolfIIvon Habsburg + SmithMinor

It is also often convenient to distinguish phrases (historically similar to the generational labels mentioned above) used to link parts of a name together, such as von, of, de etc. It is often a matter of arbitrary choice whether such components are regarded as part of the surname or not; the nameLink element is provided as a means - of making clear what the correct usage should be in a given case, as in the following examples: - Mme - de la - Rochefoucault - - - Walter - de la Mare - + of making clear what the correct usage should be in a given case, as in the following examples: Mmede laRochefoucault + Walterde la Mare

Finally, the addName and roleName elements are used to mark all name components other than those already listed. The distinction between them is that a roleName encloses an associated name component such as an aristocratic or official title which exists in some sense independently of its bearer. The distinction is not always a clear one. As elsewhere, the type attribute may be used with either element to supply culture- or application- - specific distinctions. Some typical values for this attribute for names in the Western European tradition follow: - - An inherited or life-time title of nobility such as Lord, Viscount, - Baron, etc. - - An academic or other honorific prefixed to a name e.g. Doctor, - Professor, Mrs., etc. - - Membership of some elected or appointed organization such as President, - Governor, etc. - - Military rank such as Colonel. - - A traditional descriptive phrase or nick-name such as The Hammer, The - Great, etc. - Note, however, that the role a person has in a given context (such as witness, + specific distinctions. Some typical values for this attribute for names in the Western European tradition follow: An inherited or life-time title of nobility such as Lord, Viscount, + Baron, etc.An academic or other honorific prefixed to a name e.g. Doctor, + Professor, Mrs., etc.Membership of some elected or appointed organization such as President, + Governor, etc.Military rank such as Colonel.A traditional descriptive phrase or nick-name such as The Hammer, The + Great, etc. Note, however, that the role a person has in a given context (such as witness, defendant, etc. in a legal document) should not be encoded using the roleName element, since this is intended to mark roles which function as part of a person's name, not the role of the person bearing the name in general. Information about roles, occupations, etc. of a person are encoded within the person element discussed below in .

-

Here are some further examples of the usage of these elements: - Princess - Grace - - - Grandma - Moses - - - President - Bill - Clinton - - - Colonel - Gaddafi - - - Frederick - the Great - +

Here are some further examples of the usage of these elements: PrincessGrace + GrandmaMoses + PresidentBillClinton + ColonelGaddafi + Frederickthe Great

-

A name may have any combination of the above elements: - Governor - Edmund - G. - Jerry - Moonbeam - Brown - Jr. +

A name may have any combination of the above elements: GovernorEdmundG.JerryMoonbeamBrownJr.

Although highly flexible, these mechanisms for marking personal name components will not cater for every personal name, nor for every processing need. Where the internal structure of personal names is highly complex or where name components are particularly ambiguous, feature structures are recommended as the most appropriate mechanism to mark and analyze them, as further discussed in chapter .

-

White space is allowed and therefore significant between elements within name, persName, orgName, and placeName. Therefore Mary @@ -499,7 +247,6 @@ target="#CONA"/>). The tag -->The Mint ]]> encodes MaryAnn De Mint. See for more information on whitespace in XML.

-
Organizational Names

In these Guidelines, we use the term organization for any named collection of people regarded as a single unit. @@ -512,20 +259,14 @@ target="#CONA"/>). The tag -->The sense is harder to demonstrate than that of (say) a named person. In the case of businesses or other formally constituted institutions, the component parts of an organizational name may help to characterize the organization in terms of its perceived geographical location, ownership, likely number of employees, management structure, etc.

-

Like names of persons or places, organizational names can be marked up as referring strings or as proper names with the rs or name elements respectively. The element orgName is provided for use where it is desired - to distinguish organizational names more explicitly. - - This element is a member of the same attribute classes as persName, as discussed above in .

-

The orgName element may be used to mark up any form of organizational name: About a year back, a question of considerable interest + to distinguish organizational names more explicitly. This element is a member of the same attribute classes as persName, as discussed above in .

+

The orgName element may be used to mark up any form of organizational name: About a year back, a question of considerable interest was agitated in the Pennsyla. Abolition Society This encoding is equivalent to, but more specific than, either of the following representations: About a year back, a question of considerable interest - was agitated in the - Pennsyla. Abolition Society. + was agitated in the Pennsyla. Abolition Society. About a year back, a question of considerable interest was agitated in the Pennsyla. Abolition Society. As shown above, like the rs and name elements, the orgName element has a key attribute with which an @@ -537,32 +278,18 @@ target="#CONA"/>). The tag -->The as a phrase: The feeling in Canada is one of strong aversion to the United States Government, and of predilection for self-government under the English Crown - - The Justified Ancients of Mu Mu - or as a composite of other kinds of name: - - Ernst & Young + The Justified Ancients of Mu Mu or as a composite of other kinds of name: Ernst & Young

-

The components of an organization's name may include place names as well as personal names: A spokesman from - IBM - UK - said ... or role names: THE TICKET which you will +

The components of an organization's name may include place names as well as personal names: A spokesman from IBMUK said ... or role names: THE TICKET which you will receive herewith has been formed by the Democratic Whig party after the most careful deliberation, with a reference to all the great objects of NATIONAL, STATE, COUNTY and CITY concern, and with a single eye to the Welfare and Best Interests of the Community.

As indicated above, organizational names may also be specified hierarchically particularly where the named organization is itself a department or a branch of a larger organizational entity. The Department of Modern History, Glasgow - University is an example: - Department of Modern History - Glasgow - University - - + University is an example: Department of Modern HistoryGlasgowUniversity

-

@@ -576,7 +303,6 @@ target="#CONA"/>). The tag -->The

-
Place Names

Like other proper nouns or noun phrases used as names, place names can simply be marked up with the rs element, @@ -588,99 +314,52 @@ target="#CONA"/>). The tag -->The ). A place named simply in terms of geographical features such as mountains or rivers is represented using the geogName element (see section ). Finally, an expression consisting of phrases expressing spatial or other kinds of relationship between other kinds of named place may itself be regarded as - a way of referring to a place, and hence as a kind of named place (see section ). - - - + a way of referring to a place, and hence as a kind of named place (see section ).

As members of the att.naming class, all of these elements bear the attributes key, ref, and nymRef mentioned above. These attributes are primarily useful as a means of linking a place name with information about a specific place. Recommendations for the encoding of information about a place, as distinct from its name, are provided in below.

-

Like the persName element discussed in section , the placeName element may be regarded simply as an abbreviation for the elements name type="place" or rs type="place". The following encodings are thus equivalent:Strictly, a suitable value such as figurative should be added to the two place names which are presented periphrastically in the second version of this example. This would preserve the distinction indicated by the choice of rs rather than name to encode them in the first version of this example. - After spending some time in our modern Babylon, New York, I have proceeded to the City of Brotherly Love. - After spending some time in our modern Babylon, New York, I have proceeded + After spending some time in our modern Babylon, New York, I have proceeded to the City of Brotherly Love. + After spending some time in our modern Babylon, New York, I have proceeded to the City of Brotherly Love.

Geo-political Place Names -

A place name may contain text with no indication of its internal structure: Rochester, NY More usually +

A place name may contain text with no indication of its internal structure: Rochester, NY More usually however, a place name of this kind will be further analysed in terms of its constitutive geo-political or administrative units. These may be arranged in ascending sequence according to their size or administrative importance, for example: Rochester, New York, or as a single such unit, for example Belgium. These Guidelines provide a hierarchy - of generic element names, each of which may be more exactly specified by means of a type attribute: - - - - - -

+ of generic element names, each of which may be more exactly specified by means of a type attribute:

These elements are all members of the model.placeNamePart class, members of which may be - used anywhere that text is permitted, including within each other as in the following examples: - Rochester, New York - - - Laos, Southeast Asia - - - 6ème - Paris, - France - - + used anywhere that text is permitted, including within each other as in the following examples: Rochester, New York + Laos, Southeast Asia + 6èmeParis, France

Geographic Names

Places may also be named in terms of geographic features such as mountains, lakes, or rivers, independently of geo-political units. The geogName is provided to mark up such names, as an alternative to the - placeName element discussed above. For example: Mississippi River + placeName element discussed above. For example: Mississippi River

In addition to the usual phrase level elements, the geogName element may contain the following specialized - element: - - + element:

Where the geogFeat element is used to characterize the kind of geographic feature being named, the - name element will generally also be used to mark the associated proper noun or noun phrase: - Mississippi - River - A more complex example, showing a variety of practices, follows: The isolated ridge separates two great corridors which run from Glencoe into - Glen - Etive - , the - Lairig - Gartain - and the - Lairig - Eilde -

+ name element will generally also be used to mark the associated proper noun or noun phrase: MississippiRiver A more complex example, showing a variety of practices, follows: The isolated ridge separates two great corridors which run from Glencoe into GlenEtive, the LairigGartain and the LairigEilde

The Gaelic word lairig may be glossed as sloping hill face. The most efficient way of including this information in the above encoding would be to create a separate nym element for this - component of the name and then point to it using the nymRef attribute, as further discussed in .

+ component of the name and then point to it using the nymRef attribute, as further discussed in .

Relative Place Names -

All the place name specifications so far discussed are absolute, in the sense that they define only one place. A place may however be specified in terms of its relationship to another place, for example 10 miles northeast of Paris or near the top of Mount Sinai. These relative place names will @@ -689,28 +368,9 @@ target="#CONA"/>). The tag -->The of). A distance, possibly only vaguely specified, between the referent place and the place being indicated may also be present (e.g. 10 miles, near).

Relative place names may be encoded using the following elements in combination with either a placeName or a - geogName element. - - - Some examples of relative place names are: - near the top of - - Mount - Sinai - - - - 20 km - north of - Paris - If desired, the distance specified may be normalized using the unit and - quantity attributes of measure: - 11 miles - Northwest of - Providence, RI - + geogName element. Some examples of relative place names are: near the top ofMountSinai + 20 kmnorth ofParis If desired, the distance specified may be normalized using the unit and + quantity attributes of measure: 11 milesNorthwest ofProvidence, RI

The internal structure of place names is like that of personal names—complex and subject to an enormous amount of variation across time and different cultures. The recommendations in this section should however be adequate for a @@ -732,36 +392,30 @@ target="#CONA"/>). The tag -->The

- -
-
Event Names -

The eventName element is provided in parallel to other naming mechanisms; it is intended especially for canonical names that are used in texts to mention specific named events, whether real or fictional. - -

On Monday, she was writing about the +

On Monday, she was writing about the 1618 Defenestration of Prague which initiated the - long war.

- + long war.

+

+

+ + +

-

There are two major applications of eventName: - - to indicate names of events mentioned in transcribed text, such as in the above example; and - to indicate the names of events for which details are being provided in an event element. - + to indicate names of events mentioned in transcribed text, such as in the above example; andto indicate the names of events for which details are being provided in an event element.

For the first application, as with most other naming elements, the eventName element is a member of the att.canonical class, and thus the ref (or key) attribute may be used to - refer to a an event element (about which see ) or some other data item that contains + refer to a an event element (about which see ) or some other data item that contains further information about the event.

When used as a direct child of event, an eventName provides one of the names of the event about @@ -785,22 +439,18 @@ target="#CONA"/>). The tag -->The

-
Object Names - -

+

+ -

- + +

As with other proper nouns or noun phrases used as names, the names of objects may be marked up simply with the name element. For those working with a variety of named objects the objectName element provides more - flexibility. -

The Minster Lovell Jewel is probably the most similar to the + flexibility.

The Minster Lovell Jewel is probably the most similar to the Alfred Jewel and was found in Minster - Lovell in Oxfordshire and is kept at the Ashmolean Museum.

- + Lovell in Oxfordshire and is kept at the Ashmolean Museum.

The objectName element may be used to encode any named object whether or not this is a text-bearing object. The use of objectName by itself does not categorize the object referenced, but this may be done further with the @@ -812,9 +462,7 @@ target="#CONA"/>). The tag -->The intended for named objects; where an object is mentioned through a descriptive phrase but not named explicitly the rs element should be used.

-
-
Biographical and Prosopographical Data

This module defines a number of special purpose elements which can be used to markup biographical, historical, and @@ -824,7 +472,6 @@ target="#CONA"/>). The tag -->The such as the people referenced in a marked-up collection of documents, or persons who have served as informants in the creation of spoken corpora. It is also appropriate to use these elements to register information relating to those who have taken part in the creation of a TEI document.

-

To cater for this diversity, these Guidelines propose a flexible strategy, in which encoders may choose for themselves the approach appropriate to their needs. If one were interested, for example, in converting existing DNB-type records, and wanted to preserve the text as is, the person element (see ) could simply contain the text @@ -834,14 +481,8 @@ target="#CONA"/>). The tag -->The

Basic Principles

Information about people, places, organizations, and events, of whatever type, essentially comprises a series of statements or - assertions relating to: - characteristics or traits which do not, by and large, change over time - characteristics or states which hold true only at a specific time - events or incidents which may lead to a change of state or, less frequently, trait, - external resources where other information on the subject can be found. - + assertions relating to: characteristics or traits which do not, by and large, change over timecharacteristics or states which hold true only at a specific timeevents or incidents which may lead to a change of state or, less frequently, trait,external resources where other information on the subject can be found.

-

Characteristics or traits are typically independent of an individual's volition or action and can be either physical, such as hair and eye colour; or cultural, such as ethnicity and caste. The distinction is not entirely straightforward: gender and sex can be regarded as culturally determined with physical manifestations, @@ -851,45 +492,25 @@ target="#CONA"/>). The tag -->The of European empires and their unstable constructions of race. When such a construct defined individuals' identities beyond their volition, the markup and documentation should reflect this as a culturally-determined characteristic.

-

States include, for example, marital status, place of residence, and position or occupation. Such states have a definite duration, that is, they have a beginning and an end and are typically a consequence of the individual's own action or that of others.

-

Changes in state refer to life-changing or identity-changing events such as birth, marriage, or appointment to office; such events will normally be associated with a specific date or a fairly narrow date-range. Changes in states can also cause or be caused by changes in characteristics. Any statement or assertion about these aspects of a person's life will be based on some source, possibly multiple sources, possibly contradictory. Taking all this into account it follows that each such statement or assertion needs to be documentable, put into a time frame, and be relatable to other statements or assertions.

-

The elements defined by the module described in this chapter may, for the most part, all be regarded as specializations - of one or other of the above three classes. Generic elements for state, trait, and event are also defined: - - - - - - - + -->

-

When developing a prosopography record of a named entity it is a common practice to refer explicitly to other resources, for example the Library of Congress Name Authority File, Virtual Internationl Authority File (VIAF), a gazetteer of places like Pleiades, or a printed book. - - - +

Here is a simple example: - - Rome - - 41.891775, 12.486137 - - 423025 - capital of the Roman Empire - + Rome41.891775, 12.486137423025capital of the Roman Empire

@@ -900,190 +521,70 @@ target="#CONA"/>). The tag -->The about a group of people with a distinct identity (for example a named theatrical troupe) should be recorded using the org element described in section below.

These elements may appear only within a listPerson element, which groups such descriptions together, and - optionally also describes relationships amongst the people listed. - - - + optionally also describes relationships amongst the people listed.

-

One or more listPerson elements may be supplied - within the standOff element (see ) or, when used to list the participants in + within the standOff element (see ) or, when used to list the participants in a linguistic interaction, within the particDesc (participant description) element in the profileDesc element of a TEI header. Like other forms of list, however, listPerson can also appear within the body of a text when the module defined by this chapter is included in a schema.

-

The type attribute may be used to distinguish lists of people of different kinds where this is considered convenient: - - - - - Adam Schiff - District Attorney for Manhattan in - seasons 1 to 10 of Law and Order. - - - Mike Logan - NYPDNew York Police + Adam SchiffDistrict Attorney for Manhattan in + seasons 1 to 10 of Law and Order.Mike LoganNYPDNew York Police Department Detective regularly appearing in seasons 1 to 5 of Law and Order and seasons 5 to 7 - of Law and Order: Criminal Intent. - - - Benjamin Stone - Executive Assistant District Attorney for + of Law and Order: Criminal Intent.Benjamin StoneExecutive Assistant District Attorney for Manhattan in seasons 1 to 4 of Law - and Order - - - Jack McCoy - An Executive Assistant District Attorney then District + and OrderJack McCoyAn Executive Assistant District Attorney then District Attorney for Manhattan in seasons 5 to 10 of Law and Order, in seasons 1, 9, 11, and 19 of Law and Order: Special Victims Unit, and in - season 1 of Law and Order: Trial by Jury. - - - Jamie Ross - An Assistant District Attorney for + season 1 of Law and Order: Trial by Jury.Jamie RossAn Assistant District Attorney for Manhattan in seasons 7 & 8 of Law and Order, and a defense attorney in seasons 10 & 11, and then a judge in Law and Order: Trial by - Jury. - - - Joe Fontana - NYPDNew York Police + Jury.Joe FontanaNYPDNew York Police Department Detective regularly appearing - in seasons 15 & 16 of Law and Order. - - - - - - Adam Schiff - U.S. Representative from California since 2013. - - - Mike Logan - Gridiron football player for the Pittsburgh Steelers from - 2001 to 2006. - - - Benjamin Stone - Michigan State Senator from 1968 to 1979. - - - Jack McCoy - Iowa State Representative from 1955 to 1959. - - - Jamie Ross - Broadway actor, with occasional forays into television, - from 1971 to roughly 2007. - - - Joe Fontana - A member of Canada’s House of Commons from 1987 to 2006, - and mayor of London, Ontario from 2010 to 2014. - - - - + in seasons 15 & 16 of Law and Order.Adam SchiffU.S. Representative from California since 2013.Mike LoganGridiron football player for the Pittsburgh Steelers from + 2001 to 2006.Benjamin StoneMichigan State Senator from 1968 to 1979.Jack McCoyIowa State Representative from 1955 to 1959.Jamie RossBroadway actor, with occasional forays into television, + from 1971 to roughly 2007.Joe FontanaA member of Canada’s House of Commons from 1987 to 2006, + and mayor of London, Ontario from 2010 to 2014.

- -

The person element carries several attributes. As a member of the classes att.global.responsibility, att.editLike, and att.global.source class, it carries the usual attributes for providing details about the information recorded - for that person, such as its reliability or source: - - - - In addition, a small number of very commonly used personal properties may be recorded using attributes - specific to person and personGrp: - - -

- +

The person element carries several attributes. As a member of the classes att.global.responsibility, att.editLike, and att.global.source class, it carries the usual attributes for providing details about the information recorded + for that person, such as its reliability or source: In addition, a small number of very commonly used personal properties may be recorded using attributes + specific to person and personGrp:

These attributes are intended for use where only a small amount of data is to be encoded in a more or less normalized form, possibly for many person elements, for example when encoding basic facts about respondents to a questionnaire. When however a more detailed encoding is required for all kinds of information about a person, for example in a historical gazetteer, then it will be more appropriate to use the elements age, sex and others described elsewhere in this chapter.

-

Note that the age attribute is not intended to record the person's age expressed in years, months, or other temporal unit. Rather it is intended to record into which age bracket, for the purposes of some analysis, the person falls. A simple (perhaps too simple to be useful) binary classification of age brackets would be child and adult. The actual age brackets useful to various projects are likely to be varied and idiosyncratic, and thus these Guidelines make no particular recommendation as to possible values. Instead, individual projects are recommended to - define the values they use in their own customization file, using a declaration like the following: - - - - - - - - - less than 18 years of age - - - 18 to 65 years of age - - - over 65 years of age - - - - - - The above declaration, were it properly placed in a customization file, establishes that the age + define the values they use in their own customization file, using a declaration like the following: less than 18 years of age18 to 65 years of ageover 65 years of age The above declaration, were it properly placed in a customization file, establishes that the age attribute of person has only three possible values, child, adult, and retired. For more information on customization see .

-

The person element may contain many sub-elements, each specifying a different property of the person being described. The remainder of this section describes these more specific elements. For convenience, these elements are grouped into three classes, corresponding with the tripartite division outlined above: one for traits, one for states and one for events. Each class may contain specific elements for common types of biographical information, and contains a generic element for other, user-defined, types of information.

All the elements in these three classes belong to the attribute class att.datable, which - provides the following attributes: - - as discussed in above.

- + provides the following attributes: as discussed in above.

Personal Characteristics

The model.persStateLike class contains elements describing physical or socially-constructed characteristics, traits, or states of a person. Members of the class comprise the following specific elements: - - - - - - - - - - - - - - - - - - - All, apart from langKnowledge and persona, allow content of ordinary prose containing - phrase-level elements. - Status AB1 in the RG Classification scheme - + All, apart from langKnowledge and persona, allow content of ordinary prose containing + phrase-level elements. Status AB1 in the RG Classification scheme

@@ -1096,24 +597,13 @@ exemplifying here too? --> Scholars face similar issues when marking sex and gender according to cultural systems from times and places not their own. A statement of the practice adopted in a given encoding may usefully be provided in the editorialDecl element discussed in .

-

The langKnowledge element contains either paragraphs or a number of langKnown elements; it may take a tags attribute, which provides one or more standard codes or tags for the languages. The langKnown element must have a tag attribute, which indicates the language with the same kind of - language tag. These language tags are discussed in detail in .

+ language tag. These language tags are discussed in detail in .

Furthermore, the langKnown element also has a level attribute to indicate the level of the person's - competence in the language. It is thus possible either to say: -

Speaks fluent Fulani, Wolof, and French. Some knowledge of - English.

- or - - Fulani - Wolof - French - English - - + competence in the language. It is thus possible either to say:

Speaks fluent Fulani, Wolof, and French. Some knowledge of + English.

 or FulaniWolofFrenchEnglish

The persona element may contain the same component elements as a person element. Its function is to document a distinct persona assumed by the person element containing it. A person, not necessarily fictional, @@ -1122,8 +612,7 @@ exemplifying here too? --> one specific individual, from a role, which is a set of characteristics that many different people can assume. An actor does not change their persona when adopting a different role, but none of the personas associated with one person can properly be associated with another.

- -

The persPronouns element may be used to indicate +

The persPronouns element may be used to indicate the personal pronouns used, or assumed to be used, by the individual being described. It is common practice in email signatures and biographies, for people to include their @@ -1139,8 +628,7 @@ exemplifying here too? --> preferred personal pronouns, or may be used inside a person or persona element to indicate the associated pronouns.

- -

For example, the following entry from a hypothetical +

For example, the following entry from a hypothetical prosopography lists only the nominative case of the preferred pronouns as identified by Miss Major Griffin-Gracy, a historical figure. @@ -1150,102 +638,46 @@ exemplifying here too? --> Proposal: new element <gi>persPronouns</gi> . --> - - - - Miss Major - Griffin-Gracy - - - trans woman - - -

Veteran of the Stonewall Riots. Founder of the + Miss MajorGriffin-Gracytrans woman

Veteran of the Stonewall Riots. Founder of the Griffin-Gracy Educational Retreat and Historical Center (the House of GG). Activist and advocate for transgender and gender-nonconforming people of - color.

- - - + color.

-

Personal pronouns often occur as part of the closer of an +

Personal pronouns often occur as part of the closer of an email, post, or other electronic communication. - -

- Dear all, -

With apologies for length. I'm expanding a schema …

- - - Diane Jakacki, Ph.D. - Digital Scholarship Coordinator - Affiliate Faculty in Comparative & Digital Humanities - Bucknell University - d…@….edu - (she/her/hers) - - Principal Investigator, +
Dear all,

With apologies for length. I'm expanding a schema …

Diane Jakacki, Ph.D.Digital Scholarship CoordinatorAffiliate Faculty in Comparative & Digital HumanitiesBucknell Universityd…@….edu(she/her/hers) + Principal Investigator, LAB Cooperative and REED London Online Chair, ADHO Conference Coordinating Committee - -
-

-

The sex and gender elements each carry a value attribute to give values from a project-internal taxonomy, or an - external standard. - female - woman - As elsewhere, these coded values may be used as an alternative to or normalization of the actual descriptive - text contained in the element. The previous example might equally well be given as - - - +

+

The sex and gender elements each carry a value attribute to give values from a project-internal taxonomy, or an + external standard. femalewoman As elsewhere, these coded values may be used as an alternative to or normalization of the actual descriptive + text contained in the element. The previous example might equally well be given as

-

The generic trait and state elements are also members of this class, - - - These elements can be used to extend the range of information supplied about an individual's personal +

The generic trait and state elements are also members of this class, These elements can be used to extend the range of information supplied about an individual's personal characteristics. Either may contain an optional label element, used to provide a human-readable specification for the characteristic concerned and a description of the feature itself supplied within a desc element. These may be followed by or one or more p elements supplying more detailed information about the trait. In either case, these may be followed by one or more notes or bibliographical references. The type, ref, and - key attributes may be used to indicate a fuller definition of the combination of feature and value. - - - Ethnic Albanian. - - + key attributes may be used to indicate a fuller definition of the combination of feature and value. Ethnic Albanian.

-

These elements are provided as a simple means of extending the set of descriptive features available in a standardized way. For example, there are no predefined elements for such features as eye or hair colour. If these are to be recorded, - they may simply be added as new types of trait: - - - blue - - - - brown - - + they may simply be added as new types of trait: bluebrown

-

If none of the more specialized elements listed above is appropriate, then a choice must be made between the two generic elements trait and state. If you wish to distinguish between characteristics that are generally perceived to be transient and those which are generally considered unchanging, use state for the former, and trait for the latter. It may also be helpful to note that traits are typically, but not necessarily, independent of the volition or action of the holder. If the distinction between state and trait is not considered relevant or useful, use state.

-

The persName element is repeatable and can, like all TEI elements, take the attribute xml:lang to indicate the language of the content of the element, as well as a type attribute to indicate the type of name, whether a nickname, maiden or birth name, alternative form, etc. This is useful in cases where, for example, a @@ -1258,54 +690,24 @@ exemplifying here too? --> prioritization, and hence less likelihood of offence. The Icelandic scholar and manuscript collector Árni Magnússon, to give his name in standard modern Icelandic spelling, is known in Danish as Arne Magnusson, the form which he himself, as a long term resident of Denmark, generally used; there is also a Latinized form, Arnas Magnæus, which he used in his - scholarly writings. All three forms can be given, and in any order: - - Árni Magnússon - Arne Magnusson - Arnas Magnæus - - + scholarly writings. All three forms can be given, and in any order: Árni MagnússonArne MagnussonArnas Magnæus

-

At the other extreme, a person may be named periphrastically as in the following example: - - Simon, son of Richard - Essex - 1219-1223 - - +

At the other extreme, a person may be named periphrastically as in the following example: Simon, son of RichardEssex1219-1223

-

Alternatively, the generic name element may be used for all of the naming components in a description. For example, a description of the first living held by the Icelandic clergyman and poet Jón Oddsson Hjaltalín might be - tagged as follows: -

Jón's first living — which he apparently accepted rather reluctantly — was at Háls í + tagged as follows:

Jón's first living — which he apparently accepted rather reluctantly — was at Háls í Hamarsfirði, Múlasýsla, to which he was presented on 7 April 1777. He was ordained the following month and spent three years at Háls, but was never happy there, due largely to the general penury in which he was forced to live — a recurrent theme throughout the early part of his life. In June of 1780 the bishop recommended that Jón should promoveres til andet bedre kald, end det hand hidindtil - har havt, and on 12 July it was agreed that he should exchange livings with sr. Þórður Jónsson at Kálfafell á Síðu, - Skaftafellssýsla.

ÞÍ, Stms I.15, p. 733. ÞÍ, Stms I.17, p. - 102. - + har havt, and on 12 July it was agreed that he should exchange livings with sr. Þórður Jónsson at Kálfafell á Síðu, + Skaftafellssýsla.

ÞÍ, Stms I.15, p. 733.ÞÍ, Stms I.17, p. + 102.

-

Similarly, the generic state or trait element may be used in preference to the more specific elements - listed above: - - - American citizen from 15 January 2002. - - is the same as: - American citizen from 15 January 2002. - or even: - - + listed above: American citizen from 15 January 2002. is the same as: American citizen from 15 January 2002. or even:

-
Personal Events @@ -1317,95 +719,40 @@ exemplifying here too? --> content model similar to that of state and trait. The chief difference is that event can include a placeName element to identify the name of the place where the event occurred.

Two particular events in a person's life, namely birth and death, are both ubiquitous and usually considered - particularly important, and thus may be represented by specialized elements for the purpose: - - - + particularly important, and thus may be represented by specialized elements for the purpose:

In the following example, we give a brief summary of the wedding of Jane Burden to the English writer, designer, and socialist William Morris, encoded as an event element embedded within the person element used to record data about Morris, though we could equally well have embedded the event element within the - person element for Burden, or have encoded it independently of either person element: - - - - - William Morris and Jane Burden were married at St + person element for Burden, or have encoded it independently of either person element: William Morris and Jane Burden were married at St Michael's Church, Ship Street, Oxford on 26 April 1859. The wedding was - conducted by Morris's friend R. W. Dixon with Charles Faulkner as the best man. The bride was given away by her father, Robert Burden. According to the account that Burne-Jones gave Mackail + conducted by Morris's friend R. W. Dixon with Charles Faulkner as the best man. The bride was given away by her father, Robert Burden. According to the account that Burne-Jones gave Mackail M. said to Dixon beforehand Mind you don't call her Mary but he did. The entry in the Register reads: William Morris, 25, Bachelor Gentleman, 13 George Street, son of William Morris decd. Gentleman. Jane Burden, minor, spinster, 65 Holywell Street, d. of Robert Burden, Groom. The witnesses were Jane's parents and Faulkner. None of Morris's family attended the ceremony. Morris presented Jane with a plain gold ring bearing the London hallmark for 1858. She gave her husband a double-handled antique silver - cup. - J. W. Mackail, The Life of William Morris, 1899. - - - - Robert Burden - - - R.W. Dixon - - - Charles Faulkner - - - - Edward - Burne-Jones - - - - J.W. Mackail - - In this example the ref attributes on the various name elements point either to an external + cup.J. W. Mackail, The Life of William Morris, 1899.Robert BurdenR.W. DixonCharles FaulknerEdwardBurne-JonesJ.W. Mackail In this example the ref attributes on the various name elements point either to an external source or to a person element within which other information about the person named may be found. As further discussed below (), a relation element may then be used to link them in a more - meaningful way: - - - - + meaningful way:

-

As mentioned above, all these elements, both the specific and the generic, are members of the att.datable attribute class, which means they can be limited in terms of time. The following encoding, for - example, demonstrates that the person named David Jones changed his name in 1966 to David Bowie: - - David Jones - David Bowie - - +

As mentioned above, all these elements, both the specific and the generic, are members of the att.datable attribute class, which means they can be limited in terms of time. The following encoding, for + example, demonstrates that the person named David Jones changed his name in 1966 to David Bowie: David JonesDavid Bowie

-

All the generic elements are also members of the att.global.responsibility and att.editLike classes. These classes make available the attributes cert, to indicate +

All the generic elements are also members of the att.global.responsibility and att.editLike classes. These classes make available the attributes cert, to indicate the degree of certainty, resp, the agency responsible, evidence, the nature of the evidence used, and source, a pointer to a resource from which the information derives. In this way it is possible, in the case of multiple and conflicting sources, to provide more than one view of what happened, as in the following example: - -

Born in Brixton on 8 January - 1947.

-

Born in Berkhamsted on 9 January - 1947.

 - +

Born in Brixton on 8 January + 1947.

Born in Berkhamsted on 9 January + 1947.

Personal Relationships -

When the module defined by this chapter is included in a schema, the following two elements may be used to document - relationships amongst the persons, places, or organizations identified: - - - These elements are both members of the att.typed class, from which they inherit + relationships amongst the persons, places, or organizations identified: These elements are both members of the att.typed class, from which they inherit the type and subtype attributes in the usual way. The value specified for either attribute on a listRelation element is implicitly applicable to all of its child relation elements, unless overridden.

@@ -1425,33 +772,21 @@ exemplifying here too? --> relationship employs. These relationships can be inverted: parents are passive and children active in the relationship is child of; similarly works for inverts the active and passive roles of employs.

-

For example: - - - - This example defines the relationships amongst a number of people not further described here; +

For example: This example defines the relationships amongst a number of people not further described here; we assume however that each person has been allocated an identifier such as P1, P2, etc. which can be linked to using references such as #P1, #P2, etc. Then the above set of relation - elements describe the following three relationships amongst the people referenced: - P1 and P2 are parents of P3 and P4. - P1 and P2 are linked in a mutual relationship called spouse—that is, P2 is the spouse of P1, and P1 is - the spouse of P2. - P1 has the social relationship employer with respect to P3 and P4. -

+ elements describe the following three relationships amongst the people referenced: P1 and P2 are parents of P3 and P4.P1 and P2 are linked in a mutual relationship called spouse—that is, P2 is the spouse of P1, and P1 is + the spouse of P2.P1 has the social relationship employer with respect to P3 and P4.

Relationships within places and organizations are further discussed in the relevant sections below. Relationships between for example organizations and places, or places and persons, may be handled in exactly the same way.

-
Organizational Data

The org and listOrg elements are used to store data about an organization such as its preferred name, - its locations, or key persons within it. - - - These elements are intended to be used in a way analogous to the place and person elements + its locations, or key persons within it. These elements are intended to be used in a way analogous to the place and person elements discussed elsewhere in this chapter, that is to provide a unique wrapper element for information about an entity, distinct from references to that entity which are typically encoded using a naming element such as name type="org" or orgName. The content of a naming element will represent the way an organization is named in a given context; @@ -1469,87 +804,24 @@ exemplifying here too? --> elements: the presence of the orgName element described in is however strongly recommended.

In other respects, the org element is used in much the same way as place or person. An - organization may have different names at different times: - The Silver Beetles - The Beatles - + organization may have different names at different times: The Silver BeetlesThe Beatles

The names of the people making up an organization can also change over time, (if they are known at all). For example: - - The Silver Beetles - The Beatles - - - John Lennon - Paul McCartney - George Harrison - Stuart Sutcliffe - Pete Best - - - - - John Lennon - Paul McCartney - George Harrison - Ringo Starr - - - + The Silver BeetlesThe BeatlesJohn LennonPaul McCartneyGeorge HarrisonStuart SutcliffePete BestJohn LennonPaul McCartneyGeorge HarrisonRingo Starr

-

An org may contain subordinate orgs: - Oxford University Computing Services - - Information and Support Group - - - Infrastructure Group - - Networking Team - - - System Development Team - - - - Learning Technologies Group - - - +

An org may contain subordinate orgs: Oxford University Computing ServicesInformation and Support GroupInfrastructure GroupNetworking TeamSystem Development TeamLearning Technologies Group

The following example demonstrates the use of the listOrg element to group together a number of org - elements, each of which is defined solely by means of an informal description, itself containing other names. -

The TEI institutional hosts are: - - Brown University - The host contribution is made jointly by the Brown University Women Writers - Project and the Brown University Library's Center for Digital Initiatives. - - - Nancy - Hosting is provided by a group of institutions located in Nancy, France, coordinated by - Loria and also including ATILF and INIST. - - - Oxford University - Hosting is provided by the Research Technologies Service at Oxford University - Computing Services. - - - University of Virginia - Virginia's host support comes jointly from the Institute for Advanced Technology in the - Humanities and the University of Virginia Library. - - + elements, each of which is defined solely by means of an informal description, itself containing other names.

The TEI institutional hosts are: Brown UniversityThe host contribution is made jointly by the Brown University Women Writers + Project and the Brown University Library's Center for Digital Initiatives.NancyHosting is provided by a group of institutions located in Nancy, France, coordinated by + Loria and also including ATILF and INIST.Oxford UniversityHosting is provided by the Research Technologies Service at Oxford University + Computing Services.University of VirginiaVirginia's host support comes jointly from the Institute for Advanced Technology in the + Humanities and the University of Virginia Library.

In a more elaborated version of this example, the organizational names tagged using orgName might be linked using the key or ref attribute to a unique org element elsewhere.

-
Places -

In we discuss various ways of naming places such as towns, countries, etc. In much the same way as these Guidelines distinguish between the encoding of names for people and the encoding of other data about people, so they also distinguish between the encoding of names for places and the encoding of other data about places. In this @@ -1557,22 +829,16 @@ exemplifying here too? --> named or referenced within a text. Such data may be useful as a way of normalizing or standardizing references to particular places, as the raw material for a gazetteer or similar reference document associated with a particular text or set of texts, or in conjunction with any form of geographical information system.

-

The following elements are provided for this purpose: - - - +

The following elements are provided for this purpose:

-

The model.placeStateLike class contains elements describing characteristics of a place which have a definite duration, such as its name. Any member of the model.placeNamePart may be used for this purpose, since a place element will usually contain at least one, and possibly several, placeName-like elements indicating the names associated with it, by different people, in different languages, or at different times.

-

For example, the modern city of Lyon in France was in Roman times known as Lugdunum. Although the modern and the Roman city are not physically co-extensive, they have significant areas which overlap, and we may therefore wish to regard them as the same place, while supplying both names with an indication of the time period during which each was current.

-

Places usually have physical locations in addition to names. As with the example of Lyon, the precise geographic location and extent of a place may change over time, and so locations like names may need to be qualified with indications of the time period to which they apply. Locations may be @@ -1582,123 +848,46 @@ exemplifying here too? --> city of London, either by specifying its latitude and longitude, or by specifying that we mean the city called London located in the province called Ontario within the country called Canada.

-

In addition we may wish to supply a brief characterization of the place identified, for example to state that it is a city, an administrative area such as a country, or a landmark of some kind such as a monument or a battlefield. If our typology of places is simple, the open ended type attribute is the easiest way to represent it: so we might say place type="city", place type="battlefield" etc.

- -

Within the place element, the following elements may be used to provide more information about specific aspects - of the place in a structured form: - - - + of the place in a structured form:

Varieties of Location -

A location may be specified in one or more of the following ways: - by supplying a string representing its coordinates in some standardized way within a geo element, as - shown below - by supplying one or more place name component elements (e.g. country, settlement etc.) to - place it within a geo-political context - by supplying a postal address, e.g. using the address element - by supplying a brief textual description, e.g. using the desc element - by using a non-TEI XML vocabulary such as the Geography Markup Language - We give examples of all of these methods in the remainder of this section.

- +

A location may be specified in one or more of the following ways: by supplying a string representing its coordinates in some standardized way within a geo element, as + shown belowby supplying one or more place name component elements (e.g. country, settlement etc.) to + place it within a geo-political contextby supplying a postal address, e.g. using the address elementby supplying a brief textual description, e.g. using the desc elementby using a non-TEI XML vocabulary such as the Geography Markup Language We give examples of all of these methods in the remainder of this section.

The simplest method of specifying a location is by means of its geographic coordinates, supplied within the geo element. This may be used to supply any kind of positional information, using one of the many different geodetic systems available. Such systems vary in their format, in their scope or coverage, and more fundamentally in the reference frame (the datum) used for the coordinate system itself. The default recommended by these Guidelines is to supply a string containing two real numbers separated by whitespace, of which the first indicates latitude and the second longitude according to the 1984 World Geodetic System (WGS84); this is the system currently used - by most GPS applications which TEI users are likely to encounter.See . The most recent revision of this standard is known as + by most GPS applications which TEI users are likely to encounter.See . The most recent revision of this standard is known as the Earth Gravity Model 1996.We might therefore record the information about the place known as - Lyon as follows: - - Lyon - Lugdunum - 45.769559 4.834843 - - + Lyon as follows: LyonLugdunum45.769559 4.834843

-

Identifying Lyon by its geo-political status as a settlement within a country forming part of a larger political - entity, we might represent the same place as follows: - - Lyon - Lugdunum - - EU - France - - - Elements such as bloc are specialized forms of placeName, as discussed in .

+ entity, we might represent the same place as follows: LyonLugdunumEUFrance Elements such as bloc are specialized forms of placeName, as discussed in .

We may use the same procedure to represent the location of smaller places, such as a street or even an individual - building: - Brasserie Georges - - - Lyon - IIème - Perrache - 30, Cours de Verdun - - Note the use of the type attribute to categorize more precisely both the kind of place + building: Brasserie GeorgesLyonIIèmePerrache30, Cours de Verdun Note the use of the type attribute to categorize more precisely both the kind of place concerned (a building) and the kind of name used to locate it, for example by characterizing the generic district as an arrondissement, or a quartier.

- -

We may also treat imaginary places in the same way: - Atlantis - - beyond - The Pillars of Hercules - -

- -

A location sometimes resembles a set of instructions for finding a place: - Yasgur's Farm - Woodstock Festival Site - - one mile - north west of - Bethel - New York - - +

We may also treat imaginary places in the same way: AtlantisbeyondThe Pillars of Hercules

+

A location sometimes resembles a set of instructions for finding a place: Yasgur's FarmWoodstock Festival Siteone milenorth west ofBethelNew York

-

The element address may also be used to identify a location in terms of its postal or other address: - Protestant Cemetery - Cimitero Acattolico - - Italy - Rome - Testaccio - - -

- Via Caio Cestio, 6 - 00153 Roma -
- - When, as here, the same place is given multiple locations, the type attribute should be +

The element address may also be used to identify a location in terms of its postal or other address: Protestant CemeteryCimitero AcattolicoItalyRomeTestaccio

Via Caio Cestio, 600153 Roma
When, as here, the same place is given multiple locations, the type attribute should be used to characterize the kind of location, as a means of indicating that these are alternative ways of identifying the same place, rather than that the place is spread across several locations.

-

The location element may thus identify a place to a greater or lesser degree of precision, using a variety of means: a name, a set of names, or a set of coordinates. The geo element introduced earlier is by default understood to supply a value expressed in a specific (and widely used) notation. If a location contains more than one geo, this is interpreted as being really the same place in the universe, but with different systems used to refer to it. If there is a lack of consensus about the location (of, for example, Camelot), more than one location should be used, each with its own geo.

-

By default, the content of geo is interpreted as following the standard known as the World Geodetic System (WGS). This may be modified, however, in two ways.

Firstly, the content of the geo element can be expressed some other way, that is, according to some different @@ -1708,35 +897,16 @@ exemplifying here too? --> specifically designed to represent this kind of information. This technique is used throughout these Guidelines where specialized markup is required, for example to embed mathematical expressions or vector graphics, and is further described and exemplified in . For geographic information, suitable non-TEI vocabularies include: - - the OpenGIS Geography Markup Language (GML) being defined by the OGCThe OGC is an + the OpenGIS Geography Markup Language (GML) being defined by the OGCThe OGC is an international voluntary consensus standards organization whose members maintain the Geography Markup Language standard. The OGC coordinates with the ISO TC 211 standards organization to maintain consistency between OGC and ISO standards work. GML is also an ISO standard (ISO 19136:2007). - - the Keyhole Markup Language (KML) used by Google MapsSee - - + the Keyhole Markup Language (KML) used by Google MapsSee +

In the following example, we have defined the location of the place Lyon using GML and indicated - the two names associated with it at different times: - - Lyon - Lugdunum - - - - - 45.256 -110.45 46.46 -109.48 43.84 -109.86 45.8 -109.2 45.256 -110.45 - - - - - + the two names associated with it at different times: LyonLugdunum 45.256 -110.45 46.46 -109.48 43.84 -109.86 45.8 -109.2 45.256 -110.45

-

A bibl element may be used within location to indicate the source of the location information.

@@ -1744,256 +914,88 @@ exemplifying here too? --> Roman Inscriptions of Britain, 262 -
Multiple Places

A place may contain other places. This containment relation can be directly modelled in XML: thus we can say that the - towns of Vilnius and Kaunas are both in a place called Lithuania (or Lietuva) as follows: - Lithuania - Lietuva - - Vilnius - - - Kaunas - - + towns of Vilnius and Kaunas are both in a place called Lithuania (or Lietuva) as follows: LithuaniaLietuvaVilniusKaunas

This does not, of course, imply that Vilnius and Kaunas are the only places constituting Lithuania; only that they are within it. A separate place element may indicate that it is a part of Lithuania by supplying a relation element, as discussed below ().

-

As a further example, the islands of Mauritius, Réunion, and Rodrigues are collectively known as the Mascarene Islands. Grouped together with Mauritius there are also several smaller offshore islands, with rather picturesque French names. These offshore islands do not however constitute an identifiable place as a whole. One way of representing this is as - follows: - Mascarene Islands - Mascarenhas Archipelago - - Mauritius - - - La roche qui pleure - - - Île aux cerfs - - - - - Rodrigues - - - Réunion - - + follows: Mascarene IslandsMascarenhas ArchipelagoMauritiusLa roche qui pleureÎle aux cerfsRodriguesRéunion

Here is a more complex example, showing the variety of names associated at different times and in different languages with a set of hierarchically grouped places—the settlement of Carmarthen Castle, within the town of Carmarthen, within - the administrative county of Carmarthenshire, Wales. - - Cymru - Wales - Wallie - Wallia - Le Waleis - - Carmarthenshire - - Carmarthen - Kaermerdin - Caerfyrddin - - castle of Carmarthen - - - - - + the administrative county of Carmarthenshire, Wales. CymruWalesWallieWalliaLe WaleisCarmarthenshireCarmarthenKaermerdinCaerfyrddincastle of Carmarthen

As noted previously, country, region, and settlement are all specializations of the generic placeName element; they are not specializations of the place element. If it is desired to distinguish amongst kinds of place this can only be done by means of the type attribute as in the above example.

-

This use of multiple place elements should be distinguished from the (possibly simpler) case where a number of places with some property in common are being grouped together for convenience, for example, in a gazetteer. The listPlace element is provided as a means of grouping places together where there is no implication that the - grouped elements constitute a distinct place. For example: - Herefordshire - - - Abbey Dore - - 51.969604 -2.893146 - - - - Acton Beauchamp - - - - - - Hereford - - - Leominster - - - - + grouped elements constitute a distinct place. For example: HerefordshireAbbey Dore51.969604 -2.893146Acton BeauchampHerefordLeominster

States, Traits, and Events -

There are many different kinds of information which it might be considered useful to record for a place in addition to its name and location, and the categories selected are likely to be very project-specific. As with persons therefore these Guidelines make no claim to comprehensiveness in this context. Instead, the generic state, trait, and event elements defined by this module should be used. Each of these may be customized for particular needs by means of their type attribute. These are complemented by a small number of predefined - elements of general utility: - - - - + elements of general utility:

-

These are all specializations of the generic trait element. This element may be used for almost any kind of event in the life of a place; no specialized version of this element is proposed, nor do we attempt to enumerate the possible values which might be appropriate for the type attribute on any of these generic elements.

-

Here is an example, showing how the specific and generic elements may be combined: - - Iceland - Ísland - 65.00 -18.00 - - Area: 103,000 sq km - - -

Constitutional republic

- - -

Part of the kingdom of Denmark

- - - Iceland became independent on 17 June 1944. - - -

An independent republic since June 1944

- - +

Here is an example, showing how the specific and generic elements may be combined: IcelandÍsland65.00 -18.00Area: 103,000 sq km

Constitutional republic

Part of the kingdom of Denmark

Iceland became independent on 17 June 1944.

An independent republic since June 1944

-

In the following example, the climate example is used to provided a detailed discussion of this particular - aspect of the information available about a particular place: - - Greece - - Greece's climate is divided into three well defined classes: - - - It features mild, wet winters and hot, dry summers. Temperatures rarely reach extremes, although snowfalls + aspect of the information available about a particular place: GreeceGreece's climate is divided into three well defined classes:It features mild, wet winters and hot, dry summers. Temperatures rarely reach extremes, although snowfalls do occur occasionally even in Athens, Cyclades or - Crete during the winter. - - - - It is found primarily in Western Greece + Crete during the winter.It is found primarily in Western Greece (Epirus, Central Greece, Thessaly, Western Macedonia as well as central parts of Peloponnesus like Achaea, Arcadia and parts of Laconia where the Alpine range pass - by) - - - - It is found in Central and Eastern Macedonia as + by)It is found in Central and Eastern Macedonia as well as in Thrace at places like Komotini, Xanthi and northern Evros. It features cold, - damp winters and hot, dry summers. - - - - + damp winters and hot, dry summers.

As the above example shows, state and trait elements, and others of the same class, can be nested hierarchically within each other. When this is done, values for the type attribute are to be understood as cumulatively inherited, as elsewhere in the TEI scheme (for example on category or linkGrp). In the following example, the outermost population element concerns the squirrel population between the dates given. - This is then broken down into red and gray squirrel populations, and within that into male and female: - - - 12 - 15 - - - 23 - 45 - - - The dating and responsibility attributes here behave slightly differently from the type attribute: + This is then broken down into red and gray squirrel populations, and within that into male and female: 12152345 The dating and responsibility attributes here behave slightly differently from the type attribute: responsibility is not an additive property, and therefore an element either states it explicitly, or inherits it from its nearest ancestor. Dating is slightly different again, in that a child element may specify a date more precisely than its parent, as in the example above.

-

An event may be related to other named entities, and thus may appear within an org, person, personGrp, persona, or place element as well as within a listEvent or another event.

-
-
Relations Between Places -

The relation element may also be used to express relationships of various kinds between places, or between places and persons, in much the same way as it is used to express relationships between persons alone. Returning to the Mascarene Islands example cited above, we might define the island group and its constituents separately, but indicate - the relationship by means of a relation element: - - - Mascarene islands - Mascarenhas Archipelago - - - Mauritius - - - - Rodrigues - - - Réunion - - - - + the relationship by means of a relation element: Mascarene islandsMascarenhas ArchipelagoMauritiusRodriguesRéunion

-

This stand-off style of representation has the advantage that we can now also represent the fact that a place may be a part of more than one other place; for example, Réunion is part of France, as well as part - of the Mascarenes. If we add a declaration for France to the list above: - - France - - we can now model this dual allegiance by means of a relation element: - - + of the Mascarenes. If we add a declaration for France to the list above: France we can now model this dual allegiance by means of a relation element:

- - - @@ -2269,7 +1295,7 @@ occupation and residence.

Zambia - + @@ -2326,61 +1352,34 @@ occupation and residence.

Paris Attacks took place at six different locations in Paris; this might be encoded as an event with a where attribute with six space-separated values, or using a listPlace (nested into the event or standalone).

-

Events may also be modeled as hierarchies of nested events. For example, a two part meeting might be represented as follows: - - - All day meeting to resolve content models - - first part - - - second part - - - + All day meeting to resolve content modelsfirst partsecond part

-

For event as a child element of person, note the Section .

-
Objects -

- - - - - An object is any material thing whether real, in existence, fictional, missing, or purported about which more +

An object is any material thing whether real, in existence, fictional, missing, or purported about which more information is known. Where objects have proper names the objectName element may be used to encode these. However, many objects are not named but the object element may still be used to provide a description of them. The object element is a more general descriptive form of the msDesc element. The latter should be used for describing manuscripts and similar text-bearing objects but can be viewed as a more specific form of the object element.

-

- Please note: The object element is a recent addition to TEI P5 Guidelines as of version 3.5.0 and as such might +

Please note: The object element is a recent addition to TEI P5 Guidelines as of version 3.5.0 and as such might be more prone to further revision in the next few releases as its use develops. This may be particularly evident where its contents have been borrowed from msDesc and have yet to be generalized from their use in the context of manuscript descriptions.

-

The object element usually appears inside the +

The object element usually appears inside the listObject element which is used to group descriptions of identifiable objects. The listObject - element is a member of model.listLike and so may appear inside + element is a member of model.listLike and so may appear inside standOff, or anywhere else that list is allowed. This enables the flexibility of using listObject to contain a set of metadata descriptions stored in the TEI header, or as a list of objects transcribed from a source document. The equivalent list for manuscript descriptions is listBibl.

-

- - - - - - - +

Overall, the basic structure of an object element is akin to that of msDesc in that it is providing a structured description of an object. After a group of identifying information, it has the option of paragraphs or, if the msdescription module is @@ -2392,64 +1391,25 @@ occupation and residence.

Where descendents of object still have the hallmarks of their use in manuscript description, the descriptions as relating to manuscripts should be interpreted as applying to all forms of object (text-bearing) or not.

-

The objectIdentifier element is a general-purpose +

The objectIdentifier element is a general-purpose grouping element for location or identification information relating to a single object or resource. It is very similar to an msIdentifier element with less contraints on the order of its contents. The objectIdentifier may be more or less detailed dependent on the needs of the encoder. In some cases an object may be used mostly as a common reference point for multiple objectName elements to refer back to. In situations, one might provide more detailed - information in the objectIdentifier where it is available or desirable. Compare - - - Excalibur - -

Excalibur is the name for the legendary sword of King Arthur.

- - where only a single objectName is provided and below where multiple versions are provided. - - - Excalibur - Caliburn - Caledfwlch - Calesvol - Kaledvoulc'h - Caliburnus - Wales - -

Excalibur is the main English name for the legendary + information in the objectIdentifier where it is available or desirable. Compare Excalibur

Excalibur is the name for the legendary sword of King Arthur.

 where only a single objectName is provided and below where multiple versions are provided. ExcaliburCaliburnCaledfwlchCalesvolKaledvoulc'hCaliburnusWales

Excalibur is the main English name for the legendary sword of King Arthur. In Welsh it is called Caledfwlch, in Cornish it is called Calesvol, in Breton it is called Kaledvoulc'h, and in Latin it is called Caliburnus. In some versions of the legend, Excalibur’s blade was engraved with phrases on opposite - sides: Take me up and Cast me away (or similar).

- - + sides: Take me up and Cast me away (or similar).

Moreover, the objectIdentifier may include an address element to provide the address at which the object currently resides. The use of location within this enables the provision of geographical coordinates when describing objects not housed in traditional repositories or institutions. This may also be used to supplement more traditional repository location information if available and, for example, to enable providing outputs such as maps - showing the location of encoded objects. - - Mask of Tutankhamun - 256a - 60672 - 220 - Museum of Egyptian Antiquities -

- 15 Meret Basha - Ismailia - Cairo - Egypt - - 30.047778, 31.233333 - -
- - + showing the location of encoded objects. Mask of Tutankhamun256a60672220Museum of Egyptian Antiquities
15 Meret BashaIsmailiaCairoEgypt30.047778, 31.233333

The msContents element is currently used to provide a description of the intellectual contents of any text on an object and, being optional, is not necessary if there are no intellectual contents to describe. (Such contents, especially in the @@ -2461,49 +1421,17 @@ occupation and residence.

information about surrogates for the object (such as digital facsimiles) as well as administrative and curatorial information. A full description of an object can provide more or less detail at any level to represent the state of knowledge about the object. - - - - - Mask of Tutankhamun - 256a - 60672 - 220 - Museum of Egyptian Antiquities -
- 15 Meret Basha - Ismailia - Cairo - Egypt - - 30.047778, 31.233333 - -
- - -

The back and shoulders of the mask is inscribed with a protective spell in Egyptian hieroglyphs formed of ten + Mask of Tutankhamun256a60672220Museum of Egyptian Antiquities
15 Meret BashaIsmailiaCairoEgypt30.047778, 31.233333

The back and shoulders of the mask is inscribed with a protective spell in Egyptian hieroglyphs formed of ten vertical and horizontal lines. This spell first appeared on masks in the Middle Kingdom at least 500 years - before Tutankhamun, and comes from chapter 151 of the Book of the Dead.

- - -

The mask of Tutankhamun is 54cm x 39.3cm x 49cm. It is constructed from two layers of high-karat gold that + before Tutankhamun, and comes from chapter 151 of the Book of the Dead.

The mask of Tutankhamun is 54cm x 39.3cm x 49cm. It is constructed from two layers of high-karat gold that varies in thickness from 1.5-3mm. It weighs approximately 10.23kg and x-ray crystallography shows that it is composed of two alloys of gold with a lighter 18.4 karat shade being used for the face and neck while a heavier - 22.5 karat gold was used for the rest of the mask.

-

In the mask Tutankhamun wears a nemes headcloth which has the royal insignia of a cobra (Wadjet) and vulture + 22.5 karat gold was used for the rest of the mask.

In the mask Tutankhamun wears a nemes headcloth which has the royal insignia of a cobra (Wadjet) and vulture (Nekhbet) on it. These are thought respectively to symbolize Tutankhamun's rule of both Lower Egypt and Upper Egypt. His ears are pierced for earrings. The mask has rich inlays of coloured glass and gemstones, including lapis lazuli surrounding the eye and eyebrows, quartz for the eyes, obsidian for the pupils. The broad collar is - made up of carnelian, feldspar, turquoise, amazonite, faience and other stones.

- - - -

The mask of Tutankhamun was created in Egypt around 1323 BC. It is a death mask of the 18th-dynasty ancient Egyptian Pharaoh Tutankhamun - who reigned 1332–1323 BC.

- - -

The mask of Tutankhamun was found in his burial chamber at Theban Necropolis in the Valley of the Kings in + made up of carnelian, feldspar, turquoise, amazonite, faience and other stones.

The mask of Tutankhamun was created in Egypt around 1323 BC. It is a death mask of the 18th-dynasty ancient Egyptian Pharaoh Tutankhamun + who reigned 1332–1323 BC.

The mask of Tutankhamun was found in his burial chamber at Theban Necropolis in the Valley of the Kings in 1922. On 28 October 1925 the excavation team led by English archaeologist Howard Carter opened the heavy sarcophagus and three coffins and were the first people in around 3,250 years to see the mask of Tutankhamun. Carter wrote in his diary: The pins removed, the lid was raised. The penultimate scene was disclosed – @@ -2511,120 +1439,69 @@ occupation and residence.

Osiris … the mask bears that god's attributes, but the likeness is that of Tut.Ankh.Amen – placid and beautiful, with the same features as we find upon his statues and coffins. The mask has fallen slightly back, thus its gaze is straight up to the heavens. -

- - In December 1925, the mask was removed from the tomb, placed in a crate and transported 635 - kilometres (395 mi) to the Egyptian Museum in Cairo, where it remains on public display. - - - - - When it was discovered in 1925, the 2.5kg narrow gold beard was no longer attached to - the mask and was reattached to the chin by use of a wooden dowel in 1944. - In August 2014 when the mask was removed from its display case for cleaning, the +

In December 1925, the mask was removed from the tomb, placed in a crate and transported 635 + kilometres (395 mi) to the Egyptian Museum in Cairo, where it remains on public display. When it was discovered in 1925, the 2.5kg narrow gold beard was no longer attached to + the mask and was reattached to the chin by use of a wooden dowel in 1944. In August 2014 when the mask was removed from its display case for cleaning, the beard fell off again. Those working in the museum unadvisedly used a quick-drying epoxy to attempt to fix - it, but left the beard off-centre. - The damage was noticed and repaired in January 2015 by a German-Egyptian team who - used beeswax, a material known to be used as adhesives by the ancient Egyptians. - - - - - - + it, but left the beard off-centre. The damage was noticed and repaired in January 2015 by a German-Egyptian team who + used beeswax, a material known to be used as adhesives by the ancient Egyptians.

- -

If the object is being referenced from elsewhere in the document, this is usually done with an objectName. For example here the Alfred-Jewel xml:id is referenced from a paragraph elsewhere in the document using the ref attribute on the objectName element. - - - - - - United Kingdom - Oxfordshire - Oxford - University of Oxford - Ashmolean Museum - English Treasures - AN1836p.135.371 - https://en.wikipedia.org/wiki/Alfred_Jewel - Alfred Jewel - - -

The Alfred Jewel is about 6.4 cm in length and is made of combination of filigreed gold + United KingdomOxfordshireOxfordUniversity of OxfordAshmolean MuseumEnglish TreasuresAN1836p.135.371https://en.wikipedia.org/wiki/Alfred_JewelAlfred Jewel

The Alfred Jewel is about 6.4 cm in length and is made of combination of filigreed gold surrounding a polished teardrop shaped piece of transparent quartz. Underneath the rock crystal is a cloisonné enamel image of a man with ecclesiastical symbols. The sides of the jewel holding the crystal in place contain an openwork inscription saying "AELFRED MEC HEHT GEWYRCAN", meaning 'Alfred ordered me - made'.

- - - It is generally accepted that the Alfred Jewel dates from the late 9th Century and - was most likely made in England. - The jewel was discovered in 1693 at Petherton Park, North Petherton in the English county + made'.

It is generally accepted that the Alfred Jewel dates from the late 9th Century and + was most likely made in England. The jewel was discovered in 1693 at Petherton Park, North Petherton in the English county of Somerset, on land owned by Sir Thomas Wroth. North Petherton is about 8 miles away from Athelney, where King - Alfred founded a monastery. - A description of the Alfred Jewel was first published in 1698, in the Philosophical - Transactions of the Royal Society. - It was bequeathed to Oxford University by Colonel Nathaniel Palmer (c. 1661-1718) and today is in - the Ashmolean Museum in Oxford. - - - - - -

+ Alfred founded a monastery. A description of the Alfred Jewel was first published in 1698, in the Philosophical + Transactions of the Royal Society. It was bequeathed to Oxford University by Colonel Nathaniel Palmer (c. 1661-1718) and today is in + the Ashmolean Museum in Oxford.

The Minster Lovell Jewel is probably the most similar to the Alfred Jewel and was found in Minster - Lovell in Oxfordshire and is kept at the Ashmolean Museum. -

- + Lovell in Oxfordshire and is kept at the Ashmolean Museum. +

- -

+

There is no restriction on the form, size, or type of object that may be described by an object element, however, some objects may be more adequately described by a place element depending on context. Where a description of an object is being provided in terms of identification, physical characteristics, or history, then an object element may be preferred. Where metadata is being recorded about the geo-political location, population, or similar traits, then the place element may be better suited. A corresponding relation between an object description and place may be recorded through the use of the corresp attribute. An example of a large object that might be described with the object element could be a building such as the Central Library of the National Autonomous University of Mexico.

- - -

+

- - - The Central Library of UNAM - The Central Library of the National Autonomous University of Mexico - La Biblioteca Central de la Universidad Nacional Autónoma de México - Mexico City - Coyoacán - Mexico - - - -

The Central Library encompasses an area of 16 thousand square + + + The Central Library of UNAM + The Central Library of the National Autonomous University of Mexico + La Biblioteca Central de la Universidad Nacional Autónoma de México + Mexico City + Coyoacán + Mexico + + + +

The Central Library encompasses an area of 16 thousand square meters and is built on a three meter platform. The base contains two basalt fountains and decorative reliefs inspired by pre-Hispanic art.

-

The library has ten windowless floors for book storage, each having enough space for 120 thousand volumes. +

The library has ten windowless floors for book storage, each having enough space for 120 thousand volumes. These storage areas have the necessary lighting, temperature and humidty conditions for book conservation. In the reading room, flanked by a garden on each side, the diffuse and matte light is filtered through thin tecali stone slabs. The semi-basement of the building contains the service and administrative offices of the library.

-

The building facades are covered with one of the largest murals in the world and is made from naturally +

The building facades are covered with one of the largest murals in the world and is made from naturally colored stone tiles. It is entitled Historical Representation of Culture and is by Juan O'Gorman.

- - - - At the base of the building there are two basalt fountains and decorative reliefs + + + At the base of the building there are two basalt fountains and decorative reliefs around the outside that are inspired by pre-Hispanic art. The color of the stone in these elements is left exposed to take advantage of the stone's texture as an aesthetic and expressive element, and to give a sense of continuity to the external pavement. - - -

The outside windowless portion of the building contains one of the largest murals in the world. This is + + +

The outside windowless portion of the building contains one of the largest murals in the world. This is called Historical Representation of the Culture and is a stone polychromatic mosaic based on the combination of 12 basic colors. The mural is created in an impressionist style where the coloured tiles when seen from a distance form specific figures. The 12 @@ -2635,39 +1512,31 @@ There is no restriction on the form, size, or type of object that may be describ Wall, this represents the pre-Hispanic era and is dominated by mythical elements relating to the life-death duality. The left side of the main axis there are deities and scenes pertaining to the creation of life. The right hand side of the mural contains figures - relating to death. For a more detailed description see https://en.wikipedia.org/wiki/Central_Library_(UNAM)#Murals.

- - - - - In 1948 the architect and artist Juan O'Gorman, in + relating to death. For a more detailed description see https://en.wikipedia.org/wiki/Central_Library_(UNAM)#Murals.

+ + + + + In 1948 the architect and artist Juan O'Gorman, in collaboration with architects Gustavo Saavedra and Juan Martinez de Velasco designed the building with a functionalist approach, as part of the greater project of the construction of the University City on the grounds of the Pedregal de San Angel in Mexico City. Originally the building was planned to host the National Library and National Newspaper Library of Mexico. The library finally opened its doors for the first time on 5 April 1956. In July 2007 it was declared a UNESCO world heritage site. - - - - - - The library was significantly remodelled from 1981 - 1983 with the + + + + + The library was significantly remodelled from 1981 - 1983 with the purpose of changing from closed shelving to open stacks, providing users more direct access to the collections. - - - - - - - -

- - - + + + + + +

@@ -2676,11 +1545,7 @@ There is no restriction on the form, size, or type of object that may be describ -
- - -
Names and Nyms

So far we have discussed ways in which a name or referring string encountered in running text may be resolved by @@ -2694,154 +1559,64 @@ There is no restriction on the form, size, or type of object that may be describ Russian might all be regarded as existing independently of any person to which they are attached, and also independently of any variant forms that might be attested in different sources (such as Jon or Johnny in English, or Jehan or Jojo in French). We use the term nym to refer to the canonical or normalized form of a name regarded in such a way, - and provide the following elements to encode it: - - - + and provide the following elements to encode it:

Any element which is a member of the att.naming class may use the attribute nymRef to indicate the nym with which it corresponds. Thus, given the following nym for the name - Antony: - - -

Antony
- - - an occurrence of this name in running text might be encoded as follows: - Tony Blair Note that this association (between "Tony" and "Antony") has + Antony:
Antony
 an occurrence of this name in running text might be encoded as follows: Tony Blair Note that this association (between "Tony" and "Antony") has nothing to do with any individual who might use the name.

The person identified by this particular Tony may however be indicated independently using the ref attribute, - either on the forename or on the whole name component: - Tony - - - Tony Blair - politician - + either on the forename or on the whole name component: TonyTony Blairpolitician

The nym element may be thought of as providing a specialized kind of dictionary entry. Like a dictionary entry, it may contain any element from the model.entryPart class, such as form, etym, etc. For example, we may show that the canonical form for a given nym has two orthographic variants in - this way: - -

- Ian - Iain -
- - + this way:
IanIain

-

Because a schema intending to make use of the nym or listNym element must include the dictionaries module as well as the namesdates module, many other +

Because a schema intending to make use of the nym or listNym element must include the dictionaries module as well as the namesdates module, many other elements are available in addition to form. For example, to provide a more complex etymological decomposition of - a name, we might use the existing etym element, as follows: -

Bogomil
- Means favoured by God from the Slavic elements bog + a name, we might use the existing etym element, as follows:
Bogomil
Means favoured by God from the Slavic elements bog God and mil - favour - + favour

Where it is necessary to mark the substructure of nyms, this may be done by seg elements within the - form: - -

- - Bogomil - Bogomil - -
- + form:
BogomilBogomil
 The seg element used here is provided by the TEI linking module, which would therefore also need to be included in a schema built to validate such markup. Other possibilities for more detailed linguistic analysis are provided by elements included in that and the analysis (see ) or iso-fs modules (see ).

Alternatively, each of the constituents of Bogomil might be regarded as a nym in its own right: - - -

bog
- - -
mil
- - Within running text, a name can specify all the nyms associated with it: ...Bogomil... Similarly, +
bog
mil
 Within running text, a name can specify all the nyms associated with it: ...Bogomil... Similarly, within a nym, the attribute parts is used to indicate its constituent parts, where these have been identified - as distinct nyms: - -
Bogomil
- - + as distinct nyms:
Bogomil

The nym element may also combine a number of other nym elements together, where it is intended to show that they are all regarded as variations on the same root. Thus the different forms of the name John, all being derived - from the same root, may be represented as a hierarchic structure like this: -

Iohannes
- -
John
- -
Johnny
- - -
Jon
- - - -
Ivan
- - -
Jean
- - + from the same root, may be represented as a hierarchic structure like this:
Iohannes
John
Johnny
Jon
Ivan
Jean

-

The nym element may be used for components of geographical or organizational names as well. For example: - - Lairig - Eilde - ... -

lairig
- sloping hill face - ... +

The nym element may be used for components of geographical or organizational names as well. For example: LairigEilde ...

lairig
sloping hill face ...

- -

- - - - As noted above, use of these elements implies that both the dictionaries and the +

As noted above, use of these elements implies that both the dictionaries and the namesdates modules are included in a schema.

- -
- Dates -

The following elements for the encoding of dates and times were introduced in section : - - - +

+ Dates +

The following elements for the encoding of dates and times were introduced in section :

-

The current module namesdates provides a mechanism for more detailed encoding of relative +

The current module namesdates provides a mechanism for more detailed encoding of relative dates and times. A relative temporal expression describes a date or time with reference to some other (absolute) temporal expression, and thus may contain an offset element in addition to one or more date - or time elements: - - + or time elements:

-

As members of the att.datable and att.duration classes, which in +

As members of the att.datable and att.duration classes, which in turn are members of att.datable.w3c and att.duration.w3c - respectively, the date and time elements share the following attributes: - - - + respectively, the date and time elements share the following attributes:

-
- Relative Dates and Times -

As noted above, relative dates and times such as in the Two Hundredth and First Year of the Republic, twenty +

+ Relative Dates and Times +

As noted above, relative dates and times such as in the Two Hundredth and First Year of the Republic, twenty minutes before noon, and, more ambiguously, after the lamented death of the Doctor or an hour after the game have two distinct components. As well as the absolute temporal expression or event to which reference is made (e.g. noon, the game, the death of the Doctor, [the foundation of] the Republic), they also @@ -2849,7 +1624,7 @@ There is no restriction on the form, size, or type of object that may be describ expression (e.g. the Two Hundredth and First Year, twenty minutes, an hour); and (optionally) an offset describing the direction of the distance between the time or date indicated and the referent expression (e.g. of implying after, before, after).

-

The distance component of a relative temporal expression may be encoded as a temporal element in +

The distance component of a relative temporal expression may be encoded as a temporal element in its own right using either date or time, or with the more generic measure element. A special element, offset, is provided by this module for encoding the offset component of a relative temporal expression. The absolute temporal expression contained within the relative expression may be encoded @@ -2857,73 +1632,44 @@ There is no restriction on the form, size, or type of object that may be describ date or time elements within themselves. This allows for deeply nested structures such as the third Sunday after the first Monday before Lammastide in the fifth year of the King's second marriage ... but so does natural language.

-

In the following examples, the when and dur attributes have been used to simplify processing of - variant forms of expression: - A fortnight - before - Christmas 1786 - - I reached the station

-

In the following example, a nested date element is used to show that my birthday and the cited date are +

In the following examples, the when and dur attributes have been used to simplify processing of + variant forms of expression: A fortnightbeforeChristmas 1786 + I reached the station

+

In the following example, a nested date element is used to show that my birthday and the cited date are parts of the same temporal expression, and hence to disambiguate the phrase A week before my birthday on 9th - December: - A week - before - - my birthday on 9th December - - The alternative reading of this phrase could be encoded as follows: - A week - before - my birthday on 9th December + December: A weekbeforemy birthday on 9th December + The alternative reading of this phrase could be encoded as follows: A weekbeforemy birthday on 9th December

-

Where more complex or ambiguous expressions are involved, and where it is desirable to make more explicit the +

Where more complex or ambiguous expressions are involved, and where it is desirable to make more explicit the interpretive processes required, the feature structure notation described in chapter may be used. Consider, for example, the following temporal expression which occurs in the Scottish Temperance Review - of August 1850, referring to the summer holiday known in Glasgow simply as the Fair: Not only is the city, during the Fair, a horrible + of August 1850, referring to the summer holiday known in Glasgow simply as the Fair: Not only is the city, during the Fair, a horrible nucleus of immorality and wickedness; it sends our multitudes to pollute and demoralize the country.

-

For the definition of the ana attribute, see chapter (in particular ). It is used here to link the temporal phrase with an interpretation of it. Like most traditional +

For the definition of the ana attribute, see chapter (in particular ). It is used here to link the temporal phrase with an interpretation of it. Like most traditional fairs and market days, the Glasgow Fair was established by local custom and could vary from year to year. Consequently, in order to provide such an interpretation, it is necessary to draw upon additional information which may or may not be located in the particular text in question. In this case, it is necessary at least to know the spatial and temporal context (year and place) of the fair referred to. These and other features required for the analysis of this particular - temporal expression may be combined together as one feature structure of type date-analysis: - the Fair - Glasgow - - 1850-08-08 - 1850-09-19 - For further discussion of feature structure representation see chapter .

-
- -
- Absolute Dates and Times - -

The following are examples of absolute temporal expressions.

-

- The university's view of American affairs + temporal expression may be combined together as one feature structure of type date-analysis: the FairGlasgow1850-08-081850-09-19 For further discussion of feature structure representation see chapter .

+
+
+ Absolute Dates and Times +

The following are examples of absolute temporal expressions.

+

+ The university's view of American affairs produced a stinging attack by Edmund Burke in the Commons debate of 26 October 1775 - - Friday, 14 May 1993 - -

-

It may be useful to categorize a temporal expression which is given in terms of a named event, such as a public + + Friday, 14 May 1993 + +

+

It may be useful to categorize a temporal expression which is given in terms of a named event, such as a public holiday, or a named time such as tea time or matins: In - New York, New Year's Day is the quietest of holidays, Independence Day the most turbulent. + New York, New Year's Day is the quietest of holidays, Independence Day the most turbulent.

- - - - - - - - - -

Absolute temporal expressions denoting times which are given in terms of seconds, minutes, hours, or of well-defined - events (e.g. noon, sunset) may similarly be represented using the time element. The train leaves for Boston at + + + + + + + + +

Absolute temporal expressions denoting times which are given in terms of seconds, minutes, hours, or of well-defined + events (e.g. noon, sunset) may similarly be represented using the time element. The train leaves for Boston at At we walked to the beach. - The train leaves for Boston at + The train leaves for Boston at

-
-
- More Expressive Normalizations -

The attributes for normalization of dates and times so far described use a standard format defined by XML Schema Part 2: Datatypes Second Edition. This format is widely accepted and has significant +

+
+ More Expressive Normalizations +

The attributes for normalization of dates and times so far described use a standard format defined by XML Schema Part 2: Datatypes Second Edition. This format is widely accepted and has significant software support. It is essentially a profile of ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times. The full ISO standard provides formats not available in the W3C recommendation, for example, the capability to refer to a date by its ordinal date or week date, or to refer to a century. It also provides ways of indicating duration and range.

- -

When this module is included in a schema, the following additional attributes are provided: - - - These attributes may be used in preference to their W3C equivalent when it is necessary to provide a +

When this module is included in a schema, the following additional attributes are provided: These attributes may be used in preference to their W3C equivalent when it is necessary to provide a normalized value in some form not supported by the W3C attributes. For example, a century date in the W3C format must be expressed as a range, using the from attribute together with either the to attribute or the - dur (duration) attribute: fourteenth century - fourteenth century - With the attribute when-iso, however, it is possible to express the same normalized value in any of + dur (duration) attribute: fourteenth centuryfourteenth century With the attribute when-iso, however, it is possible to express the same normalized value in any of the following additional ways: fourteenth - century - fourteenth century - fourteenth century - + centuryfourteenth centuryfourteenth century

- - - - - - - - - - - - - - - - -
- -
- Using Non-Gregorian Calendars -

All date-related encoding described above makes use of the Gregorian calendar, on which both the ISO and W3C datetime + + + + + + + + + + + + + + +

+
+ Using Non-Gregorian Calendars +

All date-related encoding described above makes use of the Gregorian calendar, on which both the ISO and W3C datetime formats are based. However, historical texts often pre-date the invention of the Gregorian calendar in the 16th century, or its adoption in Europe over the following centuries, and many other calendars are used in texts from other cultures and contexts. Non-Gregorian dates can be encoded using methods described below.

- -

First, a Calendar Description element needs to be supplied in the teiHeader as described in :

- - - -

The Julian calendar, as used in England until 1752.

 - - - -

The following attributes can now be used to encode dates using this calendar: - - - - -

The Poole by S. Giles Churchyarde was a large water in the yeare 1244.

- Here, the calendar attribute points to the calendar element in the header which defines and +

First, a Calendar Description element needs to be supplied in the teiHeader as described in :

+ + + +

The Julian calendar, as used in England until 1752.

+ + + +

The following attributes can now be used to encode dates using this calendar: +

The Poole by S. Giles Churchyarde was a large water in the yeare 1244.

Here, the calendar attribute points to the calendar element in the header which defines and describes the calendar used.

- -

The calendar attribute is used to specify the calendar used in the text content of the dating +

The calendar attribute is used to specify the calendar used in the text content of the dating element which bears it. For reasons of consistency and computability, it is often useful to complement the content of an element with attributes such as when, notBefore, notAfter, etc. For dates expressed in a non-Gregorian calendar, such normalizations may also be expressed in terms of the non-Gregorian calendar specified by the datingMethod attribute. The attributes when-custom, notBefore-custom, from-custom, etc. are provided for this purpose; the datingMethod attribute - is used to identify the calendar used in the value of these attributes: - The Tryumphs of Peace. That Celebrated the Solemnity of the right Honorable Sr Francis Iones Knight, at - his Inauguration into the Maioraltie of London, on Monday being the 30. of October, 1620. - - Here, the calendar attribute specifies the calendar used in the text content of the date + is used to identify the calendar used in the value of these attributes: The Tryumphs of Peace. That Celebrated the Solemnity of the right Honorable Sr Francis Iones Knight, at + his Inauguration into the Maioraltie of London, on Monday being the 30. of October, 1620. + Here, the calendar attribute specifies the calendar used in the text content of the date element, as before, whereas the datingMethod attribute signifies that the calendar used in the when-custom attribute is also Julian. The schema could be customized in order to constrain the content of custom attributes in a manner similar to the constraints provided on regular Gregorian dating attributes such as when, to enforce consistency in the use of non-Gregorian dates.

- -

Custom dating attributes can be combined with any of the standard dating attributes in order to provide a standardized +

Custom dating attributes can be combined with any of the standard dating attributes in order to provide a standardized Gregorian version of a non-Gregorian date. We might enhance the preceding example with the addition of when, - providing the Gregorian calendar equivalent of the Julian date: - 30. of - October, 1620. - + providing the Gregorian calendar equivalent of the Julian date: 30. of + October, 1620.

-
- - +
Module for Names and Dates -

The module described in this chapter makes available the following components: - Names, dates, persons and places - Names and dates - Noms, dates, personnes et lieux - 名稱與日期 - Nomi e date - Nomes e datas - 名前モジュール - The selection and combination of modules to form a TEI schema is described in .

+

The module described in this chapter makes available the following components: Names, dates, persons and placesNames and datesNoms, dates, personnes et lieux名稱與日期Nomi e dateNomes e datas名前モジュール The selection and combination of modules to form a TEI schema is described in .

-
diff --git a/P5/Source/Guidelines/en/NH-Non-hierarchical.xml b/P5/Source/Guidelines/en/NH-Non-hierarchical.xml index 358ec7f756..b976fab032 100644 --- a/P5/Source/Guidelines/en/NH-Non-hierarchical.xml +++ b/P5/Source/Guidelines/en/NH-Non-hierarchical.xml @@ -1,55 +1,33 @@ - - - + -
- Non-hierarchical Structures -

XML employs a strongly hierarchical document model. At various + Non-hierarchical Structures +

XML employs a strongly hierarchical document model. At various points, these Guidelines discuss problems that arise when using XML to encode textual features that either do not naturally lend themselves to representation in a strictly hierarchical form or conflict with other hierarchies represented in the - markup. Examples of such situations include: - -

Conflict between the hierarchy established by the + markup. Examples of such situations include:

Conflict between the hierarchy established by the physical structure of a document (e.g., volume, page, column, line) and its rhetorical or linguistic structure (e.g., chapters, paragraphs, sentences, - acts, scenes, etc.)

- - -

Conflict between a verse text's metrical structure + acts, scenes, etc.)

Conflict between a verse text's metrical structure (e.g., its arrangement in stanzas and metrical lines) and its rhetorical or linguistic structure (e.g., phrases, sentences, and, for plays, acts, scenes, and - speeches).

- - -

Conflict between metrical, rhetorical, or + speeches).

Conflict between metrical, rhetorical, or linguistic structure and the representation of direct speech, especially if the quoted speech is interrupted by other elements (e.g., What, she asked, was that all about) or crosses metrical, - rhetorical, or linguistic boundaries.

- - -

Conflict between different analytical views or + rhetorical, or linguistic boundaries.

Conflict between different analytical views or descriptions of a text or document, e.g., markup intended to encode diplomatic information about a word's appearance in a manuscript with markup intended - to describe its morphology or pronunciation.

- - + to describe its morphology or pronunciation.

-

Non-nesting information poses fundamental problems for any +

Non-nesting information poses fundamental problems for any XML-based encoding scheme, and it must be stated at the outset that no current solution combines all the desirable attributes of formal simplicity, capacity to represent all occurring or @@ -57,50 +35,22 @@ $Id$ mechanical validation. The representation of non-hierarchical information is thus necessarily a matter of trade-offs among various sets of advantages and disadvantages.

-

These Guidelines support several methods for handling - non-hierarchical information: - -

redundant encoding of information in multiple forms - (discussed in )

- - -

the use of empty elements to delimit the boundaries - of a non-nesting structure (discussed in )

- - -

the division of a logically single non-nesting +

These Guidelines support several methods for handling + non-hierarchical information:

redundant encoding of information in multiple forms + (discussed in )

the use of empty elements to delimit the boundaries + of a non-nesting structure (discussed in )

the division of a logically single non-nesting element into segments that nest properly in their immediate hierarchical context but can also be reconstituted virtually across these hierarchical - boundaries (discussed )

- - -

stand-off markup: the annotation of information by + boundaries (discussed )

stand-off markup: the annotation of information by pointing at it, rather than by placing XML tags within - it (discussed in )

- - Some of these methods can be used in TEI-conformant documents. Others + it (discussed in )

Some of these methods can be used in TEI-conformant documents. Others require extension.

-

In the sections which follow these techniques are described and their advantages and +

In the sections which follow these techniques are described and their advantages and disadvantages are briefly discussed. The various solutions to the problem will be exemplified using extracts from two poems. The first is the opening quatrain from William - Wordsworth's Scorn not the sonnet: - Scorn not the sonnet; critic, you have frowned, - Mindless of its just honours; with this key - Shakespeare unlocked his heart; the melody - Of this small lute gave ease to Petrarch's wound. - The second example is the third stanza from the fourth section of Robert Pinsky's - Essay on Psychiatrists: - - Catholic woman of twenty-seven with five children - And a first-rate body—pointed her finger - at the back of one certain man and asked me, - "Is that guy a psychiatrist?" and by god he was! "Yes," - She said, "He looks like a psychiatrist." - Grown quiet, I looked at his pink back, and thought. - - These two texts can be analysed in various ways. The first, which we might describe + Wordsworth's Scorn not the sonnet: Scorn not the sonnet; critic, you have frowned,Mindless of its just honours; with this keyShakespeare unlocked his heart; the melodyOf this small lute gave ease to Petrarch's wound. The second example is the third stanza from the fourth section of Robert Pinsky's + Essay on Psychiatrists: Catholic woman of twenty-seven with five childrenAnd a first-rate body—pointed her fingerat the back of one certain man and asked me,"Is that guy a psychiatrist?" and by god he was! "Yes,"She said, "He looks like a psychiatrist."Grown quiet, I looked at his pink back, and thought. These two texts can be analysed in various ways. The first, which we might describe as the Metrical View, encodes the text according to its metrical features: line divisions (as here), stanzas or cantos in larger poems, and perhaps prosodic features like stress or syllable patterns, alliteration, or rhyme. A second view, which we @@ -113,71 +63,36 @@ $Id$ Grammatical View we will restrict ourselves to encoding sentences; and for the Dialogic View, we only will distinguish direct quotation from other narration.

-
- Multiple Encodings of the Same Information -

Conceptually, the simplest method of disentangling two (or +

+ Multiple Encodings of the Same Information +

Conceptually, the simplest method of disentangling two (or more) conflicting hierarchical views of the same information is to encode it twice (or more), each time capturing a single view.

-

Thus, for example, the Metrical View of Scorn not the + <p>Thus, for example, the <term>Metrical View</term> of <title level="a">Scorn not the sonnet might be encoded as follows, using the l element to encode - each metrical line: - Scorn not the sonnet; critic, you have frowned, - Mindless of its just honours; with this key - Shakespeare unlocked his heart; the melody - Of this small lute gave ease to Petrarch's wound. -

-

The Grammatical View would be encoded by + each metrical line: Scorn not the sonnet; critic, you have frowned,Mindless of its just honours; with this keyShakespeare unlocked his heart; the melodyOf this small lute gave ease to Petrarch's wound.

+

The Grammatical View would be encoded by taking the same text and replacing the metrical markup with - information about its sentence structure: -

- Scorn not the sonnet; - critic, you have frowned, Mindless of its just honours; - with this key Shakespeare unlocked his heart; - the melody Of this small lute gave ease to Petrarch's wound. -

-

-

Likewise, the more complex passage from Pinsky could be + information about its sentence structure:

Scorn not the sonnet;critic, you have frowned, Mindless of its just honours;with this key Shakespeare unlocked his heart;the melody Of this small lute gave ease to Petrarch's wound.

+

Likewise, the more complex passage from Pinsky could be encoded in three different ways to reflect the different - metrical, grammatical, and dialogic views of its text: - - Catholic woman of twenty-seven with five children - And a first-rate body—pointed her finger - at the back of one certain man and asked me, - "Is that guy a psychiatrist?" and by god he was! "Yes," - She said, "He looks like a psychiatrist." - Grown quiet, I looked at his pink back, and thought. - - + metrical, grammatical, and dialogic views of its text: Catholic woman of twenty-seven with five childrenAnd a first-rate body—pointed her fingerat the back of one certain man and asked me,"Is that guy a psychiatrist?" and by god he was! "Yes,"She said, "He looks like a psychiatrist."Grown quiet, I looked at his pink back, and thought. - -

-Catholic woman of twenty-seven with five children And a +

Catholic woman of twenty-seven with five children And a first-rate body—pointed her finger at the back of one certain man and -asked me, "Is that guy a psychiatrist?" and by god he was! -

-

-"Yes," She said, "He looks like a -psychiatrist." -

-

- Grown quiet, I looked at his pink back, and thought. -

- +asked me, "Is that guy a psychiatrist?" and by god he was!

"Yes," She said, "He looks like a +psychiatrist."

Grown quiet, I looked at his pink back, and thought.

- -Catholic woman of twenty-seven with five children And a first-rate +Catholic woman of twenty-seven with five children And a first-rate body—pointed her finger at the back of one certain man and asked me, Is that guy a psychiatrist? and by god he was! Yes, She said, He looks like a psychiatrist. Grown quiet, I looked at his pink back, and -thought. - +thought.

-

This method is TEI-conformant. Its advantages are that each +

This method is TEI-conformant. Its advantages are that each way of looking at the information is explicitly represented in the data and that the individual views are simple to process. The disadvantages are that the method requires the @@ -191,12 +106,11 @@ thought. is possible to relate the different annotations in an indirect way: if the textual content of the annotations is identical, the very text can serve as a means for linking the different - annotations, as described in .

-
-
- Boundary Marking with Empty Elements -

A second method for accommodating non-hierarchical objects + annotations, as described in .

+
+
+ Boundary Marking with Empty Elements +

A second method for accommodating non-hierarchical objects in an XML document involves marking the start and end points of the non-nesting material. This prevents textual features that fall outside the privileged hierarchy from invalidating @@ -205,27 +119,24 @@ thought. single XML element represents the non-nesting material and, as a result, processing with XML technologies is significantly more difficult.

-

The empty elements used at each end are called +

The empty elements used at each end are called segment-boundary elements or segment-boundary delimiters. There are several variations on this method of encoding.

- -

For some common structural features, the TEI provides +

For some common structural features, the TEI provides milestone elements that can be used to mark the beginning of a textual feature. These include lb, pb, cb, handShift, and the generic milestone. Using lb, for example, it is possible to indicate both the physical lineation of a poem on the page and its grammatical division into sentences: - -

-Scorn not the sonnet;; critic, you have -frowned, Mindless of its just honours; with this -key Shakespeare unlocked his heart; the melody +

Scorn not the sonnet;; critic, you have +frowned, Mindless of its just honours;with this +key Shakespeare unlocked his heart;the melody Of this small lute gave ease to Petrarch's wound.

-

The use of these elements is by definition TEI-conformant. +

The use of these elements is by definition TEI-conformant. Care should be taken, however, that the meaning of the milestone elements is preserved: semantically, for example, lb is used to mark the start of a new @@ -235,29 +146,18 @@ wound.

verse from sources, such as Old English manuscripts, where physical line breaks are not used to indicate metrical lineation, the correspondence would break down entirely.

- - -

The segment boundaries also may be delimited by the generic +

The segment boundaries also may be delimited by the generic anchor element. Attributes can then be used to indicate the type of feature being delimited and whether a - given instance opens or closes the feature. - - + given instance opens or closes the feature. Scorn not the sonnet; - critic, you have frowned, - Mindless of its just honours; - with this key - Shakespeare unlocked his heart; - the melody - Of this small lute gave ease to Petrarch's wound. - + critic, you have frowned,Mindless of its just honours; + with this keyShakespeare unlocked his heart; + the melodyOf this small lute gave ease to Petrarch's wound.

-

This method is TEI-conformant.

- - -

Another approach is to design custom elements that provide +

This method is TEI-conformant.

+

Another approach is to design custom elements that provide richer information about the feature being delimited or its boundaries. This information can be included as attribute values or as part of the element name itself: e.g., @@ -268,73 +168,44 @@ wound.

position="end"/, or sentenceBoundaryStart/... sentenceBoundaryEnd/: - - -Scorn not the sonnet; - -critic, you have frowned, -Mindless of its just honours; -with this key -Shakespeare unlocked his heart; -the melody -Of this small lute gave ease to Petrarch's wound. - +Scorn not the sonnet; +critic, you have frowned,Mindless of its just honours; +with this keyShakespeare unlocked his heart; +the melodyOf this small lute gave ease to Petrarch's wound.

-

If the custom elements can be replaced by TEI elements and +

If the custom elements can be replaced by TEI elements and attributes without loss of information, this method is TEI-conformant (see ); if the custom elements introduce information or distinctions that cannot be captured using standard TEI elements, the method is an extension.

- - -

Finally, elements that are normally used to encode nesting +

Finally, elements that are normally used to encode nesting textual features (e.g., said, seg, l, etc.) can be adapted so that they serve as empty segment boundary delimiters when the features they encode - cross-hierarchical boundaries. Additional attributes (sID and eID in + cross-hierarchical boundaries. Additional attributes (sID and eID in the example below) are added to these elements in order to allow the unambiguous correlation of start and end points. This method has been introduced in the markup literature under various names, including Trojan milestones, HORSE markup, CLIX, and COLT. It is described in detail by - ): - - - Scorn not the sonnet;critic, you have frowned, - Mindless of its just honours; - with this key - Shakespeare unlocked his heart; - the melody - Of this small lute gave ease to Petrarch's wound. - - - Depending on how the modifications are carried out, + ): Scorn not the sonnet;critic, you have frowned, Mindless of its just honours; + with this key Shakespeare unlocked his heart; + the melody Of this small lute gave ease to Petrarch's wound. + Depending on how the modifications are carried out, this method may be TEI-conformant, may represent an extension of the - TEI, or may produce a non-conformant document. - The method is TEI-conformant if the modified elements and attributes can be mapped without loss of information to existing TEI markup structures such as - milestone or anchor elements automatically (see ). - The method represents an Extension if the + milestone or anchor elements automatically (see ).The method represents an Extension if the modified elements are placed in a distinct, non-TEI namespace (see ). - The method is non-conformant—and indeed strongly + TEI elements without loss of information--> (see ).The method is non-conformant—and indeed strongly deprecated—if the modified elements and attributes are - not placed in a distinct, non-TEI namespace (see ). -

- - - -

In each of the above examples (except the last), the relationship between the start and + not placed in a distinct, non-TEI namespace (see ).

+

In each of the above examples (except the last), the relationship between the start and end delimiters (where these exist) of a given feature is implicit: it is assumed that "end" delimiters close the nearest preceding "start" delimiter, or, in the case of milestones, that the milestone marks both the end of the preceding example and the @@ -346,30 +217,14 @@ wound.

--> noun phrase fast trains and planes. In this case, the adjective fast can be understood as either modifying trains and planes or just - trains:
- Two interpretations of the phrase - Fast trains and planes - - Graphic representation of two interpretations of the phrase Fast - trains and planes. -

-

In order to encode the possible analyses of this phrase, an + trains:

Two interpretations of the phrase + Fast trains and planesGraphic representation of two interpretations of the phrase Fast + trains and planes.

+

In order to encode the possible analyses of this phrase, an unambiguous method of associating opening and closing segment - boundary delimiters is required: - - - Fast - - trains - - and - planes - - - + boundary delimiters is required: Fasttrainsandplanes

-

In this encoding, the first interpretation, in which +

In this encoding, the first interpretation, in which fast modifies the NP trains and planes, the NP trains and planes is opened using an anchor tag with @@ -384,31 +239,30 @@ wound.

NPInterpretationB and closed with an anchor tag that has the same value on corresp.

-

Despite their advantages, segment boundary delimiters incur +

Despite their advantages, segment boundary delimiters incur the disadvantage of cumbersome processing: since the elements of the analysis (e.g., the sentences in the poems, or phrases in the above example) are not uniformly represented by nodes in the document tree, they must be reconstituted by software in an ad hoc fashion, which is likely to be difficult and may be error prone.

-

Most important for some encoders, the method also disguises +

Most important for some encoders, the method also disguises the relationship between the beginning and the ending of each logical element. This makes it impossible for standard validation software to provide the same kind of validation possible elsewhere in the encoding. When using grammar-based schema languages it is not possible to define a content model - for the range limited by empty elements.Grammar based schema languages (e.g., DTD, W3C + for the range limited by empty elements.Grammar based schema languages (e.g., DTD, W3C Schema, and RELAX NG) are used to define markup languages (e.g., XHTML or TEI). Rule-based schema languages (e.g., Schematron) can be used to define further constraints. Such a rule-based schema language permits a sequence of certain elements between empty elements to be legitimized or prohibited.

-
-
- Fragmentation and Reconstitution of Virtual Elements -

A third method involves breaking what might be considered a +

+
+ Fragmentation and Reconstitution of Virtual Elements +

A third method involves breaking what might be considered a single logical (but non-nesting) element into multiple smaller structural elements that fit within the dominant hierarchy but can be reconstituted virtually. For example, if a passage of @@ -420,46 +274,21 @@ wound.

only a portion of the complete passage of direct discourse. For this reason these elements are sometimes called partial elements.

-

In the case of our selection from Pinsky's poem, for +

In the case of our selection from Pinsky's poem, for example, the second passage of direct quotation, which crosses a line boundary and is broken up by a She said in the narrator's voice, can be made to fit within the hierarchy established by the metrical lineation by using two said elements: - - - Catholic woman of twenty-seven with five children - And a first-rate body—pointed her finger - at the back of one certain man and asked me, - Is that guy a psychiatrist? and by god he was! - Yes, - She said, He looks like a -psychiatrist. - Grown quiet, I looked at his pink back, and thought. - - +Catholic woman of twenty-seven with five childrenAnd a first-rate body—pointed her fingerat the back of one certain man and asked me,Is that guy a psychiatrist? and by god he was! + Yes,She said, He looks like a +psychiatrist.Grown quiet, I looked at his pink back, and thought.

-

Similarly, the sentences in our example from Wordsworth +

Similarly, the sentences in our example from Wordsworth could be encoded: - - - Scorn not the sonnet; - critic, you have frowned, - - - Mindless of its just honours; - with this key - - - Shakespeare unlocked his heart; - the melody - - - Of this small lute gave ease to Petrarch's wound. - -

-

There are two main problems with this type of encoding. The +Scorn not the sonnet;critic, you have frowned,Mindless of its just honours;with this keyShakespeare unlocked his heart;the melodyOf this small lute gave ease to Petrarch's wound.

+

There are two main problems with this type of encoding. The first is that it invariably means that the encoding will have more elements claiming to represent a feature than there are actual instances of that feature in the text. Thus, for @@ -467,7 +296,7 @@ psychiatrist. sonnet marks seven spans of text using seg, even though there are only four linguistic sentences in the passage.

-

The second problem is that it can be semantically +

The second problem is that it can be semantically misleading. Although they are tagged using the element for sentence, for example, very few of the textual features encoded using seg in this example represent @@ -476,7 +305,7 @@ psychiatrist. sentence; Of this small lute gave ease to Petrarch's wound is a string corresponding to no single grammatical category.

-

Taken together, these problems can make automatic analysis +

Taken together, these problems can make automatic analysis of the fragmented features difficult. An analysis that intended to count the number of sentences in Wordsworth's poem, for example, would arrive at an inflated figure if it @@ -484,33 +313,16 @@ psychiatrist. rhetorical sentences; if it wanted to do an analysis of his syntax, it would not be able to assume that seg delimited linguistic sentences.

-

The technique of fragmentation is often complemented by the +

The technique of fragmentation is often complemented by the technique of virtual joins. Virtual joins may be used to - combine objects in the text to a new hierarchy. Here is Scorn not the sonnet again; this time the + combine objects in the text to a new hierarchy. Here is Scorn not the sonnet again; this time the relationship between the parts of the fragmented sentences is indicated explicitly using the next and prev attributes described in . - - - Scorn not the sonnet; - critic, you have frowned, - - - Mindless of its just honours; - with this key - - - Shakespeare unlocked his heart; - the melody - - - Of this small lute gave ease to Petrarch's wound. - - This method of virtually joining partial elements is sometimes called +Scorn not the sonnet;critic, you have frowned,Mindless of its just honours;with this keyShakespeare unlocked his heart;the melodyOf this small lute gave ease to Petrarch's wound. This method of virtually joining partial elements is sometimes called chaining.

-

For fragments encoded using ab, l, +

For fragments encoded using ab, l, lg, div, or elements that belong to the att.segLike class, an even simpler mechanism for virtually joining fragments exists: the use of @@ -518,25 +330,8 @@ psychiatrist. I (Initial), M (Medial), or F (Final) as described in . Here is the above example recoded to - reflect this method: - - Scorn not the sonnet; - critic, you have frowned, - - - Mindless of its just honours; - with this key - - - Shakespeare unlocked his heart; - the melody - - - Of this small lute gave ease to Petrarch's wound. - -

-

This method is TEI-conformant and simple to use. Its + reflect this method: Scorn not the sonnet;critic, you have frowned,Mindless of its just honours;with this keyShakespeare unlocked his heart;the melodyOf this small lute gave ease to Petrarch's wound.

+

This method is TEI-conformant and simple to use. Its disadvantage is that it does not work well for cases of self-overlap, or if there are nested occurrences of the same element type, as it can become difficult to ascertain which @@ -544,83 +339,17 @@ psychiatrist. with which others or in which order. This problem becomes evident if we attempt to combine a detailed Grammatical view of the Pinsky example with its metrical encoding: - - - - Catholic woman of twenty-seven with five children - - - And a first-rate body—pointed her finger - - - at the back of one certain man and asked me, - - - "Is that guy a psychiatrist?" and by god he was! - "Yes," - - - She said, "He looks like a psychiatrist." - - - Grown quiet, I looked at his pink back, and thought. - - -

- -

A third method for aggregating fragmented partial elements +Catholic woman of twenty-seven with five childrenAnd a first-rate body—pointed her fingerat the back of one certain man and asked me,"Is that guy a psychiatrist?" and by god he was!"Yes,"She said, "He looks like a psychiatrist."Grown quiet, I looked at his pink back, and thought.

+

A third method for aggregating fragmented partial elements involves using markup that is not directly part of the encoding, e.g., the join element. In this method, a join element is used elsewhere in the document to indicate explicitly the members of the virtual element: - - - Scorn - not - the - sonnet; critic, you - have - frowned, - - Mindless - of - its - just - honours; with - this - key - - - Shakespeare - unlocked - his - heart; the - melody - - - Of - this - small - lute - gave - ease - to - Petrarch's - wound. - - - -

- - - - -

- +Scornnotthesonnet; critic, youhavefrowned, Mindlessofitsjusthonours; withthiskeyShakespeareunlockedhisheart; themelodyOfthissmalllutegaveeasetoPetrarch'swound.

-

This use of join is TEI-conformant.

-

The major advantage of fragmentation and virtual joins is +

This use of join is TEI-conformant.

+

The major advantage of fragmentation and virtual joins is that it allows all the hierarchies in the text to be handled explicitly: both the privileged one directly represented and the alternate hierarchy that has been split up and @@ -629,10 +358,10 @@ psychiatrist. the others, requires special processing to reconstitute the elements of the other hierarchies, and, except in the case of join, can be semantically misleading.

-
-
- Stand-off Markup -

Most markup is characterized by the embedding of elements +

+
+ Stand-off Markup +

Most markup is characterized by the embedding of elements in the text. An alternative approach separates the text and the elements used to describe it. This approach is known as stand-off markup (see section ). It @@ -648,45 +377,7 @@ psychiatrist. xml:id values on w to provide targets for xi:includeA fake namespace is given for XInclude here, to avoid the markup being interpreted - literally during processing.: - - Scorn - not - the - sonnet; critic, you - have - frowned, - - Mindless - of - its - just - honours; with - this - key - - - Shakespeare - unlocked - his - heart; the - melody - - - Of - this - small - lute - gave - ease - to - Petrarch's - wound. - - - -: Scornnotthesonnet; critic, youhavefrowned, Mindlessofitsjusthonours; withthiskeyShakespeareunlockedhisheart; themelodyOfthissmalllutegaveeasetoPetrarch'swound. @@ -701,17 +392,14 @@ psychiatrist.

-]]> - +]]> Note that the layer that uses XInclude to build another hierarchy - might well be in another document, in which case the value of href of xi:xinclude would need to be + might well be in another document, in which case the value of href of xi:xinclude would need to be the URL of the document that contains the base layer, in this case the w elements.

- -

This is very similar to the use of join discussed +

This is very similar to the use of join discussed above. The main advantages of the stand-off method are that it is possible to specify attributes on the aggregate seg elements, and that there exists off-the-shelf @@ -719,13 +407,12 @@ psychiatrist. markup may be used even when the base text being annotated is plain text, i.e. does not have any XML encoding. In this case, the range of text to be marked up is indicated by character - offsets (see , in particular ). Another distinction concerns the number + offsets (see , in particular ). Another distinction concerns the number of files which can serve as link targets. Often, one (dedicated) annotation is used as the link target of all the other annotations. It is also possible to freely interlink several layers.

-

It has been noted that stand-off markup has several +

It has been noted that stand-off markup has several advantages over embedded annotations. In particular, it is possible to produce annotations of a text even when the source document is read-only. Furthermore, annotation files can be @@ -736,74 +423,66 @@ psychiatrist. annotations, and that different annotation files can contain different layers of information. Lastly, it has also been noted that this approach is elegant.

-

But there are also several drawbacks. First, new stand-off +

But there are also several drawbacks. First, new stand-off annotated layers require a separate interpretation, and the layers—although separate—depend on each other. Moreover, although all of the information of the multiple hierarchies is included, the information may be difficult to access using generic methods.

-

Inasmuch as it uses elements not included in the TEI +

Inasmuch as it uses elements not included in the TEI namespace, stand-off markup involves an extension of the TEI.

-
-
- Non-XML-based Approaches -

There exist many non-XML methods of encoding a text that +

+
+ Non-XML-based Approaches +

There exist many non-XML methods of encoding a text that either solve or do not suffer the problem of the inability to encode overlapping hierarchies. These include, but are not limited to, the following proposals.

- - Applying the notion of concurrent markup to XML + + Applying the notion of concurrent markup to XML (). This reintroduces the CONCUR feature of SGML, which was omitted from the XML specification. - Designing a form of document representation in which + Designing a form of document representation in which several trees share all or part of the same frontier, and in which each individual view of the document has the form - of a tree (see ). - The colored XML proposal (), which stores a body of + of a tree (see ). + The colored XML proposal (), which stores a body of information as a set of intertwined XML trees. This approach eliminates unnecessary redundancy and makes the database readily updatable, while allowing the user to exploit different hierarchical access paths. - The MultiX proposal () , which represents documents as directed + The MultiX proposal () , which represents documents as directed graphs. Because XML is used to represent the graph, the document is, at least in principle, manipulable with standard XML tools. - The Just-In-Time-Trees proposal (), which stores documents + The Just-In-Time-Trees proposal (), which stores documents using XML, but processes the XML representation in non-standard ways and allows it to be mapped onto data structures that are different from those known from XML. - The - Layered Markup and Annotation - Language LMNL + The Layered Markup and Annotation + LanguageLMNL proposal. This offers alternatives to the basic XML linear form as well as its data and processing models. It uses an alternative notation to XML and - a data structure based on Core Range Algebra (). - - Markup Languages for Complex Documents - MLCD . This provides a + a data structure based on Core Range Algebra (). + Markup Languages for Complex DocumentsMLCD. This provides a notation (TexMECS) and a data structure (Goddag) as well as a draft constraint language for the representation of non-hierarchical structures; see . - -

These approaches are based either on non-standard XML + +

These approaches are based either on non-standard XML processing or data models, or not based on XML at all. Since TEI is currently based on XML they are not described any further in these Guidelines. Use of these methods with the TEI will certainly involve extensions; in most cases the documents will also be non-conformant.

-
- - + - - + - -
Index - +
+ Index +
diff --git a/P5/Source/Guidelines/en/PH-PrimarySources.xml b/P5/Source/Guidelines/en/PH-PrimarySources.xml index 532ea6cb2a..67aa927504 100644 --- a/P5/Source/Guidelines/en/PH-PrimarySources.xml +++ b/P5/Source/Guidelines/en/PH-PrimarySources.xml @@ -1,17 +1,9 @@ - + -
- Representation of Primary Sources - -

This chapter describes elements that may be used to represent primary source materials, +

+ Representation of Primary Sources +

This chapter describes elements that may be used to represent primary source materials, such as manuscripts, printed books, ephemera, or other textual documents. Some of these specialized elements, particularly at phrase-level, add to the other elements available within text to deal with textual phenomena more specific to primary source transcription. @@ -26,29 +18,23 @@ $Id$ of pages in a manuscript, or the layout of a printed page. This is not meant to be the only way of transcribing primary sources in TEI, or even a preferred way; which approach is more appropriate will depend on the specific needs of your project.

- -

Although this chapter discusses manuscript materials more frequently than other forms of written text, +

Although this chapter discusses manuscript materials more frequently than other forms of written text, most of the recommendations presented are equally applicable to facsimiles of a wide variety of media, including printed matter, monumental inscriptions, and art. Each medium has its own vocabulary of agents. In the following examples, terms such as scribe, author, editor, annotator or corrector may be re-interpreted in terms more appropriate to the medium being transcribed. In printed material, for example, the compositor plays a role analogous to the scribe, while in an authorial manuscript, the author and the scribe are the same person.

- -

This module may be used in conjunction with other modules. These recommendations are not intended to meet every transcriptional circumstance likely to be faced by any scholar. They are intended rather as a base to enable encoding of the most common phenomena found in the course of scholarly transcription of primary source materials. These guidelines do not address the encoding of physical description of textual witnesses: the materials of the carrier, the medium of the inscribing implement, the organisation of the carrier materials themselves (such as quiring, collation), authorial instructions or scribal markup, etc., except insofar as these are involved in the broader question of manuscript description, as addressed by the msdescription module described in chapter .

- -

This chapter begins by describing elements for handling digitally-encoded images of primary source materials for the purpose of creating digital facsimiles using the facsimile element ().

-

The next section () describes two ways of combining a facsimile images with a transcription; either by referencing a parallel transcription in text, or by providing an embedded transcription that prioritizes the encoding of a resource’s spatial features via the sourceDoc element and a number of transcriptional elements.

-

Section documents elements that support scholars in recording information about specific features of the text written on its physical carrier, such as and

-

Section describes how complex page layouts may be represented.

-

Section introduces the element fw (forme work) for encoding material repeated from page to page that falls outside the stream of the text.

-

Section describes how to document changes made during the production or revision of a primary source.

-

The chapter concludes with a technical overview of the structure and organization of the module described here. Some elements from other chapters are recontexualized for situations involving the transcription of primary source materials, whether within text or sourceDoc. Therefore, this overview should be read in conjunction with chapters and .

- -
- - Digital Facsimiles - -

A common approach in the TEI to representing pre-existing sources involves transcribing or otherwise converting sources into character form before marking them up. However, it is also a common practice to make a different form of +

This module may be used in conjunction with other modules. These recommendations are not intended to meet every transcriptional circumstance likely to be faced by any scholar. They are intended rather as a base to enable encoding of the most common phenomena found in the course of scholarly transcription of primary source materials. These guidelines do not address the encoding of physical description of textual witnesses: the materials of the carrier, the medium of the inscribing implement, the organisation of the carrier materials themselves (such as quiring, collation), authorial instructions or scribal markup, etc., except insofar as these are involved in the broader question of manuscript description, as addressed by the msdescription module described in chapter .

+

This chapter begins by describing elements for handling digitally-encoded images of primary source materials for the purpose of creating digital facsimiles using the facsimile element ().

+

The next section () describes two ways of combining a facsimile images with a transcription; either by referencing a parallel transcription in text, or by providing an embedded transcription that prioritizes the encoding of a resource’s spatial features via the sourceDoc element and a number of transcriptional elements.

+

Section documents elements that support scholars in recording information about specific features of the text written on its physical carrier, such as and

+

Section describes how complex page layouts may be represented.

+

Section introduces the element fw (forme work) for encoding material repeated from page to page that falls outside the stream of the text.

+

Section describes how to document changes made during the production or revision of a primary source.

+

The chapter concludes with a technical overview of the structure and organization of the module described here. Some elements from other chapters are recontexualized for situations involving the transcription of primary source materials, whether within text or sourceDoc. Therefore, this overview should be read in conjunction with chapters and .

+
+ Digital Facsimiles +

A common approach in the TEI to representing pre-existing sources involves transcribing or otherwise converting sources into character form before marking them up. However, it is also a common practice to make a different form of digital text that is instead composed of digital images of the original source, typically one per page, or other written surface. We call such a resource a digital facsimile. A digital facsimile may, in the simplest case, just @@ -62,31 +48,14 @@ $Id$ In this section we present elements designed to support these various possibilities and discuss the associated mechanisms provided by these Guidelines.

- - -

When this module is included in a schema, the class att.global - is extended to include two new pointer attributes, facs and change: - - - The change attribute is discussed further below in section . The facs attribute is used to associate any element +

When this module is included in a schema, the class att.global + is extended to include two new pointer attributes, facs and change: The change attribute is discussed further below in section . The facs attribute is used to associate any element in a transcription with an image of the corresponding part of the source, by means of the usual URI pointing mechanism.

- -

In the simple case where a digital text is composed of page images, the facs +

In the simple case where a digital text is composed of page images, the facs attribute on the pb element may be used to associate each image with an - appropriate point in the text: - - - - - - - - - - - By convention, this encoding indicates that the image indicated by the + appropriate point in the text: By convention, this encoding indicates that the image indicated by the facs attribute represents the whole of the text following the pb (page beginning) element, up to the next pb element. Any convenient milestone element (see further ) could be used in the same way; for example if the @@ -98,8 +67,7 @@ $Id$ them are scattered through many files rather than being concentrated in a single identifiable location. Nevertheless, this solution may be adequate for many straightforward digital library applications.

- -

The recommended approach to encoding facsimiles is instead to use the facs +

The recommended approach to encoding facsimiles is instead to use the facs attribute in conjunction with the elements facsimile or sourceDoc, and the elements surface, surfaceGrp, and zone, which are also provided by this module. These elements make it possible to accommodate multiple images of @@ -109,18 +77,9 @@ $Id$ facsimile editions, and ways of annotating graphics, for example so as to identify individuals appearing in group portraits and link them to data about the people represented.

- -

The following elements are available to represent components of a digital facsimile: - - - - - - - +

The following elements are available to represent components of a digital facsimile:

- -

Either of the facsimile or sourceDoc elements may be used to represent a +

Either of the facsimile or sourceDoc elements may be used to represent a digital facsimile. Either may appear within a TEI document along with, or instead of, the text element introduced in section . The sourceDoc element is used when a digital facsimile contains a transcription that prioritizes the encoding of the spatial features and layout of a text document over the text’s logical textual structure; the text element @@ -128,72 +87,32 @@ $Id$ When the digital facsimile contains only images, however, only facsimile elements should be used. In this section, we first discuss the simpler case, returning to the use of the sourceDoc element in section below. When this module is selected therefore, a legal TEI - document may thus comprise any of the following: - a TEI header and a text element - a TEI header and a facsimile element - a TEI header and a sourceDoc element - a TEI header, a facsimile element, and a text element - a TEI header, one or more sourceDoc or facsimile elements, and a text - element - + document may thus comprise any of the following: a TEI header and a text elementa TEI header and a facsimile elementa TEI header and a sourceDoc elementa TEI header, a facsimile element, and a text elementa TEI header, one or more sourceDoc or facsimile elements, and a text + element

-

Like the text element, a facsimile element may also contain an optional +

Like the text element, a facsimile element may also contain an optional front or back element, used in the same way as described in sections and .

- -

In the simplest case, a facsimile just contains a series of graphic elements, each - of which identifies an image file: - - - - - - - If desired, the binaryObject element described in +

In the simplest case, a facsimile just contains a series of graphic elements, each + of which identifies an image file: If desired, the binaryObject element described in (or any other element from the model.graphicLike class) can be used instead of a graphic.

- -

In this simple case, the four page images are understood to represent the complete +

In this simple case, the four page images are understood to represent the complete facsimile, and are to be read in the sequence given. Suppose, however, that the second page of this particular work is available both as an ordinary photograph and as an infra-red image, or in two different resolutions. The surface element may be used to group - the two image files, since these correspond with the same area of the work: - - - - - - - - - - + the two image files, since these correspond with the same area of the work:

- -

The surface element provides a way of indicating that the two images of page2 +

The surface element provides a way of indicating that the two images of page2 represent the same surface within the source material. A surface might be one side of a piece of paper or parchment, an opening in a codex treated as a single surface by the writer, a face of a monument, a billboard, a membrane of a scroll, or indeed any two-dimensional surface, of any size.

- -

The surfaceGrp element may be used to indicate that two (or more) surfaces are +

The surfaceGrp element may be used to indicate that two (or more) surfaces are associated in some way, for example because they represent the recto and verso of the same - leaf, as in this example: - - - - - - - - - - - - The surfaceGrp element may also be useful as a means of identifying other + leaf, as in this example: The surfaceGrp element may also be useful as a means of identifying other groups of written surfaces, such as adjacent faces of a monument, or gatherings of leaves.

- -

Simply grouping related graphics is not however the main purpose of the surface +

Simply grouping related graphics is not however the main purpose of the surface element: rather it is to help identify the location and size of the various two-dimensional spaces constituting the digital facsimile. Note that the actual dimensions of the object represented are not provided by the surface element ; rather, the surface @@ -201,11 +120,9 @@ $Id$ image. Four attributes supplied by the att.coordinated class are used to define this space. - - - +

-

By default, the same coordinate space is used for a surface and for all of its +

By default, the same coordinate space is used for a surface and for all of its child elements.The coordinate space may be thought of as a grid superimposed on a rectangular space. Rectangular areas of the grid are defined as four numbers a b c d: the first two identify the grid point which is at @@ -219,8 +136,7 @@ used to define a polygon of any shape using this coordinate system:--> (typically 1) in the coordinate space. In other cases it may be more convenient to use units such as millimetres. Neither practice implies any specific mapping between the coordinate system used and the actual dimensions of the physical object represented.

- -

A surface element can contain one or more zone elements, each of which +

A surface element can contain one or more zone elements, each of which represents a region or bounding box defined in terms of the same coordinate space as that of its parent surface element. A zone may be rectangular or non-rectangular: a rectangular zone is defined by a sequence of four coordinates in the @@ -230,7 +146,7 @@ used to define a polygon of any shape using this coordinate system:--> supplies a points specification in the same form as that required by the polyline or polygon elements in the SVG standard. See

-

A zone may be used to define any region of interest, such as a detail or illustration, or +

A zone may be used to define any region of interest, such as a detail or illustration, or some part of the surface which is to be aligned with a particular text element, or otherwise distinguished from the rest of the surface. A surface establishes a coordinate system which may be used to address parts or the whole of some digital representation of a @@ -238,8 +154,7 @@ used to define a polygon of any shape using this coordinate system:--> that surface, using the same coordinate system. It might be bigger or smaller than its parent surface, or might overlap its boundaries. The only constraint is that it must be defined using the same coordinate system.

- -

When an image of some kind is supplied within either a zone or a surface, the implication +

When an image of some kind is supplied within either a zone or a surface, the implication is that the image represents the whole of the zone or surface concerned. In the simple case therefore, we might imagine a surface defining a page, within which there is a graphic representing the whole of that page, and a number of zones defining parts of the page, each @@ -247,13 +162,7 @@ used to define a polygon of any shape using this coordinate system:--> graphics actually represents an area larger than the page (for example to include a binding or the surface of a desk on which the page rests), then it will be enclosed by a zone with coordinates larger than those of the parent surface.

- - -

For example, consider the following figure:

- - - Badische Landesbibliothek, Manuscript Durlach 1, Fols. 95v-96r -
This is an image of a two page spread from a manuscript in the Badische +

For example, consider the following figure:

Badische Landesbibliothek, Manuscript Durlach 1, Fols. 95v-96r
This is an image of a two page spread from a manuscript in the Badische Landesbibliothek, Karlsruhe. We have no information as to the dimensions of the original object, but the low resolution image displayed here contains 500 pixels horizontally and 321 pixels vertically. For convenience, we might map each pixel to one cell of the @@ -264,49 +173,23 @@ used to define a polygon of any shape using this coordinate system:--> the attributes which define the coordinate space; for example doubling them all would map each pixel to two grid points in the coordinate space.

- -

We therefore define a surface element corresponding with the area of the image - which represents the whole of the two page spread and embed the graphic within it: - - - -

- - - -

If desired, the binaryObject element described in (or any +

We therefore define a surface element corresponding with the area of the image + which represents the whole of the two page spread and embed the graphic within it:

+

If desired, the binaryObject element described in (or any other element from the model.graphicLike class) may be used instead of a graphic element.

- -

Since the image in this example is of a two page opening, we will probably wish to define - at least two nested zones, one for each page: - - - - - - - - - - - - - - -

-

As this example shows, in addition to acting as a container for graphic elements, +

Since the image in this example is of a two page opening, we will probably wish to define + at least two nested zones, one for each page:

+

As this example shows, in addition to acting as a container for graphic elements, zone elements may be used to identify parts of a surface for analytical purposes.

-

The relationship between zone and surface can be quite complex: for example, it may be +

The relationship between zone and surface can be quite complex: for example, it may be appropriate to treat the whole of a two page spread as a single written surface, perhaps because particular written zones span both pages. A zone may contain a nested surface, if for example a page has an additional scrap of paper attached to it. A zone may be of any shape, not simply rectangular. Discussion of these and other cases are provided in section below.

- - -

In the following extended example, we discuss a hypothetical digital edition of an early +

In the following extended example, we discuss a hypothetical digital edition of an early 16th century French work, Charles de Bovelles' Géometrie Pratique.The image is taken from the collection at , and was digitized from a copy in the Bibliothèque Municipale de Lyon, by whose kind permission it is included here. In this edition, each page has been digitized as a separate file: for example, recto page 49 @@ -315,46 +198,18 @@ used to define a polygon of any shape using this coordinate system:--> surface element for this page, which we situate within a coordinate scale running from 0 to 200 in the x (horizontal) axis, and 0 to 300 in the y (vertical) axis. The surface element contains a graphic element which represents the whole - of this surface: - - - - We can now identify distinct zones within the page image using the + of this surface: We can now identify distinct zones within the page image using the coordinate scale defined for the surface. In the following figure we show the upper part of the page, with boxes indicating four such zones. Each of these will be represented by a zone element, given within the surface element already defined, and specified in terms of the same coordinate system. Some zones of - interest are indicated by red lines in the following image.

- - Detail of p 49r from Bovelles Géometrie Pratique -
The following encoding defines each of the four zones identified in the figure - above. - - - - - - - - - - - - - Note that the location of each zone is defined independently but + interest are indicated by red lines in the following image.
Detail of p 49r from Bovelles Géometrie Pratique
The following encoding defines each of the four zones identified in the figure + above. Note that the location of each zone is defined independently but using the same coordinate system.

- -

A non rectangular-zone, for example that containing the word cloche. +

A non rectangular-zone, for example that containing the word cloche. at bottom left of the page, could also be defined, using the points attribute: - - - - - - +

- - -

In the examples above a single graphic element has been associated directly with the +

In the examples above a single graphic element has been associated directly with the surface of the page rather than nesting it within a zone. However, it is also possible to include multiple zone elements which contain a graphic element, if for example a detailed image is available. Since all zone elements use the same @@ -362,27 +217,13 @@ used to define a polygon of any shape using this coordinate system:--> demonstrate enclosure of one zone within another by means of nesting. To continue the current example, supposing that we have an additional image called Bovelles49r-detail.png containing an additional image of the figure in the - third zone above, we might encode that zone as follows: - - - - + third zone above, we might encode that zone as follows:

- - -

Within a surface or zone, individual lines can be identified using the +

Within a surface or zone, individual lines can be identified using the path element, which also carries the points attribute: -

- - Smaller detail of p 49r from Bovelles highlighting two specific lines -
- - - - - - +
Smaller detail of p 49r from Bovelles highlighting two specific lines
+ This is useful for linking an annotation or explanation to a specific line on an object surface. Any number of coordinates can be included to specify lines @@ -390,48 +231,18 @@ used to define a polygon of any shape using this coordinate system:--> story lines appearing at the beginning of chapter 40 of Tristram Shandy might be encoded: -
- - Page 152 of Tristram Shandy -
- - - - - +
Page 152 of Tristram Shandy
+

- -
-
- Combining Transcription with Facsimile - -

A digitized source document may contain nothing more than page images and a small amount of +

+
+ Combining Transcription with Facsimile +

A digitized source document may contain nothing more than page images and a small amount of metadata. It may also contain an encoded transcription of the pages represented, which may either be embedded within a sourceDoc element, or supplied in parallel with a facsimile as defined above.

-

If the transcription is regarded as a text in its own right, organized and structured +

If the transcription is regarded as a text in its own right, organized and structured independently of its physical realization in the document or documents represented by the facsimile, then the recommended practice is to use the text element to contain such a structured representation, and to present it in parallel. The text element @@ -441,39 +252,15 @@ used to define a polygon of any shape using this coordinate system:--> which the document came to take its present form, or the physical disposition of its component parts, it can be presented as an embedded transcription, as further described in section below.

-
- Parallel Transcription - -

Suppose now that we wish to align a transcription of the page discussed in the preceding +

+ Parallel Transcription +

Suppose now that we wish to align a transcription of the page discussed in the preceding section with particular zones. We begin by giving each relevant part of the facsimile an - identifier: - - - - - - - - - - - - - - - - - The alignment between transcription and image is made, as usual, - by means of the facs attribute: - - De Geometrie 49 - DU SON ET ACCORD DES CLOCHES ET des alleures des + identifier: The alignment between transcription and image is made, as usual, + by means of the facs attribute: De Geometrie 49 DU SON ET ACCORD DES CLOCHES ET des alleures des chevaulx, chariotz & charges, des fontaines:& encyclie du monde, - & de la dimension du corps humain. Chapitre septiesme -

-

Le son & accord des cloches pendans en ung mesme axe, est faict en - contraires parties.

-

LEs cloches ont quasi figures de rondes + & de la dimension du corps humain. Chapitre septiesme

Le son & accord des cloches pendans en ung mesme axe, est faict en + contraires parties.

LEs cloches ont quasi figures de rondes pyramides imperfaictes & irregulieres: & leur accord se fait par reigle geometrique. Comme si les deux cloches C & D sont pendans à ung mesme axe ou essieu A B: @@ -481,66 +268,35 @@ used to define a polygon of any shape using this coordinate system:--> comme voyez icy figuré. Car quand lune sera en hault, laultre declinera embas. Aultrement si elles declinent toutes deux ensembles en une mesme partie, elles seront discord, & sera leur - sonnerie mal plaisante à oyr.

- -

-
- + sonnerie mal plaisante à oyr.

- -

It is also possible to point in the other direction, from a surface or +

It is also possible to point in the other direction, from a surface or zone to the corresponding text. This is the function of the start attribute, which supplies the identifier of the element containing at least the start of the transcribed text found within the surface or zone concerned. Thus, another way of - linking this page with its transcription would be simply - - - - - - -

- - - De Geometrie 49 - -
- - -

- - - - - - - - - - - - - - - -
- -
- Embedded Transcription -

An embedded transcription is one in which words and other written traces + linking this page with its transcription would be simply

De Geometrie 49

+ + + + + + + + + + + + + +
+
+ Embedded Transcription +

An embedded transcription is one in which words and other written traces are encoded as subcomponents of elements representing the physical surfaces carrying them rather than independently of them.

-

The following elements are available for this purpose: - - - - - - - +

The following elements are available for this purpose:

- -

The elements surface, surfaceGrp, and zone were introduced +

The elements surface, surfaceGrp, and zone were introduced above in section . When supplied within a sourceDoc element, these elements may contain transcriptions of the written content of a source in addition to or as an alternative to digital images of them. Such transcription may be @@ -554,87 +310,70 @@ used to define a polygon of any shape using this coordinate system:--> may be indicated using the zone element. The seg element described in section may also be used to indicate smaller sequences of tokens within zone, or line as appropriate.

- -

Returning to the preceding example, we might transcribe the content of the zone to which +

Returning to the preceding example, we might transcribe the content of the zone to which we gave the identifier B49rPara2 within a sourceDoc element as follows:

- - - - - - - - LEs cloches ont quasi - figures de rondes pyramides imperfaictes & - irregulieres: & leur accord se - fait par reigle geometrique. Comme si les deux cloches C - & D sont pendans à ung mesme axe ou essieu A B: je dis que - leur accord se fera en cõtraires parties cõme - voyez icy figuré. Car quãd lune sera en hault, laultre + + + + + + + + + LEs cloches ont quasi + fi + gures de rondes pyra + mides imperfaictes & + + irregulieres: & leur accord se + fait par reigle geometrique. Com + me si les deux cloches C + & D + sont pendans à ung mesme axe + ou essieu A B: je dis que + leur ac + cord se fera en cõtraires parties + cõme + voyez icy figuré. Car quãd + lune sera en hault, laultre declinera embas. Aultrement si elles declinent toutes deux ensembles en une - mesme partie, elles seront discord, & sera leur sonnerie - mal plaisante à oyr. - - - - -

As mentioned above, some or all of the written surfaces being transcribed may be + mesme partie, elles seront discord, + & sera leur sonnerie + mal plaisante à oyr. + + + + + + + +

As mentioned above, some or all of the written surfaces being transcribed may be composed of physically distinct scraps. In the following example, taken from the Walt Whitman Archive, two pieces of newsprint have been glued to a piece of blue paper on - which a poem is being drafted:

- - Single leaf of notes possibly related to the poem eventually titled - Sleepers. From the Walt Whitman Archive (Duke 258). -
The two pieces of newsprint might simply be regarded as special kinds of zone, + which a poem is being drafted:
Single leaf of notes possibly related to the poem eventually titled + Sleepers. From the Walt Whitman Archive (Duke 258).
The two pieces of newsprint might simply be regarded as special kinds of zone, but they are also new surfaces, since they might contain additional written zones themselves (such as the numbers in this case).

- -

Using these elements, the Whitman draft above might be encoded as follows: - - - Poem - As in Visions of — at - night — - All sorts of fancies running through - the head - - - - Spring has just set in here, and the weather[...] a steamer - 2 - - - - - "The shores on either side of the Sound are... The In- - 3 - - - - +

Using these elements, the Whitman draft above might be encoded as follows: PoemAs in Visions of — atnight —All sorts of fancies running throughthe headSpring has just set in here, and the weather[...] a steamer 2"The shores on either side of the Sound are... The In- 3

- -

The metamark element used in this example is further discussed below ()

- -

Note that in this example we have not included any graphic element +

The metamark element used in this example is further discussed below ()

+

Note that in this example we have not included any graphic element corresponding with the zone or surface elements identified in the transcription. The encoder may choose to complement a transcription with graphic representations of its source at whatever level is considered effective, or not at all. Equally, the encoder may choose to provide only graphics without any transcription, to provide only a structured (non-embedded) transcription, or to provide any combination of the three.

-

This example also lacks any coordinate information to specify either the size of the two +

This example also lacks any coordinate information to specify either the size of the two newspaper fragments or whereabouts on the parent surface element they are to be found, other than the reading order implicit in their sequence. Such information could be added if desired by specifying a coordinate system on the outermost surface element, and then indicating values within that system for each of the two fragments, as was discussed above. We discuss this in further detail in section below.

- -
- Advanced Uses of surface and zone - -

As a child of sourceDoc, the surface element both identifies a specific area +

+ Advanced Uses of surface and zone +

As a child of sourceDoc, the surface element both identifies a specific area containing writing and provides a two dimensional set of coordinates which can be used to position and define dimensions for sub-parts of it. Furthermore, surfaces may nest within other surfaces, as in the case of patches or other written materials attached to the main @@ -643,30 +382,14 @@ used to define a polygon of any shape using this coordinate system:--> surface element. It is also possible, however, that a different coordinate system is required for such a nested surface, perhaps because it requires a more complex granularity. We consider both possibilities.

- -

In the earlier examples showing nested examples we did not provide any coordinate +

In the earlier examples showing nested examples we did not provide any coordinate information, for simplicity of presentation. Suppose however, that we wish to indicate the position and sizes of the newspaper scraps in above, relative to the whole page. As previously noted, the four attributes ulx, uly, lrx and lry when given on the surface element define the coordinate scheme, rather than specifying the location of that surface. We must therefore introduce an additional zone element, as in the following revised encoding for - this example - - - Poem - As in Visions of — at - night — - All sorts of fancies running through - the head - - - - Spring has just set in here, and the weather[...] a steamer - 2 - - - In this version of the encoding, the inner surface, corresponding + this example PoemAs in Visions of — atnight —All sorts of fancies running throughthe headSpring has just set in here, and the weather[...] a steamer 2 In this version of the encoding, the inner surface, corresponding with the first piece of newsprint, inherits locational information from the zone element that contains it. This zone, and the preceding one, which contains a sequence of line elements, are both positioned in terms of the coordinates specified on the @@ -674,30 +397,17 @@ used to define a polygon of any shape using this coordinate system:--> direction. On that scale, the line elements occupy a rectangle with coordinates (1,1,10,10), while the nested surface occupies a rectangle with coordinates (4,4,20,20).

-

Now suppose that we wish to define a finer scale grid for the newspaper patch, perhaps +

Now suppose that we wish to define a finer scale grid for the newspaper patch, perhaps because we wish to localize zones within it with greater accuracy. To do this we will need to specify the position of the nested surface as in the previous example, but also to - define the new coordinate system. We accomplish this as follows: - - - Poem - - the head - - - - Spring has just set in here, and the - weather [...] a steamer - - - As before, the second zone defines the position and size of the + define the new coordinate system. We accomplish this as follows: Poemthe head Spring has just set in here, and the + weather [...] a steamer As before, the second zone defines the position and size of the newspaper patch itself in terms of a coordinate system running from 0 to 50 on both X and Y axes. The nested surface element however defines a new scale for all of its components, running from 0 to 100 on both X and Y axes. The position of the nested zone containing the text Spring ... steamer is now given in terms of this scale.

- -

All of the examples so far given have involved rectangular zones, for clarity of +

All of the examples so far given have involved rectangular zones, for clarity of exposition. As noted above, the points attribute may be used to define non-rectangular zones as a series of points. For example, in the last of the Whitman examples discussed in section above, we might wish to record the @@ -705,63 +415,39 @@ used to define a polygon of any shape using this coordinate system:--> is not a rectangular zone, we use the points attribute to indicate the points defining a polygon which contains it. The values used are expressed in terms of a coordinate space running from 0 to 229 in the X dimension, and 0 to 160 in the Y dimension.

- - - - - - - - -

In exactly the same way, we may wish to identify the curved zone in the following image - containing the word Northamptonshire:

- - Gravestone of Private Moulds -
This curved zone might be encoded in the following way: - - - - - + + + + + + +

In exactly the same way, we may wish to identify the curved zone in the following image + containing the word Northamptonshire:

Gravestone of Private Moulds
This curved zone might be encoded in the following way:

-

Finally, it should be noted that a zone does not need to be entirely contained +

Finally, it should be noted that a zone does not need to be entirely contained within the two-dimensional space defined by its parent surface. For example, we might wish to encode the example in above not as a surface representing the whole of the two page spread, but as a surface representing only the written part of this opening. The written part appears 50 units from the left of the image and 20 units from the top, while the bottom right corner of the written part appears 400 units from the left of the image, and 280 units from the top. We therefore define the written surface within this - image as follows: - - - - To describe the whole image, we will now need to define a zone of + image as follows: To describe the whole image, we will now need to define a zone of interest which represents an area larger than this surface. Using the same coordinate system as that defined for the surface, its coordinates are 0,0,500,321. This zone of interest can be defined by a zone element, within which we can place the - uncropped graphic: - - - - - + uncropped graphic:

- -
- -
- -
- Scope of Transcriptions - -

When transcribing a primary source, whether using text or sourceDoc, +

+
+
+ Scope of Transcriptions +

When transcribing a primary source, whether using text or sourceDoc, scholars may wish to record information concerning individual readings of letters, words, or larger units.They may also wish to include other editorial material, such as comments on the status or possible origin of particular readings, corrections, or text supplied to fill lacunae.

- -

Such elements may also be used for digital transcriptions in which the object is not to +

Such elements may also be used for digital transcriptions in which the object is not to represent a finished text, but rather to represent the creative process, as evidenced by different layers or traces of writing in one or more documents. Transcriptions of this kind are closely focussed on the physical appearance of specific @@ -771,22 +457,14 @@ used to define a polygon of any shape using this coordinate system:--> so on. Such distinctions are considered of particular importance when dealing with authorial manuscripts, but are also relevant in the case of historical sources such as charters or other legal documents.

- -

In either case, it is customary in transcriptions to register certain features of the +

In either case, it is customary in transcriptions to register certain features of the source, such as ornamentation, underlining, deletion, areas of damage and lacunae. This - chapter provides ways of encoding such information: - methods of recording editorial or other alterations to the text, such as expansion - of abbreviations, corrections, conjectures, etc. (section ) - methods of describing important extra-linguistic phenomena in the source: unusual - spaces, lines, page and line breaks, changes of manuscript hand, etc. (section ) - methods of representing aspects of layout such as spacing or lines - - methods of representing material such as running heads, catch-words, and the like - (section ) -

- - -

The remainder of this chapter describes a model for encoding such transcriptions, in which + chapter provides ways of encoding such information: methods of recording editorial or other alterations to the text, such as expansion + of abbreviations, corrections, conjectures, etc. (section )methods of describing important extra-linguistic phenomena in the source: unusual + spaces, lines, page and line breaks, changes of manuscript hand, etc. (section )methods of representing aspects of layout such as spacing or lines + methods of representing material such as running heads, catch-words, and the like + (section )

+

The remainder of this chapter describes a model for encoding such transcriptions, in which elements such as mod, del, etc. are used to mark writing traces and their functions within the document. Each such element can be assigned to one or more editorially-defined modification groups, termed a change, by means of a global @@ -798,13 +476,10 @@ used to define a polygon of any shape using this coordinate system:--> transcription may be organized topographically in terms of lines of writing, using the line element, or in terms of further nested zones, or as a combination of the two ().

- - - -

These recommendations are not intended to meet every transcriptional circumstance likely to +

These recommendations are not intended to meet every transcriptional circumstance likely to be faced by any scholar. Rather, they should be regarded as a base which can be elaborated if necessary by different scholars in different disciplines

- - -

As a rule, all elements which may be used in the course of a transcription of a single +

As a rule, all elements which may be used in the course of a transcription of a single witness may also be used in a critical apparatus, i.e. within the elements proposed in chapter . This can generally be achieved by nesting a particular reading containing tagged elements from a particular witness within the rdg element in an app structure.

-

Just as a critical apparatus may contain transcriptional elements within its record of +

Just as a critical apparatus may contain transcriptional elements within its record of variant readings in various witnesses, one may record variant readings in an individual witness by use of the apparatus mechanisms app and rdg. This is discussed in section .

- -
- Altered, Corrected, and Erroneous Texts - -

In the detailed transcription of any source, it may prove necessary to record various +

+ Altered, Corrected, and Erroneous Texts +

In the detailed transcription of any source, it may prove necessary to record various types of actual or potential alteration of the text: expansion of abbreviations, correction of the text (either by author, scribe, or later hand, or by previous or current editors or scholars), addition, deletion, or substitution of material, and @@ -836,55 +508,37 @@ recommendations form a good basis for such future work.--> either elements defined in the core module (defined in chapter ) or specialized elements available only when the module described in this chapter is available.

- -
- Core Elements for Transcriptional Work -

In transcribing individual sources of any type, encoders may record corrections, +

+ Core Elements for Transcriptional Work +

In transcribing individual sources of any type, encoders may record corrections, normalizations, additions, and omissions using the elements described in section . Representation of abbreviations and their expansions may also involve use of elements described in section . Elements - particularly relevant to this chapter include: - - - - - - - - - + particularly relevant to this chapter include:

-

All of these elements bear additional attributes for specifying who is responsible +

All of these elements bear additional attributes for specifying who is responsible for the interpretation represented by the markup, and the associated certainty. In addition, some of them bear an attribute allowing the markup to be categorized by - type and source. - - - - - The specific aspect of the markup described by these attributes differs + type and source. The specific aspect of the markup described by these attributes differs on different elements; for further discussion, see the relevant sections below, especially section .

-

The following sections describe how the core elements just named may be used in the +

The following sections describe how the core elements just named may be used in the transcription of primary source materials.

-
- -
- Abbreviation and Expansion - -

The writing of manuscripts by hand lends itself to the use of abbreviation to shorten +

+
+ Abbreviation and Expansion +

The writing of manuscripts by hand lends itself to the use of abbreviation to shorten scribal labour. Commonly occurring letters, groups of letters, words, or even whole phrases, may be represented by significant marks. This phenomenon of manuscript abbreviation is so widespread and so various that no taxonomy of it is here attempted. Instead, methods are shown which allow abbreviations to be encoded using the core elements mentioned above.

-

A manuscript abbreviation may be viewed in two ways. One may transcribe it as a +

A manuscript abbreviation may be viewed in two ways. One may transcribe it as a particular sequence of letters or marks upon the page: thus, a p with a bar through the descender, a superscript hook, a macron. One may also interpret the abbreviation in terms of the letter or letters it is seen as standing for: thus, per, re, n. Both of these views are supported by these Guidelines.

- -

In many cases the glyph found in the manuscript source also exists in the Unicode +

In many cases the glyph found in the manuscript source also exists in the Unicode character set: for example the common Latin brevigraph ⁊, standing for et and often known as the Tironian et can be directly represented in any XML document as the Unicode character with code @@ -893,64 +547,45 @@ recommendations form a good basis for such future work.--> chapter . This module allows the encoder great flexibility both in processing and in documenting non-standard characters or glyphs, including the ability to provide detailed documentation and images for them.

- -

These two methods of coding abbreviation may also be combined. An encoder may record, +

These two methods of coding abbreviation may also be combined. An encoder may record, for any abbreviation, both the sequence of letters or marks which constitutes it, and its sense, that is, the letter or letters for which it is believed to stand. For example, in the following fragment the phrase euery persone is - represented by a sequence of abbreviated characters:

- - Detail from fol. 126v of Bodleian MS Laud Misc 517 -
These lines may be transcribed directly, using the g element to + represented by a sequence of abbreviated characters:
Detail from fol. 126v of Bodleian MS Laud Misc 517
These lines may be transcribed directly, using the g element to indicate the two brevigraphs as follows: euery persone that loketh after heuen hath a place in this ladder - - - - - - - - Note that in each case the g element may contain a + Note that in each case the g element may contain a suggested replacement for the referenced brevigraph; this is purely advisory however, and may not be appropriate in all cases. The referenced character definitions may be located elsewhere in this or some other document, typically forming part of a charDecl element, as described in .

- -

The transcriber may also wish to indicate that, because of the presence of these +

The transcriber may also wish to indicate that, because of the presence of these particular characters, the two words are actually abbreviations, by using the - abbr element: euery - persone ... Alternatively, the + abbr element: euerypersone ... Alternatively, the transcriber may choose silently to expand these abbreviations, using the - expan element: euery - persone ... And, of course, the choice element + expan element: euerypersone ... And, of course, the choice element can be used to show that one encoding is an alternative for the other: eueryeuery

-

When abbreviated forms such as these are expanded, two processes are carried out: +

When abbreviated forms such as these are expanded, two processes are carried out: some characters not present in the abbreviation are added (always), and some characters or glyphs present in the abbreviation are omitted or replaced (often). For example, when the abbreviation Dr. is expanded to Doctor, the dot in the abbreviation is removed, and the letters octo are added. Where detailed markup of abbreviated words is required, these two aspects may be marked up explicitly, using the following - elements: - - - Using these elements, a transcriber may indicate the status of the + elements: Using these elements, a transcriber may indicate the status of the individual letters or signs within both the abbreviation and the expansion. The am element surrounds characters or signs such as tittles or tildes, used to indicate the presence of an abbreviation, which are typically removed or replaced - by other characters in the expanded form of the abbreviation: euy - sone ... while the ex + by other characters in the expanded form of the abbreviation: euysone ... while the ex element may be used to indicate those characters within the expansion which are not - present in the abbreviated form. euery - persone ... The content of the abbr + present in the abbreviated form. euerypersone ... The content of the abbr element should usually include the whole of the abbreviated word, while the expan element should include the whole of its expansion. If this is not considered necessary, the am and ex elements may be used within a choice element, as in this example: euery persone ...

-

As implied in the preceding discussion, making decisions about which of these various +

As implied in the preceding discussion, making decisions about which of these various methods of representing abbreviation to use will form an important part of an encoder's practice. As a rule, the abbr and am elements should be preferred where it is wished to signify that the content of the element is an @@ -967,7 +602,7 @@ recommendations form a good basis for such future work.--> throughout. If the highest priority is to present a reading transcription, while indicating that some letters or words are not actually present in the original, the choice will be to use ex or expan throughout.

-

Further information may be attached to instances of these elements by the +

Further information may be attached to instances of these elements by the note element, on which see section , and by use of the resp and cert attributes. In this instance from the English Brut, a note is attached to an editorial expansion of the tail on @@ -984,34 +619,25 @@ recommendations form a good basis for such future work.--> supplied for the resp attribute should point to the name of the editor responsible for this and possibly other interventions; an appropriate element therefore might be a respStmt element in the header like the following: - - - Editorial emendations - Malcom Parkes - Observe that the cert and resp + Editorial emendationsMalcom Parkes Observe that the cert and resp attributes are used with the ex element only to indicate confidence in the content of the element (i.e. the expansion), and responsibility for suggesting this expansion respectively.

-

The choice element may be used to indicate that the proposed expansion is +

The choice element may be used to indicate that the proposed expansion is one way of encoding what might equally well be represented as an abbreviation, represented by the hooked D, as follows: For alle the while that I had - gooɗ - goode I was + gooɗgoode I was welbeloued If it is desired to express aspects of certainty and responsibility for some other aspect of the use of these elements, then the mechanisms discussed in chapter should be used. See also for discussion of the issues of certainty and responsibility in the context of transcription.

- -

If more than one expansion for the same abbreviation is to be recorded, multiple +

If more than one expansion for the same abbreviation is to be recorded, multiple notes may be supplied. It may also be appropriate to use the markup for critical apparatus; an example is given in section .

-
- - -
- Correction and Conjecture - -

The sic, corr, and choice elements, defined in the core module should be used to indicate passages deemed in +

+
+ Correction and Conjecture +

The sic, corr, and choice elements, defined in the core module should be used to indicate passages deemed in need of correction, or actually corrected, during the transcription of a source. For example, in the manuscript of William James's A Pluralistic Universe as edited by Fredson Bowers (Cambridge: Harvard University Press, 1977), a sentence @@ -1024,18 +650,18 @@ recommendations form a good basis for such future work.--> represented as a choice: But Oneone must have lived ...

-

Similarly, in this example from Albertus Magnus, both a manuscript error +

Similarly, in this example from Albertus Magnus, both a manuscript error angues and its correction augens are registered within a choice element: Nos autem iam ostendimus quod nutrimentum et anguesaugens.

-

Note that the corr element is used to provide a corrected form which is +

Note that the corr element is used to provide a corrected form which is not present in the source; in the case of a correction made in the source itself, whether scribal, authorial, or by some other hand, the add, del, and subst elements described in should be used.

-

The sic element is used to mark passages considered by the transcriber to be +

The sic element is used to mark passages considered by the transcriber to be erroneous; in such cases, the corr element indicates the transcriber's correction of them. Where the transcriber considers that one or more words have been erroneously omitted in the original source and corrects this omission, the @@ -1045,7 +671,7 @@ recommendations form a good basis for such future work.--> transcriber supplies the word we omitted by the author: You see that I avoid the word create for we create nothing we develope.

-

As with expan and abbr, the choice as to whether to record simply +

As with expan and abbr, the choice as to whether to record simply that there is an apparent error, or simply that a correction has been applied, or to record both possible readings within a choice element is left to the encoder. The decision is likely to be a matter of editorial policy, which might be @@ -1055,12 +681,11 @@ recommendations form a good basis for such future work.--> highest priority is to present a reading transcription, while indicating that perceived errors in the original have been corrected, the choice will be to use only corr throughout.

- -

Further information may be attached to instances of these elements by the +

Further information may be attached to instances of these elements by the note element and resp and cert attributes. Instances of these elements may also be classified according to any convenient typology using the type attribute.

-

For example, consider the following encoding of an emendation in the Hengwrt +

For example, consider the following encoding of an emendation in the Hengwrt manuscript proposed by E. Talbot Donaldson: Telle me also, to what conclusioun Were membres maad, of generacioun And of so parfit wis a wightwright ywroght? This emendation of the Hengwrt copy text, based on a Latin @@ -1077,19 +702,15 @@ recommendations form a good basis for such future work.--> same annotation to refer to several corrections, by supplying more than one pointer in the target attribute of the note, as shown in the example below.

-

The attribute cert may be used to indicate the degree of confidence +

The attribute cert may be used to indicate the degree of confidence ascribed by the encoder to the proposed emendation on a broad scale: high, medium, or low. The attribute resp is used to indicate who is responsible for the proposed emendation. Its value is a pointer, which will typically indicate a respStmt or name element in the header of the transcribed document, but can point anywhere, for example to some online authority file. Using these two attributes, the corr element presented above might usefully be - enhanced as follows: - - E Talbot Donaldson - And of so parfit wis a wightwright ywroght?

- -

As remarked above, where the same annotation applies to several corrections, this may + enhanced as follows: E Talbot Donaldson And of so parfit wis a wightwright ywroght?

+

As remarked above, where the same annotation applies to several corrections, this may be represented by supplying multiple pointers on the note. Consider for example such corrections as the following, in Dudo of S. Quentin. Parkes cites two cases in this manuscript of the same phenomenon: quamuis mensiners que nutu dei gesta @@ -1098,7 +719,7 @@ recommendations form a good basis for such future work.--> graphically what the scribe should be copying but which does not make sense in the context.

-

The target attribute on the note element indicates the +

The target attribute on the note element indicates the choice elements which exemplify this kind of scribal error. This necessitates the addition of an identifier to each choice element. However, if the number of corrections is large and the number of notes is small, it may well @@ -1116,24 +737,18 @@ recommendations form a good basis for such future work.--> provide documentation explaining the circumstances in which particular codes are judged appropriate. A suitable location for this might be within the correction element of the encodingDesc of the header, which - might include a list such as the following: - -

The following codes are used to categorize corrections identified in this - transcription: - - Substitution of a more familiar word which resembles graphically + might include a list such as the following:

The following codes are used to categorize corrections identified in this + transcription: Substitution of a more familiar word which resembles graphically what the scribe should be copying but which does not make sense in the - context. - -

A subtype attribute may be used + context.

A subtype attribute may be used in conjunction with the type for subclassification purposes: the above examples might thus be represented as choice type="substitution" subtype="graphicResemblance" for example.

-

For a given project, it may well be desirable to limit the possible values for the +

For a given project, it may well be desirable to limit the possible values for the type or subtype attributes automatically. This is easily done but requires customization of the TEI system using techniques described in , in particular , which should be consulted for further information on this topic.

-

When making a correction in a source which forms part of a textual tradition attested +

When making a correction in a source which forms part of a textual tradition attested by many witnesses, a textual editor will sometimes use a reading from one witness to correct the reading of the source text. In the general case, such encoding is best achieved with the mechanisms provided by the module for textual criticism described @@ -1149,38 +764,20 @@ recommendations form a good basis for such future work.--> text, a list of witnesses used in this text will be given, one of which has an identifier Gg. Each witness will be represented either by a witness element (see ) or more fully by an - msDesc element (see ): - - - Cambridge - University Library - Gg.1. 27 - - - + msDesc element (see ): CambridgeUniversity LibraryGg.1. 27

- -

The app element described in chapter provides a more - powerful way of representing all three possible readings in parallel: And of so parfit wis a - wight - wright - wyf -

-

This encoding simply records the three readings found in the various traditions, and +

The app element described in chapter provides a more + powerful way of representing all three possible readings in parallel: And of so parfit wis a wightwrightwyf

+

This encoding simply records the three readings found in the various traditions, and gives (by means of the wit attribute) an indication of the witnesses supporting each. If the resp attribute were supplied on the rdg element, it would indicate the person responsible for asserting that the manuscript indicated has this reading, who is not necessarily the same as the person responsible for asserting that this reading should be used to correct the others. Editorial intervention elements such as corr can however be nested within a - rdg to provide this additional information: And of so parfit wis a - wight - wright - wyf - This encoding asserts that the reading wyf + rdg to provide this additional information: And of so parfit wis a wightwrightwyf This encoding asserts that the reading wyf found in Gg is regarded as a correction by Parkes.

- -

Like the resp attribute, the cert attribute may be used with +

Like the resp attribute, the cert attribute may be used with both corr and rdg elements. When used on the rdg element, these attributes indicate confidence in and responsibility for identifying the reading within the sources specified; when used on the corr element they @@ -1189,39 +786,24 @@ recommendations form a good basis for such future work.--> attribute, or by the wit attribute of a parent rdg), the reading supplied within a corr has been provided by the person indicated by the resp attribute.

- -

If it is desired to express certainty of or responsibility for some other aspect of +

If it is desired to express certainty of or responsibility for some other aspect of the use of these elements, then the mechanisms discussed in chapter may be found useful. See also for further discussion of the issues of certainty and responsibility in the context of transcription.

-
- -
- Additions and Deletions - -

Additions and deletions observed in a source text may be described using the - following elements: - - - - - Of these, add and del are included in the core module, +

+
+ Additions and Deletions +

Additions and deletions observed in a source text may be described using the + following elements: Of these, add and del are included in the core module, while addSpan and delSpan are available only when using the module defined in this chapter. These particular elements are members of the att.spanning class, from which they inherit the following - attribute: - - + attribute:

- -

Further characteristics of each addition and deletion, such as the hand used, its +

Further characteristics of each addition and deletion, such as the hand used, its effect (complete or incomplete, for example), or its position in a sequence of such operations may conveniently be recorded as attributes of these elements, all of which - are members of the att.transcriptional class: - - + are members of the att.transcriptional class:

- - -

As described in section , the add element is used to +

As described in section , the add element is used to record any manuscript addition observed in the text, whether it is considered to be authorial or scribal. In the autograph manuscript of Max Beerbohm's The Golden Drugget, the author's addition of do ever may be @@ -1233,8 +815,7 @@ recommendations form a good basis for such future work.--> holograph

- -

The del element is used to record manuscript deletions in a similar way. In +

The del element is used to record manuscript deletions in a similar way. In the autograph manuscript of D. H. Lawrence's Eloi, Eloi, lama sabachthani the author's deletion of my may be recorded as follows. In this case, the hand attribute indicating that the @@ -1242,9 +823,7 @@ recommendations form a good basis for such future work.--> that the deletion was by strike-through: For I hate this my body, which is so dear to me ... D H Lawrence holograph

- - -

If deletions are classified systematically, the type attribute may be +

If deletions are classified systematically, the type attribute may be useful to indicate the classification; when they are classified by the manner in which they were effected, or by their appearance, however, this will lead to a certain arbitrariness in deciding whether to use the type or the @@ -1252,22 +831,12 @@ recommendations form a good basis for such future work.--> that the rend attribute be used for description of the appearance or method of deletion, and that the type attribute be reserved for higher level or more abstract classifications.

- -

The place attribute is also available to indicate the location of an +

The place attribute is also available to indicate the location of an addition. For example, consider the following passage from a draft letter by Robert - Graves:

- - Draft letter from Robert Graves to Desmond Flower, 17 Dec 1938 (detail). - -
At the end of this extract, the writer inserts the word cant, above + Graves:
Draft letter from Robert Graves to Desmond Flower, 17 Dec 1938 (detail). +
At the end of this extract, the writer inserts the word cant, above the line, with a stroke to indicate insertion. Assuming that we have previously - defined the identifier RG somewhere: - - - - - - , this extract might now be encoded as follows: The O.E.D. is not a + defined the identifier RG somewhere: , this extract might now be encoded as follows: The O.E.D. is not a dictionary so much as a corpus of precedents in the: current, obsolete, cant, cataphretic and nonce-words are all included. A little earlier in the same extract, @@ -1283,8 +852,7 @@ recommendations form a good basis for such future work.--> We do not deal with these possibilities here, and mention them only to indicate that any encoding of manuscript material of this complexity will need to make decisions about what is and is not worth mentioning.

- - - - - -

An encoder may also wish to indicate that an addition replaces a specific deletion, +

An encoder may also wish to indicate that an addition replaces a specific deletion, that is to encode a substitution as a single intervention in the text. This may be achieved by grouping the addition and deletion together within a subst element. At the end of the passage illustrated above, Graves first writes It is @@ -1329,8 +895,7 @@ a line through it.

element and of the seq attribute to indicate the order in which interventions such as deletions are believed to have occurred are further discussed in section below.

- -

The add and del elements defined in the core module suffice only +

The add and del elements defined in the core module suffice only for the description of additions and deletions which fit within the structure of the text being transcribed, that is, which each deletion or addition is completely contained by the structural element (paragraph, line, division) within which it @@ -1340,8 +905,7 @@ a line through it.

treatment is needed. The addSpan and delSpan elements are provided by this module for that purpose. (For a general discussion of the issue see further ).

- -

In this example of the use of addSpan, the insertion by Helgi Ólafsson of a +

In this example of the use of addSpan, the insertion by Helgi Ólafsson of a gathering containing four neo-Eddic poems into Lbs 1562 4to is recorded as follows. A handNote element is first declared, within the header of the document, to associate the @@ -1350,19 +914,8 @@ a line through it.

is placed to mark the beginning of the span of added text, and an anchor is used to mark its end. The hand attribute on the addSpan element ascribes responsibility for the addition to the manuscript to Helgi, and the - spanTo attribute points to the end of the added text: - - -
- -
-
-
-
- -
-

-

The delSpan element is used in the same way. An authorial manuscript will + spanTo attribute points to the end of the added text:

+

The delSpan element is used in the same way. An authorial manuscript will often contain several @@ -1371,39 +924,29 @@ in the Eliot typescript mentioned above, there are --> several l element, such deletions are problematic: deletion of two consecutive lines should be regarded as a single deletion, but the del element must be properly nested within a single l element. The delSpan element - solves this problem: - Flowed up the hill and down King William Street, - - To where Saint Mary Woolnoth kept the time, - With a dead sound on the final stroke of nine. - - There I saw one I knew, and stopped him, crying "Stetson!... + solves this problem: Flowed up the hill and down King William Street,To where Saint Mary Woolnoth kept the time,With a dead sound on the final stroke of nine.There I saw one I knew, and stopped him, crying "Stetson!...

-

It is also often the case that deletions and additions may themselves contain other +

It is also often the case that deletions and additions may themselves contain other deletions and additions. For example, in Thomas Moore's autograph of the second version of Lalla Rookh two lines are marked for omission by vertical strike-through. Within the first of the two lines, the word upon has also been struck out, and the word - over has been added: - Tis moonlight + over has been added: Tis moonlight upon - over Oman's sky - Her isles of pearl look lovelily In this + over Oman's skyHer isles of pearl look lovelily In this case the anchor and delSpan have been placed within the structural elements (the ls) rather than between, as in the previous example. This is to indicate that placement of these empty elements is arbitrary.

-

The text deleted must be at least partially legible, in order for the encoder to be +

The text deleted must be at least partially legible, in order for the encoder to be able to transcribe it. If all of part of it is not legible, the gap element should be used to indicate where text has not been transcribed, because it could not be. The unclear element described in section may be used to indicate areas of text which cannot be read with confidence. See further section and section .

-
- -
- Substitutions - -

Substitution of one word or phrase for another is perhaps the most common of all +

+
+ Substitutions +

Substitution of one word or phrase for another is perhaps the most common of all phenomena requiring special treatment in transcription of primary textual sources. It may be simply one word written over the top of another, or deletion of one word and its replacement by another written above it by the same hand on the same occasion; @@ -1411,23 +954,17 @@ in the Eliot typescript mentioned above, there are --> several may be a long chain of substitutions on the same stretch of text, with uncertainty as to the order of substitution and as to which of many possible readings should be preferred.

-

As we have shown, the simplest method of recording a substitution is simply to record +

As we have shown, the simplest method of recording a substitution is simply to record both the addition and the deletion. However, when the module defined by this chapter is in use, additional elements are available to indicate that the encoder believes - the addition and the deletion to be part of the same intervention: a substitution. - - - Using the subst element, the example at the end of the last - section might be encoded as follows: - Tis moonlight - uponover Oman's sky - Her isles of pearl look lovelily Since + the addition and the deletion to be part of the same intervention: a substitution. Using the subst element, the example at the end of the last + section might be encoded as follows: Tis moonlight + uponover Oman's skyHer isles of pearl look lovelily Since the purpose of this element is solely to group its child elements together, the order in which they are presented is not significant. When both deletion and addition are present, it may not always be clear which occurs first: using the seq attribute is a simple way of resolving any such ambiguities.

- -

For example, returning to the example from William James, in a passage first written +

For example, returning to the example from William James, in a passage first written out by James as One must have lived longer with this system, to appreciate its advantages, the word this is first replaced by such a and this is then replaced by @@ -1435,9 +972,7 @@ in the Eliot typescript mentioned above, there are --> several other substitutions, ignored here for the sake of clarity. This may be encoded as follows, representing the two changes as a sequence of additions and deletions: One must have lived longer - with this - such a - a system, to appreciate its advantages. Note + with thissuch aa system, to appreciate its advantages. Note the nesting of an add element within a del to record text first added, then deleted in the source. The numbers assigned by the seq attribute may be used to identify the order in which the various additions and @@ -1447,15 +982,13 @@ in the Eliot typescript mentioned above, there are --> several of the overlay levels implicit in the manuscripts of James Joyce's Ulysses. A fuller and more complex way of supporting such an approach is discussed in .

- -

A special case of a substitution may consist of a superfluous word +

A special case of a substitution may consist of a superfluous word or phrase that is silently replaced by some addition. E.g. a scribe abandons a word (without indicating it should be deleted), and then writes a replacement word immediately after. Here the encoder may interpret this as an unmarked deletion which can then be combined with a corresponding addition to a substitution.

- -

The case of a single substitution or scribal correction that involves non-contiguous +

The case of a single substitution or scribal correction that involves non-contiguous addition and deletion can be handled by using the substJoin element to make an explicit connection between one or more add and del elements. In the following example from Thomas Moore's Lalla Rookh, the deletion and addition are @@ -1468,67 +1001,46 @@ in the Eliot typescript mentioned above, there are --> several Note that, unlike subst, the placement of the substJoin is arbitrary. It may occur before or after the relevant add and del elements.

- -

As a more complex example, consider the following passage: -

- - Detail from Dulce et decorum est autograph manuscript in the - English Faculty Library, Oxford University. -
This passage might be encoded as follows: - And towards our distant rest began to trudge, - Helping the worst amongst usDragging the worst amongt - us, who'd no boots - But limped on, blood-shod. All went lame; half-all blind; - Drunk with fatigue ; deaf even to the hoots - Of tired, outstripped fif five-nines that dropped - behind. In this representation, - the authorial slip (amongt for - amongst) is retained without comment. - the other two authorial corrections are marked as substitutions, each - combining a deletion and an addition. - the false start fif in the last line is simply marked - as a deletion; - +
Detail from Dulce et decorum est autograph manuscript in the + English Faculty Library, Oxford University.
This passage might be encoded as follows: And towards our distant rest began to trudge,Helping the worst amongst usDragging the worst amongt + us, who'd no bootsBut limped on, blood-shod. All went lame; half-all blind;Drunk with fatigue ; deaf even to the hootsOf tired, outstripped fif five-nines that dropped + behind. In this representation, the authorial slip (amongt for + amongst) is retained without comment.the other two authorial corrections are marked as substitutions, each + combining a deletion and an addition. the false start fif in the last line is simply marked + as a deletion;

-

The app element presented in chapter provides similar +

The app element presented in chapter provides similar facilities, by treating each state of the text as a distinct reading. The rdg element has a varSeq attribute which may be used in the same way as the seq attribute to indicate the preferred sequence. The - James example above might thus be represented as follows: One must have lived longer with - this - such a - a - system, to appreciate its advantages. + James example above might thus be represented as follows: One must have lived longer with thissuch aa system, to appreciate its advantages.

-
- -
- Cancellation of Deletions and Other Markings -

An author or scribe may mark a word or phrase in some way, and then on reflection +

+
+ Cancellation of Deletions and Other Markings +

An author or scribe may mark a word or phrase in some way, and then on reflection decide to cancel the marking. For example, text may be marked for deletion and the deletion then cancelled, thus restoring the deleted text. Such cancellation may be - indicated by the restore element: - -

-

This element bears the same attributes as the other transcriptional elements. These + indicated by the restore element:

+

This element bears the same attributes as the other transcriptional elements. These may be used to supply further information such as the hand in which the restoration is carried out, the type of restoration, and the person responsible for identifying the restoration as such, in the same way as elsewhere.

-

Presume that Lawrence decided to restore my to the phrase of +

Presume that Lawrence decided to restore my to the phrase of Eloi, Eloi, lama sabachthani first written For I hate this my body, with the my first deleted then restored by writing stet in the margin. This may be encoded: For I hate this my body

-

Another feature commonly encountered in manuscripts is the use of circles, lines, or +

Another feature commonly encountered in manuscripts is the use of circles, lines, or arrows to indicate transposition of material from one point in the text to another. No specific markup for this phenomenon is proposed at this time. Such cases are most simply encoded as additions at the point of insertion and deletions at the point of encirclement or other marking.

-
- -
- Text Omitted from or Supplied in the Transcription -

Where text is not transcribed, whether because of damage to the original, or because +

+
+ Text Omitted from or Supplied in the Transcription +

Where text is not transcribed, whether because of damage to the original, or because it is illegible, or for some other reason such as editorial policy, the gap core element may be used to register the omission; where such text is transcribed, but the editor wishes to indicate that they consider it to be superfluous, for @@ -1537,13 +1049,8 @@ in the Eliot typescript mentioned above, there are --> several editor believes text to be interpolated but genuine, the secl element may be used instead. Where text not present in the source is supplied (whether conjecturally or from other witnesses) to fill an apparent gap in the text, the supplied - element may be used. - - - - -

-

By its nature, the gap element has no content. It marks a point in the text + element may be used.

+

By its nature, the gap element has no content. It marks a point in the text where nothing at all can be read, whether because of authorial or scribal erasure, physical damage, or any other form of illegibility. Its attributes allow the encoder to specify the amount of text which is illegible in this way at this point, using any @@ -1551,49 +1058,33 @@ in the Eliot typescript mentioned above, there are --> several manuscript of The Golden Drugget cited above, the author has erased a passage amounting about 10 cm in length by inking over it completely: Others —and here is one of them...

-

In an autograph letter of Sydney Smith now in the Pierpont Morgan library three words +

In an autograph letter of Sydney Smith now in the Pierpont Morgan library three words in the signature are quite illegible: I am dr Sr yr Sydney Smith The degree of precision attempted when measuring the size of a gap will vary with the purpose of the encoding and the nature of the material: no particular recommendation is made here.

- -

As noted above, the gap element should only be used where text has not been +

As noted above, the gap element should only be used where text has not been transcribed. If partially legible text has been transcribed, one of the elements damage and unclear should be used instead (these elements are described in section ); if the text is legible and has been transcribed, but the editor wishes to indicate that they regard it is superfluous or redundant, then the element surplus may be used in preference to the core element sic used to indicate text regarded as erroneous.

- -

Amongst the many examples cited in Hans Krummrey & Silvio Panciera's classic text +

Amongst the many examples cited in Hans Krummrey & Silvio Panciera's classic text on the editing of epigraphic inscriptions is the following. In a late classical inscription, the form dedikararunt is encountered. The editor may choose any of the following three possibilities:

- - mark this as an erroneous form - dedikararunt - - additionally supply a corrected form - dedikararunt - dedikarunt - - - indicate that the erroneous form contains surplus characters which the editor + + mark this as an erroneous form dedikararunt + additionally supply a corrected form dedikararuntdedikarunt + indicate that the erroneous form contains surplus characters which the editor wishes to suppress dedikararunt - - -

The surplus element may also be used to mark up interpolations, as in the - following example taken from a 13th century Italian source: - a darmi morte, poi m'avete preso a - tradimento - sì com' l'uccellator prende l'uccello - - e lettere dintorno che diriano in questa - guisa - Più v'amo, dëa, che non faccio Deo - The words marked as surplus here are metrically inconsistent with + +

The surplus element may also be used to mark up interpolations, as in the + following example taken from a 13th century Italian source: a darmi morte, poi m'avete preso a + tradimentosì com' l'uccellator prende l'uccelloe lettere dintorno che diriano in questa + guisaPiù v'amo, dëa, che non faccio Deo The words marked as surplus here are metrically inconsistent with the rest and have been marked by the editor as such.

- -

In the case of an interpolation which the editor regards as genuine (i.e. written by +

In the case of an interpolation which the editor regards as genuine (i.e. written by the author in question), but out of its original place, the secl element should be used instead of surplus. For example: @@ -1614,8 +1105,7 @@ in the Eliot typescript mentioned above, there are --> several Bothe, meaning Bothe regarded this line as Plautine, but probably interpolated. It is easy to see how the line might have crept in as a gloss on the metaphor in the previous line.

- -

If some part of the source text is completely illegible or missing, an encoder may +

If some part of the source text is completely illegible or missing, an encoder may sometimes wish to supply new (conjectural) material to replace it. This conjectural reading is analogous to a correction in that it contains text provided by the encoder and not attested in the source. This is not however a correction, since no error is @@ -1634,34 +1124,28 @@ in the Eliot typescript mentioned above, there are --> several the missing reading. Both gap and supplied may be used in combination with unclear, damage, and other elements; for discussion, see section .

-
- -
- Hands and Responsibility -

This section discusses in more detail the representation of aspects of responsibility +

+
+ Hands and Responsibility +

This section discusses in more detail the representation of aspects of responsibility perceived or to be recorded for the writing of a primary source. These include points at which one scribe takes over from another, or at which ink, pen, or other characteristics of the writing change. A discussion of the usage of the hand, resp, and cert attributes is also included.

-
- Document Hands - -

For many text-critical purposes it is important to signal the person responsible (the +

+ Document Hands +

For many text-critical purposes it is important to signal the person responsible (the hand) for the writing of a whole document, a stretch of text within a document, or a particular feature within the document. A hand, as the name suggests, need not necessarily be identified with a particular known (or unknown) scribe or author; it may simply indicate a particular combination of writing features recognized within one or more documents. The examples given above of the use of the hand attribute with coding of additions and deletions illustrate this.

- -

The handNote element is used to provide information about each hand - distinguished within the encoded document. - - +

The handNote element is used to provide information about each hand + distinguished within the encoded document.

- -

A handNote element, with an identifier given by its xml:id +

A handNote element, with an identifier given by its xml:id attribute, may appear in either of two places in the TEI header, depending on which modules are included in a schema. When the transcr module defined by the present chapter is used, the element handNotes is @@ -1679,92 +1163,66 @@ in the Eliot typescript mentioned above, there are --> several summary describing all the hands discursively, while the handNotes element gives specific details of each. The choice will depend on individual encoders' priorities.

- -

As shown above, the hand attribute is available on several elements to +

As shown above, the hand attribute is available on several elements to indicate the hand in which the content of the element (usually a deletion or addition) is carried out. The handShift element may also be used within the body of a transcription to indicate where a change of hand is detected for whatever - reason. - - + reason.

-

A handShift element can be used to +

A handShift element can be used to indicate a change of hand even within an element with a hand attribute. The text following the handShift must be considered to be in the new hand.

-

Both handShift and handNote are members of the att.handFeatures class, and thus share the following attributes: - - +

Both handShift and handNote are members of the att.handFeatures class, and thus share the following attributes:

- -

A single hand may employ different writing styles and inks within a document, or may +

A single hand may employ different writing styles and inks within a document, or may change character. For example, the writing style might shift from anglicana to secretary, or the ink from blue to brown, or the character of the hand may change. Simple changes of this kind may be indicated by assigning a new value to the appropriate attribute within the handShift element. It is for the encoder to decide whether a change in these properties of the writing style is so marked as to require treatment as a distinct hand.

-

Where such a change is to be identified, the new attribute indicates the +

Where such a change is to be identified, the new attribute indicates the hand applicable to the material following the handShift. The sequence of such handShift elements will often, but not necessarily, correspond with the order in which the material was originally written. Where this is not the case, the facilities described in section may be found helpful.

- -

As might be expected, a single hand may also vary renditions within the same writing +

As might be expected, a single hand may also vary renditions within the same writing style, for example medieval scribes often indicate a structural division by emboldening all the words within a line. Such changes should be indicated by use of the rend attribute, in the same manner as underlining, emboldening, font shifts, etc. are represented in transcription of a printed text, rather than by introducing a new handShift element.

- -

In the following example there is a change of ink within a single hand. This is +

In the following example there is a change of ink within a single hand. This is simply indicated by a new value for the medium attribute on the - handShift element: When wolde the cat dwelle in his ynne - - And if the cattes skynne be slyk and + handShift element: When wolde the cat dwelle in his ynneAnd if the cattes skynne be slyk and gaye

- -

In the following example, the encoder has identified two distinct hands within the +

In the following example, the encoder has identified two distinct hands within the document and given them identifiers h1 and h2, by means of the - following declarations included in the document's TEI header: - - Carefully written - with regular descenders - Unschooled - scrawl - - + following declarations included in the document's TEI header: Carefully written + with regular descendersUnschooled + scrawl

-

Then the change of hand is indicated in the text: ... and that good Order Decency and regular worship may be once +

Then the change of hand is indicated in the text: ... and that good Order Decency and regular worship may be once more introduced and Established in this Parish according to the Rules and Ceremonies of the Church of England and as under a good Consciencious and sober Curate there would and ought to be and for that purpose the parishioners pray

- -

When a more precise or nuanced discussion of the writing in a manuscript is required, +

When a more precise or nuanced discussion of the writing in a manuscript is required, the handNote and scriptNote elements discussed in should be used. Either element may serve as the target for a handShift.

- -
- -
- Hand, Responsibility, and Certainty Attributes - -

The hand and resp attributes have similar, but not identical, +

+
+ Hand, Responsibility, and Certainty Attributes + +

The hand and resp attributes have similar, but not identical, meanings. Observe their distinctive uses in the following encoding of the William James passage mentioned above in section . In this example, the But inserted by James is tagged as an add, and the consequent editorial correction of One to - one treated separately: But - Oneone must have lived ... - - editorial changes - Fredson Bowers - - - authorial changes - William James - + one treated separately: ButOneone must have lived ... + editorial changesFredson Bowers + authorial changesWilliam James As in this example, hand should be reserved for indicating the hand of any form of marking—here, addition but also deletion, correction, annotation, underlining, etc.—within the primary text being transcribed. The scribal or authorial @@ -1772,7 +1230,7 @@ in the Eliot typescript mentioned above, there are --> several attribute. The value of the hand attribute should be a pointer to a hand identifiers typically declared in the document header but potentially in another document or repository (see section ).

-

The resp attribute, by contrast, indicates the person responsible for +

The resp attribute, by contrast, indicates the person responsible for deciding to mark up this part of the text with this particular element. In the case of the add element, for example, the resp attribute will indicate the responsibility for identifying that the addition is indeed an addition, and also @@ -1788,7 +1246,7 @@ in the Eliot typescript mentioned above, there are --> several fashion to indicate, for example, when an encoding decision is based on the work of a previous editor or on an article. In that case, the source would point to a bibl in the bibliography.

-

resp attribute signifies the person responsible for supplying the expansion and the cert attribute signifies the degree of editorial confidence felt in the expansion.

-

This close definition of the use of the resp and cert +

This close definition of the use of the resp and cert attributes with each element is intended to provide for the most frequent circumstances in which encoders might wish to make unambiguous statements regarding the responsibility for and certainty of aspects of their encoding. The @@ -1820,7 +1278,7 @@ attribute (sic, abbr, del, etc.). In all--> certainty concerning the content, attributes, and application of a particular element, the more general mechanisms for representing certainty and responsibility described in chapter should be used.

- -

It should be noted that the certainty and responsibility mechanisms described in +

It should be noted that the certainty and responsibility mechanisms described in chapter replicate all the functions of the resp and cert attributes on particular elements. For example, the encoding of Donaldson's conjectured emendation of wight to wright in line 117 of Chaucer's Wife of Bath's Prologue (see ) may be encoded as follows using the resp and cert attributes on the corr element: - - wightwright Exactly the same information could be conveyed - using the certainty and responsibility mechanisms, as follows: - wrightwight - - The choice of which + wightwright Exactly the same information could be conveyed + using the certainty and responsibility mechanisms, as follows: wrightwight The choice of which mechanism to use is left to the encoder. In transcriptions where only such statements of responsibility and certainty are made as can be accommodated within the resp and cert attributes of particular elements, it will be @@ -1856,100 +1310,76 @@ lead to unpredictable results.

elements. Where many statements of responsibility and certainty are made which cannot be so accommodated, it may be economical to use the respons and certainty elements throughout.

-

The above discussion supposes that in each case an encoder is able to specify exactly +

The above discussion supposes that in each case an encoder is able to specify exactly what it is that one wishes to state responsibility for and certainty about. Situations may arise when an encoder wishes to make a statement concerning certainty or responsibility but is unable or unwilling to specify so precisely the domain of the certainty or responsibility. In these cases, the note element may be used with the type attribute set to cert or resp and the content of the note giving a prose description of the state of affairs.

-
- -
- Damage and Conjecture -

The carrier medium of a primary source may often sustain physical damage which makes +

+
+ Damage and Conjecture +

The carrier medium of a primary source may often sustain physical damage which makes parts of it hard or impossible to read. In this section we discuss elements which may be used to represent such situations and give recommendations about how these should be used in conjunction with the other related elements introduced previously in this chapter.

- - -
- Damage, Illegibility, and Supplied Text -

The gap and supplied elements described above (section ) should be used with appropriate attributes where the degree of +

+ Damage, Illegibility, and Supplied Text +

The gap and supplied elements described above (section ) should be used with appropriate attributes where the degree of damage or illegibility in a text is such that nothing can be read and the text must be either omitted or supplied conjecturally or from one or more other sources. In many cases, however, despite damage or illegibility, the text may yet be read with - reasonable confidence. In these cases, the following elements should be used: - - - As members of the class att.damaged, these - elements bear the following attributes: - - The class att.damaged is a subclass of the + reasonable confidence. In these cases, the following elements should be used: As members of the class att.damaged, these + elements bear the following attributes: The class att.damaged is a subclass of the class att.dimensions, itself a subclass of the class att.ranging. Consequently these elements also - therefore bear at least the following attributes: - - - From the att.spanning class, - damageSpan inherits the following additional attribute: - - + therefore bear at least the following attributes: From the att.spanning class, + damageSpan inherits the following additional attribute:

-

The following examples all refer to the recto of folio 5 of the unique manuscript of +

The following examples all refer to the recto of folio 5 of the unique manuscript of the Elder Edda. Here, the manuscript of Vóluspá has been damaged through irregular rubbing so that letters in various places are obscured and in some cases cannot be read at all.

-

In the first line of this leaf, the transcriber may believe that the last three +

In the first line of this leaf, the transcriber may believe that the last three letters of daga can be read clearly despite the damage: um aldr daga yndisniota

-

If, as is often the case, the damage crosses structural divisions, so that the +

If, as is often the case, the damage crosses structural divisions, so that the damage element cannot be nested properly within the containing div elements, the damageSpan element may be used, in the same - way as the delSpan and addSpan elements discussed in section .

- - - -

-

[...]

-

[...] + way as the delSpan and addSpan elements discussed in section .

[...]

[...]

Note that in this example the spanTo element points to the next pb element rather than to an inserted anchor element, since it is the whole of the leaf (the text between the two pb elements) which has sustained damage. For other techniques of handling non-nesting information, see chapter .

-

If, as is also likely, the damage affects several disjoint parts of the text, each +

If, as is also likely, the damage affects several disjoint parts of the text, each such part must be marked with a separate damage or damageSpan element. To indicate that each of these is to be regarded as forming part of the same damaged area, the group attribute may be used as in the following example. In this (imaginary) text of Fitzgerald's translation from Omar Khayam, water damage - has affected an area covering parts of several lines: The Moving Finger wries; and having writ, - Moves on: nor all your Piety nor - Wit - Shall lure it back to - cancel half a Line, - Nor all your Tears wash out a Word of it - + has affected an area covering parts of several lines: The Moving Finger wries; and having writ,Moves on: nor all your Piety nor + WitShall lure it back to + cancel half a Line,Nor all your Tears wash out a Word of it

-

A more general solution to this problem is provided by the join element +

A more general solution to this problem is provided by the join element discussed in which may be used to link together arbitrary elements of any kind in the transcription. Here, several phenomena of illegibility and conjecture all result from a single cause: an area of damage to the text caused by rubbing at various points. The damage is not continuous, and affects the text at irregular points. In cases such as this, the join element may be used to indicate which tagged features are part of the same physical phenomenon.

- -

If the damage has been so severe as to render parts of the text only imperfectly +

If the damage has been so severe as to render parts of the text only imperfectly legible, the unclear element should be used to mark the fact. Returning to the Eddic example above, an encoder less confident in the daga reading might indicate this as follows: um aldr daga yndisniota

-

If it is desired to supply more information about the kind of damage, it is also +

If it is desired to supply more information about the kind of damage, it is also possible to nest an unclear element within the damage element: um aldr daga yndisniota

-

Alternatively, the transcriber may not feel able to read the last three letters of +

Alternatively, the transcriber may not feel able to read the last three letters of daga but may wish to supply them by conjecture. Note the use of the resp attribute to assign the conjecture to Finnur Jónsson: um aldr daga @@ -1957,21 +1387,16 @@ lead to unpredictable results.

a damage element: um aldr daga yndisniota The transcriber may also provide alternative conjectures by enclosing multiple supplied elements within a choice element.

-

Contrast the use of gap in the next line, where the transcriber believes +

Contrast the use of gap in the next line, where the transcriber believes that four letters cannot be read at all because of the damage: þar komr inn dimmi dreki fliugandi naþr frann neþan As with supplied, this gap might be enclosed by a damage element.

-

Where elements are nested in this way, information about agency, etc. is by default +

Where elements are nested in this way, information about agency, etc. is by default inherited. In the following imaginary example, there is a smoke-damaged part within which two stretches can be read with some difficulty, and a third stretch which - cannot be read at all: - and the proof of this is - - margin - - + cannot be read at all: and the proof of this ismargin

-

The above examples record imperfect legibility due to damage. When imperfect +

The above examples record imperfect legibility due to damage. When imperfect legibility is due to some other reason (typically because the handwriting is ill-formed), the unclear element should be used without any enclosing damage element. In Robert Southey's autograph of The Life of @@ -1981,43 +1406,38 @@ lead to unpredictable results.</p> from time to time invited in like manner his att<unclear>ention</unclear></egXML> The <att>cert</att> attribute on the <gi>unclear</gi> element may be used to indicate the level of editorial confidence in the reading contained within it.</p> - </div> - <div type="div3" xml:id="PHCOMB"> - <head>Use of the <gi>gap</gi>, <gi>del</gi>, <gi>damage</gi>, <gi>unclear</gi>, and + </div> + <div type="div3" xml:id="PHCOMB"> + <head>Use of the <gi>gap</gi>, <gi>del</gi>, <gi>damage</gi>, <gi>unclear</gi>, and <gi>supplied</gi> Elements in Combination</head> - <p>The <gi>gap</gi>, <gi>damage</gi>, <gi>unclear</gi>, <gi>supplied</gi>, and + <p>The <gi>gap</gi>, <gi>damage</gi>, <gi>unclear</gi>, <gi>supplied</gi>, and <gi>del</gi> elements may be closely allied in their use. For example, an area of damage in a primary source might be encoded with any one of the first four of these elements, depending on how far the damage has affected the readability of the text. Further, certain of the elements may nest within one another. The examples given in the last sections illustrate something of how these elements are to be distinguished - in use. This may be formulated as follows: <list rend="bulleted"> - <item>where the text has been rendered completely illegible by deletion or damage + in use. This may be formulated as follows: <list rend="bulleted"><item>where the text has been rendered completely illegible by deletion or damage and no text is supplied by the editor in place of what is lost: place an empty <gi>gap</gi> element at the point of deletion or damage. Note that the <gi>gap</gi> could be wrapped in a <gi>del</gi> or <gi>damage</gi> element. Use the <att>reason</att> attribute to state the cause (damage, deletion, etc.) of - the loss of text.</item> - <item>where the text has been rendered completely illegible by deletion or damage + the loss of text.</item><item>where the text has been rendered completely illegible by deletion or damage and text is supplied by the editor in place of what is lost: surround the text supplied at the point of deletion or damage with the <gi>supplied</gi> element. Use the <att>reason</att> attribute to state the cause (damage, deletion, etc.) - of the loss of text leading to the need to supply the text.</item> - <item>where the text has been rendered partly illegible by deletion or damage so + of the loss of text leading to the need to supply the text.</item><item>where the text has been rendered partly illegible by deletion or damage so that the text can be read but without perfect confidence: transcribe the text and surround it with the <gi>unclear</gi> element. Use the <att>reason</att> attribute to state the cause (damage, deletion, etc.) of the uncertainty in transcription and the <att>cert</att> attribute to indicate the confidence in - the transcription.</item> - <item>where there is deletion or damage but at least some of the text can be read + the transcription.</item><item>where there is deletion or damage but at least some of the text can be read with perfect confidence: transcribe the text and surround it with the <gi>del</gi> element (for deletion) or the <gi>damage</gi> element (for damage). Use appropriate attribute values to indicate the cause and type of deletion or damage. Observe that the <att>degree</att> attribute on the <gi>damage</gi> element permits the encoding to show that a letter, word, or phrase is not perfectly preserved, though it may be read with - confidence.</item> - <item>where there is an area of deletion or damage and parts of the text within + confidence.</item><item>where there is an area of deletion or damage and parts of the text within that area can be read with perfect confidence, other parts with less confidence, other parts not at all: in transcription, surround the whole area with the <gi>del</gi> element (for deletion; or the <gi>delSpan</gi> element @@ -2029,49 +1449,46 @@ lead to unpredictable results.</p> illegible and no text is supplied by the editor may be marked with the <gi>gap</gi> element. For each element, one may use appropriate attribute values to indicate the cause and type of deletion or damage and the certainty - of the reading.</item> - </list></p> - <p>The rules for combinations of the <gi>add</gi> and <gi>del</gi> elements, and for the + of the reading.</item></list></p> + <p>The rules for combinations of the <gi>add</gi> and <gi>del</gi> elements, and for the interpretation of such combinations, are similar: </p> - <list rend="bulleted"> - <item>if one <gi>add</gi> element (with identifier <ident>ADD1</ident>) contains + <list rend="bulleted"> + <item>if one <gi>add</gi> element (with identifier <ident>ADD1</ident>) contains another (with identifier <ident>ADD2</ident>), then the addition <ident>ADD1</ident> was first made to the text, and later a second addition (<ident>ADD2</ident>) was made within that added text: <egXML xmlns="http://www.tei-c.org/ns/Examples">This is the text <add xml:id="ADD1">with some added <add xml:id="ADD2">(interlinear!)</add> material</add> as written.</egXML></item> - <item>if one <gi>del</gi> element contains another, and the <att>seq</att> attribute + <item>if one <gi>del</gi> element contains another, and the <att>seq</att> attribute does not indicate otherwise, it should be assumed that the inner deletion was made before the enclosing one. In the following example, the word <mentioned>redundant</mentioned> was deleted before a second deletion removed the entire passage: <egXML xmlns="http://www.tei-c.org/ns/Examples"><del>This sentence contains some <del>redundant</del> unnecessary verbiage.</del></egXML></item> - <item>if a <gi>del</gi> element contains an <gi>add</gi> element, the normal + <item>if a <gi>del</gi> element contains an <gi>add</gi> element, the normal interpretation will be that an addition was made within a passage which was later deleted in its entirety: <egXML xmlns="http://www.tei-c.org/ns/Examples"><del>This sentence was deleted <add>originally</add> from the text.</del></egXML></item> - <item>if an <gi>add</gi> element contains a <gi>del</gi> element, the normal + <item>if an <gi>add</gi> element contains a <gi>del</gi> element, the normal interpretation will be that a deletion was made from a passage which had earlier been added: <egXML xmlns="http://www.tei-c.org/ns/Examples"><add>This sentence was added <del>eventually</del> to the text.</add></egXML></item> - <item>When some text has been blackened out so thoroughly that can no longer be read, + <item>When some text has been blackened out so thoroughly that can no longer be read, the encoding should be: <egXML xmlns="http://www.tei-c.org/ns/Examples">runs out the door in <gap extent="1 word"/> shirt</egXML></item> - <item>For consistency, one might prefer to encode the deletion as such, using <gi>del</gi>, + <item>For consistency, one might prefer to encode the deletion as such, using <gi>del</gi>, and containing a <gi>gap</gi>, as in the following example: <egXML xmlns="http://www.tei-c.org/ns/Examples">runs out the door in <del><gap extent="1 word"/></del> shirt</egXML></item> - <item>This is something that would be necessary if one wanted to encode a <gi>subst</gi> including an illegible deletion: + <item>This is something that would be necessary if one wanted to encode a <gi>subst</gi> including an illegible deletion: <egXML xmlns="http://www.tei-c.org/ns/Examples">sum<subst><del><gap extent="2 characters"/></del><add place="inline">mo</add></subst>ns</egXML></item> - <item>If some parts of the deleted text are readable, and other parts unreadable, it should be encoded as in the following example: + <item>If some parts of the deleted text are readable, and other parts unreadable, it should be encoded as in the following example: <egXML xmlns="http://www.tei-c.org/ns/Examples">Billy in The <del><gap extent="1 character"/>ng<gap extent="2 characters"/></del> Silver Dollar.. </egXML></item> - </list> - </div> + </list> </div> - - - <div xml:id="alterations"> - <head>Marking up the Writing Process</head> - <p>Modifications of various kinds (correction, addition, deletion, etc.) are frequently + </div> + <div xml:id="alterations"> + <head>Marking up the Writing Process</head> + <p>Modifications of various kinds (correction, addition, deletion, etc.) are frequently found within a single document, and may also be inferred when different documents are compared, although it may be an open question as to whether inter-document discrepancies <!-- at the @@ -2079,25 +1496,18 @@ lead to unpredictable results.</p> alterations. When two witnesses are collated, we may observe that a word present in one is missing from the other: this does not necessarily imply that the word was added to the first witness, nor that it was deleted from the other. </p> - - <p>In this section we discuss a number of elements which may be useful when attempting to + <p>In this section we discuss a number of elements which may be useful when attempting to record traces of the writing process within a document. </p> - - <div xml:id="PH-mod"> - <head>Generic Modification</head> - - - - <p>Most, if not all, transcriptional elements imply a certain level of semantic + <div xml:id="PH-mod"> + <head>Generic Modification</head> + <p>Most, if not all, transcriptional elements imply a certain level of semantic interpretation. For instance, using the <gi>add</gi> element to encode a word or phrase that occupies interlinear space involves a decision that it has been deliberately inserted as an addition rather than an alternative, and indeed a judgment that it was written after, rather than before, the other lines. Where it is felt desirable to keep the recording of <soCalled>what is on the page</soCalled> entirely separate from <soCalled>what is the editor’s interpretation</soCalled>, the - generic <gi>mod</gi> element may be preferred. <specList> - <specDesc key="mod"/> - </specList> This element simply indicates any kind of modification that has been + generic <gi>mod</gi> element may be preferred. <specList><specDesc key="mod"/></specList> This element simply indicates any kind of modification that has been identified in the document, without prejudice as to its function. Occurrences of the <gi>mod</gi> element may be categorized by means of their <att>type</att> attribute, and visual aspects of their appearance can be described by means of the @@ -2107,42 +1517,33 @@ lead to unpredictable results.</p> boundaries of some other XML element, for example from the middle of one line tagged as a <gi>line</gi> to the middle of another <gi>line</gi> some distance further on in the document. </p> - <egXML xmlns="http://www.tei-c.org/ns/Examples"> - <line>words words words <mod rend="wavy-underlining" spanTo="#enduw"/>words with wavy + <egXML xmlns="http://www.tei-c.org/ns/Examples"><line>words words words <mod rend="wavy-underlining" spanTo="#enduw"/>words with wavy underline</line> <!-- more lines here --> <line>wavy underlining finishes here<anchor xml:id="enduw"/> more words</line> </egXML> - <!-- QUERY real example needed --> - <!-- also more discussion of spanTo --> - - <p>The distinction between an example such as that above and the simple use of + <!-- QUERY real example needed --> + <!-- also more discussion of spanTo --> + <p>The distinction between an example such as that above and the simple use of <gi>hi</gi> to mark the visual salience of the underlining (apart from the use of the <att>spanTo</att> attribute) is that <gi>hi</gi> does not imply that the visual effect being recorded is understood to represent some kind of modification. </p> - </div> - - <div xml:id="PH-meta"> - <head>Metamarks</head> - - <p>By <term>metamark</term> we mean marks such as numbers, arrows, crosses, or other + </div> + <div xml:id="PH-meta"> + <head>Metamarks</head> + <p>By <term>metamark</term> we mean marks such as numbers, arrows, crosses, or other symbols introduced by the writer into a document expressly for the purpose of indicating how the text is to be read. Such marks thus constitute a kind of markup of - the document, rather than forming part of the text. <specList> - <specDesc key="metamark" atts="function target "/> - </specList> + the document, rather than forming part of the text. <specList><specDesc key="metamark" atts="function target "/></specList> </p> - - <p>Unlike marginal notes or other additions to the text, metamarks are used by the + <p>Unlike marginal notes or other additions to the text, metamarks are used by the writer to indicate a deliberate alteration of the writing itself, such as <q>move this passage over there</q>. An addition or annotation by contrast would typically concern some property of the passage other than its intended location or status within the text flow. A metamark may contain text, or some other graphic which the encoder wishes to represent, or it may simply consist of arrows, dots, lines etc. which the encoder simply describes.</p> - - <!-- QUERY should it contain <desc> as a child? --> - - <p>The <gi>metamark</gi> element carries a <att>function</att> attribute which specifies + <!-- QUERY should it contain <desc> as a child? --> + <p>The <gi>metamark</gi> element carries a <att>function</att> attribute which specifies the function of the metamark, using values such as <val>reorder</val>, <val>flag</val>, <val>delete</val>, <val>insert</val> or <val>used</val>. The passage to which the metamark applies may be indicated in either of two ways: the @@ -2152,44 +1553,27 @@ lead to unpredictable results.</p> latter case, the <gi>metamark</gi> itself must be supplied at the position in the document where the passage concerned begins; in the former case it may be supplied at any convenient point. Both attributes should not be supplied. </p> - - <p>The following example is taken from an 15th century legal book from the city of - Göttingen, containing regulations of everyday life issued by the city council <figure> - <graphic url="Images/ka04_1v-dtl.jpg" width="70%"/> - <head><title>Kundige bok 2, fol 1v. - +

The following example is taken from an 15th century legal book from the city of + Göttingen, containing regulations of everyday life issued by the city council

Kundige bok 2, fol 1v.

- - -

In the second paragraph, the word lege ("read") +

In the second paragraph, the word lege ("read") was written in the left hand margin, next to the sentence beginning Ock en schullen de bruwere.... It is thought to function as a metamark, indicating that this sentence forms part of the regulations. A further sentence was then added, while at some later stage the text and also the metamark were deleted. We might - encode this as follows as an embedded transcription (keeping in mind that the elements described here can also be used within text): - - lege - Ock en schullen de bruwere des hilgen dages - nicht over setten noch uppe den stillen fridach bruwen. - - Noch nymande over setten, se en sehin denne erst, dat uppe den bonen neyn + encode this as follows as an embedded transcription (keeping in mind that the elements described here can also be used within text): legeOck en schullen de bruwere des hilgen dages + nicht over setten noch uppe den stillen fridach bruwen.Noch nymande over setten, se en sehin denne erst, dat uppe den bonen neyn stro noch, huw noch flaß ligghe, by pine eyner halven roden, deme bruwere so - wol alse dem bruwheren to murende. - - + wol alse dem bruwheren to murende.

-

The change attribute used here to indicate the sequencing of these various +

The change attribute used here to indicate the sequencing of these various interventions is discussed below, in section . The elements addSpan and delSpan are discussed in section .

- -

The metamark element may also be used to encode the symbols etc. often found - in marked-up proofs such as the following, taken from the Walt Whitman archive:

- - From a corrected proof of Miracles (Walt Whitman - Archive) -

- -

In this example, the whole of what was originally the 14th section of the poem has +

The metamark element may also be used to encode the symbols etc. often found + in marked-up proofs such as the following, taken from the Walt Whitman archive:

From a corrected proof of Miracles (Walt Whitman + Archive)

+ +

In this example, the whole of what was originally the 14th section of the poem has been marked for deletion, both by horizontal and vertical lines, and by the proofreading mark resembling the deleatur or dele deletion symbol to left and right of the section. The deletion itself might be encoded by using the normal del or delSpan @@ -2197,36 +1581,36 @@ lead to unpredictable results.

different case from that of the next example, in which the writer does not intend to suppress the content, but only to mark that it has been copied to another manuscript or reused.

-

-

- - From "I am that halfgrown angry boy" (MS q 25), David M. Rubenstein Rare +

+

+ + From "I am that halfgrown angry boy" (MS q 25), David M. Rubenstein Rare Book & Manuscript Library, Duke University. -
-

-

This page contains internal deletions, additions, and retracings but these are +

+

+

This page contains internal deletions, additions, and retracings but these are semantically quite different from the apparent deletion signalled by the larger of the two single vertical lines, which shows that the written material has been transferred or re-used, not deleted.

- - - - - I am that halfgrown angry boy, fallen asleep - The tears of foolish passion yet undried - upon my cheeks. - - I pass through the travels and fortunes of + + + + + I am that halfgrown angry boy, fallen asleep + The tears of foolish passion yet undried + upon my cheeks. + + I pass through the travels and fortunes of thirty - years and become old, - Each in its due order comes and goes, - And thus a message for me comes. - The - - Entered - Yes - - -

In this embedded transcription example, we class as metamarks both the long vertical line and the annotation + years and become old, + Each in its due order comes and goes, + And thus a message for me comes. + The + + Entered - Yes + + +

In this embedded transcription example, we class as metamarks both the long vertical line and the annotation Entered - yes. Both metamarks are assumed to indicate that the whole of the written zone with identifier X2 is marked as having been used. metamark can be similarly used within text to encode the same phenomenon as part of a transcription that privileges logical over physical and layout structures.

- -
- -
- Fixation and Clarification - -

A writer may sometimes rewrite material a second time without significant change and +

+
+ Fixation and Clarification +

A writer may sometimes rewrite material a second time without significant change and in the same place. We consider this a distinct activity from addition as usually defined because no new textual material results; instead the status of existing material is reaffirmed. We may distinguish two variants of this: @@ -2251,47 +1632,31 @@ has identifier z2. --> subsequently reaffirmed, for example by inking it over; and clarification, where the first version was badly written and has been rewritten for clarity. The element retrace is provided for both cases; its - cause attribute may be used to distinguish these or other cases. - - + cause attribute may be used to distinguish these or other cases.

- -

In this simple example, taken from the papers of Henrik Ibsen, the writer wrote the +

In this simple example, taken from the papers of Henrik Ibsen, the writer wrote the word skuldren hastily, and then returned to it to make the - letter l larger and clearer:

- - From autograph ms of Peer Gynt, Collin 2869, 4°, - I.1.1, the Royal Library of Copenhagen -
We might transcribe this word as follows: + letter l larger and clearer:
From autograph ms of Peer Gynt, Collin 2869, 4°, + I.1.1, the Royal Library of Copenhagen
We might transcribe this word as follows: Skuldren

- -

A single rewrite may not be sufficient, and it may be that the document becomes +

A single rewrite may not be sufficient, and it may be that the document becomes almost unreadable as a result of repeated clarification. In the following example, we can distinguish at least three attempts to write the letters - er in the word bægerklang:

- - Detail from autograph ms Brand in The Royal - Library, Denmark (KBK Collin 262) - -
We might encode this by nesting the retrace element as follows: + er in the word bægerklang:
Detail from autograph ms Brand in The Royal + Library, Denmark (KBK Collin 262)
We might encode this by nesting the retrace element as follows: - ved Bæg - er - ... + ved Bæger ... The change attribute used here is discussed further below ().

- -

The retrace element is used only for cases where text has been written +

The retrace element is used only for cases where text has been written multiple times. When metamarks and other markup-like strokes have been rewritten multiple times, the redo element described in the next section should be used in preference.

-
- -
- Confirmation, Cancellation, and Reinstatement of Modifications - -

A writer may indicate that an alteration is itself to be altered: for example, a struck-through passage may be restored via a dotted underlining, or the underlining of a passage may be deleted by a wavy line.

- -

The following elements are provided to represent these situations: - - - +

The following elements are provided to represent these situations:

- - Wenn ihr nur piepſet iſt die Welt ſchon matt. --> - - - -

The element restore () is provided for the +

The element restore () is provided for the comparatively simple case where a simple deletion is marked as having been subsequently cancelled. The undo element discussed here is more widely applicable and may be used for any kind of cancellation. It points to the element or @@ -2329,31 +1686,19 @@ has identifier z2. --> requires a distinct undo element, however. Either of the attributes target or spanTo may be used to indicate the passages concerned.

- -

Consider the following imaginary example:

- - Imaginary example demonstrating restoring and undoing -
We hypothesize that the text has gone through three states or changes, as - follows: - This is just some sample text, we need a real example. - This is not a real example. - This is just some text, not a real example. - +

Consider the following imaginary example:

Imaginary example demonstrating restoring and undoing
We hypothesize that the text has gone through three states or changes, as + follows: This is just some sample text, we need a real example. This is not a real example.This is just some text, not a real example.

- -

This sequence of events might be encoded as follows: - This is - just some sample text, we need +

This sequence of events might be encoded as follows: + This is just some sample text, we need not a real example. using two undo elements, each with a spanTo attribute, to delimit the two parts of the deletion which were reverted at change s3. Note that in this case, since target is not supplied, it is the effect of the parent element (the del) which is assumed to be undone.

- -

Alternatively, we might more economically use the generic seg element to delimit the two sequences whose deletion is being reverted, and +

Alternatively, we might more economically use the generic seg element to delimit the two sequences whose deletion is being reverted, and then use the target attribute on a single undo element: - This is - just some sample text, we + This is just some sample text, we need not a real example. @@ -2361,103 +1706,68 @@ has identifier z2. -->

-
- -
- Transpositions - -

A transposition occurs when metamarks are found in a document indicating +

+
+ Transpositions +

A transposition occurs when metamarks are found in a document indicating that passages should be moved to a different position. Typically this may be done using arrows, asterisks or numbers, or other means. By definition the result of a transposition is not present in the document, and should not therefore be encoded, if the intention is to represent the actual appearance of the document. Instead, the - following elements may be used to indicate the intended reordering: - - -

-

Consider for example, the following extract from an Ibsen manuscript

- - Extract from autograph Digte (Poems) NBO Ms. 4º 1110a -
The underlined numbers 1 and 2 here indicate that, although the word + following elements may be used to indicate the intended reordering:

+

Consider for example, the following extract from an Ibsen manuscript

Extract from autograph Digte (Poems) NBO Ms. 4º 1110a
The underlined numbers 1 and 2 here indicate that, although the word bör precedes the word hör in the text, the order of the two words should be reversed. We may encode this as follows: - - bör2. og hör1. + bör2. og hör1. - - - - - - +

- -

Note the use of the generic seg element to identify the sections of text - being transposed. The following example uses an embedded transcription approach, which typically identifies lines of writing with the line element. This makes it trivial to refer to the transposed line, but when encoding transposition within text the encoder will need to find a way to identify the line with another element, such as seg.

- - Detail from autograph ms of Den episke Brand (KBK Collin - 2869) -
- - 2.) thi da er du med Himmelen i Pagt; — - - 1.) da kan du - Folkets Jøkelhjerter tine; - - - - - - - - When transposition is made, the whole element indicated is understood to be +

Note the use of the generic seg element to identify the sections of text + being transposed. The following example uses an embedded transcription approach, which typically identifies lines of writing with the line element. This makes it trivial to refer to the transposed line, but when encoding transposition within text the encoder will need to find a way to identify the line with another element, such as seg.

Detail from autograph ms of Den episke Brand (KBK Collin + 2869)
+ 2.) thi da er du med Himmelen i Pagt; — 1.) da kan du + Folkets Jøkelhjerter tine; When transposition is made, the whole element indicated is understood to be moved, not just its contents. In the above example, the metamarks are thus understood to be moved along with the lines to which they apply.

- - - -

One or more listTranspose elements may be +

One or more listTranspose elements may be supplied either embedded within the text, in the profileDesc of the header, or in a standOff depending on local preference. Each listTranspose can contain one or more transpose elements, each of which defines a single transposition.

-
- -
- Alternative Readings -

- - Detail from autograph manuscript of the second version of Lalla - Rookh, Pierpont Morgan MA 310 -
In this example two alternative readings are provided, but no preference is +
+
+ Alternative Readings +

Detail from autograph manuscript of the second version of Lalla + Rookh, Pierpont Morgan MA 310
In this example two alternative readings are provided, but no preference is indicated. While the author apparently first composed the line Alone before his native river -, at some later point, he entertained the possibility of using the word beside instead of before. The manuscript supplies no indication of which word Moore favours at this point, although in fact, in the first printed edition of Lalla Rookh the word beside was chosen.

-

The element alt provided by the linking module +

The element alt provided by the linking module gives a simple way of encoding the state of this manuscript, as follows: Alone before beside his native river ­—

-

The mode attribute here indicates that the two possible readings indicated +

The mode attribute here indicates that the two possible readings indicated by the target attribute are mutually exclusive. The weights attribute indicates the relative importance or preference to be attached to the two readings on a scale running from zero (most improbable) to one (most probable). In this case, we have a very strong preference for the second reading because this is the one that appears in the published version of the poem. The alt element is further discussed in section .

-
- - + - -
- Instant Corrections -

The use of elements such as del and add necessarily implies that +

+ Instant Corrections +

The use of elements such as del and add necessarily implies that the modifications they indicate were made at some time after the original writing. An exception to this is where a false start or instant correction has been identified: the author starts to write, and then immediately corrects what has been written.

-

The instant attribute defined by this module may be used on any element +

The instant attribute defined by this module may be used on any element which is a member of the att.editLike class to modify this default assumption. When the value of instant is set to true, the addition or deletion is considered to belong to the same change as its parent element, while false means some change later than that of its parent.

-

An example of false start or instant correction can be seen in the following line: -

- - Detail fron [I am a curse], one of the drafts for Whitman's - Song of Myself -
in which we can detect the following sequence of events: - The letter T is written and then immediately deleted - The word The is written, deleted, and replaced by the word - His - The added word His is then deleted - The initial letter i of the words iron - necklace is overwritten with a capital I - To indicate that the first of these acts must have taken place during the +

An example of false start or instant correction can be seen in the following line: +

Detail fron [I am a curse], one of the drafts for Whitman's + Song of Myself
in which we can detect the following sequence of events: The letter T is written and then immediately deletedThe word The is written, deleted, and replaced by the word + HisThe added word His is then deletedThe initial letter i of the words iron + necklace is overwritten with a capital I To indicate that the first of these acts must have taken place during the main act of writing, before the other deletion and additions, we might encode this - revision campaign as follows: - T - - The - - His - - - - i - I - ron necklace + revision campaign as follows: TTheHisiIron necklace

-
-
- -
- Aspects of Layout -

The following methods are available to capture general aspects of the layout of material on +

+
+
+ Aspects of Layout +

The following methods are available to capture general aspects of the layout of material on a page where this is considered important. Within the sourceDoc element, as already indicated, the element surface and surfaceGrp enable the encoder to represent directly the structure of a codex as gatherings or quires, leaves, and - surfaces, as in the following example: - - - - - - - - - - - - - - - - - - - - -

-

In some cases, it may be preferable to define surfaces corresponding with each two + surfaces, as in the following example:

+

In some cases, it may be preferable to define surfaces corresponding with each two page opening, for example where it is clear that the writer regarded each such opening as a single writing surface, with written zones or other features crossing the page divide. An - example is shown here:

- - Opening from autograph ms of Proust's A la recherche du temps perdu - (f 42v-43r) -
+ example is shown here:
Opening from autograph ms of Proust's A la recherche du temps perdu + (f 42v-43r)

-

The coloured lines added to this image indicate a number of zones of writing, colour coded +

The coloured lines added to this image indicate a number of zones of writing, colour coded to indicate the order in which they were written (purple, then green, then red). For example, the zone marked in red on the left contains a note referring to the purple zone on the right.

- -

This approach assumes that the transcription will primarily be organized in the same way as +

This approach assumes that the transcription will primarily be organized in the same way as the physical layout of the source, using embedded transcription elements. Alternatively, where the a non-embedded transcription has been provided, using the text element, it is still possible to record gathering breaks, page breaks, column breaks, line breaks etc in the source, using the elements described in section . Detailed metadata about the physical make-up of a source will usually be summarized by the physDesc component of an msDesc element discussed in .

- -
- Space -

The author or scribe may have left space for a word, or for an initial capital, and for +

+ Space +

The author or scribe may have left space for a word, or for an initial capital, and for some reason the word or capital was never supplied and the space left empty. The presence of significant space in the text being transcribed may be indicated by the - space element. - - Note that this element should not be used to mark normal inter-word space or + space element. Note that this element should not be used to mark normal inter-word space or the like.

-

In line 694 of Chaucer's Wife of Bath's Prologue in the Holkham +

In line 694 of Chaucer's Wife of Bath's Prologue in the Holkham manuscript the scribe has left a space for a word where other manuscripts read preestes: By god if wommen had writen storyes As han within her @@ -2603,10 +1865,10 @@ referring to the zone marked in purple on the right by the value of the reason attribute. The source of the supplied text is shown by the value of the source attribute as the Hengwrt manuscript; the transcriber responsible for supplying the text is ES.

-
-
- Lines -

One of the more common forms of modification encountered in written documents of any +

+
+ Lines +

One of the more common forms of modification encountered in written documents of any kind is the presence of lines written under, beside, or through the text. Such lines may be of various types: they may be solid, dashed or dotted, doubled or tripled, wavy or straight, or a combination of these and other renderings. The line may be used for @@ -2620,14 +1882,14 @@ referring to the zone marked in purple on the right strike-through of my in the autograph of Eloi, Eloi, lama sabachthani may be encoded: For I hate this my body, which is so dear to me

-

There will be instances, however, where a scholar wishes only to register the occurrence +

There will be instances, however, where a scholar wishes only to register the occurrence of lines in the text, without making any judgement as to what the lines signify. In these cases the hi element may be used, with the rend attribute to mark the style of line. In the manuscript of a letter by Robert Browning to George Moulton-Barrett the underlining of the phrase had obtained all the letters to Mr Boyd may be marked-up as follows: I have once — by declaring I would prosecute by law — hindered a man's proceedings who had obtained all the letters to Mr Boyd

-

The above examples presume the common case where a single word or phrase is marked by a +

The above examples presume the common case where a single word or phrase is marked by a line, with no doubt as to where the marking begins or ends and with no overlapping of the area of text with other marked areas of text. Where there is doubt, the certainty element may be used to record the doubt. In the Browning example @@ -2636,17 +1898,15 @@ referring to the zone marked in purple on the right by law — hindered a man's proceedings who had obtained all the letters to Mr Boyd - - may begin with previous word -

-

Where the area of text marked overlaps other areas of text, for example crossing a + may begin with previous word

+

Where the area of text marked overlaps other areas of text, for example crossing a structural division, one of the spanning mechanisms mentioned above must be used; for example where the line is thought to mark a deletion, the delSpan element may be used. Where it is desired simply to record the marking of a span of text in circumstances where it is not possible to surround the text with a hi element, the span element may be used with the rend or type attribute indicating the style of line-marking.

-

More work needs to be done on clarifying the treatment of other textual features marked +

More work needs to be done on clarifying the treatment of other textual features marked by lines which might so overlap or nest. For example, in many Middle English manuscripts (e.g. the Jesus and Digby verse collections), marginal sidebars may indicate metrical structure: couplets may be linked in pairs, with the pairs themselves linked into @@ -2654,7 +1914,7 @@ referring to the zone marked in purple on the right on which there is some annotation: in many manuscripts of Chaucer's Wife of Bath's Prologue lines 655–8 are marked with nesting parentheses against which the scribe has written nota.

-

Such features could be captured by use of the note element, containing a prose +

Such features could be captured by use of the note element, containing a prose description of the manuscript at this point, enhanced by a link to a visual representation (or facsimile) of the feature in question. For example, in the Chaucer example just cited, one may wish to record that the nota is @@ -2666,14 +1926,11 @@ referring to the zone marked in purple on the right nota points both at all four lines and at two pairs of lines within the four lines. The metamark element discussed in section above provides better facilities for this kind of complex annotation.

-
-
- - -
- Transcription and Ruby - -

These Guidelines also provide special elements to support the +

+
+
+ Transcription and Ruby +

These Guidelines also provide special elements to support the encoding of ruby annotations, which are common in East Asian textual traditions. These elements provide a method of capturing a specific type of annotation, in addition to the generic methods like the @@ -2683,53 +1940,37 @@ referring to the zone marked in purple on the right be captured in conjunction with ruby base text and annotations. See for more information about these elements.

-
- -
- Headers, Footers, and Similar Matter - -

Such information as page numbers, signatures, or catchwords may be recorded in a +

+
+ Headers, Footers, and Similar Matter +

Such information as page numbers, signatures, or catchwords may be recorded in a specialized fw element provided for that purpose. Although the name derives from the term forme work, used in description of early printed documents (the forme being the block used to hold movable type), the fw element may be used for such features of any document, written or printed. Note that the purpose of this element is to record page numbers etc. actually present in the document being encoded, not necessarily to provide a complete or accurate pagination of it.

-

Information about pagination etc. may also be provided using the n attribute of +

Information about pagination etc. may also be provided using the n attribute of the pb or gb elements, or by other appropriate milestone elements, as further discussed in section : since this information is usually provided by the encoder, it is not subject to the constraint that it should be present only if textually present in the source being encoded. In text-critical situations it may be useful to provide both a normalized version of the pagination and a representation of the catch-word or numbering, especially when the latter presents a - variant reading, or is significant for compositor identification. - - The fw element may be used to encode any of the unchanging portions of - a page forme, such as: - running heads (whether repeated or changing on every page, or alternating - pages) - running footers - page numbers - catch-words - other material repeated from page to page, which falls outside the stream of the - text - It should not be used for marginal glosses, annotations, or textual variants, which + variant reading, or is significant for compositor identification. The fw element may be used to encode any of the unchanging portions of + a page forme, such as: running heads (whether repeated or changing on every page, or alternating + pages)running footerspage numberscatch-wordsother material repeated from page to page, which falls outside the stream of the + text It should not be used for marginal glosses, annotations, or textual variants, which should be tagged using gloss, note, or the text-critical tags described in chapter , respectively.

-

For example: Poëms. - 29 - E3 - TEMPLE +

For example: Poëms.29E3TEMPLE

-
- - - -
- Identifying Changes and Revisions -

A major purpose of genetic editing is the identification of revision +

+
+ Identifying Changes and Revisions +

A major purpose of genetic editing is the identification of revision campaigns or, more generally, changes. An editor may wish to regard a particular set of alterations (deletions, additions, substitutions, transpositions, etc.) or any other act of writing as a single object for which we use the general term change, to indicate both that one or more of such @@ -2737,37 +1978,29 @@ referring to the zone marked in purple on the right way, for example that one is a consequence of the other. They might also wish to group together certain revisions, regardless of when they might have occurred, based on a variety of other shared characteristics (e.g., corrections of factual errors or revisions that - incorporate suggestions made by a given reader). To document this we need: - a system to assign phenomena to a particular change as defined above - a way to characterize each such change, in itself and in relation to others. -

- -

The element creation (within the TEI header profile description) contains all + incorporate suggestions made by a given reader). To document this we need: a system to assign phenomena to a particular change as defined abovea way to characterize each such change, in itself and in relation to others.

+

The element creation (within the TEI header profile description) contains all information relating to the genesis or production of a text. It may contain a listChange element which contains a number of change elements, one for - each set of alterations identified: - - - + each set of alterations identified:

- -

In the following example an editor has identified four distinct sets of alterations:

- - - - - First stage, written in ink - Second stage, with revisions written in the author's hand +

In the following example an editor has identified four distinct sets of alterations:

+ + + + + First stage, written in ink + Second stage, with revisions written in the author's hand using pencil - Fixation of the pencilled revisions together with further + Fixation of the pencilled revisions together with further revisions in the author's hand using ink - Additions in a different hand, probably at a later + Additions in a different hand, probably at a later stage - - - - -

The listChange element carries an attribute ordered, which can take the + + + + +

The listChange element carries an attribute ordered, which can take the values true or false (the default). The attribute specifies whether the order of child elements signifies a temporal order for the revision campaigns which they document. In the example above, the editor has asserted that the four sets @@ -2786,68 +2019,67 @@ referring to the zone marked in purple on the right step-by-step, starting with change elements of smaller coverage, whose members are certainly related, and then in a subsequent pass grouping these in turn, thereby extending their reach.

- - - - - - An unrelated change note - - Alterations on one manuscript page, certainly + + + + + An unrelated change note + + Alterations on one manuscript page, certainly related - Alterations on another manuscript page, certainly + Alterations on another manuscript page, certainly related - - Another unrelated change note - - - - -

A nested listChange element is also useful to indicate a partial + + Another unrelated change note + + + + +

A nested listChange element is also useful to indicate a partial ordering of change elements.

- - - The first stage - - - A revision of the first stage - Another revision of the first stage - - The last stage - - -

In addition to the possibility of being ordered by their sequence within + A revision of the first stage + Another revision of the first stage + + The last stage + + +

In addition to the possibility of being ordered by their sequence within a listChange element, change elements may carry a number of attributes from the att.datable class (period, when, notBefore, notAfter, from, and to) which allow each element to be dated as exactly or inexactly as necessary, in the same way as is currently possible for the TEI date element.

- - - - - - - The first draft of + + + + + + + The first draft of Persuasion, completed by the date July 16 1816 which is written after the word Finis at page 30. - After the 16th of July + After the 16th of July Austen starts revision of the two final chapters, by rewriting the end and adding a new zone (pages 32-35) to be inserted at page 19. This stage is documented by the deletion of the date (July 16 1816) at page 30, and the addition of more text and of a new date (July 18. 1816) at page 31 - Before publication, after July 18th, + Before publication, after July 18th, 1816 chapters 10-11 were broken into three chapters, 10, 11, 12, as witnessed by the print. - - - - -

Each change element, apart from declaring a distinct moment or phase in the creation of the + + + + +

Each change element, apart from declaring a distinct moment or phase in the creation of the document, may also contain references to other annotations contained within the teiHeader or in the document (as shown in the previous example). Such references, along with the textual content, are purely documentary - in the second stage and is repeated or fixed in the third. Also the substitution in the second line is done repeatedly: initially it takes place in the second stage, but is fixated as a whole in the third.

--> -

The interpretation of change elements with respect to a particular text passage is based on a number +

The interpretation of change elements with respect to a particular text passage is based on a number of implicit assumptions and constraints which have the effect of minimizing the amount of tagging necessary. The system is also flexible enough to support an explicit distinction between acts of writing and textual alterations, since either of these can be associated with changes described in the encoding. The following example shows an encoding in which the same passage is transcribed twice, once from a documentary perspective, and once from a - textual one: - - - - First stage, written in ink by a - scribe - Revised by Goethe using pencil - Fixation of the revised passages and further revisions by Goethe using - ink - - - - - - - - - Nun - - Ihr wanſtige Schuften mit den Feuerbacken - - - feiſt - - Ihr glüht ſo recht vom Höllen Schwefel ſatt. [...] - - - - - - - Ihr - Nun - wanſtige Schuften mit den Feuerbacken - Ihr glüht ſo recht vom Höllen Schwefel - ſatt - feiſt - . - - - + textual one: First stage, written in ink by a + scribeRevised by Goethe using pencilFixation of the revised passages and further revisions by Goethe using + inkNunIhr wanſtige Schuften mit den FeuerbackenfeiſtIhr glüht ſo recht vom Höllen Schwefel ſatt. [...] IhrNun wanſtige Schuften mit den FeuerbackenIhr glüht ſo recht vom Höllen Schwefel ſattfeiſt.

- -

The documentary transcription stresses the writing process, while the textual transcription +

The documentary transcription stresses the writing process, while the textual transcription emphasizes textual alterations. In either case, the change of writing activity associated with a particular feature in the transcript is explicitly indicated. From the documentary perspective, by assigning particular modifications to a specific change element, we describe the @@ -3000,13 +2185,10 @@ following ...--> the merit of not confusing the presentation of the interventions concerned with writing sequence information, at the price of requiring a distinct identifier on each intervention.-->

-
- - - -
- Other Primary Source Features not Covered in these Guidelines -

We repeat the advice given at the beginning of this chapter, that these recommendations are +

+
+ Other Primary Source Features not Covered in these Guidelines +

We repeat the advice given at the beginning of this chapter, that these recommendations are not intended to meet every transcriptional circumstance ever likely to be faced by any scholar. They are intended rather as a base to enable encoding of the most common phenomena found in the course of scholarly transcription of primary source materials. These @@ -3015,50 +2197,41 @@ following ...--> organisation of the carrier materials themselves (as quiring, collation, etc.), and authorial instructions or scribal markup, except insofar as these are involved in the broader question of manuscript description, as addressed by the msdescription module described in chapter .

-
- -
- Module for Transcription of Primary Sources -

The module described in this chapter makes available the following components: - - Transcription of Primary Sources - Transcription of primary sources - 原文轉錄 - Représentation de sources primaires - Trascrizione di fonti primarie - Transcrição de fontes primárias - 転記モジュール - +

+
+ Module for Transcription of Primary Sources +

The module described in this chapter makes available the following components: + Transcription of Primary SourcesTranscription of primary sources原文轉錄Représentation de sources primairesTrascrizione di fonti primarieTranscrição de fontes primárias転記モジュール The selection and combination of modules to form a TEI schema is described in .

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
diff --git a/P5/Source/Guidelines/en/PrefatoryNote.xml b/P5/Source/Guidelines/en/PrefatoryNote.xml index c0c541c781..7075dce917 100644 --- a/P5/Source/Guidelines/en/PrefatoryNote.xml +++ b/P5/Source/Guidelines/en/PrefatoryNote.xml @@ -1,45 +1,32 @@ - - - + - -
Prefatory Notes -

This Appendix contains (in reverse chronological +

+ Prefatory Notes +

This Appendix contains (in reverse chronological order) the Introductory Notes prefixed to each revision of the TEI Guidelines since its first publication in 1994.

- -
Prefatory Note (March 2002) -

The primary goal of this revision has been to make available a new +

+ Prefatory Note (March 2002) +

The primary goal of this revision has been to make available a new and corrected version of the TEI Guidelines which: - -is expressed in XML and conforms to a TEI-conformant XML - DTD; -generates a set of DTD fragments that can be combined +is expressed in XML and conforms to a TEI-conformant XML + DTD;generates a set of DTD fragments that can be combined together to form either SGML or XML document type - definitions; - corrects blatant errors, typographical mishaps, and other - egregious editorial oversights; -can be processed and maintained using readily available XML + definitions;corrects blatant errors, typographical mishaps, and other + egregious editorial oversights;can be processed and maintained using readily available XML tools instead of the special-purpose ad hoc software originally - used for TEI P3. - + used for TEI P3.

-

A second major design goal of this revision has been to ensure that the +

A second major design goal of this revision has been to ensure that the DTD fragments generated would not break existing documents: in other words, that any document conforming to the original TEI P3 SGML DTD would also conform to the new XML version of it. Although full backwards compatibility cannot be guaranteed, we believe our implementation is consistent with that goal.

-

In most respects, the TEI Guidelines have stood the test of time remarkably +

In most respects, the TEI Guidelines have stood the test of time remarkably well. The present edition makes no substantial attempt to rewrite those few parts of them which have now been rendered obsolete by changes since their first publication, though an indication is given in the text of where such rewriting is @@ -50,7 +37,7 @@ these tasks require the existence of an informed and active TEI Council to direct and validate such extension and maintenance work, in response to the changing needs and priorities of the TEI user community.

-

Two exceptions to the above principles may be cited: firstly, the +

Two exceptions to the above principles may be cited: firstly, the chapter which originally provided a Gentle Introduction to SGML has been completely rewritten to provide a similarly gentle introduction to XML; secondly the chapter @@ -59,43 +46,41 @@ close connexion between Unicode and XML. The editors gratefully acknowledge the assistance of the ad hoc workgroup chaired by Christian Wittern, which undertook to provide expert advice and correction at very short notice, in the latter task.

-

The preparation of this new version relied extensively on +

The preparation of this new version relied extensively on preliminary work carried out by the former North American editor of the TEI Guidelines, C.M. Sperberg-McQueen. In a TEI working paper written in 1999TEI ED W69, available from the TEI web site at . he sketched out a precise blueprint for the conversion of the TEI from SGML to XML, which we have implemented, with only slight modification.

-

The Editors would also like to express thanks to the +

The Editors would also like to express thanks to the team of volunteers from the TEI community who helped us with the task of proofreading the first draft during the summer of 2001; and to Sebastian Rahtz of Oxford University Computing Services, without whose skill and enthusiasm this new edition would not have been possible.

-

A substantial proportion of the work of preparing this new edition was +

A substantial proportion of the work of preparing this new edition was funded with the assistance of a grant from the US National Endowment for the Humanities, whose continued support of the TEI has also been crucial to the effort of setting up the TEI Consortium.

-

Finally, we would like to thank all our colleagues on the interim +

Finally, we would like to thank all our colleagues on the interim management board of the TEI Consortium, in particular its Chairman John Unsworth, for their continued support of the TEI's work, and their willingness to devote effort to the difficult task of overseeing its transition to a new organizational infrastructure.

-

Summary details of the changes made in the present and previous +

Summary details of the changes made in the present and previous editions are given in their Prefatory Notes, all of which are now reproduced in an Appendix to the present edition: see .

-Lou Burnard and Syd Bauman (TEI Editors) + Lou Burnard and Syd Bauman (TEI Editors) Oxford and Providence, March 2002. -
- - - -
Introductory Note (November 2001) -

To complete the work started in June of this year, the TEI Editors +

+
+ Introductory Note (November 2001) +

To complete the work started in June of this year, the TEI Editors asked for volunteers from the TEI community to proofread the preliminary XML version. 24 volunteers responded to this call during August, and gave invaluable help both by identifying a number of previously un-noticed errors, and by suggesting areas in @@ -103,7 +88,7 @@ which more substantial revision should be undertaken in the future. The Editors gratefully acknowledge the assistance of the following individuals during this exercise:

-

+

Jimmy Adair, Syd Bauman, Michael Beddow, @@ -130,60 +115,52 @@ Elisabeth Solopova, Christian Wittern, Martin Wynne.

-

In addition to error correction, and clear delineation of those sections in +

In addition to error correction, and clear delineation of those sections in which substantial revision is yet to be undertaken for TEI P5, the present draft differs from earlier ones in the following respects: - -Formal Public Identifiers have been introduced as a means of +Formal Public Identifiers have been introduced as a means of constructing TEI DTDs and an SGML Open Catalog is now included with the -standard release; -Some systematic errors and omissions in the reference section +standard release; Some systematic errors and omissions in the reference section have been removed; the format of this section has been substantially changed, we -hope for the better; -The chapters on obtaining the TEI DTDs and WSDs have been +hope for the better;The chapters on obtaining the TEI DTDs and WSDs have been brought up to date; the chapter on modification has been expanded to -include a discussion of the TEI Lite customization; -All examples and cited markup has been checked for XML validity +include a discussion of the TEI Lite customization;All examples and cited markup has been checked for XML validity against the published DTDs, and corrected where faulty; examples have -been formatted in a (more or less) consistent style. - +been formatted in a (more or less) consistent style.

-Lou Burnard and Syd Bauman (Editors) + Lou Burnard and Syd Bauman (Editors) Oxford and Providence, November 2001. -
-
Introductory Note (June 2001) -

This is a preliminary version of a revised and fully XML-compliant +

+
+ Introductory Note (June 2001) +

This is a preliminary version of a revised and fully XML-compliant edition of the TEI Guidelines. Although work on revising and correcting the text of the document is incomplete, by making available this preliminary version we hope to facilitate testing of the XML document type declarations which it describes by as wide a range of TEI users as possible.

-

The primary goal of this revision is to make available the +

The primary goal of this revision is to make available the corrected (May 1999) edition of the Guidelines in a new version which: - -is expressed in XML and itself conforms to a TEI-conformant XML - DTD; -generates a set of XML DTD fragments that can be combined +is expressed in XML and itself conforms to a TEI-conformant XML + DTD;generates a set of XML DTD fragments that can be combined together in the same way as the existing TEI (P3) SGML DTD - fragments to form true TEI XML DTD fragments without loss of functionality; -can be processed and maintained using readily available XML + fragments to form true TEI XML DTD fragments without loss of functionality;can be processed and maintained using readily available XML tools instead of the special-purpose ad hoc software originally - used for TEI P3. - + used for TEI P3. As noted elsewhere, a number of errors were corrected in the May 1999 edition. A (much) smaller number of errors have also been corrected in this edition, but no new material has been added. We expect the expansion and modification of the Guidelines to become a real possibility in the context of the newly formed TEI Consortium, which has funded the preparation of this present edition.

-

A major design goal of both this and the previous revision has been +

A major design goal of both this and the previous revision has been to ensure that the DTD fragments generated would not break existing documents: in other words, that any document conforming to the original TEI P3 SGML DTD would also conform to the new XML version of it. Although full backwards compatibility cannot be guaranteed, we believe our implementation is consistent with that goal.

-

In making this new version, we relied extensively on preliminary +

In making this new version, we relied extensively on preliminary work carried out by the outgoing North American editor of the TEI Guidelines, Michael Sperberg-McQueen. In a TEI working paper written in 1999, TEI ED @@ -196,28 +173,23 @@ which has funded the preparation of this present edition.

express our thanks to Sebastian Rahtz of Oxford University Computing Services, for his invaluable assistance in preparing this new edition.

-

We list here in summary form all the changes made in the present +

We list here in summary form all the changes made in the present edition. Full technical details are provided in documents TEI EDW69 and TEI EDW70, available from the TEI web site. - -A new keyword TEI.XML has been added. By setting +A new keyword TEI.XML has been added. By setting its value to INCLUDE, rather than the default IGNORE, -the user can request generation of an XML rather than an SGML DTD; -The content models of all elements have been checked, and, where +the user can request generation of an XML rather than an SGML DTD;The content models of all elements have been checked, and, where necessary, changed so that they are equally valid as SGML or as -XML; -The declared value for all attributes has been changed to a form -which is equally valid as SGML or as XML; -All the examples have been checked for conformance and converted to -use XML syntax, where possible. (This process is currently incomplete.) -Some errors and duplications in the class +XML; The declared value for all attributes has been changed to a form +which is equally valid as SGML or as XML;All the examples have been checked for conformance and converted to +use XML syntax, where possible. (This process is currently incomplete.)Some errors and duplications in the class membership of elements from the names and dates tagsets have been corrected.

-

To implement the first of these, we have parameterized the +

To implement the first of these, we have parameterized the tag omissibility indicators - o and - - used within element declarations in the DTD. When XML is to be generated, the parameter entities concerned are redeclared with the null string as their value.

-

The second change was achieved by removing SGML-specific features +

The second change was achieved by removing SGML-specific features (ampersand connectors, inclusion and exclusion exceptions, various types of attribute content) from the DTD and revising the syntax of the DTD to conform to XML requirements (specifically in the @@ -230,7 +202,7 @@ EDW70, some constraints (exclusion exceptions, for example) which could be carried out by a generic SGML parser using TEI P3 will have to be implemented by a special purpose TEI validator using TEI P4.

-

Much work remains to be done, firstly in testing the new DTD +

Much work remains to be done, firstly in testing the new DTD fragments against as wide a range of TEI materials as possible, secondly in revising the discussion of markup theory and practice within the text to reflect current thinking. A few sections of the @@ -240,12 +212,12 @@ rewriting. For the most part, however, we think the Guidelines have stood the test of time well and can be recommended to a new generation of text encoders scarcely born at the time they were first formulated.

-

Lou Burnard and Steve De Rose (Editors)

-

Oxford and Providence, May 2001.

-
-
-Introductory Note (May 1999) -

No work of the size and complexity of the TEI +

Lou Burnard and Steve De Rose (Editors)

+

Oxford and Providence, May 2001.

+
+
+ Introductory Note (May 1999) +

No work of the size and complexity of the TEI Guidelines could reasonably be expected to be error-free on publication, nor to remain long uncorrected. It has however taken rather longer than might have been anticipated to complete production of the present @@ -255,142 +227,119 @@ promotion of the TEI encoding scheme have ensured its continued survival in the rapidly changing world of digital scholarship, and also to the many helpfully critical users whose assiduous uncovering and reporting of our errors have made possible the present revision.

-

At its first meeting in Bergen, in June 1996, the TEI Technical Review +

At its first meeting in Bergen, in June 1996, the TEI Technical Review Committee (TRC) approved the setting up of a small working committee to oversee the production of a revised edition of the TEI Guidelines, to include corrections of as many as possible of the `corrigible errors' notified to the editors since publication of the first edition in May 1994, the bulk of which are summarized in a TEI working paper (TEI EDW67, available from the TEI web site).

-

During the spring of 1997, this TRC Core Subcommittee reviewed nearly 200 +

During the spring of 1997, this TRC Core Subcommittee reviewed nearly 200 comments and proposals which the editors had collected from public debate and discussion over the preceding two years, and provided invaluable technical guidance in disposition of them. We are glad to take this opportunity of expressing our thanks to this subcommittee, whose members were Elli Mylonas, Dominic Dunlop, and David T. Barnard.

-

The work of making the corrections and regenerating the text proceeded +

The work of making the corrections and regenerating the text proceeded rather fitfully during 1998 and 1999, largely because of increasing demands on the editors' time from their other responsibilities. With the establishment of the new TEI Consortium, it is be hoped that maintenance of the Guidelines will be placed on a more secure footing. Some specific areas in which we anticipate future revisions being carried out are listed below.

-
-Typographic Corrections Made - - examples of TEI markup throughout the text were all checked against the +
+ Typographic Corrections Made + + examples of TEI markup throughout the text were all checked against the relevant DTD fragment and an embarassingly large number of tagging errors corrected; - various minor typographic and spelling errors were corrected; - the corrigible errors listed in working paper TEI EDW67 were all + various minor typographic and spelling errors were corrected; + the corrigible errors listed in working paper TEI EDW67 were all corrected: some of these required specific changes to the DTD which are listed in the next section. - -
-
-Specific Changes in the DTD -

A major goal of this revision was to avoid changes which might invalidate + +

+
+ Specific Changes in the DTD +

A major goal of this revision was to avoid changes which might invalidate existing data, even where existing constructs seemed erroneous in retrospect. To that end, wherever changes have been made in content models for existing elements, they have as far as possible been made so that the DTD will now accept a superset of what was previously legal. Only one new element (ab) has been added.

-

Where possible, a few content models have been changed in such a way as to +

Where possible, a few content models have been changed in such a way as to facilitate conversion to XML, but XML compatibility is not a goal of this revision.

-

Brief details of all changes made in the DTD follow: - - Several changes were made in class membership, in order to correct +

Brief details of all changes made in the DTD follow: +Several changes were made in class membership, in order to correct unreachability problems. Specifically: - - elements geogName, persName, - placeName were added to the m.data class; - geogName and placeName were removed from the - m.placepart class; - the elements addSpan, delSpan, gap, were - added to the m.Edit class; - a new class m.editIncl was defined, with members + elements geogName, persName, + placeName were added to the m.data class; geogName and placeName were removed from the + m.placepart class;the elements addSpan, delSpan, gap, were + added to the m.Edit class; a new class m.editIncl was defined, with members addSpan, delSpan, and gap; this class was then added to the global inclusion class m.globIncl along with anchor (erroneously a member of the m.Seg class, from which it is now removed), m.metadata and m.refsys; - - - added name element to m.addrPart class; - added dateline to m.divtop and - m.divbot classes; - added epilogue and castList to - m.dramafront class; - added divGen to m.front class; - added dateline to m.divtop and - m.divtop classes; - added u element to a.declaring class; - defined new class m.fmchunk (front matter chunk), + added name element to m.addrPart class;added dateline to m.divtop and + m.divbot classes;added epilogue and castList to + m.dramafront class;added divGen to m.front class;added dateline to m.divtop and + m.divtop classes;added u element to a.declaring class;defined new class m.fmchunk (front matter chunk), comprising argument, byline, docAuthor, docDate, docEdition, docImprint, docTitle, epigraph, head, and titlePart for use in - simplification of the content model for front element; - defined new element ab (anonymous block), and added it to the - m.chunk class; - corrected an error whereby global attributes were not properly defined + simplification of the content model for front element;defined new element ab (anonymous block), and added it to the + m.chunk class;corrected an error whereby global attributes were not properly defined for elements specifying a non-default value for any of the a.global attributes: elements affected include: foreign, hi, del, pb, lb, cb, - language, anchor, and when; - changed content models to permit empty list and empty - availability elements; - changed content model for series element to permit #PCDATA; - - changed content model for setting element to permit - date element as a direct child; - added a key attribute to the distance element, - for consistency with other elements in its class; - changed content model for orgName element to make it more - consistent with e.g. persName; - changed content model for opener element to include - argument, byline, and epigraph; - changed content models for app, rdgGrp, and - wit elements; - revised attributes on hand element.

-

A number of content models were changed with a view to + language, anchor, and when;changed content models to permit empty list and empty + availability elements;changed content model for series element to permit #PCDATA; + changed content model for setting element to permit + date element as a direct child; added a key attribute to the distance element, + for consistency with other elements in its class;changed content model for orgName element to make it more + consistent with e.g. persName;changed content model for opener element to include + argument, byline, and epigraph;changed content models for app, rdgGrp, and + wit elements;revised attributes on hand element.

+

A number of content models were changed with a view to easing the creation of an XML compatible version of the Guidelines. Specifically: removed ampersand connectors from cit, -respStmt, publicationStmt, and graph; -changed the mixed content models for sense, re, persName, +respStmt, publicationStmt, and graph;changed the mixed content models for sense, re, persName, placeName, geogName, dateStruct, timeStruct, and dateline to make them XML-conformant.

-
-
-Outstanding Errors -

A small number of other known problems remain uncorrected in this version +

+
+ Outstanding Errors +

A small number of other known problems remain uncorrected in this version and are briefly listed below. Please watch the TEI mailing list for announcements of their correction.

- -elements of class model.inter don't always behave + + elements of class model.inter don't always behave as they should (e.g. one cannot insert a table before anything else in a div); - some mixed-content problems consequent on the definition of + some mixed-content problems consequent on the definition of macro.specialPara need to be addressed systematically; in particular, the treatment of list items or notes which contain several paragraphs continues to surprise many users: no whitespace is allowed between the paragraphs; - the resp attributes on editorial elements are not + the resp attributes on editorial elements are not consistently defined; - the discussions of DTD invocation, and the DTD itself, all use + the discussions of DTD invocation, and the DTD itself, all use system identifiers instead of formal public identifiers. - -

Our next priority however will be the production of a fully XML-compliant version + +

Our next priority however will be the production of a fully XML-compliant version of the TEI DTD, work on which is already well advanced.

-C.M. Sperberg-McQueen and Lou Burnard, May 1999 -
-
-
Preface (April 1994) -

These Guidelines are the result of over five years' effort by + C.M. Sperberg-McQueen and Lou Burnard, May 1999 +

+
+
+ Preface (April 1994) +

These Guidelines are the result of over five years' effort by members of the research and academic community within the framework of an international cooperative project called the Text Encoding Initiative (TEI), established in 1987 under the joint @@ -398,7 +347,7 @@ sponsorship of the Association for Computers and the Humanities, the Association for Computational Linguistics, and the Association for Literary and Linguistic Computing.

-

The impetus for the project came from the humanities computing +

The impetus for the project came from the humanities computing community, which sought a common encoding scheme for complex textual structures in order to reduce the diversity of existing encoding practices, simplify processing by machine, and encourage the sharing of @@ -411,7 +360,7 @@ and set of encoding conventions based upon it, suitable for processing and analysis of any type of text, in any language, and intended to serve the increasing range of existing (and potential) applications and use.

-

What is published here is a major milestone in this effort. It +

What is published here is a major milestone in this effort. It provides a single, coherent framework for all kinds of text encoding which is hardware-, software- and application-independent. Within this framework, it specifies encoding conventions for a number of key text @@ -420,7 +369,7 @@ scheme presented here to cover additional text types and features, as well as to continue to refine its encoding recommendations on the basis of extensive experience with their actual application and use.

-

We therefore offer these Guidelines to the user community for use in +

We therefore offer these Guidelines to the user community for use in the same spirit of active collaboration and cooperation with which they have so far been developed. The TEI is committed to actively supporting the wide-spread and large-scale use of the Guidelines @@ -430,14 +379,14 @@ will in some instances adapt and extend them as necessary to suit particular needs; we invite such users to engage in the further development of these Guidelines by working with us as they do so.

-

Like any standard which is actually used, these Guidelines do not +

Like any standard which is actually used, these Guidelines do not represent a static finished work, but rather one which will evolve over time with the active involvement of its community of users. We invite and encourage the participation of the user community in this process, in order to ensure that the TEI Guidelines become and remain useful in all sorts of work with machine-readable texts.

-

This document was made possible in part by financial support from +

This document was made possible in part by financial support from the U.S. National Endowment for the Humanities, an independent federal agency; Directorate General XIII of the Commission of the European Communities; the Andrew W. Mellon Foundation; and the Social Science @@ -451,53 +400,52 @@ Ohio State University, as well as the employers and host institutions of the members of the TEI working committees and work groups listed in the acknowledgments.

-

The production of this document has been greatly facilitated by the +

The production of this document has been greatly facilitated by the willingness of many software vendors to provide us with evaluation versions of their products. Most parts of this text have been processed at some time by almost every currently available SGML-aware software system. In particular, we gratefully acknowledge the assistance of the following vendors: - -Berger-Levrault AIS s.a. (for Balise); -E2S n.v. (for E2S Advanced SGML Editor); -Electronic Book Technology (for DynaText); -SEMA Group and Yard Software (for Mark-It and Write-It); -Software Exoterica (for CheckMark and Xtran); -SoftQuad, Inc., (for Author/Editor and RulesBuilder); -Xerox Corporation (for Ventura Publisher). +Berger-Levrault AIS s.a. (for Balise);E2S n.v. (for E2S Advanced SGML Editor);Electronic Book Technology (for DynaText);SEMA Group and Yard Software (for Mark-It and Write-It);Software Exoterica (for CheckMark and Xtran);SoftQuad, Inc., (for Author/Editor and RulesBuilder);Xerox Corporation (for Ventura Publisher).

-

Details of the software actually used to produce the current document +

Details of the software actually used to produce the current document are given in the colophon at the end of the work.

-
-
Acknowledgments -

Many people have given of their time, energy, expertise, and support +

+
+ Acknowledgments +

Many people have given of their time, energy, expertise, and support in the creation of this document; it is unfortunately not possible to thank them all adequately. Below are listed those who have served as formal members of the TEI's Work Groups and Working Committees during its six-year history; others not so officially enfranchised also contributed much to the quality of the result.

-

The editors take this opportunity to acknowledge our debt to those +

The editors take this opportunity to acknowledge our debt to those who have patiently endured and corrected our misunderstandings of their work; we hope that they will feel the wait has not been in vain. For any errors and inconsistencies remaining, we must accept responsibility; any virtue in what is here presented, we gladly ascribe to the energies of the keen intellects listed below.

-

C. M. Sperberg-McQueen and Lou Burnard

-
TEI Working Committees (1990-1993)Not all members listed were able to serve throughout the development +

C. M. Sperberg-McQueen and Lou Burnard

+
+ TEI Working Committees (1990-1993) + Not all members listed were able to serve throughout the development of the Guidelines. - - -

Chair: Dominik Wujastyk (Wellcome Institute for the History of + + + +

Chair: Dominik Wujastyk (Wellcome Institute for the History of Medicine)

-

Members 1990–1992: J. D. Byrum (Library of Congress); +

Members 1990–1992: J. D. Byrum (Library of Congress); Marianne Gaunt (Rutgers University); Richard Giordano (Manchester University); Barbara Ann Kipfer (Independent Consultant); Hans Jørgen Marker (Danish Data Archive, Odense); -Marcia Taylor (University of Essex);

 - -

Chair: Stig Johansson (University of Oslo)

-

Members 1990–1992: Roberto Cencioni (Commission of the European +Marcia Taylor (University of Essex);

+ + + +

Chair: Stig Johansson (University of Oslo)

+

Members 1990–1992: Roberto Cencioni (Commission of the European Communities); David R. Chesnutt (University of South Carolina); Robin C. Cover (Dallas Theological Seminary); @@ -510,10 +458,12 @@ Elli Mylonas (Harvard University); Wilhelm Ott (University of Tübingen); Allen H. Renear (Brown University); Manfred Thaller (Max-Planck-Institut für Geschichte, -Göttingen)

 - -

Chair: D. Terence Langendoen (University of Arizona)

-

Members 1990–1992: +Göttingen)

+ + + +

Chair: D. Terence Langendoen (University of Arizona)

+

Members 1990–1992: Robert Amsler (Bell Communications Research); Stephen Anderson (Johns Hopkins University); Branimir Boguraev (IBM T. J. Watson Research Center); @@ -525,80 +475,70 @@ Nelleke Oostdijk (University of Nijmegen); William Poser (Stanford University); Beatrice Santorini (University of Pennsylvania); Gary Simons (Summer Institute of Linguistics); -Antonio Zampolli, University of Pisa.

 - -

Chair: David T. Barnard (Queen's University)

-

Members 1990–1994: David G. Durand (Boston University); +Antonio Zampolli, University of Pisa.

+ + + +

Chair: David T. Barnard (Queen's University)

+

Members 1990–1994: David G. Durand (Boston University); Jean-Pierre Gaspart (Associated Consultants and Software Engineers sa/nv); Nancy M. Ide (Vassar College); Lynne A. Price (Software Exoterica / Xerox PARC); Frank Tompa (University of Waterloo); -Giovanni Battista Varile (Commission of the European Communities).

 -

In addition, the two TEI editors served ex officio on each +Giovanni Battista Varile (Commission of the European Communities).

+ + +

In addition, the two TEI editors served ex officio on each committee.

-

Following publication of the first draft of the TEI Guidelines (P1) +

Following publication of the first draft of the TEI Guidelines (P1) in November 1990, a number of specialist work groups were charged with responsibility for drafting revisions and extensions, which, together with material already presented in P1, constitute the basis of the present work.

-

In addition, many members of the work groups listed below met on +

In addition, many members of the work groups listed below met on three occasions to review the emerging proposals in detail at technical review meetings convened by the TEI Steering Committee. These meetings, held in Myrdal, Norway (November 1991), Chicago (May 1992) and Oxford (May 1993), were largely responsible for the technical content and organization of the present work. Attendants at these meetings are starred in the list below. - -Chair: Harry Gaylord* (University of Groningen); -Syun Tutiya* (Chiba University). -Chair: Peter Robinson* (Oxford University); +Chair: Harry Gaylord* (University of Groningen); +Syun Tutiya* (Chiba University).Chair: Peter Robinson* (Oxford University); David Chesnutt* (University of South Carolina); Robin Cover* (Dallas Theological Seminary); Robert Kraft (University of Pennsylvania); -Peter Shillingsburg (Mississippi State University). -Chair: Steven J. DeRose* (Electronic Book Technologies Inc); +Peter Shillingsburg (Mississippi State University).Chair: Steven J. DeRose* (Electronic Book Technologies Inc); David Durand (Boston University); Edward A. Fox (Virginia State University); Eve Wilson (University of -Kent). -Chair: Paul Ellison* (University of Exeter); +Kent).Chair: Paul Ellison* (University of Exeter); Anders Berglund (Independent Consultant); Dale Waldt (Thompson -Professional Publishing). -Chair: Douglas Biber* (University of Northern Arizona); +Professional Publishing).Chair: Douglas Biber* (University of Northern Arizona); Jeremy Clear (Birmingham University); -Gunnel Engwall (University of Stockholm). -Chair: Claus Huitfeldt* (University of Bergen); +Gunnel Engwall (University of Stockholm).Chair: Claus Huitfeldt* (University of Bergen); Dino Buzzetti (University of Bologna); Jacqueline Hamesse (University of Louvain); Mary Keeler (Georgetown University); Christian Kloesel (Indiana University); Allen Renear* (Brown University); -Donald Spaeth (Glasgow University). -Chair: David Robey* (University of Manchester); +Donald Spaeth (Glasgow University).Chair: David Robey* (University of Manchester); Elaine Brennan* (Brown University); David Chisholm (University of Arizona); -Willard McCarty (University of Toronto). -Chair: Elli Mylonas* (Harvard University); +Willard McCarty (University of Toronto).Chair: Elli Mylonas* (Harvard University); John Lavagnino* (Brandeis University); -Rosanne Potter (University of Iowa). -Chair Thomas N. Corns* (University of Wales); +Rosanne Potter (University of Iowa).Chair Thomas N. Corns* (University of Wales); Christian Delcourt (University of Liège). - -Chair: D. Terence Langendoen* (University of Arizona); + Chair: D. Terence Langendoen* (University of Arizona); Stephen R. Anderson (Johns Hopkins University); Nicoletta Calzolari (University of Pisa); Geoffrey Sampson* (University of Sussex); -Gary Simons* (Summer Institute of Linguistics). -Chair: Stig Johansson* (University of Oslo); +Gary Simons* (Summer Institute of Linguistics).Chair: Stig Johansson* (University of Oslo); Jane Edwards (University of California at Berkeley); -Andrew Rosta (University College London). -Chair: Paul Fortier* (University of Manitoba); +Andrew Rosta (University College London).Chair: Paul Fortier* (University of Manitoba); Christian Delcourt (University of Liège;); Ian Lancashire (University of Toronto); Rosanne Potter (University of Iowa); -David Robey* (University of Manchester). - -Chair: Daniel Greenstein* (University of Glasgow); +David Robey* (University of Manchester).Chair: Daniel Greenstein* (University of Glasgow); Peter Denley (Queen Mary Westfield College, London); Ingo Kropac (University of Graz); Hans Jørgen Marker (Danish Data Archive, Odense); @@ -607,9 +547,7 @@ Kevin Schurer (University of Cambridge); Donald Spaeth (Glasgow University); Manfred Thaller (Max-Planck-Institut für Geschichte, Göttingen).This Workgroup was jointly -sponsored by the Association for History and Computing. - -Chairs: Robert Amsler* (Bell Communications Research) and +sponsored by the Association for History and Computing.Chairs: Robert Amsler* (Bell Communications Research) and Nicoletta Calzolari (University of Pisa); Susan Armstrong-Warwick (University of Geneva); John Fought (University of Pennsylvania); @@ -617,63 +555,37 @@ Louise Guthrie (University of New Mexico); Nancy M. Ide* (Vassar College); Frank Tompa (University of Waterloo); Carol Van Ess-Dykema (US Department of Defense); -Jean Veronis (University of Aix-en-Provence). -Chair: Robert Ingria* (Bolt Beranek Newman Inc); +Jean Veronis (University of Aix-en-Provence).Chair: Robert Ingria* (Bolt Beranek Newman Inc); Susan Armstrong-Warwick (University of Geneva); -Nicoletta Calzolari (University of Pisa). -Chair: Alan Melby* (Brigham Young University) +Nicoletta Calzolari (University of Pisa).Chair: Alan Melby* (Brigham Young University) Gerhard Budin (University of Vienna); Gregory Shreve (Kent State University); Richard Strehlow (Oak Ridge National Laboratory); -Sue Ellen Wright (Kent State University).

-
Advisory Board -

Members of the TEI Advisory Board during the lifetime of the +Sue Ellen Wright (Kent State University).

+
+
+ Advisory Board +

Members of the TEI Advisory Board during the lifetime of the project are listed below, grouped under the name of the organization represented. - -Chad McDaniel (University of Maryland). -Elizabeth A. R. Brown (Brooklyn College, CUNY). -Jocelyn Penny Small (Rutgers University). -Allen Renear (Brown University). -Clifford A. Lynch (University of California). -1989–93: Scott Deerwester (University of Chicago); 1993- : -Martha Evens (Illinois Institute of Technology). -David Chesnutt (University of South Carolina). -1989–91: Manfred Thaller, Max-Planck-Institut für +Chad McDaniel (University of Maryland).Elizabeth A. R. Brown (Brooklyn College, CUNY).Jocelyn Penny Small (Rutgers University).Allen Renear (Brown University).Clifford A. Lynch (University of California).1989–93: Scott Deerwester (University of Chicago); 1993- : +Martha Evens (Illinois Institute of Technology).David Chesnutt (University of South Carolina).1989–91: Manfred Thaller, Max-Planck-Institut für Geschichte, Göttingen; 1991- : Daniel Greenstein (Glasgow -University). -1989–93: Wilhelm Ott (University of Tübingen); 1993- : -Winfried Bader (University of Tübingen). -Anne-Maria di Sciullo (Université du Québec -à Montréal) -Barbara Ann Kipfer (Independent Consultant). -1989–92: Betsy Kiser (OCLC); 1992- : +University).1989–93: Wilhelm Ott (University of Tübingen); 1993- : +Winfried Bader (University of Tübingen).Anne-Maria di Sciullo (Université du Québec +à Montréal)Barbara Ann Kipfer (Independent Consultant).1989–92: Betsy Kiser (OCLC); 1992- : Deborah Bendig and Andrea Keyhani (OCLC). -J. D. Byrum Jr. (The Library of Congress). -Stephen Anderson (The Johns Hopkins University) -Randall Jones (Brigham Young University) and -Ian Lancashire (University of Toronto).

-
Steering Committee Membership -

Members of the Steering Committee of the TEI during the preparation +Institutions:J. D. Byrum Jr. (The Library of Congress).Stephen Anderson (The Johns Hopkins University)Randall Jones (Brigham Young University) and +Ian Lancashire (University of Toronto).

+
+
+ Steering Committee Membership +

Members of the Steering Committee of the TEI during the preparation of this work were: - - - -1987–1993: Robert A. Amsler (Bell Communications Research); -1987–1993: Donald E. Walker (Bell Communications Research); -1993–1994: Susan Armstrong-Warwick (University of Geneva); -1994–1999: Judith Klavans (Columbia University). - - -1987–1999: Nancy M. Ide (Vassar College); -1987–1994: C. M. Sperberg-McQueen (University of Illinois at -Chicago); -1994–1999: David Barnard (Queen's University). - - -1987–1999: Susan M. Hockey (Center for Electronic Texts in the -Humanities); -1987–1999: Antonio Zampolli (University of Pisa).

+1987–1993: Robert A. Amsler (Bell Communications Research);1987–1993: Donald E. Walker (Bell Communications Research);1993–1994: Susan Armstrong-Warwick (University of Geneva);1994–1999: Judith Klavans (Columbia University).1987–1999: Nancy M. Ide (Vassar College);1987–1994: C. M. Sperberg-McQueen (University of Illinois at +Chicago);1994–1999: David Barnard (Queen's University).1987–1999: Susan M. Hockey (Center for Electronic Texts in the +Humanities);1987–1999: Antonio Zampolli (University of Pisa).

+
+
diff --git a/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml b/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml index e0d5582f47..95be506e16 100644 --- a/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml +++ b/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml @@ -1,20 +1,11 @@ - - - + -
- Attributes -
- About the Attributes Appendix -

This appendix gives you a list of attributes and links to the reference pages for the elements on which they appear. There are distinctly-named attributes in revision of TEI P5 of the TEI Guidelines.

- - -
+ Attributes +
+ About the Attributes Appendix +

This appendix gives you a list of attributes and links to the reference pages for the elements on which they appear. There are distinctly-named attributes in revision of TEI P5 of the TEI Guidelines.

+
+ +
diff --git a/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml b/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml index 9c1a06179d..f974a2f376 100644 --- a/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml +++ b/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml @@ -1,21 +1,11 @@ - - - + -
- Attribute Classes -
- About the Attribute Classes Appendix -

This appendix gives you a list of attribute classes and links to the reference pages for them. There are distinctly-named attribute classes in revision of TEI P5 of the TEI Guidelines.

- - - -
+ Attribute Classes +
+ About the Attribute Classes Appendix +

This appendix gives you a list of attribute classes and links to the reference pages for them. There are distinctly-named attribute classes in revision of TEI P5 of the TEI Guidelines.

+
+ +
diff --git a/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml b/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml index 1c7e849c4b..a94654fee7 100644 --- a/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml +++ b/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml @@ -1,20 +1,11 @@ - - - + -
- Model Classes -
- About the Model Classes Appendix -

This appendix gives you a list of model classes and links to the reference pages for them. There are distinctly-named model classes in revision of TEI P5 of the TEI Guidelines.

- - -
+ Model Classes +
+ About the Model Classes Appendix +

This appendix gives you a list of model classes and links to the reference pages for them. There are distinctly-named model classes in revision of TEI P5 of the TEI Guidelines.

+
+ +
diff --git a/P5/Source/Guidelines/en/REF-ELEMENTS.xml b/P5/Source/Guidelines/en/REF-ELEMENTS.xml index 50c7266c48..cdf8e20403 100644 --- a/P5/Source/Guidelines/en/REF-ELEMENTS.xml +++ b/P5/Source/Guidelines/en/REF-ELEMENTS.xml @@ -1,27 +1,17 @@ - - - + -
- Elements -
- About the Elements Appendix -

This appendix gives you links to reference pages for all elements in the TEI Guidelines. + Elements +

+ About the Elements Appendix +

This appendix gives you links to reference pages for all elements in the TEI Guidelines. There are TEI elements in revision of TEI P5 of the TEI Guidelines.

-

The elements listed here are in the TEI Namespace: +

The elements listed here are in the TEI Namespace: http://www.tei-c.org/ns/1.0 unless otherwise noted on that element's reference page.

- -
- +
+
diff --git a/P5/Source/Guidelines/en/REF-MACROS.xml b/P5/Source/Guidelines/en/REF-MACROS.xml index 16b991845c..7c4ad896c8 100644 --- a/P5/Source/Guidelines/en/REF-MACROS.xml +++ b/P5/Source/Guidelines/en/REF-MACROS.xml @@ -1,20 +1,11 @@ - - - + -
- Datatypes and Other Macros -
- About the Datatypes and Macros Appendix -

This appendix gives you a list of datypes and links to the reference pages for them. There are distinctly-named data specifications in revision of TEI P5 of the TEI Guidelines.

- - -
+ Datatypes and Other Macros +
+ About the Datatypes and Macros Appendix +

This appendix gives you a list of datypes and links to the reference pages for them. There are distinctly-named data specifications in revision of TEI P5 of the TEI Guidelines.

+
+ +
diff --git a/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml b/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml index 86f566266e..0549f9a4a6 100644 --- a/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml +++ b/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml @@ -1,28 +1,17 @@ - + -
+
Linking, Segmentation, and Alignment - -

This chapter discusses a number of ways in which encoders may +

This chapter discusses a number of ways in which encoders may represent analyses of the structure of a text which are not necessarily linear or hierarchic. The module defined by this chapter provides for the following common requirements: - - to link disparate elements - using the xml:id attribute (section ); - to link disparate elements without using the - xml:id attribute (sections and ); - to segment text into elements convenient for + to link disparate elements + using the xml:id attribute (section );to link disparate elements without using the + xml:id attribute (sections and );to segment text into elements convenient for the encoder and to mark arbitrary points within documents (section - ); - to represent correspondence or + );to represent correspondence or alignment among groups of text elements, both those with content and those which are empty (section );We use the term alignment as a special case for the more general notion of correspondence. Using A @@ -33,28 +22,19 @@ provides for the following common requirements: relation in which A1 corresponds to B1, A2 corresponds to B2, and A3 corresponds to B3 is an alignment. On the other hand, a relation in which A1 corresponds to B2, B1 to C2, and C1 to A2 is - not an alignment. - to synchronize elements of a + not an alignment.to synchronize elements of a text, that is to represent temporal correspondences and alignments among text elements (section ) and also to - align them with specific points in time (section ); - to specify that one text element is identical - to or a copy of another (section ); - to aggregate possibly noncontiguous elements - (section ); - to specify that different elements are + align them with specific points in time (section );to specify that one text element is identical + to or a copy of another (section );to aggregate possibly noncontiguous elements + (section );to specify that different elements are alternatives to one another and to express - preferences among the alternatives (section ); - to store markup separately from the data it describes - or is related to (section ); - to associate segments of a text + preferences among the alternatives (section );to store markup separately from the data it describes + or is related to (section );to associate segments of a text with interpretations or analyses of their significance (section - ); - to group together elements used to provide stand-off - annotation, including contextual information (section ). -

-

These facilities all use the same set of techniques based on the + );to group together elements used to provide stand-off + annotation, including contextual information (section ).

+

These facilities all use the same set of techniques based on the W3C XPointer framework () This provides a variety of schemes; the most convenient of which, and that recommended by these Guidelines, makes use of the @@ -86,8 +66,8 @@ elaborate and more general ones, which use specialized elements.

representing locations in a document by a variety of means not dependent on the use of xml:id attributes.

-Pointers and Links -

In section we introduced the simplest + Pointers and Links +

In section we introduced the simplest pointer elements, ptr and ref. Here we introduce additionally the link element, which represents an association between two (or more) locations by @@ -95,10 +75,7 @@ specifying each location explicitly. Its own location is irrelevant to the intended linkage. All three elements use the attribute target, provided by the att.pointing class as a means of indicating the location or locations referenced or pointed to. - - - - + The ptr element may be called a pure pointer, because its primary function is simply to point. A pointer sets up a connection between an @@ -111,13 +88,10 @@ if that target may be discontinuous in the document. The link element specifies at least two targets and represents an association between them, independent of its own location.

-

These three elements also share a common set of attributes, derived +

These three elements also share a common set of attributes, derived from the att.pointing and att.typed classes: - - - -

-

Double connection among elements could also be expressed by a +

+

Double connection among elements could also be expressed by a combination of pointer elements, for example, two ptr elements, or one ptr element and one note element. All that is required is that the value of the @@ -131,7 +105,7 @@ encoding: points to sa-p1. This is logically equivalent to the more compact encoding:

-

As noted elsewhere, the target attribute may take as value one or more URI reference. In the simplest case, each such reference will indicate an element in the current document (or in some other @@ -143,12 +117,11 @@ linking where identifiers are not available is described below in section .

-Using Pointers and Links -

As an example of the use of mechanisms which establish + Using Pointers and Links +

As an example of the use of mechanisms which establish connections among elements, consider the practice (common in 18th century English verse and elsewhere) of providing footnotes -citing parallel passages from classical authors.

-The +citing parallel passages from classical authors.
The figure shows the original page of Pope's Dunciad which is discussed in the text.
Such footnotes can of course simply be encoded using the @@ -164,18 +137,9 @@ Allusions to the most excellent of the Moderns. In the source text, the text of the poem shares the page with two sets of notes, one headed Remarks and the other Imitations. -(Diff'rent our parties, but with equal grace -The Goddess smiles on Whig and Tory race, - - Virg. Æn. 10. - -Tros Rutulusve fuat; nullo discrimine habebo. -—— Rex Jupiter omnibus idem. - - 'Tis the same rope at sev'ral ends they twist, -To Dulness, Ridpath is as dear as Mist) +(Diff'rent our parties, but with equal graceThe Goddess smiles on Whig and Tory race,Virg. Æn. 10.Tros Rutulusve fuat; nullo discrimine habebo.—— Rex Jupiter omnibus idem.'Tis the same rope at sev'ral ends they twist,To Dulness, Ridpath is as dear as Mist)

-

This use of the note element can be called +

This use of the note element can be called implicit pointing (or implicit linking). It relies on the juxtaposition of the note to the text being commented on for the connection to be understood. @@ -187,37 +151,22 @@ lines, or what?), or if it is decided to place the note at some distance from the text, then the pointing or the linking must be made explicit. We now consider various methods for doing that.

-

Firstly, a ptr element might be placed at an +

Firstly, a ptr element might be placed at an appropriate point within the text to link it with the annotation: -(Diff'rent our parties, but with equal grace -The Goddess smiles on Whig and Tory race, - -'Tis the same rope at sev'ral ends they twist, -To Dulness, Ridpath is as dear as Mist) - - Virg. Æn. 10. - -Tros Rutulusve fuat; nullo discrimine habebo. -—— Rex Jupiter omnibus idem. - - +(Diff'rent our parties, but with equal graceThe Goddess smiles on Whig and Tory race, + 'Tis the same rope at sev'ral ends they twist,To Dulness, Ridpath is as dear as Mist)Virg. Æn. 10.Tros Rutulusve fuat; nullo discrimine habebo.—— Rex Jupiter omnibus idem. The note element has been given an arbitrary identifier (note3.284) to enable it to be specified as the target of the pointer element. Because there is nothing in the text to signal the existence of the annotation, the rend attribute has been given the value unmarked.

-

Secondly, the target attribute of the +

Secondly, the target attribute of the note element can be used to point at its associated text, provided that an xml:id attribute has been supplied for the associated text: -(Diff'rent our parties, but with equal grace -The Goddess smiles on Whig and Tory race, -'Tis the same rope at sev'ral ends they twist, -To Dulness, Ridpath is as dear as Mist) - - +(Diff'rent our parties, but with equal graceThe Goddess smiles on Whig and Tory race,'Tis the same rope at sev'ral ends they twist,To Dulness, Ridpath is as dear as Mist) Given this encoding of the text itself, we can now link the various notes to it. In this case, the note itself contains a pointer to the place in the text which it is @@ -225,27 +174,13 @@ annotating; this could be encoded using a ref element, which bears a target attribute of its own and contains a (slightly misquoted) extract from the text marked as a quote element: - - Verse 283–84. - - ——. With equal grace - Our Goddess smiles on Whig and Tory race. - - - Virg. Æn. 10. - -Tros Rutulusve fuat; nullo discrimine habebo. -—— Rex Jupiter omnibus idem. - - +Verse 283–84. + ——. With equal graceOur Goddess smiles on Whig and Tory race. + Virg. Æn. 10.Tros Rutulusve fuat; nullo discrimine habebo.—— Rex Jupiter omnibus idem.

-

Combining these two approaches gives us the following +

Combining these two approaches gives us the following associations: - - a pointer within one line indicates the note - the note indicates the line - a pointer within the note indicates the line - +a pointer within one line indicates the notethe note indicates the linea pointer within the note indicates the line Note that we do not have any way of pointing from the line itself to the note: the association is implied by containment of the pointer. We do not as yet have a true double link between text and note. To @@ -254,44 +189,24 @@ well as for the verse lines, and use a link element to associate the two. Note that the ptr element and the target attribute on the note may now be dispensed with: - - - Verse 283–84. - - ——. With equal grace - Our Goddess smiles on Whig and Tory race. - - Virg. Æn. 10. - -Tros Rutulusve fuat; nullo discrimine habebo. -—— Rex Jupiter omnibus idem. - - - +Verse 283–84. +——. With equal graceOur Goddess smiles on Whig and Tory race.Virg. Æn. 10.Tros Rutulusve fuat; nullo discrimine habebo.—— Rex Jupiter omnibus idem.

-

The target attribute of the link element +

The target attribute of the link element here bears the identifier of the note followed by that of the verse line. We could also allocate an identifier to the reference within the note and encode the association between it and the verse line in the same way: - - Verse 283–84. - - ——. With equal grace - Our Goddess smiles on Whig and Tory race. - - - - - +Verse 283–84. +——. With equal graceOur Goddess smiles on Whig and Tory race. Indeed, the two links could be combined into one, as follows:

-Groups of Links -

Clearly, there are many reasons for which an encoder might + Groups of Links +

Clearly, there are many reasons for which an encoder might wish to represent a link or association between different elements. For some of them, specific elements are provided in these Guidelines; some of these are discussed elsewhere in the @@ -311,12 +226,12 @@ It is also a member of the att.pointing and att.typed classes, and therefore also carries the attributes specified in section above, in particular the type attribute.

-

The linkGrp element provides a convenient way of +

The linkGrp element provides a convenient way of establishing a default for the type attribute on a group of links of the same type: by default, the type attribute on a link element has the same value as that given for type on the enclosing linkGrp.

-

Typical software might hide a web entirely from the user, but +

Typical software might hide a web entirely from the user, but use it as a source of information about links, which are displayed independently at their referenced locations. Alternatively, software might provide a direct view of the link @@ -326,32 +241,15 @@ To continue our previous example, this text contains many other notes of a kind similar to the one shown above. Here are a few more of the lines to which annotations have to be attached, followed by the annotations themselves: -A place there is, betwixt earth, air and seas -Where from Ambrosia, Jove retires for ease. - -Sign'd with that Ichor which from Gods distills. - - - Ovid Met. 12. - -Orbe locus media est, inter terrasq; fretumq; -Cœlestesq; plagas — - - - +A place there is, betwixt earth, air and seasWhere from Ambrosia, Jove retires for ease.Sign'd with that Ichor which from Gods distills.Ovid Met. 12.Orbe locus media est, inter terrasq; fretumq;Cœlestesq; plagas — Alludes to Homer, Iliad 5 ... To avoid having to repeat the specification of type as imitation on each note, we may specify it once for all on a linkGrp element containing all links of this type. - - - - - -

-

Additional information for applications that use +

+

Additional information for applications that use linkGrp elements can be provided by means of special attributes. First, the domains attribute can be used to identify the text elements within which the individual @@ -363,24 +261,15 @@ have as its value the identifiers of the body and the back, to enable an application to verify that the link targets are in fact contained by appropriate elements, or to limit its search space: - - - - - - - - - -

-

Note that there must be a single parent element for each +

+

Note that there must be a single parent element for each domain; if some notes are contained by a section with identifier dunnotes, and others by a section with identifier dunimits, an intermediate pointer must be provided (as described in section ) within the linkGrp and its identifier used instead.

-

Next, the targFunc attribute can be used to +

Next, the targFunc attribute can be used to provide further information about the role or function of the various targets specified for each link in the group. The value of the targFunc attribute is a list of names @@ -396,26 +285,20 @@ example, we might think of the note as containing the sourc as containing the goal of the imitation. Accordingly, we can specify the linkGrp in the preceding example thus: - - - - - - -

- - - - +

+ + + +
-Intermediate Pointers -

In the preceding examples, we have shown various ways of + Intermediate Pointers +

In the preceding examples, we have shown various ways of linking an annotation and a single verse line. However, the example cited in fact requires us to encode an association between the note and a pair of verse lines (lines 284 and 285); we call these two lines a span.

-

There are a number of possible ways of correcting this error: one +

There are a number of possible ways of correcting this error: one could use the target attribute to indicate one end of the span and the special purpose targetEnd attribute on the note element to point to the other. Another possibility might @@ -424,10 +307,9 @@ assign that an xml:id attribute, which can then be linked to the note and ref elements. This could be done using for example the lg element defined in section or the virtual join element discussed in section .

-

A third possibility would be to use an +

A third possibility would be to use an intermediate pointer as follows: - - + When the target attribute of a ptr or ref element specifies more than one element, the indicated elements are intended to be combined or aggregated in @@ -438,33 +320,28 @@ of the ptr then provides an identifier which can be linked to the note and ref elements:

-

The all value of evaluate is used on the +

The all value of evaluate is used on the link element to specify that any pointer encountered as a target of that element is itself evaluated. If evaluate had the value none, the link target would be the pointer itself, rather than the objects it points to.

-

Where a linkGrp element is used to group a +

Where a linkGrp element is used to group a collection of link elements, any intermediate pointer elements used by those link elements should be included within the linkGrp.

-
+
Pointing Mechanisms

This section introduces more formally the pointing mechanisms available in the TEI. In addition to those discussed so far, the TEI provides methods of pointing: - -into documents other than the current document; -to a particular element in a document other than the -current document using its xml:id; -to a particular element whether in the current document or -not, using its position in the XML element tree; -at arbitrary content in any XML document using TEI-defined -XPointer schemes. - + into documents other than the current document;to a particular element in a document other than the +current document using its xml:id;to a particular element whether in the current document or +not, using its position in the XML element tree;at arbitrary content in any XML document using TEI-defined +XPointer schemes.

-

All TEI attributes used to point at something else are declared as +

All TEI attributes used to point at something else are declared as having the datatype teidata.pointer, which is defined as a URI referenceThe URI (Universal Resource Indicator) is defined in RFC 3986; the @@ -486,8 +363,8 @@ identified by the URI. -->

recommended. More detailed information on the use of these mechanisms is readily available elsewhere.

-Pointing Elsewhere -

Like the ubiquitous if misnamed XHTML pointing attribute href, the TEI pointing attributes can point to a + Pointing Elsewhere +

Like the ubiquitous if misnamed XHTML pointing attribute href, the TEI pointing attributes can point to a document that is not the current document (the one that contains the pointing element) whether it is in the same local filesystem as the current document, or on a different system entirely. In either case, @@ -502,61 +379,47 @@ ancestor that has one. However this may not be the case, since xml:base attributes are accumulated through the hierarchy by concatenation of path segments, beginning at the top of the hierarchy and proceeding down to the context node.

-

The following example demonstrates an absolute URI reference +

The following example demonstrates an absolute URI reference that points to a remote document: The current base URI in force is as defined in the W3C XML Base recommendation.

-

This example points explicitly to a location on the Web, +

This example points explicitly to a location on the Web, accessible via HTTP. Suppose however that we wish to access a document stored locally in a file. Again we will supply an absolute URI reference, but this time using a different protocol: This Debian package is distributed under the terms of the GNU General Public License.

-

In the following example, we use a relative URI reference +

In the following example, we use a relative URI reference to point to a local document: -

- - The figure shows the page from the Orbis - pictus of Comenius which is discussed in the text. -
+
The figure shows the page from the Orbis + pictus of Comenius which is discussed in the text.
 Since no xml:base is specified here, the location of the resource Images/compic.png is determined relative to the resource indicated by the current base URI, which is the current document.

- - -

In the following example, however, we first change the current base +

In the following example, however, we first change the current base URI by setting a new value for xml:base. The resource required is then identified by means of a relative URI: -

- On Ancient Persian Manners -

In the very first story of The Gulistan of +<egXML xmlns="http://www.tei-c.org/ns/Examples"><div type="chap" xml:base="http://classics.mit.edu/"><head>On Ancient Persian Manners</head><p>In the very first story of <ref target="Sadi/gulistan.2.i.html"><title>The Gulistan of Sa'di, - Sa'di relates moral advice worthy of Miss Minners ...

- -

-

As noted above, the current base URI is found on the nearest + Sa'di relates moral advice worthy of Miss Minners ...

+

As noted above, the current base URI is found on the nearest ancestor. It is technically possible to use xml:base as a means to shorten URIs, but this usage is not recommended. Abbreviated pointers provide a more flexible and consistent method for creating shorthand links.

- -
-Pointing Locally -

A shorthand pointer, in which the URI consists only of + Pointing Locally +

A shorthand pointer, in which the URI consists only of # followed by the value of an xml:id acts as a pointer to the element in the current document with that xml:id, -as in the following example.

-
- Limitations on exclusive rights: Fair use -

Notwithstanding the provisions of +as in the following example.

Limitations on exclusive rights: Fair use

Notwithstanding the provisions of section 106, the fair use of a copyrighted work, including such use by reproduction in copies or phonorecords or by any other means specified by that section, @@ -566,21 +429,15 @@ as in the following example. - the purpose and character of the use, including + the purpose and character of the use, including whether such use is of a commercial nature or is for nonprofit - educational purposes; - the nature of the copyrighted work; - the amount and substantiality of the portion + educational purposes;the nature of the copyrighted work;the amount and substantiality of the portion used in relation to the copyrighted work as a whole; - and - the effect of the use upon the potential market - for or value of the copyrighted work. - + andthe effect of the use upon the potential market + for or value of the copyrighted work. The fact that a work is unpublished shall not itself bar a finding of fair use if such finding is made upon consideration - of all the above factors.

-
+ of all the above factors.

This method of pointing, by referring to the xml:id of the target element as a bare name only (e.g., #sect106) is the simplest and often the best approach where it can be applied, i.e. where @@ -589,116 +446,67 @@ document, and where the target element carries an identifier. It is the method used extensively in previous sections of this chapter and elsewhere in these Guidelines.

-
Using Abbreviated Pointers -

Even in the case of relative links on the local file system, ref or target attributes may become quite lengthy and make XML code difficult to read. To deal with this problem, the TEI provides a useful method of using abbreviated pointers and documenting a way to dereference them automatically.

-

Imagine a project which has a large collection of XML documents organized like this:

- anthology - - poetry - - poem.xml - - - prose - - novel.xml - - - + poetry + poem.xml + prose + novel.xml + references - - people - - personography.xml - - - + people + personography.xml + - -

If you want to link a name in the novel.xml file to a person in the personography.xml file, the link will look like this: - - Fred - + Fred If there are many names to tag in a single paragraph, the XML encoding will be congested, and such lengthy links are prone to typographical error. In addition, if the project organization is changed, every relative link will have to be found and altered.

-

One way to deal with this is to use what is often referred to as a "magic token". You could make such links using the key attribute: - - Fred - + Fred and document the meaning of the key using (for instance) a taxonomy element in the TEI header, as described in . However, such a link cannot be mechanically processed by an external system that does not know how to interpret it; a human will have to read the header explanation and write code explicitly to reconstruct the intended link.

-

A more robust alternative is to use a private URI scheme. This is a method of constructing a simple, key-like token which functions as a teidata.pointer, and can therefore be used as the value of any attribute which has that datatype, such as ref and target. Such a scheme consists of a prefix with a colon, and then a value. You might, for example, use the prefix psn (for "person"), and structure your name tags like this: - - Fred - + Fred How is this different from a magic token? Essentially, it isn't, except that TEI provides a structured method of dereferencing it (turning it into a computable path, such as ../../references/people/personography.xml#fred) by means of a declaration inside encodingDesc in the TEI header, using the elements and attributes for prefix declaration: - - - - - +

+

This is how you might document a private URI scheme using the psn: prefix: - -

This is how you might document a private URI scheme using the psn: prefix: - - - - -

+

In the context of this project, private URIs with the prefix "psn" point to person elements in the project's personography.xml file. -

- - - +

This specifies that where a teidata.pointer value is constructed with a psn: prefix, a regular-expression replace operation can be performed on it to construct the full or relative URI to the target document or fragment. listPrefixDef is a child of encodingDesc, and it contains any number of prefixDef elements. Each prefixDef element provides a method of dereferencing or expanding an abbreviated pointer, based on a regular expression. The ident attribute specifies the prefix to which the expansion applies (without the colon). The matchPattern attribute contains a regular expression which is matched against the component of the pointer following the first colon, and the replacementPattern provides the string which will be used as a replacement. In this example, using psn:fred, the value fred would be matched by the matchPattern, and also captured (through the parentheses in the regular expression); it would then be replaced by the value ../../references/people/personography.xml#fred (with the the $1 in the replacementPattern being replaced by the captured value). The p element inside the prefixDef can be used to provide a human-readable explanation of the usage of this prefix.

-

Through this mechanism, any processor which encounters a teidata.pointer with a protocol unknown to it can check the listPrefixDef in the header to see if there is an available expansion for it, and if there is, it can automatically provide the expansion and generate a full or relative URI.

-

For any given prefix, it may be useful to supply more than one expansion. For instance, in addition to pointing at the person element in the personography file, it might also be useful to point to an external source which is available on the network, representing the same information in a different way. So there might be a second prefixDef like this: - - -

+

Private URIs with the prefix "psn" can be converted to point to a fragment on the Personography page of the project Website. -

- - +

Any number of prefixDef elements may be provided for the same prefix. A processor may decide to process one or all of them; if it processes only one, it should choose the first one with the correct ident value, so the primary or most important prefixDef for any given prefix should appear first in its parent listPrefixDef.

-

When creating private URI schemes, it is recommended that you avoid using any existing registered prefix. A list of registered prefixes is maintained by IANA at .

-

Note that this mechanism can also be used to dereference other abbreviated pointing systems which are based on prefixes, such as Tag URIs.

-

The matchPattern and replacementPattern attributes are also used in dereferencing canonical reference patterns, and further examples of the use of regular expressions are shown in .

-
- -
-TEI XPointer Schemes - -

The pointing schemes described in this chapter are part of a number of +

+ TEI XPointer Schemes +

The pointing schemes described in this chapter are part of a number of such schemes envisaged by the W3C, which together constitute a framework for addressing data within XML documents, known as the XPointer Framework (Grosso et al @@ -706,8 +514,7 @@ XPointer Framework (Grosso et al addressing methods, each of which is known as an XPointer Scheme. The W3C has predefined a set of such schemes, and maintains a register for their expansion.

- -

One important scheme, also defined by the W3C, and recommended +

One important scheme, also defined by the W3C, and recommended by these Guidelines is the xpath() pointer scheme, which allows for any part of an XML structure to be selected using the syntax defined by the XPath specification. This is further @@ -716,10 +523,9 @@ six other pointer schemes, which provide access to parts of an XML document such as points within data content or stretches of data content. These additional TEI pointer schemes are defined in sections to below.

- -
Introduction to TEI Pointers - -

Before discussing the TEI pointer schemes, we introduce slightly +

+ Introduction to TEI Pointers +

Before discussing the TEI pointer schemes, we introduce slightly more formally the terminology used to define them. So far, we have discussed only ways of pointing at components of the XML information set node such as elements and attributes. However, there is often a @@ -739,33 +545,24 @@ character positions (string-index(), into account. Conversely, XPath (disregarding functions that return atomic values) is a method for locating nodes in the tree and treats those nodes as indivisible units, meaning it is unable to address parts of nodes in their document context.

- -

The TEI pointer scheme thus distinguishes the following +

The TEI pointer scheme thus distinguishes the following kinds of object: - - -A node is an instance of one of the node kinds defined in +A node is an instance of one of the node kinds defined in the XQuery and XPath Data Model 3.1. It represents a single item in the XML information set for a document. For pointing purposes, the only nodes that are of interest are Text Nodes, -Element Nodes, and Attribute Nodes. - -A Sequence follows the definition in the XPath 3.1 Data +Element Nodes, and Attribute Nodes.A Sequence follows the definition in the XPath 3.1 Data Model, with one alteration. A Sequence is an ordered collection of zero or more items, where an item is either a node or a partial text node. - - -A Text Stream is the concatenation of the text nodes in a document +A Text Stream is the concatenation of the text nodes in a document and behaves as though all tags had been removed. A text stream begins at a reference node and encompasses all of the text inside that node (if any) and all the text following it in document order. In XPath terms, this would encompass all of the text nodes beginning at a particular node, and following it on the following axis. - - -A Point represents a dimensionless point between nodes or characters in +A Point represents a dimensionless point between nodes or characters in a document. Every point is adjacent to either characters or elements, and never to another point. Points can only be referenced in relation to an element or text node in the document (i.e. something addressable by either @@ -776,41 +573,25 @@ Note that points within attribute values cannot mark the beginning or end of a range extending beyond the attribute value, because points indicate a position within a document. Since attribute nodes are by definition un-ordered, they cannot be said to have a fixed position. - - +

- -

The TEI recommends the following seven pointer schemes: - - -Addresses a node or node sequence using the XPath syntax. () - -addresses the point before (left) or after (right) a node or node -sequence ( and ) - -addresses a point inside a text node ( - -addresses the range between two points () - -addresses a range of a specified length starting from a -specified point () - -addresses a range which matches a specified string within a node -() - +

The TEI recommends the following seven pointer schemes: +Addresses a node or node sequence using the XPath syntax. ()addresses the point before (left) or after (right) a node or node +sequence ( and )addresses a point inside a text node (addresses the range between two points ()addresses a range of a specified length starting from a +specified point ()addresses a range which matches a specified string within a node +()

-

The xpath() scheme refers to the +

The xpath() scheme refers to the existing XPath specification which is adopted with one modification: the default namespace for any XPath used as a parameter to this scheme is assumed to be the TEI namespace http://www.tei-c.org/ns/1.0.

-

The other six schemes overlap in functionality with a W3C draft +

The other six schemes overlap in functionality with a W3C draft specification known as the XPointer scheme draft, but are individually much simpler. At the time of this writing, there is no current or scheduled activity at the W3C towards revising this draft or issuing it as a recommendation.

- -

A note on namespaces: The W3C defines an +

A note on namespaces: The W3C defines an xmlns() scheme (see XPointer xmlns() Scheme) which when prepended to a resolvable pointer allows for the definition of @@ -822,12 +603,13 @@ provided no new prefixes need to be defined. If the schemes described here are used to address non-TEI elements, then any new prefixes to be used in pointer XPaths may be defined using the xmlns() scheme.

-
- -
-xpath() -

Sequence xpath(XPATH)

-

The xpath() scheme locates zero or more nodes within an XML +

+
+ xpath() +

+ Sequence xpath(XPATH) +

+

The xpath() scheme locates zero or more nodes within an XML Information Set. The single argument XPATH is an XPath selection pattern, as defined in XSLT 3.0, that returns a node or sequence of nodes. XPaths returning atomic values @@ -835,23 +617,20 @@ scheme.

scheme because they represent extracted values rather than locations in the source document. Because the schemes below involve starting at a node and navigating from there, and because attribute nodes have no intrinsic order, XPath expressions that address - attribute nodes should be avoided in schemes other than xpath().

-

The example below, and all subsequent examples in this section refer + attribute nodes should be avoided in schemes other than xpath().

+

The example below, and all subsequent examples in this section refer to the following TEI fragment: - -

+
si non habuiabui quidquam vaco sib cohorte mi rescribas semper in mentementem habeabe supra res scriptas -auge et opto ut bene valeas
- +auge et opto ut bene valeas

-

A TEI Pointer that referenced the reg element in the +

A TEI Pointer that referenced the reg element in the choice in line 1 of the example might look like: #xpath(//lb[@n='1']/following-sibling::choice[1]/reg). Note that XPath values must be assumed to start from the document root. They cannot be relative @@ -859,14 +638,14 @@ to the following TEI fragment: should be taken to ensure that XPaths used in TEI Pointers match only a single node, unless multiple matches are desired. The examples that follow are relatively simple because the document they refer to is short and does not contain many elements.

-

When an XPath is interpreted by a TEI processor, the +

When an XPath is interpreted by a TEI processor, the information set of the referenced document is interpreted without any additional information supplied by any schema processing that may or may not be present. In particular this means that no whitespace normalization is applied to a document before the XPath is interpreted.

-

This pointer scheme allows easy, direct use of the most +

This pointer scheme allows easy, direct use of the most widely-implemented XML query method. It is probably the most robust pointing mechanism for the common situation of selecting an XML element or its contents where an @@ -877,40 +656,44 @@ robust than the other mechanisms discussed in this section even if the designated document changes. For durability in the presence of editing, use of xml:id is always recommended when possible.

-
- -
-left() -

Point left( IDREF | XPATH )

-

The left() scheme locates the +

+
+ left() +

+ Point left( IDREF | XPATH ) +

+

The left() scheme locates the point immediately preceding the node addressed by its argument, which is either an XPATH as defined above or an IDREF, the value of an xml:id occurring in the document addressed by the base URI in effect for the pointer.

-

Example: the pointer #left(//supplied[1]) +

Example: the pointer #left(//supplied[1]) indicates the point between the first lb and the first supplied in the example above.

-

Example: #left(//gap[1]) indicates the point immediately before +

Example: #left(//gap[1]) indicates the point immediately before the first gap element in line two and the string si.

-

Example: #left(line1) indicates the point immediately before -the lb n="1" element.

- -
-right() -

Point right( IDREF | XPATH )

-

The right() scheme locates the +

Example: #left(line1) indicates the point immediately before +the lb n="1" element.

+
+
+ right() +

+ Point right( IDREF | XPATH ) +

+

The right() scheme locates the point immediately following the node addressed by its argument.

-

Example: the pointer #right(//lb[@n='3']) +

Example: the pointer #right(//lb[@n='3']) indicates the point between the third lb and the s]]> element in the example.

-
- -
-string-index() -

Point string-index( IDREF | XPATH, OFFSET )

-

The string-index() scheme locates a +

+
+ string-index() +

+ Point string-index( IDREF | XPATH, OFFSET ) +

+

The string-index() scheme locates a point based on character positions in a text stream relative to the node identified by the IDREF or XPATH parameter. The OFFSET parameter is a positive, negative, or zero integer which determines @@ -919,9 +702,9 @@ position immediately before the first character in either the first text node descendant of the node addressed in the first parameter or the first following text node, if the addressed element contains no text node descendants.

-

Example: #string-index(//lb[@n='2'],1) indicates the point +

Example: #string-index(//lb[@n='2'],1) indicates the point between the s and the i in the word si in line 2.

-

Note: The OFFSET parameter (and similarly the +

Note: The OFFSET parameter (and similarly the LENGTH parameter found below in the string-range() scheme) are measured in characters. What is considered a single character will depend on the Normalization Form in use (see @@ -929,19 +712,20 @@ depend on the Normalization Form in use (see FORMS). A letter followed by a combining diacritic counts as two characters, but the same diacritic precombined with a letter would count as a single character. Compare, for example, é (U+0060 -followed by U+0301) and é (>U+00E9). These are +followed by U+0301) and é (>U+00E9). These are equivalent, and a conversion between Normalization Forms C and D will transform one into the other. This specification does not mandate a particular Normalization Form (see ), but users and implementers should be aware that it affects the character count and therefore the result of evaluating pointers that rely on character counting.

-
- -
-range() -

Sequence range( POINTER, POINTER[, POINTER, POINTER ...])

-

The range() scheme takes as parameters one +

+
+ range() +

+ Sequence range( POINTER, POINTER[, POINTER, POINTER ...]) +

+

The range() scheme takes as parameters one or more pairs of POINTERs, which are each members of the set IDREF, XPATH, left(), right(), or @@ -953,24 +737,25 @@ that node is a member of the addressed sequence. If a sequence addressed by a range pointer overlaps, but does not wholly contain, an element (i.e. it contains only the start but not the end tag or vice-versa), then that element is not part of the sequence.

-

Range()s may address sequences of +

Range()s may address sequences of non-contiguous nodes. For example, a range() might select text beginning before an app, encompassing the content of a single rdg and continuing after the app.

-

Example: #range(left(//lb[@n='3']),left(//lb[@n='4'])) indicates +

Example: #range(left(//lb[@n='3']),left(//lb[@n='4'])) indicates the whole of line 3 from the ]]> to the point right before the following ]]>.

-

Example: #range(right(//lb[@n='3']),string-index(//lb[@n='3'],15)) +

Example: #range(right(//lb[@n='3']),string-index(//lb[@n='3'],15)) indicates the sequence semper in mente]]> (an element, a text node, another element, and a partial text node).

-

Example: #range(string-index(//lb[@n='3'],7),string-index(//lb[@n='3'],10),string-index(//lb[@n='3'],15),string-index(//lb[@n='3'],21)) indicates +

Example: #range(string-index(//lb[@n='3'],7),string-index(//lb[@n='3'],10),string-index(//lb[@n='3'],15),string-index(//lb[@n='3'],21)) indicates the non-contiguous sequence in mentem.

-
- -
-string-range() -

Sequence string-range(IDREF | XPATH, OFFSET, LENGTH[, OFFSET, LENGTH ...])

-

The string-range() scheme +

+
+ string-range() +

+ Sequence string-range(IDREF | XPATH, OFFSET, LENGTH[, OFFSET, LENGTH ...]) +

+

The string-range() scheme locates a sequence based on character positions in a text stream relative to the node identified by the first parameter. The location of the beginning of the addressed sequence is determined precisely @@ -982,37 +767,36 @@ the length of the text stream captured by the sequence. As with contain text nodes and elements. The string-range() scheme can accept multiple OFFSET, LENGTH pairs to address a non-contiguous sequence in much the -same way that range() can accept multiple pairs of pointers.

-

Because string-range() addresses points in the text stream, tags are +same way that range() can accept multiple pairs of pointers.

+

Because string-range() addresses points in the text stream, tags are invisible to it. For example, if an empty tag like lb is encountered while processing a string-range(), it will be included in the resulting sequence, but the LENGTH count will not increment when it is captured.

-

Example: #string-range(//lb[@n='5'],0,27) indicates +

Example: #string-range(//lb[@n='5'],0,27) indicates the whole of line 5 from the text immediately following the lb to the point right before the closing ab tag.

-

Example: #string-range(//lb[@n='3'],7,8) +

Example: #string-range(//lb[@n='3'],7,8) indicates the sequence in mente.

-

Example: #string-range(//lb[@n='3'],7,3,15,6) indicates +

Example: #string-range(//lb[@n='3'],7,3,15,6) indicates the non-contiguous sequence in mentem.

-
- -
-match() -

Sequence match(IDREF | XPATH, 'REGEX' [, INDEX])

-

The match scheme locates a sequence based on matching the REGEX parameter +

+
+ match() +

+ Sequence match(IDREF | XPATH, 'REGEX' [, INDEX]) +

+

The match scheme locates a sequence based on matching the REGEX parameter against a text stream relative to the reference node identified by the first parameter. REGEX is a regular expression as defined by XQuery 1.0 and XPath 2.0 Functions and Operators (Second Edition), with some modifications: - - Because the regular expression is delimited by apostrophe +Because the regular expression is delimited by apostrophe characters, any such characters (' or U+0027) occurring inside the expression must be escaped using the URI - percent-encoding scheme %27. - Regular expressions in match() are assumed to + percent-encoding scheme %27. Regular expressions in match() are assumed to operate in single-line mode. The end of the string to be matched against is either the end of the text contained by the element in the first parameter or the end of the document, if that parameter @@ -1020,27 +804,25 @@ modifications: therefore matches the beginning of the text stream inside or following the reference node, and the meta-character $ matches the end of that stream. - - + The optional INDEX parameter is an integer greater than 0 which specifies which match should be chosen when there is more than one possibility. If omitted, the first match in the text stream will be used to resolve the match().

-

Like string-range(), match() may capture elements +

Like string-range(), match() may capture elements in the indicated sequence, even though they are ignored for purposes of evaluating the match.

-

Example: #match(//lb[@n='5'],'opto.*valeas') indicates the sequence +

Example: #match(//lb[@n='5'],'opto.*valeas') indicates the sequence t bene valeas]]> in line 5.

-

Example: #match(//lb[@n='3'],'semper') would indicate the +

Example: #match(//lb[@n='3'],'semper') would indicate the word semper, but would not capture the unclear elements in semper]]>, just their text children.

-
-
-
-Canonical References - -

By canonical reference we mean any means +

+
+
+ Canonical References +

By canonical reference we mean any means of pointing into documents, specific to a community or corpus. For example, biblical scholars might understand Matt 5:7 to mean the book called Matthew, chapter @@ -1050,7 +832,7 @@ selecting the element which corresponds to the seventh div element within the fifth div element within the div element with the n attribute valued Matt.

-

Several elements in the TEI scheme (gloss, +

Several elements in the TEI scheme (gloss, ptr, ref, and term) bear a special attribute, cRef, just for this purpose. Using the system described in this section, an encoder may specify @@ -1062,7 +844,7 @@ it were the value of the target attribute. The cRef and target attributes are mutually exclusive: only one or the other may be specified on any given occurrence of an element.

-

For the cRef attribute to function as required, a mechanism is needed to define the +

For the cRef attribute to function as required, a mechanism is needed to define the mapping between (for example) the book called Matt and the part of the XML structure which corresponds with it. This is provided by the refsDecl element -

The example in section 10 is taken + or 18 USC Append.

The example in section 10 is taken from Subject Matter and Scope of - Copyright.

- + Copyright.

-

See for another related use of the matchPattern and replacementPattern attributes.

-
-
Miscellaneous Usages -

Canonical reference pointers are intended for use by TEI +

See for another related use of the matchPattern and replacementPattern attributes.

+
+
+ Miscellaneous Usages +

Canonical reference pointers are intended for use by TEI encoders. However, this specification might be useful to the development of a process for recognizing canonical references in non-TEI documents (such as plain text documents), possibly as part of their conversion to TEI.

-
+
Citation Structures

Citation structures provide a more thorough and concise mechanism for describing canonical references @@ -1222,38 +969,25 @@ to $ during processing.

describes a single step in a reference, such as Matt, and may nest to handle multi-part references.

The equivalent structure to the set of cRefPatterns in would be: - - - - - - - - - +

An application wishing to resolve a canonical reference such as Matt 5:7 might follow this procedure: - - Ascertain the correct refsDecl - following the rules summarized in section . - Begin with the outer citeStructure. If it has a delim attribute + Ascertain the correct refsDecl + following the rules summarized in section .Begin with the outer citeStructure. If it has a delim attribute and the reference begins with the value of delim then take the portion of - the reference after the value of delim as input for the next child citeStructure. - For each nested citeStructure, if the input reference string contains the value + the reference after the value of delim as input for the next child citeStructure.For each nested citeStructure, if the input reference string contains the value of the delim, then split the string on the value of the delim attribute. If the input string does not contain delim, then stop. Take the portion of the input string after the value of delim and use it as the input string for the child citeStructure. After processing the outer citeStructure, the output will be ('Matt 5:7'), after the second, ('Matt', '5:7'). The end result will be a - sequence like ('Matt','5','7'). - For each item in the resulting sequence, resolve the matching node by evaluating + sequence like ('Matt','5','7').For each item in the resulting sequence, resolve the matching node by evaluating the XPath in match with the predicate found in use, using the context of the previously matched node, if any. Start with the outer citeStructure and move to the next child citeStructure for each step in the sequence. For example, for the first citeStructure, we could construct an XPath //div[@n='Matt']. The full XPath after the reference Matt 5:7 is resolved will be - //div[@n='Matt']/div[@n='5']/div[@n='7']. - + //div[@n='Matt']/div[@n='5']/div[@n='7']. One advantage citeStructure has is that it can be used to generate canonical references, using the declared citation structure to query the text structure. This means it is possible to automatically produce a list of resolvable citations for a TEI document. It also @@ -1263,11 +997,7 @@ to $ during processing.

document sections they identify, using the citeData element. For example, if a TEI document is divided into chapters with a div per chapter and those chapters have titles, contained in head elements, then we might declare a citation structure for the document thus: - - - - - +

This specifies that chapter references are given in the form ch. n, where n is the position of the div in the body of the document, and that we may obtain @@ -1278,8 +1008,7 @@ to $ during processing.

Blocks, Segments, and Anchors - -

In this section, we discuss three general purposes elements which +

In this section, we discuss three general purposes elements which may be used to mark and categorize both a span of text and a point within one. These elements have several uses, most notably to provide elements which can be given identifiers for use when aligning or @@ -1289,28 +1018,18 @@ of the TEI markup scheme in a theory-neutral manner, by providing for two neutral or anonymous elements to which the encoder can add any meaning not supplied by other TEI defined elements. - - - - - + The elements anchor, ab, and seg are members of the class att.typed, from which they inherit the following attributes: - - - + The elements ab, and seg are members of the class att.fragmentable, from which they inherit the following attribute: - - - + The seg element is also a member of the class att.segLike from which it inherits the following attribute: - - - +

The anchor element may be thought of as an empty seg, or as an artifice enabling an identifier to be @@ -1349,18 +1068,13 @@ English. This was revised by young other similar element.

Several examples of uses for the seg element are provided elsewhere in these Guidelines. For example: - -as a means of marking segments significant in a metrical -or rhyming analysis (see section ) -as a means of marking typographic lines in drama (see -section ) or title pages (see section ) -as a means of marking prosody- or pause-defined units in -transcribed speech (see section ) -as a means of marking linguistic or other analyses in a + as a means of marking segments significant in a metrical +or rhyming analysis (see section )as a means of marking typographic lines in drama (see +section ) or title pages (see section )as a means of marking prosody- or pause-defined units in +transcribed speech (see section )as a means of marking linguistic or other analyses in a theory-neutral manner (see chapter passim)

- -

In the following simple example, the seg element simply +

In the following simple example, the seg element simply delimits the extent of a stutter, a textual feature for which no element is provided in these Guidelines. Don't say I-I-I'm afraid, Melvin, just say I'm afraid. @@ -1371,13 +1085,9 @@ that may be the output of an automatic parsing system. This example also demonstrates the use of the xml:id attribute to carry an identifier which other parts of a document may use to point to, or align with: - - Literate and illiterate speech - in a language like English - are plainly different. - +Literate and illiterate speechin a language like Englishare plainly different.

-

As the above example shows, seg elements may be +

As the above example shows, seg elements may be nested directly within one another, to any degree of analysis considered appropriate. This is taken a little further in the following example, where the type and @@ -1385,28 +1095,8 @@ following example, where the type and categorize each word of the sentence (the xml:id attributes have been removed to reduce the complexity of the example): - - -Literate -and -illiterate -speech - - -in -a -language -like -English - - -are -plainly -different - - . -

-

(The example values shown are chosen for simplicity of +LiterateandilliteratespeechinalanguagelikeEnglishareplainlydifferent.

+

(The example values shown are chosen for simplicity of comprehension, rather than verisimilitude). It should also be noted that specialized segment elements are defined in section to facilitate this particular kind of @@ -1417,19 +1107,14 @@ and characters, which may be felt preferable to the more generic approach typified by use of the seg element. Using these, the first phrase above might be encoded simply as - - Literate - and - illiterate - speech - +Literateandilliteratespeech Note the way in which the type attribute of these specialized elements now carries the value carried by the subtype attribute of the more general seg element. For an analysis not using these traditional linguistic categories however, the seg element provides a simple but powerful mechanism.

-

In language corpora and similar material, the seg +

In language corpora and similar material, the seg element may be used to provide an end-to-end segmentation as an alternative to the more specific s element proposed in chapter for the markup of orthographic @@ -1440,13 +1125,9 @@ mark both features within s-units and segments composed of s-units, as in the following example:See section , where the text from which this fragment is taken is analyzed. - - Sigmund, the son of Volsung, - was a king in Frankish country. - Sinfiotli was the eldest of his sons. - ... -

-

Like other elements, the seg tag must be properly +Sigmund, the son of Volsung, + was a king in Frankish country.Sinfiotli was the eldest of his sons. ...

+

Like other elements, the seg tag must be properly enclosed within other elements. Thus, a single seg element can be used to group together words in different sentences only if the sentences are not themselves tagged. The @@ -1457,16 +1138,15 @@ not. Give me a dozen. Or two or three.]]>

-

The part attribute may be used as one simple +

The part attribute may be used as one simple method of overcoming this restriction: -Give me a dozen. -Or two or three. +Give me a dozen.Or two or three. Another solution is to use the join element discussed in section ; this requires that each of the seg elements be given an identifier. For further discussion of this generic encoding problem, see also chapter .

-

The seg element has the same content as a paragraph +

The seg element has the same content as a paragraph in prose: it can therefore be used to group together consecutive sequences of model.inter class elements, such as lists, quotations, notes, stage directions, etc. as well @@ -1484,24 +1164,23 @@ codes. The description should be provided as a series of paragraphs within the segmentation element of the encoding description in the TEI header, as described in section .

-

The seg element may also be used to encode +

The seg element may also be used to encode simultaneous or mutually exclusive variants of a text when the more special purpose elements for simple editorial changes, abbreviation and expansion, addition and deletion, or for a critical apparatus are not appropriate. In these circumstances, one seg is encoded for each possible variant, and the set of them is enclosed in a choice element.

-

For example, if one were writing dual-platform instructions for +

For example, if one were writing dual-platform instructions for installation of software, it might be useful to use seg to record platform-specific pieces of mutually exclusive text. -…pressing option -alt-f will …

-

Elsewhere in this chapter we provide a number of examples +…pressing optionalt-f will …

+

Elsewhere in this chapter we provide a number of examples where the seg element is used simply to provide an element to which an identifier may be attached, for example so that another segment may be linked or related to it in some way.

-

The ab (anonymous block) element functions like the +

The ab (anonymous block) element functions like the seg element, but is used for portions of the text which occur at the chunk level (See ). It is therefore a member of the @@ -1509,13 +1188,11 @@ way.

but unlike p, ab may nest within other ab elements. So it may be used to represent texts with irregular chunk-level structures.

-

Probably the most common use for ab is as a container for +

Probably the most common use for ab is as a container for text that does not naturally belong in a paragraph. The text of an epitaph, for example, may not be paragraph-like, but still requires a container: - - - SACRED +SACRED to the memory of Mrs. ALICE HUTTON born at Chesterfield in @@ -1525,26 +1202,17 @@ a container: Septr. 26th. 1777. This stone is placed by her only Child - ANN BOOTH POLLOK - + ANN BOOTH POLLOK Encoders may also prefer to treat other types of short documents, such as receipts, in this way.

-

The ab element may also be used, for +

The ab element may also be used, for example, to tag the canonical verse divisions of Biblical texts: - - The First Book of Moses, Called - Genesis - - In the beginning God created the heaven and the -earth. - And the earth was without form, and void; and darkness +The First Book of Moses, CalledGenesisIn the beginning God created the heaven and the +earth.And the earth was without form, and void; and darkness was upon the face of the deep. And the Spirit of God -moved upon the face of the waters. - And God said, Let there be light: and there was -light. - - +moved upon the face of the waters.And God said, Let there be light: and there was +light.

-

In other cases, where the text clearly indicates paragraph +

In other cases, where the text clearly indicates paragraph divisions containing one or more verses, the p element may be used to tag the paragraphs, and the seg element used to subdivide them. The ab element is provided as @@ -1552,60 +1220,37 @@ an alternative to the p element; it may not be used within paragraphs. The seg element, by contrast, may appear only within and not between paragraphs (or anonymous block elements). - - Das Erste Buch Mose. - -

-Am Anfang schuff Gott Himel vnd Erden. -Vnd die Erde war wüst vnd leer / vnd es war +Das Erste Buch Mose.

Am Anfang schuff Gott Himel vnd Erden.Vnd die Erde war wüst vnd leer / vnd es war finster auff der Tieffe / Vnd der Geist Gottes schwebet auff - dem Wasser.

-

-Vnd Gott sprach / Es werde Liecht / Vnd es ward - Liecht.

- - + dem Wasser.

Vnd Gott sprach / Es werde Liecht / Vnd es ward + Liecht.

-

The ab element is also useful for marking dramatic +

The ab element is also useful for marking dramatic speeches when it is not clear whether the speech is to be regarded as prose or verse. If, for example, an encoder does not wish to express an opinion as to whether the opening lines of Shakespeare's The Tempest are to be regarded as -prose or as verse, they might be tagged as follows: - - Actus primus, Scena prima. - A tempestuous noise of +prose or as verse, they might be tagged as follows: Actus primus, Scena prima. A tempestuous noise of Thunder and Lightning heard: -Enter a Ship-master, and a Boteswaine. - Master. - Bote-swaine. - Botes. - Heere Master: What cheere? - Mast. - Good: Speake to th' Mariners: fall too't, yarely, +Enter a Ship-master, and a Boteswaine.Master.Bote-swaine.Botes.Heere Master: What cheere?Mast.Good: Speake to th' Mariners: fall too't, yarely, or we run our selues a ground, bestirre, bestirre. Exit. - - Enter Mariners. - Botes. - Heigh my hearts, cheerely, cheerely my harts: yare, yare: + Enter Mariners.Botes.Heigh my hearts, cheerely, cheerely my harts: yare, yare: Take in the toppe-sale: Tend to th' Masters whistle: Blow - till thou burst thy winde, if roome e-nough. - - + till thou burst thy winde, if roome e-nough. See further and .

- - - - - + + + + +
-Synchronization -

In the previous section we discussed two particular kinds of + Synchronization +

In the previous section we discussed two particular kinds of alignment: alignment of parallel texts in different languages; and alignment of texts and portions of an image. In this section we address another specialized form of alignment: synchronization. The need to @@ -1615,22 +1260,19 @@ may arise in any text in which quoted speech occurs, or events are described within a time frame. The methods described here are also generalizable for other kinds of alignment (for example, alignment of text elements with respect to space).

-
-Aligning Synchronous Events - -

Provided that explicit elements are available to represent the +

+ Aligning Synchronous Events +

Provided that explicit elements are available to represent the parts or places to be synchronized, then the global linking attribute synch may be used to encode such synchronization, once it has been identified. - - - + This is another of the attributes made globally available by the mechanism described in the introduction to this chapter. Alternatively, the link and linkGrp elements may be used to make explicit the fact that the synchronous elements are aligned.

-

To illustrate the use of these mechanisms for marking synchrony, +

To illustrate the use of these mechanisms for marking synchrony, consider the following representation of a spoken text:

-

This representation uses numbers in brackets to mark the points at +

This representation uses numbers in brackets to mark the points at which speakers overlap each other. For example, the [1] in A's first speech is to be understood as coinciding with the [1] in B's second speech.This sample is taken from a conversation collected and transcribed for the British National Corpus.

-

To encode this we use the spoken texts module, described +

To encode this we use the spoken texts module, described in chapter , together with the module described in the present chapter. First, we transcribe this text, marking the synchronous points with anchor elements, and @@ -1653,75 +1295,57 @@ providing a synch attribute on one of each of the pairs of synchronous anchors. As noted in the example given above (section ), correspondence, and hence synchrony, is a symmetric relation; therefore the attribute need only be specified on one of the pairs of synchronous anchors. -

- +
The first time in twenty five years, we've cooked Christmas for a blooming great - load of people. -So you're + load of people. So you're - -It will be + It will be nice in a way, but, - be strange. -Yeah + be strange. Yeah , yeah, cos it, its the - -not -

-

We can encode this same example using link and + not

+

We can encode this same example using link and linkGrp elements to make the temporal alignment explicit. A back element has been used to enclose the linkGrp element, but the links may be located anywhere the encoder finds convenient: - - - - - - - - - - + The xml:id attributes are provided for the link and linkGrp elements here for reasons discussed in the next section, .

-

As with other forms of alignment, synchronization may be expressed +

As with other forms of alignment, synchronization may be expressed between stretches of speech as well as between points. When complete utterances are synchronous, for example, if one person says What? and another No! at the same time, that can be represented without anchor elements as follows. -What? -No!

-

A simple way of expressing overlap (where one speaker +What?No!

+

A simple way of expressing overlap (where one speaker starts speaking before another has finished) is thus to use the seg element to encode the overlapping portions of speech. For example, - So you're - It will be nice in a way, but, - be strange. - Yeah , yeah, cos it, - its the - not + So you're It will be nice in a way, but, + be strange. Yeah , yeah, cos it, + its the not Note in this encoding how synchronization has been effected between an empty unclear element and the content of a seg element, and between the content of a u element and that of another seg, using the synch attribute. Alternatively, a linkGrp could be used in the same -way as above.

-
-Placing Synchronous Events in Time -

A synchronous alignment specifies which points in a spoken text occur +way as above.

+
+
+ Placing Synchronous Events in Time +

A synchronous alignment specifies which points in a spoken text occur at the same time, and the order in which they occur, but does not say at what time those points actually occur. If that information is available to the encoder it can be represented by means of the when and timeline elements, whose description and attributes are the following:

-

Each when element indicates a point in time, either directly +

Each when element indicates a point in time, either directly by means of the absolute attribute, whose value is a string which specifies a particular time, or indirectly by means of the since attribute, which points to another when. If @@ -1730,82 +1354,54 @@ the since is used, then the interval and time that has elapsed since the time specified by the element pointed to by the since attribute; the value -1 can be given to indicate that the interval is unknown.

-

If the when elements are uniformly spaced in time, then the +

If the when elements are uniformly spaced in time, then the interval and unit values need be given once in the timeline, and not repeated in any of the when elements. If the intervals vary, but the units are all the same, then the unit attribute alone can be given in the timeline element, and the interval attribute given in the when element.

-

The origin attribute in the timeline element +

The origin attribute in the timeline element points to a when element which specifies the reference or origin for the timings within the timeline; this must, of course, specify its position in time absolutely. If the origin of a timeline is unknown, then this attribute may be omitted.

-

The following timeline might be used to accompany the marked +

The following timeline might be used to accompany the marked up conversation shown in the preceding section: - - - - - - - - - + The information in this timeline could now be linked to the information in the linkGrp which provides the temporal alignment (synchronization) for the text, as follows: - - - - - - - -

-

To avoid the need for two distinct link groups (one marking the +

+

To avoid the need for two distinct link groups (one marking the synchronization of anchors with each other, and the other marking their alignment with points on the time line) it would be better to link the when elements with the synchronous points directly: - - - - - - - -

- - -

Finally, suppose that a digitized audio recording is also +

Finally, suppose that a digitized audio recording is also available, and an XML file that assigns identifiers to the various temporal spans of sound is available. For example, the following Synchronized Multimedia Integration Language (SMIL, pronounced "smile") fragment: - - + URIs pointing to the audio elements could also be included as a fourth component in each of the above link elements, thus providing a synchronized audio track to complement the transcribed text.

-

For further discussion of this and related aspects of encoding +

For further discussion of this and related aspects of encoding transcribed speech, refer to chapter .

- - - -
-
- -Correspondence and Alignment -

In this section we introduce the notions of + + + + +

+
+
+ Correspondence and Alignment +

In this section we introduce the notions of correspondence, expressed by the corresp attribute, and of alignment, which is a special kind of correspondence involving an ordered set of @@ -1814,27 +1410,25 @@ correspondences. Both cases may be represented using the section . We also discuss the special case of alignment in time or synchronization, for which special purpose elements are proposed in section .

-
- Correspondence -

A common requirement in text analysis is to represent +

+ Correspondence +

A common requirement in text analysis is to represent correspondences between two or more parts of a single document, or between places in different documents. Provided that explicit elements are available to represent the parts or places to be linked, then the global linking attribute corresp may be used to encode such correspondence, once it has been identified. - - - + This is one of the attributes made available by the mechanism described in the introduction to this chapter (). Correspondence can also be expressed by means of the link element introduced in section .

-

Where the correspondence is between spans, the +

Where the correspondence is between spans, the seg element should be used, if no other element is available. Where the correspondence is between points, the anchor element should be used, if no other element is available.

-

The use of the corresp attribute with spans of +

The use of the corresp attribute with spans of content is illustrated by the following example: Shirley, which made its Friday night debut only a month ago, was @@ -1854,7 +1448,7 @@ still is being considered. this attribute is used, therefore, encoders are encouraged to specify their intent in the associated encoding description in the TEI header.

-

Essentially, what the corresp attribute does is +

Essentially, what the corresp attribute does is to specify that elements bearing this attribute and those to which the attribute points are doubly linked. In the example above, the use of the corresp attribute indicates that the seg element containing the show and the @@ -1872,11 +1466,8 @@ its Friday night debut only a month ago, was not listed on NBC's new schedule, although the network says the show still is being considered. - - - -

-

In the following example, we use the same mechanism to +

+

In the following example, we use the same mechanism to express a correspondence amongst the anchors introduced following the fifth word after English in a text: @@ -1888,14 +1479,12 @@ English was still full of flaws English. This was revised by young - - - - -

-
- Alignment of Parallel Texts -

One very important application area for the alignment of + +

+
+
+ Alignment of Parallel Texts +

One very important application area for the alignment of parallel texts is multilingual corpora. Consider, for example, the need to align translation pairs of sentences drawn from a corpus such as @@ -1918,7 +1507,7 @@ English. This was revised by young results produced by a human judge.See , from which the example in the text is taken.

-

The alignment produced by Gale and Church's program can +

The alignment produced by Gale and Church's program can be expressed in four different ways. The encoder must first decide whether to represent the alignment in terms of points within each text (using the anchor element) or in @@ -1930,10 +1519,9 @@ English. This was revised by young either corresp attributes attached to the individual anchor or seg elements, or using a free-standing linkGrp element.

-

We present first a solution using anchor +

We present first a solution using anchor elements bearing only corresp attributes: -

-

According to our survey, 1988 +

According to our survey, 1988 sales of mineral water and soft drinks were much higher than in 1987, reflecting the growing popularity of these products. Cola drink manufacturers in particular achieved above-average growth rates. @@ -1943,10 +1531,7 @@ due to an increase in the sales volume. Following a two-year transitional period, the new Foodstuffs Ordinance for Mineral Water came into effect on April 1, 1988. Specifically, it contains more stringent requirements -regarding quality consistency and purity guarantees.

-
-
-

Quant aux eaux minérales +regarding quality consistency and purity guarantees.

Quant aux eaux minérales et aux limonades, elles rencontrent toujours plus d'adeptes. En effet, notre sondage fait ressortir des ventes nettement supérieures à celles de 1987, pour les boissons à base de cola @@ -1959,9 +1544,8 @@ sur les denrées alimentaires concernant entre autres les eaux minérales, entrée en vigueur le 1er avril 1988 après une période transitoire de deux ans, exige surtout une plus grande constance dans la qualité et une garantie de la -pureté.

-

-

There is no requirement that the corresp +pureté.

+

There is no requirement that the corresp attribute be specified in both English and French texts, since (as noted above) this attribute is defined as representing a mutual association. However, it may simplify processing to do @@ -1972,76 +1556,47 @@ pureté.

aligned, not simply the points themselves. If for example one text contained material omitted from the other, this approach would not be appropriate.

-

We now present the same passage using the alternative +

We now present the same passage using the alternative linkGrp mechanism and marking explicitly the segments which have been aligned: -

-

- According to our survey, 1988 sales of mineral +

According to our survey, 1988 sales of mineral water and soft drinks were much higher than in 1987, reflecting the growing popularity of these products. Cola drink manufacturers in particular achieved above-average -growth rates. - The higher turnover was largely due to an -increase in the sales volume. - Employment and investment levels also climbed. - Following a two-year transitional period, the new +growth rates.The higher turnover was largely due to an +increase in the sales volume.Employment and investment levels also climbed.Following a two-year transitional period, the new Foodstuffs Ordinance for Mineral Water came into effect on April 1, 1988. Specifically, it contains more stringent requirements regarding quality consistency and purity -guarantees.

-
-
-

- Quant aux eaux minérales et aux limonades, +guarantees.

Quant aux eaux minérales et aux limonades, elles rencontrent toujours plus d'adeptes. En effet, notre sondage fait ressortir des ventes nettement supérieures à celles de 1987, pour les -boissons à base de cola notamment. - La progression des chiffres d'affaires +boissons à base de cola notamment.La progression des chiffres d'affaires résulte en grande partie de l'accroissement du volume -des ventes. - L'emploi et les investissements ont -également augmenté. - La nouvelle ordonnance fédérale sur +des ventes.L'emploi et les investissements ont +également augmenté.La nouvelle ordonnance fédérale sur les denrées alimentaires concernant entre autres les eaux minérales, entrée en vigueur le 1er avril 1988 après une période transitoire de deux ans, exige surtout une plus grande constance dans la -qualité et une garantie de la pureté.

-
- - - - - -

-

Note that use of the ab element allows us to mark up the +qualité et une garantie de la pureté.

+

Note that use of the ab element allows us to mark up the orthographic sentences in both languages independently of the alignment: the first translation pair in this example might be marked up as follows: -

- - According to our survey, 1988 sales of mineral water and soft +
According to our survey, 1988 sales of mineral water and soft drinks were much higher than in 1987, reflecting the growing popularity -of these products. - Cola drink manufacturers in particular achieved above-average -growth rates. - -
-
- - Quant aux eaux minérales et aux limonades, elles -rencontrent toujours plus d'adeptes. - En effet, notre sondage fait ressortir des ventes nettement +of these products.Cola drink manufacturers in particular achieved above-average +growth rates.
Quant aux eaux minérales et aux limonades, elles +rencontrent toujours plus d'adeptes.En effet, notre sondage fait ressortir des ventes nettement supérieures à celles de 1987, pour les boissons à -base de cola notamment. - -
 -

-
-A Three-way Alignment -

The preceding encoding of the alignment of parallel passages from +base de cola notamment.

+

+
+
+ A Three-way Alignment +

The preceding encoding of the alignment of parallel passages from two texts requires that those texts and the alignment all be part of the same document. If the texts are in separate documents, then complete URIs, whether absolute or relative (section ), will be required. These external pointers may appear @@ -2049,53 +1604,28 @@ anywhere within the document, but if they are created solely for use in encoding links, they may for convenience be grouped within the linkGrp (or other grouping element that uses them for linking).

-

To demonstrate this facility, we consider how we might encode the +

To demonstrate this facility, we consider how we might encode the alignments in an extract from Comenius' Orbis Sensualium Pictus, in the English translation of Charles Hoole (1659). -

- -
+
Each topic covered in this work has three parts: a picture, a prose text in Latin describing the topic, and a carefully-aligned translation of the Latin into English, German, or some other vernacular. Key terms in the two texts are typographically distinct, and are linked to the picture by numbers, which appear in the two texts and within the picture as well.

-

First, we consider the text portions. The English and Latin portions +

First, we consider the text portions. The English and Latin portions have been encoded as distinct div elements. Identifiers have been attached to each typographic line, but no other encoding added, to simplify the example. -

- The Study -

-The Study -is a place -where a Student, -a part from men, -sitteth alone, -addicted to his Studies, -whilst he readeth -Books,

-
-
- Muséum -

-Museum -est locus -ubi Studiosus, -secretus ab hominibus, -solus sedet, -Studiis deditus, -dum lectitat -Libros,

-

- -

Next we consider the non-textual parts of the page. Encoding this +

Next we consider the non-textual parts of the page. Encoding this requires providing two distinct components: firstly a digitized rendering of the page itself, and secondly a representation of the areas within that image which are to be aligned. In section we present a @@ -2103,13 +1633,7 @@ simple way of doing this using the TEI-defined markup for alignment of facsimiles. In the present chapter we demonstrate a more powerful means of aligning arbitrary polygons and points, which uses the XML notation SVG (see SVG). This provides appropriate facilities for both these requirements: - - - - - - - + This example of SVG defines two rectangles at the locations with the specified x and y coordinates. A view is defined on these, enabling them to be @@ -2121,12 +1645,10 @@ alignment, as shown next (for further discussion of the handling of discussion of using non-TEI XML vocabularies such as SVG within a TEI document, see section ).

-

As printed, the Comenius text exhibits three kinds of alignment. - - The English and Latin portions are printed in two +

As printed, the Comenius text exhibits three kinds of alignment. + The English and Latin portions are printed in two parallel columns, with corresponding phrases, (represented above by - seg elements), more or less next to each other. - Particular words or phrases are marked as terms in the + seg elements), more or less next to each other.Particular words or phrases are marked as terms in the two languages by a change of rendition: the English text, which otherwise uses black letter type throughout, has the words The Study, a Student, @@ -2134,8 +1656,7 @@ alignment, as shown next (for further discussion of the handling of a roman font; in the Latin text, which is printed in roman, the corresponding words (Museum, Studiosus, Studiis, - and Libros) are all in italic. - Numbered labels appear within the text portions, + and Libros) are all in italic.Numbered labels appear within the text portions, linking keywords to each other and to sections of the picture. These labels, which have been left out of the above encoding, are attached to the first, third, and last segments in each language @@ -2144,34 +1665,20 @@ alignment, as shown next (for further discussion of the handling of books are each aligned with the correct term for them in the two languages.

-

The first kind of alignment might be represented by using the +

The first kind of alignment might be represented by using the corresp attribute on the seg element. The second kind might be represented by using the gloss and term mechanism described in section . The third kind of alignment might be represented using pointers embedded within the texts, for example: - - -where a Student, -ubi Studiosus, - - +where a Student,ubi Studiosus, We choose however to use the link element, since this provides a more efficient way of representing the three-way alignment between English, Latin, and picture without redundancy. - - - - - - - - - -

-

This map, of course, only aligns whole segments and image portions, +

+

This map, of course, only aligns whole segments and image portions, since these are the only parts of our encoding which bear identifiers and can therefore be pointed to. To add to it the alignment between the typographically distinct words mentioned above, new elements must @@ -2185,7 +1692,7 @@ to convey the wrong information about the words in question. Simply tagging them as additional embedded seg elements with identifiers that can be aligned like the others is also a possibility.

-

These solutions all require the addition of further markup to the text. This +

These solutions all require the addition of further markup to the text. This may pose no problems, or it may be infeasible, for example because the text is held on a read-only medium. If it is not feasible to add more markup to the original text, some form of stand-off markup will be @@ -2194,63 +1701,41 @@ various pointer schemes discussed in this chapter may be used, not simply those which rely on the existence of an xml:id attribute. Suppose our example had been more lightly tagged, as follows: - -

- The Study - The Study - is a place - where a Student, -
-
- Muséum - Museum - est locus - ubi Studiosus, -
-

-

To express the same alignment mentioned above, we could use an +

The StudyThe Studyis a placewhere a Student,
MuséumMuseumest locusubi Studiosus,

+

To express the same alignment mentioned above, we could use an XPath expression to identify the required ab elements: - - - - - + In the absence of any markup around individual substrings of the element content, the string-range pointer scheme discussed in may also be helpful: for example, to indicate that the words Studies and Studiis correspond, we might express the link between them as follows: - -

- -
-
-Identical Elements and Virtual Copies -

This section introduces the notion of a virtual element, +

+
+
+
+ Identical Elements and Virtual Copies +

This section introduces the notion of a virtual element, that is, an element which is not explicitly present in a text, but the presence of which an application can infer from the encoding supplied. In this section, we are concerned with virtual elements made by simply cloning existing elements. In the next section (), we discuss virtual elements made by aggregating existing elements.

-

Provided +

Provided that explicit elements are available to represent the parts or places to be linked, then the global linking attributes sameAs and copyOf may be used to encode this kind of equivalence: - - - +

-

It is useful to be able to represent the fact that one element of +

It is useful to be able to represent the fact that one element of text is identical to others, for analytical purposes, or (especially if the elements have lengthy content) to obviate the need to repeat the content. For example, consider the repetition of the date element in the following material:

In small clumsy letters he wrote: April 4th, -1984.

-

He sat back. A sense of complete helplessness had -descended upon him. ...

-

His small but childish handwriting straggled up +1984.

He sat back. A sense of complete helplessness had +descended upon him. ...

His small but childish handwriting straggled up and down the page, shedding first its capital letters and finally even its full stops: April 4th, 1984. @@ -2262,7 +1747,7 @@ could recode the last line of the above example as follows: April 4th, 1984 Last night to the flicks ...

-

The sameAs attribute may be used to document the fact +

The sameAs attribute may be used to document the fact that two elements have identical content. It may be regarded as a special kind of link. It should only be attached to an element with identical content to that which it targets, or to one the content of which @@ -2275,7 +1760,7 @@ bears a sameAs attribute indicating the first occurrence of the element concerned, it is implied that each chorus is identical, and there is no need for the first occurrence to specify any of its copies.

-

The copyOf attribute is used in a similar way to +

The copyOf attribute is used in a similar way to indicate that the content of the element bearing it is identical to that of another. The difference is that the content is not itself repeated. The effect of this attribute is thus to create a @@ -2283,7 +1768,7 @@ repeated. The effect of this attribute is thus to create a attribute, the repeated date in the first example above could be recoded as follows:

-

An application program should replace whatever is the actual content +

An application program should replace whatever is the actual content of an element bearing a copyOf attribute with the content of the element specified by it. If the content of the element specified includes other elements, these will become embedded within the element @@ -2293,35 +1778,17 @@ place. If, for example, the element bearing a copyOf attribute requires a mandatory sub-component, then this component must be present (though possibly empty), even though it will be replaced by the content of the targetted element.

-

The following example demonstrates how the copyOf +

The following example demonstrates how the copyOf attribute may be used in conjunction with the seg element to highlight the differences between almost identical repetitions: -Mikado - My object all sublime - I shall achieve in time— - To let the punishment fit the crime, - ; - And make each pris'ner pent - Unwillingly represent - A source of innocent merriment, - ! - -Chorus - His - He will - - - - - - - +MikadoMy object all sublimeI shall achieve in time—To let the punishment fit the crime,;And make each pris'ner pentUnwillingly representA source of innocent merriment,!ChorusHis He will

-

For further examples of the use of this attribute, see and .

-
-Aggregation -

Because of the strict hierarchical organization of elements, or for +

For further examples of the use of this attribute, see and .

+
+
+ Aggregation +

Because of the strict hierarchical organization of elements, or for other reasons, it may not always be possible or desirable to include all the parts of a possibly fragmented text segment within a single element. In section we introduced the notion of @@ -2335,35 +1802,26 @@ finally introduce the join element, which is a special-purpose linking element specifically for representing the aggregation of parts, and the joinGrp for grouping join elements.

-

The linking attributes for aggregation are next and +

The linking attributes for aggregation are next and prev; each of these attributes has a single identifier as its value:

-

It is recommended that the elements indicated by these attributes be of the same type as the element bearing them.

- -

The join element is also a member of the class of att.pointing elements, and so may carry any of the +

It is recommended that the elements indicated by these attributes be of the same type as the element bearing them.

+

The join element is also a member of the class of att.pointing elements, and so may carry any of the attributes of that class; for the list, see section .

-

Here is the material on which we base our first illustration of the +

Here is the material on which we base our first illustration of the use of these mechanisms. Our problem is to represent the s-units identified below as qs3 and qs4 as a single (but discontinuous) whole: Monsieur Paul, after he has taken equal parts of goose breast and the finest pork, and broken a certain number of egg yolks into them, and ground them very, very fine, -cooks all with seasoning for some three hours. - -But, -she pushed her face nearer, and looked with +cooks all with seasoning for some three hours.But,she pushed her face nearer, and looked with ferocious gloating at the pâté - inside me, her eyes like X rays, - - he never stops stirring it! - Figure to yourself the work of it — - stir, stir, never stopping! - + inside me, her eyes like X rays,he never stops stirring it!Figure to yourself the work of it —stir, stir, never stopping!

-

Using the prev and next attributes, we can +

Using the prev and next attributes, we can link the s-units with identifiers qs3 and qs4, either singly or doubly as follows: But, he never stops stirring it!]]> @@ -2374,10 +1832,10 @@ link the s-units with identifiers qs3 and qs4, either sing Double linking of the two s-units, as illustrated by the last of these encodings, is equivalent to specifying a link element:

-

Such a link element must carry a type +

Such a link element must carry a type attribute with a value of join to specify that the link is to be understood as joining its targets into a single aggregate.

-

The join element is equivalent to a link element of +

The join element is equivalent to a link element of type join. Unlike the link element, the join element can @@ -2395,49 +1853,38 @@ As a further example, consider the following list of authors' names. The object of the join element here is to provide another list, composed of those authors from the larger list who happen to come from Heidelberg: - -Authors - Figge, Udo - Heibach, Christiane - Heyer, Gerhard - Philipp, Bettina - Samiec, Monika - Schierholz, Stefan - - -Authors from Heidelberg

-

The following example shows how join can be used to +AuthorsFigge, Udo Heibach, Christiane Heyer, Gerhard Philipp, Bettina Samiec, Monika Schierholz, Stefan Authors from Heidelberg

+

The following example shows how join can be used to reconstruct a text cited in fragments presented out of order. The poem being remembered (an unusual translation of a well-known poem by Basho) runs When the old pond / gets a new frog, / it's a new pond.

- -Hughie -

How does it go? - - da-da-da - gets a new frog - ... - + + + Hughie +

How does it go? + da-da-dagets a new frog...

- -Louie -

- -When the old pond -... - -

- -Dewey -

- ... + + + Louie +

+ + When the old pond + ... + +

+ + + Dewey +

+ ... It's a new pond. -

- - - -

As with other forms of link, a grouping element joinGrp +

+ + + +

As with other forms of link, a grouping element joinGrp is available for use when a number of join elements of the same kind co-occur. This avoids the need to specify the result attribute for each join if they are all of @@ -2450,26 +1897,16 @@ represented by its contents are legal. Thus if we had created many together, and require that their components are all contained by an element with the identifier MFKFhungry as follows: - - - - - +

-

The join element is useful as a means of representing +

The join element is useful as a means of representing non-hierarchic structures (as further discussed in chapter ). It may also be used as a convenient way of representing a variety of analytic units, like the span and interp elements discussed in chapter . As an example, consider the following famous Zen koan: - -

Zui-Gan called out to himself every day, Master.

-

Then he answered himself, Yes, sir.

-

And then he added, Become sober.

-

Again he answered, Yes, sir.

-

And after that, he continued, do not be deceived by -others.

-

Yes, sir; yes, sir, he replied.

-

Suppose now that we wish to represent an interpretation of the above +

Zui-Gan called out to himself every day, Master.

Then he answered himself, Yes, sir.

And then he added, Become sober.

Again he answered, Yes, sir.

And after that, he continued, do not be deceived by +others.

Yes, sir; yes, sir, he replied.

+

Suppose now that we wish to represent an interpretation of the above passage in which we distinguish between the various voices adopted by Zui-Gan. In the following encoding, the who attribute has been used for this @@ -2480,32 +1917,18 @@ each voice as the target for these pointers.) Note also that we add xml:id attributes to each distinct speech fragment, which we can then use to link the material spoken by each voice: - - -

Zui-Gan called out to himself every day, - Master.

-

Then he answered himself, - Yes, sir.

-

And then he added, - Become sober.

-

Again he answered, - Yes, sir.

-

And after that, +

Zui-Gan called out to himself every day, + Master.

Then he answered himself, + Yes, sir.

And then he added, + Become sober.

Again he answered, + Yes, sir.

And after that, he continued, - do not be deceived by others.

-

Yes, sir; yes, sir, - he replied.

- -

-

However, by using the join element, we can directly + do not be deceived by others.

Yes, sir; yes, sir, + he replied.

+

However, by using the join element, we can directly represent the complete speech attributed to each voice: - - - what Zui-Gan said - - what Master said -

-

Note the use of the desc child element within the two +what Zui-Gan saidwhat Master said

+

Note the use of the desc child element within the two joins making up the q element here. These enable us to document the speakers of the two virtual q elements represented by the join elements; this is necessary because the @@ -2513,51 +1936,25 @@ there is no way of specifying the attributes to be associated with a virtual element, in particular there is no way to specify a who value for them.

-

Suppose now that xml:id attributes, for whatever +

Suppose now that xml:id attributes, for whatever reasons, are not available. Then ptr elements may be created using any of the methods described in section . The xml:id attributes of these elements may now be specified by the target attribute on the join elements. - - - - -

Zui-Gan called out to himself every day, Master.

-

Then he answered himself, Yes, sir.

-

And then he added, Become sober.

-

Again he answered, Yes, sir.

-

And after that, he continued, do not be deceived by others.

-

Yes, sir; yes, sir, he replied.

- - - - - - - - - - - what Zui-Gan said - - what Master said - - - -

-

The extended pointer with identifier +

Zui-Gan called out to himself every day, Master.

Then he answered himself, Yes, sir.

And then he added, Become sober.

Again he answered, Yes, sir.

And after that, he continued, do not be deceived by others.

Yes, sir; yes, sir, he replied.

what Zui-Gan saidwhat Master said

+

The extended pointer with identifier rzuiq2, for example, may be read as the first q in the first p, within the sixth div1 element of the current document.

- - - - -
-
-Alternation -

This section proposes elements for the representation of alternation. + + + + +

+
+ Alternation +

This section proposes elements for the representation of alternation. We say that two or more elements are in exclusive alternation if any of those elements could be present in a text, but one and only one of them is; in addition, we say that those elements @@ -2565,7 +1962,7 @@ are mutually exclusive. We say that the elements are in inclusive alternation if at least one (and possibly more) of them is present. The elements that are in alternation may also be called alternants.

-

The need to mark exclusive alternation arises frequently in text +

The need to mark exclusive alternation arises frequently in text encoding. A common situation is one in which it can be determined that exactly one of several different words appears in a given location, but it cannot be determined which one. One way to mark such an exclusive @@ -2579,30 +1976,25 @@ appears. To assign responsibility and degree of certainty to the choice, one can use the certainty tag described in chapter . Also see that chapter for further discussion of certainty in general.

-

The exclude and select attributes may be used +

The exclude and select attributes may be used with any element assuming that they have been declared following the procedure discussed in the introduction to this chapter. - - -

-

A more general way to mark alternation, encompassing both exclusive +

+

A more general way to mark alternation, encompassing both exclusive and inclusive alternation, is to use the linking element alt. The description and attributes of this tag and of the associated grouping tag altGrp are as follows. These elements are also members of the att.pointing class and therefore have all the attributes associated with that class.

-

To take a simple hypothetical example, suppose in transcribing a +

To take a simple hypothetical example, suppose in transcribing a spoken text, we encounter an utterance that we can understand either as We had fun at the beach today. or as We had sun at the beach today. We can represent the exclusive alternation of these two possibilities by means of the exclude attribute as follows. -

- We had fun at the beach today. - We had sun at the beach today. -

-

If it is then determined that the speaker said fun, +

We had fun at the beach today.We had sun at the beach today.

+

If it is then determined that the speaker said fun, not sun, the encoder could amend the text by deleting the alternant containing sun and the exclude attribute on the remaining alternant. Alternatively, the encoder could @@ -2610,71 +2002,47 @@ preserve the fact that there was uncertainty in the original transcription by retaining the alternants, and assigning the we.fun value to the select attribute value on the div element that encompasses the alternants, as in: -

- We had fun at the beach - today. - We had sun at the beach today. -

-

The above alternation (including the select attribute) +

We had fun at the beach + today.We had sun at the beach today.

+

The above alternation (including the select attribute) could be recoded by assigning the exclude attributes to tags that enclose just the words or even the characters that are mutually exclusive, as in:See section for discussion of the w and c tags that can be used in the following examples instead of the seg type="word" and seg type="character" tags. -

- We had +
We had fun sun - at the beach today. -
 -
- We had - -f -s + at the beach today.
 +
We had + fs un - at the beach today. -

-

Now suppose that the transcriber is uncertain whether the first word + at the beach today.

+

Now suppose that the transcriber is uncertain whether the first word in the utterance is We or Lee, but is certain that if it is Lee, then the other uncertain word is definitely fun and not sun. The three utterances that are in mutual exclusion can be encoded as follows. -

- - We had fun at the beach today. - We had sun at the beach today. - Lee had fun at the beach today. - -

-

The preceding example can also be encoded with exclude +

We had fun at the beach today.We had sun at the beach today.Lee had fun at the beach today.

+

The preceding example can also be encoded with exclude attributes on the word segments We, Lee, fun, and sun: - - We - Lee +WeLee had fun sun at the beach today.

-

The value of the select attribute is defined as a list of +

The value of the select attribute is defined as a list of identifiers; hence it can also be used to narrow down the range of alternants, as in: -

- We had fun at the beach today. - We had sun at the beach today. - Lee had fun at the beach today. -
+
We had fun at the beach today.We had sun at the beach today.Lee had fun at the beach today.
 This is interpreted to mean that either the first or the third u element tag appears, and is thus equivalent to just the alternation of those two tags: -
- We had fun at the beach - today. - Lee had fun at the beach today. -

-

The exclude attribute can also be used in case there is +

We had fun at the beach + today.Lee had fun at the beach today.

+

The exclude attribute can also be used in case there is uncertainty about the tag that appears in a certain position. For example, the occurrence of the word May in the s-unit Let's go to May can be interpreted, in the absence of @@ -2684,10 +2052,10 @@ attribute. Let's go to May .

-

Note the use of the copyOf attribute discussed in +

Note the use of the copyOf attribute discussed in section ; this avoids having to repeat the content of the element whose correct tagging is in doubt.

-

The copyOf and the exclude attributes also +

The copyOf and the exclude attributes also provide for a simple way of indicating uncertainty about exactly where a particular element occurs in a document.An alternative way of representing this problem is discussed in chapter . @@ -2699,39 +2067,28 @@ document, or as the first div2 of the second div1. One solution would be to record the div2 in its entirety in the first of these positions, and a virtual copy of it in the second, and mark them as excluding each other as follows: - - - - - - - - - + + In this case, the select attribute, if used, would appear on the body element.

-

Mutual exclusion can also be expressed using a link; the +

Mutual exclusion can also be expressed using a link; the first example in this section can be recoded by removing the exclude attributes from the u elements, and adding a link element as follows:In this example, we have placed the link next to the elements that represent the alternants. It could also have been placed elsewhere in the document, perhaps within a linkGrp. -

- We had fun at the beach today. - We had sun at the beach today. - -

-

Now we define the specialized linking element alt, making +

We had fun at the beach today.We had sun at the beach today.

+

Now we define the specialized linking element alt, making it a member of the class att.pointing, and assigning it a mode attribute, which can have either of the values excl (for exclusive) or incl (for inclusive). Then the following equivalence holds: =

-

The preceding link element may therefore be recoded as the +

The preceding link element may therefore be recoded as the following alt element.

-

Another attribute that is defined specifically for the alt +

Another attribute that is defined specifically for the alt element is weights, which is to be used if one wishes to assign probabilistic weights to the targets (alternants). Its value is a list of numbers, corresponding to the targets, expressing the @@ -2740,18 +2097,15 @@ is used to indicate whether the weights are stated as percentages (percent="Y", the default) or as the actual probabilities (percent="N")--> If the alternants are mutually exclusive, then the weights must sum to 1.0.

-

Suppose in the preceding example that it is equiprobable whether +

Suppose in the preceding example that it is equiprobable whether fun or sun appears. Then the alt element that represents the alternation may be stated as follows:

-

The assignment of a weight of 1.0 to one target (and weights of 0 +

The assignment of a weight of 1.0 to one target (and weights of 0 to all the others) is equivalent to selecting that target. Thus the following encoding is equivalent to the second example at the beginning of this section. -We had fun at the beach today. -We had sun at the beach today. - - +We had fun at the beach today.We had sun at the beach today. @@ -2805,16 +2159,14 @@ The sum of the weights for alt mode="incl" tags ranges from 0% to the alternation is equivalent to exclusive alternation; if the sum is (100 x k)%, then all of the alternants must appear, and the situation is better encoded without an alt tag.

- -

If it is desired, alt elements may be grouped together in +

If it is desired, alt elements may be grouped together in an altGrp element, and attribute values shared by the individual alt elements may be identified on the altGrp element. The targFunc attribute defaults to the value first.alternant next.alternant.

- -

To illustrate, consider again the example of a transcribed +

To illustrate, consider again the example of a transcribed utterance, in which it is uncertain whether the first word is We or Lee, whether the third word is fun or @@ -2829,39 +2181,31 @@ probability that fun occurs is 50% and that Lee occurs is 60%. This situation can be encoded as follows. - - We - Lee +WeLee had fun sun - at the beach today. - - - - - - + at the beach today. As noted above, when the mode attribute on an alt has the value incl, then each weight states the probability that the corresponding alternative occurs, given that at least one of the other alternatives occurs.

-

From the information in this encoding, we can determine that the +

From the information in this encoding, we can determine that the probability is about 28.5% that the utterance is We had fun at the beach today, 28.5% that it is We had sun at the beach today, and 43% that it is Lee had fun at the beach today.

-

Another very similar example is the following regarding the text of a +

Another very similar example is the following regarding the text of a Broadway song. In three different versions of the song, the same line reads Her skin is tender as a leather glove, Her skin is tender as a baseball glove, and Her skin is tender as Dimaggio's glove.The variant readings are found in the commercial sheet music, the performance score, and the Broadway cast recording.

-

If we wish to express this textual variation using the alt +

If we wish to express this textual variation using the alt element, we can record our relative confidence in the readings Dimaggio's (with probability 50%), a leather (25%), and a baseball (25%).

-

Let us extend the example with a further (imaginary) variation, +

Let us extend the example with a further (imaginary) variation, supposing for the sake of the argument that the next line is variously given as and she bats from right to left (with probability 50%) or now ain't that too damn bad (with @@ -2874,38 +2218,21 @@ contains Dimaggio's is 10%, and each of the others is 45%. This can be encoded, with an altGrp element containing a combination of exclusive and inclusive alt elements, as follows. -

- Her skin is tender as +
Her skin is tender as Dimaggio's a leather a baseball - glove, - and she bats from right to left. - now ain't that too damn bad. -
- - - - - - - - - - - -

- - - -
- -
-Stand-off Markup -
- Introduction - -

Most of the mechanisms defined in this chapter rely to a + glove,and she bats from right to left.now ain't that too damn bad.

+ + + + +
+
+ Stand-off Markup +
+ Introduction +

Most of the mechanisms defined in this chapter rely to a greater or lesser extent on the fact that tags in a marked-up document can both assert a property for a span of text which they enclose, and assert the existence of an association between @@ -2916,84 +2243,51 @@ combination of exclusive and inclusive alt elements, as follows. recommended by these Guidelines for this purpose is the standard XInclude mechanism defined by the W3C; another is to use pointers as demonstrated elsewhere in this chapter.

- -

There are many reasons for using stand-off markup: the source +

There are many reasons for using stand-off markup: the source text might be read-only so that additional markup cannot be added, or a single text may need to be marked up according to several hierarchically incompatible schemes, or a single scheme may need to accommodate multiple hierarchical ambiguities, so that a single markup tree is not the most faithful representation of the source material.

-

This section describes a generic mechanism for expressing +

This section describes a generic mechanism for expressing all kinds of markup externally as stand-off tags, for use whenever it is appropriate; and a place in the TEI structure (standOff) to contain certain common kinds of stand-off markup.

- -

Throughout this section the following terms will be systematically used in + +

Throughout this section the following terms will be systematically used in specific senses. - - - a document to which the stand-off markup refers (a source document can be either XML or - plain text); there may be more than one source document. - - markup that is already present in an XML source document - - markup that is either outside of the source document + a document to which the stand-off markup refers (a source document can be either XML or + plain text); there may be more than one source document.markup that is already present in an XML source documentmarkup that is either outside of the source document and points in to it to the data it describes, or is pointed at by the data that refers to it; or alternatively is in another part of the source document and points elsewhere within the document to the data it describes, or is pointed - at by data elsewhere that refers to it. - - a document that contains stand-off markup that points to a different, source document - - the action of creating a new XML document with external markup and data integrated with the - source document data, and possibly some source document markup as well - - a process applied to markup from a pre-existing XML + at by data elsewhere that refers to it.a document that contains stand-off markup that points to a different, source documentthe action of creating a new XML document with external markup and data integrated with the + source document data, and possibly some source document markup as wella process applied to markup from a pre-existing XML document, which splits it into two documents, an XML (external) document containing some of the markup of the original document, and another (source) XML document containing whatever text content and markup has not been extracted into the stand-off document; if all markup has been externalized from a document, the new source may be a plain - text document - + text document

-

The three major requirements satisfied by this scheme for stand-off markup are: - - any valid TEI markup can be either internal or - external, - external markup can be internalized by +

The three major requirements satisfied by this scheme for stand-off markup are: + any valid TEI markup can be either internal or + external,external markup can be internalized by applying it to the document content by either substituting the existing markup or adding to it, - to form a valid TEI document, and - the external markup itself specifies whether + to form a valid TEI document, andthe external markup itself specifies whether an internalized document is to be created by substituting the existing internal markup or by adding to - it. -

- - - -
- -
- Overview of XInclude -

Stand-off markup which relies on the inclusion of virtual + it.

+ +
+
+ Overview of XInclude +

Stand-off markup which relies on the inclusion of virtual content is adequately supported by the W3C XInclude recommendation, which is also recommended for use by these Guidelines.The version on which this text is based is the W3C Recommendation dated 20 December @@ -3008,16 +2302,14 @@ combination of exclusive and inclusive alt elements, as follows. requires support for the element() scheme of XPointer, these Guidelines permit the use of any of the pointing schemes discussed in section .

- -

XInclude is a W3C recommendation which specifies a syntax for the +

XInclude is a W3C recommendation which specifies a syntax for the inclusion within an XML document of data fragments placed in different resources. Included resources can be either plain text or XML. XInclude instructions within an XML document are meant to be replaced by a resource targetted by a URI, possibly augmented by an XPointer that identifies the exact subresource to be included.

- -

The xi:include element uses the href attribute to specify the location of +

The xi:include element uses the href attribute to specify the location of the resource to be included; its value is an URI containing, if necessary, an XPointer. Additionally, it uses the parse attribute (whose only valid values are text and xml) to specify whether @@ -3029,13 +2321,10 @@ combination of exclusive and inclusive alt elements, as follows. alternative content to be used when the external resource cannot be fetched for some reason. Its use is not however recommended for stand-off markup.

- -
-
- - Stand-off Markup in TEI - -

The operations of internalizing and externalizing markup are +

+
+ Stand-off Markup in TEI +

The operations of internalizing and externalizing markup are very useful and practically important. XInclude processing as defined by the W3C is internalization of one or more source documents' content into a stand-off document. TEI use of @@ -3053,8 +2342,7 @@ combination of exclusive and inclusive alt elements, as follows. in textual phenomena of interest is in fact the major reason that stand-off markup is needed. XInclude defines a semantics for this case that involves only complete elements.

- -

When a range selection partially overlaps a number of elements in a +

When a range selection partially overlaps a number of elements in a source document, XInclude specifies that the partially overlapping elements should be included as well as all completely overlapping elements and characters (partially overlapping characters are not @@ -3063,12 +2351,7 @@ or end of a selected range will be included as wrappers for those of their children that are completely or partially selected by the range. For example, given the following source document: - - -

home, home on Brokeback Mountain.

-

That was the song that I sang

- - +

home, home on Brokeback Mountain.

That was the song that I sang

 and the following external document:
description of overlapping markup structures.

- -

When overlapping hierarchies need to be represented @@ -3119,24 +2401,14 @@ The semantics of XInclude require the creation of well-formed XML results even t links and facilitating adjustments to the source document without breaking external documents that reference it.

- - -

Any tag can be externalized by + +

Any tag can be externalized by removing its content and replacing it with an xi:include element that contains an XPointer pointing to the desired content.

-

For instance the following portion of a TEI document: - - -1755 -To make a prairie it takes a clover and one bee, -One clover, and a bee, -And revery. -The revery alone will do, -If bees are few. - - +

For instance the following portion of a TEI document: +1755To make a prairie it takes a clover and one bee,One clover, and a bee,And revery.The revery alone will do,If bees are few. can be externalized by placing the actual text in a separate document, and providing exactly the same markup with the xi:include elements: @@ -3175,10 +2447,8 @@ If bees are few.\n ]]>

- - - -

Please note that this specification requires that the + +

Please note that this specification requires that the XInclude namespace declaration is present in all cases. The xi:fallback element contains text or XML fragments to be placed in the document if the inclusion fails for any @@ -3189,10 +2459,10 @@ If bees are few.\n for use with stand-off markup. These Guidelines recommend against the use of xi:fallback for stand-off markup.

-
-
- Well-formedness and Validity of Stand-off Markup -

The whole source fragment +

+
+ Well-formedness and Validity of Stand-off Markup +

The whole source fragment identified by an XInclude element, as well as any markup therein contained is inserted in the position specified, and an XInclude processor is required to ensure that the resulting @@ -3201,50 +2471,40 @@ If bees are few.\n document contains XML markup. A plain text source document will always create a well-formed internalized document.

-

While a TEI customization may permit +

While a TEI customization may permit xi:include elements in various places in a TEI document instance, in general these Guidelines suggest that validity be verified after the resolution of all the xi:include elements.

-
-
- Including Text or XML Fragments -

When the source text is plain text the overall form of the +

+
+ Including Text or XML Fragments +

When the source text is plain text the overall form of the XPointer pointing to it is of minimal importance. The form of the XPointer matters considerably, on the other hand, when the source document is XML.

-

In this case, it is rather important to distinguish whether +

In this case, it is rather important to distinguish whether we intend to substitute the source XML with the new one, or just to add new markup to it. The XPointers used in the references can express both cases.

-

A simple way is to make sure to select only textual data in +

A simple way is to make sure to select only textual data in the XPointer. For instance, given the following document: - - - -

To make a prairie it takes a clover - and one bee,
-
One clover, and - a bee,
-
And revery.
-
The revery alone will do,
-
If bees are few.
- - - +
To make a prairie it takes a clover + and one bee,
One clover, and + a bee,
And revery.
The revery alone will do,
If bees are few.
 the expression range(element(/1/2/1.0),element(/1/2/11.1)) will select the whole poem, text content and div elements and hypertext links (NB: in XPointer whitespace-only text nodes count).

-

On the contrary, the expressions +

On the contrary, the expressions xpointer(//text()/range-to(.)) and xpointer(string-range(//text(),"To")/range-to(//text(),"few.") will only select the text of the poem, with no markup inside.

-

Thus, the following could be a valid stand-off document for +

Thus, the following could be a valid stand-off document for the Source.xhtml document: @@ -3273,9 +2533,8 @@ will only select the text of the poem, with no markup inside.

]]>

-
-
- +
+
The standOff Container @@ -3285,11 +2544,8 @@ will only select the text of the poem, with no markup inside.

Examples include contextual information about named entities (typically encoded using listBibl, listOrg, listNym, listPerson, or listPlace), annotations indicating the morphosyntactic features of a text, and - annotations commenting on or associating parts of a text with additional information. - - + annotations commenting on or associating parts of a text with additional information.

-

As a member of model.resource, standOff may occur as a child of TEI (or teiCorpus). If the metadata that describes the standOff is largely the same as the metadata that describes the associated resource @@ -3297,65 +2553,11 @@ will only select the text of the poem, with no markup inside.

associated resource may appear as children of the same TEI element. The example below has a transcription with placename elements in the text linked to a list of place elements in the standOff section. - - - - - - - - - - Cilicia - https://pleiades.stoa.org/places/658440 - - - Creta - Crete - https://pleiades.stoa.org/places/589748 - - - - Rhodus - Rhodes - https://pleiades.stoa.org/places/590031 - - - Syria - https://pleiades.stoa.org/places/1306 - - - - - - -
-
- Bellum Alexandrinum -

- Bello Alexandrino conflato Caesar - - Rhodo - Ordo - atque ex Syria - Ciliciaque omnem classem arcessit; - Creta - certa - sagittarios, equites ab rege Nabataeorum + Ciliciahttps://pleiades.stoa.org/places/658440CretaCretehttps://pleiades.stoa.org/places/589748RhodusRhodeshttps://pleiades.stoa.org/places/590031Syriahttps://pleiades.stoa.org/places/1306

Bellum Alexandrinum

Bello Alexandrino conflato Caesar + RhodoOrdo atque ex Syria + Ciliciaque omnem classem arcessit; Cretacerta sagittarios, equites ab rege Nabataeorum Malcho euocat; tormenta undique conquiri et - frumentum mitti, auxilia adduci iubet. - -

- -
- -
- - - - + frumentum mitti, auxilia adduci iubet.

@@ -3369,11 +2571,7 @@ will only select the text of the poem, with no markup inside.

TEI documents. Targets are represented using the target attribute on annotation. URI bodies are represented using ref or ptr and embedded text bodies using note. Lifecycle and license information may be given using - respStmt, revisionDesc, and licence. - - -

- + respStmt, revisionDesc, and licence.

TEI annotations are, in general, intended to capture the output of processes that annotate TEI texts without altering the text and markup in the text. They allow this kind of output to be represented directly in TEI, and thus to be processed using the same toolchains @@ -3382,7 +2580,6 @@ will only select the text of the poem, with no markup inside.

to rewrite the TEI text using inline persName. Projects may wish to use this mechanism to layer information onto a TEI text in case where using inline elements might result in complicated markup.

-

The example below illustrates how stand-off annotations can be used to connect words in a text with place elements in a list. The words Gallia and Galliae in the edition are connected by an annotation in the standOff section which points to them @@ -3390,86 +2587,21 @@ will only select the text of the poem, with no markup inside.

the standOff section). If the set of annotations were created in a process separate from the creation of the transcription and then imported into the transcription document, then wrapping them in a TEI element with its own teiHeader providing metadata for - the annotations might be advisable. - - - - - De Bello Gallico - - - - - - -
-
-

- Gallia est omnis divisa in partes tres, quarum unam + the annotations might be advisable. De Bello Gallico

Gallia est omnis divisa in partes tres, quarum unam incolunt Belgae, aliam Aquitani, tertiam qui ipsorum lingua Celtae, nostra - Galli appellantur. - - Belgae ab extremis Galliae finibus oriuntur, + Galli appellantur.Belgae ab extremis Galliae finibus oriuntur, pertinent ad inferiorem partem fluminis Rheni, spectant in septentrionem et - orientem solem. - Aquitania a Garumna flumine ad Pyrenaeos montes et + orientem solem.Aquitania a Garumna flumine ad Pyrenaeos montes et eam partem Oceani quae est ad Hispaniam pertinet; spectat inter occasum solis - et septentriones.] - -

- -
- -
- - - - - - Gallia - Gaul - https://pleiades.stoa.org/places/993 - - - - - - - - - - - - - creator - Fred Editor - - - - - - - - - - - - - - - - - + et septentriones.]

GalliaGaulhttps://pleiades.stoa.org/places/993creatorFred Editor

-
- -
-Connecting Analytic and Textual Markup -

In chapters and and elsewhere, +

+ Connecting Analytic and Textual Markup +

In chapters and and elsewhere, provision is made for analytic and interpretive markup to be represented outside of textual markup, either in the same document or in a different document. The elements in these separate domains can be connected, @@ -3478,33 +2610,17 @@ either with the pointing attributes ana (for instance), or by means of link and linkGrp elements. Numerous examples are given in these chapters.

-

Another more specific form of annotation is available through the TEI ruby element and its +

Another more specific form of annotation is available through the TEI ruby element and its children, described in detail in .

- -
-
- Module for Linking, Segmentation, and Alignment -

The module described in this chapter makes available the +

+
+ Module for Linking, Segmentation, and Alignment +

The module described in this chapter makes available the following components: - - Linking, Segmentation, and Alignment - Linking, segmentation, and alignment - Liens, segmentation et alignement - 連結、分割與隊列 - Collegamento, segmentazione e allineamento - Ligação, segmentação e alinhamento - リンクモジュール - + Linking, Segmentation, and AlignmentLinking, segmentation, and alignmentLiens, segmentation et alignement連結、分割與隊列Collegamento, segmentazione e allineamentoLigação, segmentação e alinhamentoリンクモジュール The selection and combination of modules to form a TEI schema is described in . - - - - - - - - +

-
+
diff --git a/P5/Source/Guidelines/en/SG-GentleIntroduction.xml b/P5/Source/Guidelines/en/SG-GentleIntroduction.xml index 1a10159351..7f4e72fcef 100644 --- a/P5/Source/Guidelines/en/SG-GentleIntroduction.xml +++ b/P5/Source/Guidelines/en/SG-GentleIntroduction.xml @@ -1,17 +1,9 @@ - +
- -A Gentle Introduction to XML - -

The encoding scheme defined by these Guidelines is formulated as an + A Gentle Introduction to XML +

The encoding scheme defined by these Guidelines is formulated as an application of the Extensible Markup Language (XML) (). XML is widely used for the definition of device-independent, system-independent methods of storing and processing texts in electronic form. It is now also the @@ -21,8 +13,7 @@ its basic concepts and attempt to explain to the reader encountering them for the first time how and why they are used in the TEI scheme. More detailed technical accounts of TEI practice in this respect are provided in chapters , , and of these Guidelines.

- -

Strictly speaking, XML is a metalanguage, that is, a +

Strictly speaking, XML is a metalanguage, that is, a language used to describe other languages, in this case, markup languages. Historically, the word markup has been used to describe annotation or other @@ -33,7 +24,7 @@ be omitted or printed in a particular font, and so forth. As the formatting and printing of texts was automated, the term was extended to cover all sorts of special codes inserted into electronic texts to govern formatting, printing, or other processing.

-

Generalizing from that sense, we define markup, or +

Generalizing from that sense, we define markup, or (synonymously) encoding, as any means of making explicit an interpretation of a text. Of course, all printed texts are implicitly encoded (or marked up) in this sense: punctuation marks, @@ -49,15 +40,13 @@ classical period, words are written continuously with no intervening spaces or punctuation.; it is a process of making explicit what is conjectural or implicit, a process of directing the user as to how the content of the text should be (or has been) interpreted.

- -

By markup language we mean a set of markup conventions +

By markup language we mean a set of markup conventions used together for encoding texts. A markup language must specify how markup is to be distinguished from text, what markup is allowed, what markup is required, and what the markup means. XML provides the means for doing the first three; documentation such as these Guidelines is required for the last.

- -

The present chapter attempts to give an informal introduction to +

The present chapter attempts to give an informal introduction to those parts of XML of which a proper understanding is necessary to make best use of these Guidelines. The interested reader should also consult one or more of the many excellent introductory textbooks and @@ -67,35 +56,26 @@ select any one of them would be invidious. some recommended online courses include and .

- -
What's Special about XML? - -

XML has three highly distinctive advantages: - -it places emphasis on descriptive rather than -procedural markup; -it distinguishes the concepts of syntactic correctness and of -validity with respect to a document type definition; -it is independent of any one hardware or software +

+ What's Special about XML? +

XML has three highly distinctive advantages: +it places emphasis on descriptive rather than +procedural markup;it distinguishes the concepts of syntactic correctness and of +validity with respect to a document type definition;it is independent of any one hardware or software system. These three aspects are discussed briefly below, and then in more depth in the remainder of this chapter.

- -

XML is frequently compared with HTML, the language in which web +

XML is frequently compared with HTML, the language in which web pages have generally been written, which shares some of the above characteristics. Compared with HTML, however, XML has some other important features: XML is extensible: it does not consist of a fixed set of -tags; -XML documents must be well-formed according to a defined -syntax; -an XML document can be formally validated against a set of schema rules for consistent application; -XML is more interested in the meaning of data than in its +tags;XML documents must be well-formed according to a defined +syntax;an XML document can be formally validated against a set of schema rules for consistent application;XML is more interested in the meaning of data than in its presentation.

- -
Descriptive Markup - -

In a descriptive markup system, the markup codes used do little +

+ Descriptive Markup +

In a descriptive markup system, the markup codes used do little more than categorize parts of a document. Markup codes such as para or \end{list} simply identify a portion of a document and assert of it that the following item is a @@ -108,8 +88,7 @@ skip down one line, and go to the new left margin, etc. In XML, the instructions needed to process a document for some particular purpose (for example, to format it) are sharply distinguished from the markup used to describe it.

- -

Usually, the markup or other information needed to process a +

Usually, the markup or other information needed to process a document will be maintained separately from the document itself, typically in a distinct document called a stylesheet, though it may do much more than simply define the rendition or visual @@ -118,8 +97,7 @@ any detail the ways that a stylesheet can be used or defined, nor do we discuss the popular W3C Stylesheet Languages XSLT and CSS. See further , , and .

- -

When descriptive markup is used, the same document can +

When descriptive markup is used, the same document can readily be processed in many different ways, using only those parts of it which are considered relevant. For example, a content analysis program might disregard entirely the footnotes embedded in an @@ -130,11 +108,10 @@ For example, one program might extract names of persons and places from a document to create an index or database, while another, operating on the same text, but using a different stylesheet, might print names of persons and places in a distinctive typeface.

-
- -
Types of Document - -

A second key aspect of XML is its notion of a document +

+
+ Types of Document +

A second key aspect of XML is its notion of a document type: documents are regarded as having types, just as other objects processed by computers do. The type of a document is formally defined by its constituent parts and their structure. The definition @@ -146,8 +123,7 @@ consisted of a title and possibly an to this formal definition, would not formally be a report, and neither would a sequence of paragraphs followed by an abstract, whatever other report-like characteristics these might have for the human reader.

- -

If documents are of known types, a special-purpose program (called +

If documents are of known types, a special-purpose program (called a parser), once provided with an unambiguous definition of a document type, can check that any document claiming to be of that type does in fact conform to the specification. A parser @@ -158,11 +134,10 @@ documents of the same type can be processed in a uniform way. Programs can be written which take advantage of the knowledge encapsulated in the document type information, and which can thus behave in a more intelligent fashion.

-
- -
Data Independence - -

A basic design goal of XML is to ensure that documents encoded +

+
+ Data Independence +

A basic design goal of XML is to ensure that documents encoded according to its provisions can move from one hardware and software environment to another without loss of information. The two features discussed so far both address this requirement at an abstract level; @@ -182,7 +157,7 @@ known as Unicode.See - - -

Most modern computing systems now support Unicode directly; for +

Most modern computing systems now support Unicode directly; for those which do not, XML provides a mechanism for the indirect representation of single characters by means of their character number, known as character references; see further .

-
-
-
Textual Structures -

A text is not an undifferentiated sequence of words, much less of +

+
+
+ Textual Structures +

A text is not an undifferentiated sequence of words, much less of bytes. For different purposes, it may be divided into many different units, of different types or sizes. A prose text such as this one might be divided into sections, chapters, paragraphs, and sentences. A verse text might be divided into cantos, stanzas, and lines. Once printed, sequences of prose and verse might be divided into volumes, gatherings, and pages.

- -

Structural units of this kind are most often used to identify +

Structural units of this kind are most often used to identify specific locations or refer to points within a text (the third sentence of the second paragraph in chapter ten; canto 10, line 1234; page 412, etc.) but they may also be used to @@ -226,8 +200,7 @@ analysis is less useful for locating parts of the text (the 93rd speech by Horatio in Act 2) than for facilitating comparisons between the words used by one character and those of another, or those used by the same character at different points of the play.

- -

In a prose text one might similarly wish to regard as units of +

In a prose text one might similarly wish to regard as units of different types passages in direct or indirect speech, passages employing different stylistic registers (narrative, polemic, commentary, argument, etc.), passages of different authorship and so @@ -236,8 +209,7 @@ criticism) the physical appearance of one particular printed or manuscript source may be of importance: paradoxically, one may wish to use descriptive markup to describe presentational features such as typeface, line breaks, use of whitespace and so forth.

- -

These textual structures overlap with one another in complex and +

These textual structures overlap with one another in complex and unpredictable ways. Particularly when dealing with texts as instantiated by paper technology, the reader needs to be aware of both the physical organization of the book and the logical structure of the @@ -248,19 +220,18 @@ or paragraphs) and presentational ones (such as page divisions). For many types of research, the interplay among different levels of analysis is crucial: the extent to which syntactic structure and narrative structure mesh, or fail to mesh, for example, or the -extent to which phonological structures reflect morphology.

- -
XML Structures - -

This section describes the simple and consistent mechanism for the +extent to which phonological structures reflect morphology.

+
+
+ XML Structures +

This section describes the simple and consistent mechanism for the markup or identification of textual structure provided by XML. It also describes the methods XML provides for the expression of rules defining how units of textual structure can meaningfully be combined in a text.

- -
Elements - -

The technical term used in XML for a textual unit, viewed as a +

+ Elements +

The technical term used in XML for a textual unit, viewed as a structural component, is element. Different types of elements are given different names, but XML provides no way of expressing the meaning of a particular type of element, other than its @@ -277,7 +248,7 @@ intended use in text markup. That is the chief purpose of documents such as the TEI Guidelines. From the need to choose element names indicative of function comes the technical term for the name of an element type, which is generic identifier, or GI.

-

Within a marked-up text (a document instance), each +

Within a marked-up text (a document instance), each element must be explicitly marked or tagged in some way. This is done by inserting a tag at the beginning of the element (a start-tag) and another at its end (an @@ -306,17 +277,16 @@ silliest stuff that ere I heard of in the example above) is known as the content of the element. Sometimes there may be nothing between the start and the end-tag; in this case the two may optionally be merged together into a single composite tag with the -solidus at the end, like this: quote/.

- -
Content Models: an Example - -

An element may be empty, that is, it may have no +solidus at the end, like this: quote/.

+
+
+ Content Models: an Example +

An element may be empty, that is, it may have no content at all, or it may contain just a sequence of characters with no other elements. Often, however, elements of one type will be embedded (contained entirely) within elements of a different type.

- -

To illustrate this, we will consider a very simple structural +

To illustrate this, we will consider a very simple structural model. Let us assume that we wish to identify within an anthology only poems, their headings, and the stanzas and lines of which they are composed. In XML terms, our document type is the @@ -326,26 +296,8 @@ composed. In XML terms, our document type is the stanza, each stanza having embedded within it a number of line elements. Fully marked up, a text conforming to this model might appear as follows: - - - - The SICK ROSE - - O Rose thou art sick. - The invisible worm, - That flies in the night - In the howling storm: - - - Has found out thy bed - Of crimson joy: - And his dark secret love - Does thy life destroy. - - - -

-

It should be stressed that this example does not use +The SICK ROSEO Rose thou art sick.The invisible worm,That flies in the nightIn the howling storm:Has found out thy bedOf crimson joy:And his dark secret loveDoes thy life destroy.

+

It should be stressed that this example does not use the names proposed for corresponding elements elsewhere in these Guidelines: the above is thus not a valid TEI document.The element names here have been chosen for @@ -357,19 +309,15 @@ sake of visual clarity only; they have no particular significance in the XML encoding itself. Also, the line ]]> is an XML comment and is not treated as part of the text.

-

As it stands, the above example is what is known as a +

As it stands, the above example is what is known as a well-formed XML document because it obeys the following simple rules: - -there is a single element +there is a single element enclosing the whole document: this is known as the root -element (anthology in our case); -each element is completely contained by the root element, +element (anthology in our case);each element is completely contained by the root element, or by an element that is so contained; elements do not partially -overlap one another; -a tag explicitly marks the start and end of each element. - +overlap one another;a tag explicitly marks the start and end of each element.

-

A well-formed XML document can be processed in a number of useful +

A well-formed XML document can be processed in a number of useful ways. A simple indexing program could extract only the relevant text elements in order to make a list of headings, first lines, or words used in the poem text; a simple formatting program could insert blank @@ -388,8 +336,7 @@ of making sense of the tags embedded within it with no need for the sort of transformations and translations needed for files which have been saved in one or other of the proprietary formats preferred by most word-processing programs.

- -

As we noted above, one of the attractions of XML is that it enables +

As we noted above, one of the attractions of XML is that it enables us to apply our own names for the elements rather than requiring us always to use names predefined by other agencies. Clearly, however, if we wish to exchange our poems with others, or to include poems others @@ -416,8 +363,7 @@ tags belonging to different markup vocabularies; we discuss this further below (). One particularly useful namespace prefix is predefined for XML: it is xml and we will see examples of its use below.

- -

Namespaces allow us to represent the fact that a name belongs to a +

Namespaces allow us to represent the fact that a name belongs to a group of names, but don't allow us to do much more by way of checking the integrity or accuracy of our tagging. Simple well-formedness alone is not enough for the full range of what might be useful in marking up @@ -438,12 +384,11 @@ Definition, both abbreviated as DTD, may also be encountered. Throughout these Guidelines we use the term schema for any kind of formal document grammar.

-
-
- -
Validating a Document's Structure - -

The design of a schema may be as lax or as restrictive as the +

+
+
+ Validating a Document's Structure +

The design of a schema may be as lax or as restrictive as the occasion warrants. A balance must be struck between the convenience of following simple rules and the complexity of handling real texts. This is particularly the case when the rules being defined @@ -462,8 +407,7 @@ from an interpretation of a text. There is no single schema encompassing the absolute truth about any text, although it may be convenient to privilege some schemas above others for particular types of analysis.

- -

XML is widely used in environments where uniformity of document +

XML is widely used in environments where uniformity of document structure is a major desideratum. In the production of technical documentation, for example, it is of major importance that sections and subsections should be properly nested, that cross-references @@ -474,7 +418,7 @@ also greatly simplify the task of tagging accurately elements of less rigidly constrained texts. By making these schema rules explicit, scholars reduce their own burdens with consistently marking up and verifying the electronic text. By defining and sharing their schema rules, scholars openly express a project-specific interpretation of the structure and significant particularities of the text being encoded.

-

Schema validation for XML is usually written in the RELAX NG language () originally +

Schema validation for XML is usually written in the RELAX NG language () originally developed within the OASIS Technical Committee and now an ISO standardISO/IEC FDIS 19757-2 Document Schema Definition Language (DSDL) — Part 2: Regular-grammar-based @@ -483,9 +427,9 @@ text being encoded.

Guidelines, we give examples using the compact syntax of RELAX NG for ease of reading. The specifications for the TEI Guidelines are first expressed in the TEI language itself and a RELAX NG schema is generated from them for processing convenience. Details about schema customization using the TEI ODD language are addressed in , and .

- -
An Example Schema -

For the purposes of illustrating how a schema works to restrict how XML may be written, we use the RELAX NG compact syntax in what follows. The following schema can be used to validate our example poem: +

+ An Example Schema +

For the purposes of illustrating how a schema works to restrict how XML may be written, we use the RELAX NG compact syntax in what follows. The following schema can be used to validate our example poem:

- -

Note that this is not the only way in which a RELAX NG schema might +

Note that this is not the only way in which a RELAX NG schema might be written; we have adopted this idiom, however, because it matches that used throughout the rest of these Guidelines.

- -

A RELAX NG schema expresses rules about the possible structure of a +

A RELAX NG schema expresses rules about the possible structure of a document in terms of patterns; that is, it defines a number of named patterns, each of which acts as a kind of template against which an input document can be matched. The meaning of a @@ -521,14 +463,15 @@ word element, and the content model for the element is given within the curly braces following that. Each of these parts is discussed further below.

-

The last line of the schema above tells a RELAX NG validator which +

The last line of the schema above tells a RELAX NG validator which element (or elements) in a document can be used as the root element: in our case only anthology. This enables the validator to detect whether a particular document is well-formed but incomplete; it also simplifies the processing task by providing an entry point.

-
Generic Identifier -

Following the word element each pattern declaration gives +

+ Generic Identifier +

Following the word element each pattern declaration gives the generic identifier (often abbreviated to GI) of the element being defined, for example poem, heading, etc. A GI may contain letters, @@ -540,9 +483,11 @@ of namespaces, as further discussed in section foo is not the same as an element with the GI Foo; the root element of a TEI-conformant -document is TEI, not tei.

-
Content Model -

The second part of each declaration, enclosed in curly braces, is +document is TEI, not tei.

+
+
+ Content Model +

The second part of each declaration, enclosed in curly braces, is called the content model of the element being defined, because it specifies what may legitimately be contained within it. In RELAX NG, the content model is defined in terms of other patterns, either by @@ -558,11 +503,11 @@ branches of the tree downwards (for example, from antholo to poem to stanza to line and heading) will lead eventually to text. In our example, heading and line are so defined, since their content -models say text only and name no embedded elements.

- -
Occurrence Indicators - -

The declaration for stanza in the example above states +models say text only and name no embedded elements.

+
+
+ Occurrence Indicators +

The declaration for stanza in the example above states that a stanza consists of one or more lines. It uses an occurrence indicator (the plus sign) to indicate how many times something matching the pattern line_p may be @@ -579,10 +524,11 @@ permitted, but no stanza could have more than a single line. The declaration for poem in the example above thus states that a poem cannot have more than one heading, but may have none, and that it must have at least one stanza and may have -several.

- -
Connectors -

The content model {heading_p?, stanza_p+} contains more than +several.

+
+
+ Connectors +

The content model {heading_p?, stanza_p+} contains more than one component, and thus needs additionally to specify the order in which these patterns (heading_p and stanza_p) may appear. This ordering is determined by the connector (the comma) @@ -591,9 +537,11 @@ comma connector indicates that the patterns concerned must appear in the sequence given. Another commonly encountered connector is the vertical bar, representing alternation. If the comma in this example were replaced by a vertical bar, then a poem would consist of either a heading or just -stanzas—but not both!

-
Groups -

In our example so far, the components of each content model have +stanzas—but not both!

+
+
+ Groups +

In our example so far, the components of each content model have been either single patterns or text. We often need to define content models in more complicated ways, in which the components are lists of patterns, combined by connectors. Such lists may also be modified by occurrence indicators and themselves combined by @@ -612,7 +560,7 @@ for it. We could define a couplet as a firstLine fol

-

The patterns firstLine_p and secondLine_p define elements +

The patterns firstLine_p and secondLine_p define elements firstLine and secondLine; these will have exactly the same content model as the existing line element. We will therefore add the following two lines to our example schema: by applying the occurrence indicator to the group rather than to each element within it, would allow a single poem to contain a mixture of stanzas, couplets, and lines.

-

A group of this kind can contain text as well as named +

A group of this kind can contain text as well as named elements: this combination, known as mixed content, allows for elements in which the sub-components appear with intervening stretches of character data. For example, if we wished to @@ -637,16 +585,14 @@ assuming we have also added a pattern for the line to

- -

Some XML schema languages place no constraints on the way that +

Some XML schema languages place no constraints on the way that mixed content models may be defined, but in the XML DTD language, when text appears with other elements in a content model, it must always appear as the first option in an alternation; it may appear once only, and in the outermost model group; and if the group containing it is repeated, the star operator must be used. Although these constraints are not strictly necessary in RELAX NG schemas, all TEI content models currently obey them.

- -

Quite complex models can be built in this way, to match +

Quite complex models can be built in this way, to match the structural complexity of many types of text. For example, consider the case of stanzaic verse in which a refrain or chorus appears. Like a stanza, a refrain consists of repetitions of the line element. A refrain can appear at the start of a poem only, @@ -670,25 +616,25 @@ explicit by this content model are the requirements that at least one stanza must appear in a poem, if it is not composed simply of lines, and that if there is both a heading and a stanza they must appear in that order.

-

Note that the apparent complexity of this model derives from the +

Note that the apparent complexity of this model derives from the constraints expressed informally above. A simpler model, such as would not enforce any of them, and would therefore permit such anomalies as a poem consisting only of refrains, or an arbitrary mixture of lines and refrains.

- - - -

It is beyond the scope of this "Gentle Introduction to XML" to provide a complete orientation to schema writing with Relax NG, but interested readers may wish to consult more thorough tutorials on the subject.For a complete tutorial introduction to RELAX NG, see . The examples and explanation provided here may be helpful to consult when reading the schema declarations posted for groupings of TEI elements that share the same content model, such as macro.phraseSeq, whose declaration features an example of mixed text and element content. Due to the complexity of the TEI schema as expressed in Relax NG, it is best to customize its content model in TEI itself by writing an ODD, as discussed in .

-
-
-
-
Complicating the Issue -

In the simple cases described so far, we have assumed that one + +

It is beyond the scope of this "Gentle Introduction to XML" to provide a complete orientation to schema writing with Relax NG, but interested readers may wish to consult more thorough tutorials on the subject.For a complete tutorial introduction to RELAX NG, see . The examples and explanation provided here may be helpful to consult when reading the schema declarations posted for groupings of TEI elements that share the same content model, such as macro.phraseSeq, whose declaration features an example of mixed text and element content. Due to the complexity of the TEI schema as expressed in Relax NG, it is best to customize its content model in TEI itself by writing an ODD, as discussed in .

+
+
+
+
+ Complicating the Issue +

In the simple cases described so far, we have assumed that one can identify the immediate constituents of every element in a textual structure. A poem consists of stanzas, and an anthology consists of poems. Stanzas do not float around unattached to poems or @@ -699,11 +645,13 @@ ancestor at one end and many children (mostly the elements containing simple text) at the other. For example, we could represent an anthology containing two poems, the first of which contains two four-line stanzas and the second a single stanza, by a tree structure like the following figure:

-
- - - -

This graphic represents the hierarchical structure of an XML document, +

+ +
+ + + +

This graphic represents the hierarchical structure of an XML document, resembling a family tree. Most XML processing systems now use a standardized way of accessing parts of an XML document called XPath.The official specification is at ; many introductory tutorials are available in the XML references cited above @@ -720,7 +668,7 @@ poems contained by anthologies. An XPath expression can refer to any collection of elements: for example, the expression /anthology/poem refers to all poems in an anthology and the expression /anthology/poem/heading refers to all their headings.

-

The forward slash (‘/’, U+002F SOLIDUS) within an XPath expression behaves in much the same way +

The forward slash (‘/’, U+002F SOLIDUS) within an XPath expression behaves in much the same way as a forward slash or backslash does in a filename specification. To use a family tree analogy, a single slash indicates that the item to the immediate left is a parent of the item(s) to the right of it. For example, @@ -732,8 +680,7 @@ children, grandchildren, and other descendants of the family tree using two forward slashes together. For example, the XPath expression /anthology/poem//line will refer to all of the lines of all of the stanzas of all the poems, without having to represent the stanza element in the XPath.

- -

Clearly, there are many such trees that might be drawn to describe +

Clearly, there are many such trees that might be drawn to describe the structure of this or other anthologies. Some of them might be representable as further subdivisions of this tree: for example, we might subdivide the lines into individual words, since in our simple @@ -751,8 +698,7 @@ example, be interested in syntactic structures or other linguistic constructs, which rarely respect the formal boundaries of verse. Or, to take a simpler example, we might want to represent the pagination of different editions of the same text.

- -

In the OHCO model of text, representation of cases where different +

In the OHCO model of text, representation of cases where different elements overlap so that several different trees may be identified in the same document is generally problematic. All the elements marked up in a document, no matter what namespace they belong to, must fit @@ -767,11 +713,10 @@ in chapter of these Guidelines. These mechanisms all depend on the use of attributes, which may be used both to identify particular elements within a document and to point to, link, or align them into arbitrary structures.

- - -
-
Attributes -

In the XML context, the word attribute, like +

+
+ Attributes +

In the XML context, the word attribute, like some other words, has a specific technical sense. It is used to describe information that is in some sense descriptive of a specific element occurrence but not regarded as part of its content. For @@ -780,7 +725,7 @@ occurrences of some elements in a document to indicate their degree of reliability, or to add an identifier attribute so that you could refer to particular element occurrences from elsewhere within a document. Attributes are useful in precisely such circumstances.

-

Although different elements may have attributes with the same name +

Although different elements may have attributes with the same name (for example, in the TEI scheme, every element is defined as having an attribute named n), they are always regarded as different, and may have different values assigned to them. If an @@ -789,17 +734,15 @@ are supplied in the document instance as attribute-value pairs inside the start-tag for the element occurrence. An end-tag cannot contain an attribute-value specification, since it would be redundant.

-

The order in which attribute-value pairs are supplied inside a tag +

The order in which attribute-value pairs are supplied inside a tag has no significance; they must, however, be separated by at least one whitespace (blank, newline, or tab) character. The value part must always be given inside matching quotation marks, either single or doubleIn the unlikely event that both kinds of quotation marks are needed within the quoted string, either or both can also be presented in escaped form, using the predefined character entities &apos; or &quot;.

-

For example: - - ... - +

For example: + ... Here attribute values are being specified for two attributes previously declared for the poem element: xml:id and status. For the instance of a poem in this @@ -815,15 +758,13 @@ processed at all. The xml:id attribute is a slightly special case in that, by convention, it is always used to supply a unique value to identify a particular element occurrence, which may be used for cross-reference purposes, as discussed further below ().

- -
Declaring Attributes - -

Attributes are declared in a schema in the same way as elements. +

+ Declaring Attributes +

Attributes are declared in a schema in the same way as elements. As well as specifying an attribute's name and the element to which it is to be attached, it is possible to specify (within limits) what kind of value is acceptable for an attribute.

- -

In the compact syntax of RELAX NG, an attribute is defined by means +

In the compact syntax of RELAX NG, an attribute is defined by means of an attribute pattern, like the following: @@ -834,13 +775,11 @@ value is an attribute pattern defining an attribute named restrictions as other names in XML; they need not be unique across the whole schema, however, but only within the list of attributes for a given element.

- -

A pattern defining the possible values for this attribute is given +

A pattern defining the possible values for this attribute is given within the curly braces, in just the same way as a content model is given for an element pattern. In this case, the attribute's value must be one of the strings presented explicitly above.

- -

The attribute pattern definition must be included or referenced +

The attribute pattern definition must be included or referenced within the definition for every element to which the attribute is attached. We therefore modify the definition for the poem_p pattern given above as follows: @@ -859,8 +798,7 @@ will still be valid; without this occurrence indicator the status attribute would be required.

- -

Instead of supplying a list of explicit values, an attribute +

Instead of supplying a list of explicit values, an attribute pattern can specify that the attribute must have a value of a particular type, for example a text string, a numeric value, a normalized date, etc. This is accomplished by supplying a pattern @@ -876,8 +814,7 @@ unbroken string of characters (status="awful", valid for this attribute. Sometimes, of course, the set of possible values cannot be predefined. Where it can, as in this case, it is generally better to do so.

- -

Schema languages vary widely in the extent to which they support +

Schema languages vary widely in the extent to which they support validation of attribute values. Some languages predefine a small set of possibilities. Others allow the schema designer to use values from a predefined library of possible datatypes, or to @@ -892,22 +829,16 @@ and discussed further in ). In addition to the two possibilities already mentioned—plain text or an explicit list of possible strings—other datatypes likely to be encountered include the following: - - -values must be either true or false - -values must represent a numeric quantity of some -kind - -values must represent a possible date and time in some calendar -

-

Two further datatypes of particular usefulness in managing XML documents +values must be either true or falsevalues must represent a numeric quantity of some +kindvalues must represent a possible date and time in some calendar

+

Two further datatypes of particular usefulness in managing XML documents are commonly known as ID—for identifier—and URI—for Universal Resource Indicator, or pointer for short. These are discussed in the next section.

-
-
Identifiers and Indicators -

It is often necessary to refer to an occurrence of one textual +

+
+ Identifiers and Indicators +

It is often necessary to refer to an occurrence of one textual element from within another, an obvious example being phrases such as see note 6 or as discussed in chapter 5. When a text is being produced the actual numbers associated with the notes or @@ -925,7 +856,7 @@ identifier, its values must be unique within a given document. The cross-reference itself will be supplied by an element bearing an attribute of a specific kind, which must also be declared in the schema.

-

Suppose, for example, we wish to include a reference within +

Suppose, for example, we wish to include a reference within the notes on one poem that refers to another poem. We will first need to provide some way of attaching a label to each poem: this is easily done using the xml:id attribute. @@ -934,23 +865,16 @@ the parser may safely ignore the lack of one in those that do not. Only poems to which we intend to refer need use this attribute; for each such poem we should now include in its start-tag some unique identifier, for example: - - ... - - ... - - ... - + ... ... ...

-

Next we need to define a new element for the cross-reference +

Next we need to define a new element for the cross-reference itself. This will not have any content—it is only a pointer—but it has an attribute, the value of which will be the identifier of the element pointed at. This is achieved by the following definition:

- -

The poemRef element has no content, but a single attribute +

The poemRef element has no content, but a single attribute called target. The value of this attribute must be a pointer or web reference of type anyURI;The word anyURI is a predefined name, used in schema languages to mean that any Uniform Resource @@ -961,8 +885,7 @@ Schema datatype library. furthermore, because there is no indication of optionality on the attribute pattern, it must be supplied on each occurrence—a poemRef with no referent is an impossibility.

- -

With these declarations in force, we can now encode a reference to +

With these declarations in force, we can now encode a reference to the poem whose xml:id attribute specifies that its identifier is Rose as follows: @@ -977,7 +900,7 @@ xmlns="http://www.tei-c.org/ns/Examples">]]>) -->

-

A processor may take any number of actions when it encounters a +

A processor may take any number of actions when it encounters a link encoded in this way: a formatter might construct an exact page and line reference for the location of the poem in the current document and insert it, or just quote the poem's title or first lines. @@ -986,8 +909,7 @@ activate a link to the poem being referred to, for example by displaying it in a new window. Note, however, that the purpose of the XML markup is simply to indicate that a cross-reference exists: it does not necessarily determine what the processor is to do with it.

- -

The target of a URI can be located anywhere: it may not necessarily +

The target of a URI can be located anywhere: it may not necessarily be part of the same document, nor even located on the same computer system. Equally, it can be a resource of any kind, not necessarily an XML document or document fragment. It is thus a very convenient way of @@ -1000,24 +922,22 @@ with a target attribute of datatype URI: With these additions to the schema, we can now represent the location of the illustration within our text -like this: - By providing a location from which a reproduction of +like this: By providing a location from which a reproduction of the required image can be downloaded, this encoding makes it possible for appropriate software able to display the image as well as record its existence.

-

Attributes form part of the structure of an XML document in the +

Attributes form part of the structure of an XML document in the same way as elements, and can therefore be accessed using XPath. For example, to refer to all the poems in our anthology whose status attribute has the value draft, we might use an XPath such as /anthology/poem[@status='draft']. To find the headings of all such poems, we would use the XPath /anthology/poem[@status='draft']/heading.

-
-
- -
Other Components of an XML Document - -

In addition to the elements and attributes so far discussed, an XML +

+
+
+ Other Components of an XML Document +

In addition to the elements and attributes so far discussed, an XML document can contain a few other formally distinct things. An XML document may contain references to predefined strings of data that a validator must resolve before attempting to validate the document's @@ -1032,8 +952,7 @@ document is processed in a particular way by some class of processor formatter to start a new page at some specific point in a document); such flags are called processing instructions. We discuss each of these three cases in the rest of this section.

- -

The XML declaration should be supplied at the very +

The XML declaration should be supplied at the very beginning of every XML file; while it looks like a processing instruction, it is not, and may not occur anywhere other than at the very beginning of an XML file. For example: ). The XML declaration is documentary, but should normally be supplied at the start of any XML file. If it is missing many XML-aware processors will be unable to process the associated text correctly.

- -
Character References - -

As mentioned above, all XML documents use the same internal +

+ Character References +

As mentioned above, all XML documents use the same internal character encoding. Since not all computer systems currently support this encoding directly, a special syntax is defined that can be used to represent individual characters from the Unicode character set in a portable way by providing their numeric value, in decimal or hexadecimal notation.

- -

For example, the character é is represented +

For example, the character é is represented within an XML document as the Unicode character with hexadecimal value 00E9. If such a document is being prepared on (or exported to) a system using a different character set in which this @@ -1069,8 +986,7 @@ that what follows is a hexadecimal value) or &#0233; (its decimal equivalent). References of this type do not need to be predefined, since the underlying character encoding for XML is always the same.

- -

To aid legibility, however, it is also possible to use a mnemonic +

To aid legibility, however, it is also possible to use a mnemonic name (such as eacute) for such character references, provided that each such name is mapped to the required Unicode value by means of a construct known as an entity @@ -1078,8 +994,7 @@ declaration. A reference to a named character entity always takes the form of an ampersand, followed by the name, followed by a semicolon. For example an XML document containing the string T&C might be encoded as T&amp;C.

- -

There is a small set of such character +

There is a small set of such character entity references that do not have to be declared because they form part of the definition of XML. These include the names used for characters such as the ampersand (amp) and the open angle @@ -1089,8 +1004,7 @@ predeclared entity names are those for quotation marks (quot and apos for double and single respectively), and for completeness the closing angle bracket or greater-than sign (gt).

- -

For all other named character entities, a set of entity declarations +

For all other named character entities, a set of entity declarations must be provided to an XML processor before the document referring to them can be validated. The declaration itself uses a non-XML syntax inherited from SGML; for example, to define an entity named @@ -1100,20 +1014,17 @@ could have any of the following forms: ]]> or, using decimal notation: ]]>

- -

Entities of this kind are useful also for string +

Entities of this kind are useful also for string substitution purposes, where the same text needs to be repeated uniformly throughout a text. For example, if a declaration such as ]]> is included with a document, then references such as &TEI; may be used within it, each of which will be expanded in the same way and replaced by the string Text Encoding Initiative before the text is validated.

- - -
-
Namespaces - -

A valid XML document necessarily specifies the schema in which its +

+
+ Namespaces +

A valid XML document necessarily specifies the schema in which its constituent elements are defined. However, a well-formed XML document is not required to specify its schema (indeed, it may not even have a schema). It would still be useful to indicate that the element names used @@ -1122,7 +1033,7 @@ to include in a document elements that are defined (possibly differently) in different schemas. A cabinet-maker's schema might well define an element called table with very different characteristics from those of a documentalist's.

-

The concept of namespace was introduced into the XML +

The concept of namespace was introduced into the XML language as a means of addressing these and related problems. If the markup of an XML document is thought of as an expression in some language, then a namespace may be thought of as analogous to the @@ -1136,15 +1047,14 @@ is a set of element definitions, whereas a namespace is really only a property of a collection of elements: the only tangible form it takes in an XML document is its distinctive prefix and the identifying name associated with it.

- -

Suppose for example that we wish to extend our anthology to include +

Suppose for example that we wish to extend our anthology to include a complex diagram. We might start by considering whether or not to extend our simple schema to include XML markup for such features as arcs, polygons, and other graphical elements. XML can be used to represent any kind of structure, not simply text, and there are clear advantages to having our text and our diagrams all expressed in the same way.

-

Fortunately we do not need to invent a schema for the +

Fortunately we do not need to invent a schema for the representation of graphical components such as diagrams; it already exists in the shape of the Scalable Vector Graphics (SVG) language defined by the W3C.The W3C Recommendation is @@ -1158,72 +1068,38 @@ the document contains elements taken from the SVG namespace, if only to ensure that processing software does not confuse our line element with the SVG line, which means something quite different.

-

An XML document need not specify any namespace: it is then said to +

An XML document need not specify any namespace: it is then said to use the null namespace. Alternatively, the root element of a document may supply a default namespace, understood to apply to all elements which have no namespace prefix. This is the function of the xmlns attribute which provides a unique name for the default namespace, in the form of a URI: - - - - - + In exactly the same way, on the root element for each part of our document which uses the SVG language, we might introduce the SVG namespace name: - - - - - - - - - + Although a namespace name usually uses the URI (Uniform Resource Identifier) syntax, it is not treated as an online address and an XML processor regards it just as a string, providing a longer name for the namespace.

-

The xmlns attribute can also be used to associate a short prefix +

The xmlns attribute can also be used to associate a short prefix name with the namespace it defines. This is very useful if we want to mingle elements from different namespaces within the same document, since the prefix can be attached to any element, overriding the implicit namespace for itself (but not its children): - - - - - - - - - +

-

There is no limit on the number of namespaces that a document can +

There is no limit on the number of namespaces that a document can use. Provided that each is uniquely identified, an XML processor can identify those that are relevant, and validate them appropriately. To extend our example further, we might decide to add a linguistic analysis to each of the poems, using a set of elements such as aux, adj, etc., derived from some pre-existing XML vocabulary for linguistic analysis. - - - - - - - - O - Rose - thou - art - sick - - - +ORosethouartsick

- -
Marked Sections -

We mentioned above that the syntax of XML requires the encoder to +

+ Marked Sections +

We mentioned above that the syntax of XML requires the encoder to take special action if characters with a syntactic meaning in XML (such as the left angle bracket or ampersand) are to be used in a document to stand for themselves, rather than to signal the start of a @@ -1238,7 +1114,7 @@ namespace from that of the document itself, which is the approach taken in the present Guidelines. Another and simpler approach is provided by one of the features inherited by XML from its parent SGML: the marked section.

-

A marked section is a block of text within an XML document +

A marked section is a block of text within an XML document introduced by the characters <![CDATA[ and terminated by the characters ]]>. Between these rather strange brackets, markup recognition is turned off, and any tags or entity @@ -1248,13 +1124,11 @@ anthology, we may find ourselves often producing text like the following: line element: [...]]]]]>]]>

- -
-
- -
Processing Instructions - -

Although one of the aims of using XML is to remove any information +

+
+
+ Processing Instructions +

Although one of the aims of using XML is to remove any information specific to the processing of a document from the document itself, it is occasionally very convenient to be able to include such information—if only so that it can be clearly distinguished from the @@ -1267,7 +1141,7 @@ always be occasions when it may be necessary to override these. An XML processing instruction inserted into the document is one very simple and effective way of doing this without interfering with other aspects of the markup.

-

Here is an example XML processing instruction: Here is an example XML processing instruction: ]]> It begins with <? and ends with ?>. In between are two strings separated by a space: the first is the name of some processor (tex in the above @@ -1278,54 +1152,46 @@ must be a valid XML name other than XML, Xml, or xml, etc. The second string can be any arbitrary sequence of characters, not including the closing character-sequence ?>.

-
-
- -
Putting It All Together - -

In this chapter we have discussed most of the components of an XML +

+
+
+ Putting It All Together +

In this chapter we have discussed most of the components of an XML document and its associated schema. We have described informally how an XML document is represented, and also introduced one way of representing the rules a RELAX NG validator might use to validate it. In a working system, the following issues will also need to be addressed: - -how does a processor determine the schema (or schemas) that -should be used to validate a given XML document instance? -if a document contains entity references that must be processed before the -document can be validated, where are those entities defined? -an XML document instance may be stored in a number of different -operating system files; how should they be assembled together? -how does a processor determine which stylesheets it should use +how does a processor determine the schema (or schemas) that +should be used to validate a given XML document instance?if a document contains entity references that must be processed before the +document can be validated, where are those entities defined?an XML document instance may be stored in a number of different +operating system files; how should they be assembled together?how does a processor determine which stylesheets it should use when processing an XML document, or how to interpret any processing -instructions it contains? -how does a processor enforce more exact validation than simple -datatypes permit (for example of element content)? - +instructions it contains?how does a processor enforce more exact validation than simple +datatypes permit (for example of element content)?

- -

Different schema languages and different XML processing systems +

Different schema languages and different XML processing systems take very different positions on all of these topics, since none of them is explicitly addressed in the XML specification itself. Consequently, the best answer is likely to be specific to a particular software environment and schema language. Since this chapter is concerned with XML considered independently of its processing environment, we only -address them in summary detail here.

- -
Associating Entity Definitions with a Document +address them in summary detail here.

+
+ Associating Entity Definitions with a Document Instance -

In we introduced the syntax used for the +

In we introduced the syntax used for the definition of named character entities such as eacute, which XML inherited from SGML. Different schema languages vary in the ways they make a collection of such definitions available to an XML processor, but fortunately there is one method that all current schema languages support.

-

As well as, and following, the XML declaration (), an XML document instance may be prefixed with a +

As well as, and following, the XML declaration (), an XML document instance may be prefixed with a special DOCTYPE statement. This declarative statement has been inherited by XML from SGML; in its full form it provides a large number of facilities, but we are here concerned only with the small subset of those facilities recognized by all schema languages.

-

Here is an example DOCTYPE statement which we might consider +

Here is an example DOCTYPE statement which we might consider prefixing to the final version of our anthology: @@ -1344,11 +1210,11 @@ responsible for deciding the licensing conditions if they change their minds later. The word anthology following the string DOCTYPE in this example is, of course, the name of the root element of the document to which this declaration is prefixed; however, only an XML -DTD processor will take note of this fact.

- -
Associating a Document Instance with Its Schema - -

In the past, different schema languages adopted entirely different attitudes to +DTD processor will take note of this fact.

+
+
+ Associating a Document Instance with Its Schema +

In the past, different schema languages adopted entirely different attitudes to this question, leading to a variety of different methods of associating schemas with document instances. However, a W3C Working Group Note, Associating Schemas with XML documents, @@ -1368,8 +1234,7 @@ The href pseudo-attribute points to the lo See the XML Model WG Note for more information on the pseudo-attributes available and how to use them.

- -

A document instance may be valid according to many +

A document instance may be valid according to many different schemas, each appropriate to a different processing task. All of these may be expressed in the same way: @@ -1377,16 +1242,15 @@ different schemas, each appropriate to a different processing task. All of these This example includes a standard schema in XML Schema format, along with a Schematron schema which might be used for checking the format and linking of names.

- -

Any modern XML processing software tool will provide +

Any modern XML processing software tool will provide convenient methods of validating documents which are appropriate to the particular schema language chosen. In the interests of maximizing portability of document instances, they should contain as little processing-specific information as possible.

- -
-
Assembling Multiple Resources into a Single Document -

As we have already indicated, a single XML document may be made up +

+
+ Assembling Multiple Resources into a Single Document +

As we have already indicated, a single XML document may be made up of several different operating system files that need to be pulled together by a processor before the whole document can be validated. The XML DTD language defines a special kind of entity (a @@ -1395,16 +1259,17 @@ whole files into a document for this purpose, in much the same way as the character or string entities discussed in . Neither RELAX NG nor W3C Schema directly supports this mechanism, however, and we do not discuss it further here.

-

An alternative way of achieving the same effect is to use a special +

An alternative way of achieving the same effect is to use a special kind of pointer element to refer to the resources that need to be assembled, in exactly the same way as we proposed for the illustration in our anthology. The W3C Recommendation XML Inclusions (XInclude). defines a generic mechanism for this purpose, which is supported by an increasing number of XML -processors.

- -
Stylesheet Association and Processing -

As mentioned above, the processing of an XML document will usually +processors.

+
+
+ Stylesheet Association and Processing +

As mentioned above, the processing of an XML document will usually involve the use of one or more stylesheets, often but not exclusively to provide specific details of how the document should be displayed or rendered. In general, there is no reason to associate a document @@ -1412,7 +1277,7 @@ instance with any specific stylesheet and the schema languages we have discussed so far do not therefore make any special provision for such association. The association is made when the stylesheet processor is invoked, and is thus entirely application-specific.

-

However, since one very common application for XML documents is to +

However, since one very common application for XML documents is to serve them as browsable documents over the Web, the W3C has defined a procedure and a syntax for associating a document instance with its stylesheet (see ). This Recommendation @@ -1420,27 +1285,26 @@ allows a document to supply a link to a default stylesheet and also to categorize the stylesheet according to its MIME type, for example to indicate whether the stylesheet is written in CSS or XSLT, using a specialized form of processing instruction.

-

Assuming therefore that we have made a CSS-conformant stylesheet +

Assuming therefore that we have made a CSS-conformant stylesheet for our anthology and stored it in a file called anthology.css which is available from the same location as the anthology itself, we could make it available over the Web simply by adding a processing instruction like the following to the anthology: ]]>

-

Multiple stylesheets can be defined for the same document, and +

Multiple stylesheets can be defined for the same document, and options are available to specify how a web browser should select amongst them. For example, if the document also contained a directive: ]]>a different stylesheet called anthology_m.css could be used when rendering the document on a handheld device such as a mobile phone.

-

Most modern web browsers support CSS (although the extent +

Most modern web browsers support CSS (although the extent of their implementation varies), and some of them support XSLT.

- -
Content Validation - -

As we noted above, most schema languages provide some degree of +

+ Content Validation +

As we noted above, most schema languages provide some degree of datatype validation for attribute values (). They vary greatly in the validation facilities they offer for the content of elements, other than the syntactic constraints already discussed. Thus, while we may very easily check @@ -1451,8 +1315,7 @@ treated differently, it is difficult or impossible to express co-occurrence constraints: for example, if the status of a poem is draft we might wish to permit elements such as editorialQuery within its content, but not otherwise.

- -

The XML DTD language offers very little beyond syntactic checking +

The XML DTD language offers very little beyond syntactic checking of element content. By contrast, a major impetus behind the design and development of the W3C schema language was the addition of a much more general and powerful constraint language to the existing structural @@ -1469,10 +1332,11 @@ a different component of DSDL known as Schematron can be used. Schematron is a pattern matching (rather than a grammar-based) language, which allows us to test the components of a document against templates that express constraints such as those mentioned above.

- -

Like other XML processors, Schematron uses XPath to identify parts +

Like other XML processors, Schematron uses XPath to identify parts of an XML document; in addition, it provides elements that describe assertions to be tested and conditions which must be validated, as well as elements to report the results of the test.

+
+
+
-
diff --git a/P5/Source/Guidelines/en/ST-Infrastructure.xml b/P5/Source/Guidelines/en/ST-Infrastructure.xml index 7110750331..900fb3538e 100644 --- a/P5/Source/Guidelines/en/ST-Infrastructure.xml +++ b/P5/Source/Guidelines/en/ST-Infrastructure.xml @@ -1,11 +1,5 @@ - +
The TEI Infrastructure @@ -62,13 +56,9 @@ with others.-->

TEI Modules

These Guidelines define several hundred elements and attributes for marking up documents of - any kind. Each definition has the following components: - a prose description - a formal declaration, expressed using a special-purpose XML vocabulary defined by + any kind. Each definition has the following components: a prose descriptiona formal declaration, expressed using a special-purpose XML vocabulary defined by these Guidelines in combination with elements taken from the ISO schema language RELAX - NG - usage examples -

+ NGusage examples

Each chapter of these Guidelines presents a group of related elements, and also defines a corresponding set of declarations, which we call a module. All the definitions are collected together in the reference sections provided as an appendix. Formal declarations @@ -80,120 +70,7 @@ with others.-->

section below.

The following table lists the modules defined by the current release of these Guidelines: - - - Module name - Formal public identifier - Where defined - - - analysis - Analysis and Interpretation - - - - certainty - Certainty and Uncertainty - - - - core - Common Core - - - - corpus - Metadata for Language Corpora - - - - - dictionaries - Print Dictionaries - - - - drama - Performance Texts - - - - figures - Tables, Formulae, Figures - - - - gaiji - Character and Glyph Documentation - - - - header - Common Metadata - - - - iso-fs - Feature Structures - - - - linking - Linking, Segmentation, and Alignment - - - - msdescription - Manuscript Description - - - - namesdates - Names, Dates, People, and Places - - - - nets - Graphs, Networks, and Trees - - - - spoken - Transcribed Speech - - - - tagdocs - Documentation Elements - - - - tei - TEI Infrastructure - - - - - textcrit - Text Criticism - - - - textstructure - Default Text Structure - - - - transcr - Transcription of Primary Sources - - - - verse - Verse - - -
+ Module nameFormal public identifierWhere definedanalysisAnalysis and InterpretationcertaintyCertainty and UncertaintycoreCommon CorecorpusMetadata for Language CorporadictionariesPrint DictionariesdramaPerformance TextsfiguresTables, Formulae, FiguresgaijiCharacter and Glyph DocumentationheaderCommon Metadataiso-fsFeature StructureslinkingLinking, Segmentation, and AlignmentmsdescriptionManuscript DescriptionnamesdatesNames, Dates, People, and PlacesnetsGraphs, Networks, and TreesspokenTranscribed SpeechtagdocsDocumentation ElementsteiTEI InfrastructuretextcritText CriticismtextstructureDefault Text StructuretranscrTranscription of Primary SourcesverseVerse

For each module listed above, the corresponding chapter gives a full description of the classes, elements, and macros which it makes available when it is included in a schema. Other @@ -221,14 +98,7 @@ with others.-->

A Simple Customization

The simplest customization of the TEI scheme combines just the four recommended modules - mentioned above. In ODD format, this schema specification takes this form: - - - - - - -

+ mentioned above. In ODD format, this schema specification takes this form:

This schema specification contains references to each of four modules, identified by the key attribute on the moduleRef element. The schema specification itself is also given an identifier (TEI-minimal). An ODD processor will @@ -246,61 +116,32 @@ with others.-->

therefore, for clarity of exposition, each chapter focusses on elements drawn from a single module. In reality, of course, the markup of a text will draw on elements taken from many different modules, partly because texts are heterogeneous objects, and partly because - encoders have different goals. Some examples of this heterogeneity include: - a text may be a collection of other texts of different types: for example, an - anthology of prose, verse, and drama; - a text may contain other smaller, embedded texts: for example, a poem or song - included in a prose narrative; - some sections of a text may be written in one form, and others in a different form: + encoders have different goals. Some examples of this heterogeneity include: a text may be a collection of other texts of different types: for example, an + anthology of prose, verse, and drama;a text may contain other smaller, embedded texts: for example, a poem or song + included in a prose narrative;some sections of a text may be written in one form, and others in a different form: for example, a novel where some chapters are in prose, others take the form of - dictionary entries, and still others the form of scenes in a play; - an encoded text may include detailed analytic annotation, for example of rhetorical - or linguistic features; - an encoded text may combine a literal transcription with a diplomatic edition of the - same or different sources; - the description of a text may require additional specialized metadata elements, for - example when describing manuscript material in detail. -

+ dictionary entries, and still others the form of scenes in a play; an encoded text may include detailed analytic annotation, for example of rhetorical + or linguistic features; an encoded text may combine a literal transcription with a diplomatic edition of the + same or different sources; the description of a text may require additional specialized metadata elements, for + example when describing manuscript material in detail.

The TEI provides mechanisms to support all of these and many other use cases. The architecture permits elements and attributes from any combination of modules to co-exist within a single schema. Within particular modules, elements and attributes are provided to support differing views of the granularity of a text, for example: - - a definition of a corpus or collection as a series of TEI documents, - sharing a common TEI header (see chapter ) - a definition of composite texts which combine optional front- and back-matter with a - group of collected texts, themselves possibly composite (see section ) - an element for the representation of embedded texts, where one - narrative appears to float within another (see section ) -

+ a definition of a corpus or collection as a series of TEI documents, + sharing a common TEI header (see chapter )a definition of composite texts which combine optional front- and back-matter with a + group of collected texts, themselves possibly composite (see section )an element for the representation of embedded texts, where one + narrative appears to float within another (see section )

Subsequent chapters of these Guidelines describe in detail markup constructs appropriate for these and many other possible features of interest. The markup constructs can be combined as needed for any given set of applications or project.

For example, a project aiming to produce an ambitious digital edition of a collection of manuscript materials, to include detailed metadata about each source, digital images of the content, along with a detailed transcription of each source, and a supporting biographical - and geographical database might need a schema combining several modules, as follows: - - - - - - - - - - - - -

+ and geographical database might need a schema combining several modules, as follows:

Alternatively, a simpler schema might be used for a part of such a project: those preparing the transcriptions, for example, might need only elements from the core, textstructure, and transcr modules, and might therefore prefer to use a simpler schema such as that - generated by the following: - - - - - + generated by the following:

The TEI architecture also supports more detailed customization beyond the simple selection of modules. A schema may suppress elements from a module, suppress some of their attributes, @@ -368,15 +209,14 @@ with others.-->

some detail in the next section. A full list of all attribute classes is given in below.

Global Attributes -

The following attributes are defined in the infrastructure module for every TEI element. - - +

The following attributes are defined in the infrastructure module for every TEI element.

Some of these attributes (specifically xml:id, n, xml:lang, xml:base and xml:space) are provided by the att.global attribute class itself. The others are provided by one its subclasses att.global.rendition, att.global.responsibility, or att.global.source. - Their usage is discussed in the following subsections.

Several other globally-available + Their usage is discussed in the following subsections.

+

Several other globally-available attributes are defined by other subclasses of the att.global class. These are provided by other modules, and are therefore discussed in the chapter discussing that module. A brief summary table is provided in section below.

@@ -408,32 +248,15 @@ Georgie, and Dim, ... </p> label. For example, the numbers given to the items of a numbered list may be recorded with the n attribute; this would make it possible to record errors in the numeration of the original, as in this list of chapters, transcribed from a faulty - original in which the number 10 is used twice, and 11 is omitted: - About These Guidelines - A Gentle Introduction to XML - Verse - Drama - Spoken Materials - Dictionaries - The n attribute may also be used to record non-unique names + original in which the number 10 is used twice, and 11 is omitted: About These GuidelinesA Gentle Introduction to XMLVerseDramaSpoken Materials Dictionaries The n attribute may also be used to record non-unique names associated with elements in a text, possibly together with a unique identifier as in the - following example:
- -
- -
-
+ following example:

As noted above there is no requirement to record a value for either the xml:id or the n attribute. Any XML processor can identify the sequential position of one element within another in an XML document without any additional tagging. An encoding in which each line of a long poem is explicitly labelled - with its numerical sequence such as the following - - - - - is therefore probably redundant.

+ with its numerical sequence such as the following is therefore probably redundant.

Language Indicators @@ -451,59 +274,16 @@ Georgie, and Dim, ... </p> should be explicitly identified by use of the xml:lang attribute on an element at an appropriate level wherever possible.

In the following example schematic, an English language TEI header is attached to an - English language text: - - - - - - - - + English language text:

The same effect would be obtained by specifying the default language for both header - and text: - - - - - - - - + and text:

The latter approach is necessary in the case where the two differ: for example, where - an English language header is applied to a French text: - - - - - - - - + an English language header is applied to a French text:

The same principle applies at any hierarchic level. In the following example, the - default language of the text is French, but one section of it is in German: - - - - - - -

- -
-
- -
-
- -
- - - - + default language of the text is French, but one section of it is in German:

Similarly, in the following example the xml:lang attribute on the term element allows us to record the fact that the technical terms used are @@ -545,27 +325,7 @@ Georgie, and Dim, ... </p>

The rendition element defined in may be used to hold repeatedly-used format descriptions. A rendition element can then be associated with any element, either by default, or by means of the global rendition - attribute. For example: - - - font-style: italic; - - font-family: serif; - - - - -

-

- -

-

- -

-
- - - + attribute. For example: font-style: italic;font-family: serif;

The rendition attribute always points to one or more rendition elements, each of which defines some aspect of the rendering or appearance of the text @@ -587,19 +347,14 @@ Georgie, and Dim, ... </p> stylesheet. The TEI uses such languages simply to describe the appearance of a source document, rather than to control how it should be formatted.

In the TEI scheme, it is possible to supply information about the appearance of - elements within a source document in the following distinct ways: - One or more properties may be specified as the + elements within a source document in the following distinct ways: One or more properties may be specified as the default for a set of elements (based on an external scheme, by default CSS), using rendition elements - and their selector attributes; - One or more properties may be specified for individual element occurrences, + and their selector attributes;One or more properties may be specified for individual element occurrences, using the rend attribute with any convenient set of one or more - sequence-indeterminate tokens; - One or more properties may be specified for individual element occurrences, - using the rendition attribute to point to rendition elements; - One or more properties may be supplied explicitly for individual element - occurrences, using the style attribute. - + sequence-indeterminate tokens; One or more properties may be specified for individual element occurrences, + using the rendition attribute to point to rendition elements; One or more properties may be supplied explicitly for individual element + occurrences, using the style attribute.

If the same property is specified in more than one of the above ways, the one with the highest number in the list above is understood to be applicable. The resulting @@ -616,15 +371,12 @@ Georgie, and Dim, ... </p> source document, not intended output renditions, although often the two may be closely related.

- -
Sources, certainty, and responsibility

The source attribute is used to indicate the source of an element and its content, for example by pointing to a bibliographic citation for a quotation to indicate the source from which it derives. The target of the pointer may be an entry in a bibliographic list of some kind, or a pointer to a digital version of the source itself.

- -

As with other TEI pointers, the value of this attribute +

As with other TEI pointers, the value of this attribute is expressed as any form of URI, for example an absolute URL, a relative URL, or a private scheme URI that is expanded to a relative or absolute URL as documented in a @@ -633,32 +385,20 @@ Georgie, and Dim, ... </p> to point to a bibl elsewhere in the bibliography of the document which contains a bibliographic source for the quotation itself: - -

- - Grammatical theories +

Grammatical theories are in flux, and the more we learn, the less we - seem to know. - -

- - The Chicago Manual of Style, + seem to know.

The Chicago Manual of Style, 15th edition. Chicago: University of Chicago Press (2003), p.147. - -

+

+

Alternatively, the quotation might be directly linked to the online edition of this source using a full URI : - -

- - Grammatical theories +

Grammatical theories are in flux, and the more we learn, the less we - seem to know. - -

+ seem to know.

The source attribute is @@ -666,19 +406,14 @@ Georgie, and Dim, ... </p> the location from which declarations for the components being defined may be obtained by an ODD processor. For example, a customization wishing to include the p element specifically as it was in version 2.0.1 of TEI P5 would indicate the source for this on an elementRef element like the following: - - - + Here the value of the source attribute is provided using private URI syntax, using a short cut predefined for the TEI Guidelines. More generally, an ODD customization can point to a URI from which a compiled version of any ODD can be downloaded. The above shortcut is equivalent to - - - + Elements such as moduleRef or elementRef can use the source attribute in this way to point to any previously compiled set of TEI ODD specifications which are to be included in a schema, as further discussed in section

-

The cert attribute provides a method of indicating the encoder's certainty concerning an intervention or interpretation represented by the markup. It is typically used where the encoder wishes to supply one or more possible corrections to a text, indicating the @@ -702,26 +437,12 @@ for they shall be called the children of God. but a more precise element such as respStmt, author, or editor which can document the exact role played by the agent. In the following example, we indicate that the correction of n to u was made by a particular named transcriber: - - - - - Punkes, Panders, baſe extortionizing - slanues, - - - - - - Transcriber - Janelle Jenstad - - + Punkes, Panders, baſe extortionizing + slanues,TranscriberJanelle Jenstad Pointing to multiple respStmts allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, transcribing, encoding, editing, proofing etc.). If appropriate, the name element inside a respStmt may also be associated with a more detailed person or org element using methods discussed in chapter .

-
Evaluation of Links

Several TEI elements carry attributes whose values are defined as anyURI, @@ -733,21 +454,7 @@ for they shall be called the children of God. information about xml:base is provided by

In essence xml:base is used to set a context for all relative URLs within - the scope of the element on which it is specified. For example: - -

-

- - -

-
-
-

- - -

-
- The first ptr element here is within the scope of a + the scope of the element on which it is specified. For example:

The first ptr element here is within the scope of a div which supplies a value for xml:base; its target is therefore to be found at http://www.example.org/elsewhere.xml. The second ptr, however, is within the scope of a div which does not change the @@ -787,12 +494,7 @@ for they shall be called the children of God. in a given case, depending on an element's content model. For an element that can contain only other elements with no intervening non-whitespace characters, whitespace is considered to have no semantic significance, and should therefore be discarded by a - processor. For example, in a choice element, such as - - 1724 - 1728 - - since non-whitespace text is not permitted between the choice + processor. For example, in a choice element, such as 17241728 since non-whitespace text is not permitted between the choice start-tag and the sic tags or between the sic and corr tags, any whitespace found there has no significance and can be ignored completely by a processor.

@@ -808,15 +510,9 @@ for they shall be called the children of God. be normalized. This means that all space, carriage return, linefeed, and tab characters are converted into spaces, all consecutive spaces are then deleted and replaced by one space, and then space immediately after a start-tag or immediately before an end-tag is - deleted. The result is that this encoding, - - Edward - George - Bulwer-Lytton, Baron Lytton of + deleted. The result is that this encoding, EdwardGeorgeBulwer-Lytton, Baron Lytton of Knebworth - - - would be rendered as Edward George Bulwer-Lytton, Baron Lytton of + would be rendered as Edward George Bulwer-Lytton, Baron Lytton of Knebworth. The space before his name has been removed, a space is included between his forenames, the comma is preserved, and the newlines within his name have all been removed.

@@ -849,19 +545,15 @@ one, or vice versa, should be done with care.

The xml:space="preserve" attribute is rarely used in TEI documents because such layout features are generally captured with less risk and more precision by using native TEI elements such as lb or space, or by using the renditional - attributes described in section .

-
Other Globally Available Attributes + attributes described in section .

+
+
+ Other Globally Available Attributes

The following table lists for convenience other potentially available global attributes. The table specifies the name of the attribute class providing the attributes concerned, the module which must be included in a schema if the attributes are to be made available, and the section of these Guidelines where the class is discussed. - - class namemodule namesee further - att.global.linkinglinking - att.global.analyticanalysis - att.global.facstranscr - att.global.changetranscr -
+ class namemodule namesee furtheratt.global.linkinglinkingatt.global.analyticanalysisatt.global.facstranscratt.global.changetranscr

@@ -895,7 +587,7 @@ one, or vice versa, should be done with care.

- + @@ -906,7 +598,6 @@ one, or vice versa, should be done with care.

- @@ -922,7 +613,6 @@ one, or vice versa, should be done with care.

-
@@ -1010,43 +700,28 @@ one, or vice versa, should be done with care.

Informal Element Classifications

Most TEI elements may also be informally classified as belonging to one of the following - groupings: - - high level, possibly self-nesting, major divisions of texts. These elements + groupings: high level, possibly self-nesting, major divisions of texts. These elements populate such classes as model.divLike or model.div1Like, and typically form the largest component units - of a text. - - elements such as paragraphs and other paragraph-level elements, which can appear + of a text. elements such as paragraphs and other paragraph-level elements, which can appear directly within texts or within divisions of them, but not (usually) within other chunks. These elements populate the class model.divPart, - either directly or by means of other classes such as model.pLike (paragraph-like elements), model.entryLike, etc. - - elements such as highlighted phrases, book titles, or editorial corrections which + either directly or by means of other classes such as model.pLike (paragraph-like elements), model.entryLike, etc.elements such as highlighted phrases, book titles, or editorial corrections which can occur only within chunks, but not between them (and thus cannot appear directly within a division). These elements populate the class model.phrase.Note that in this context, phrase means any string of characters, and can apply to individual words, parts of words, and groups of words indifferently; it does not refer only to linguistically-motivated phrasal units. This may cause confusion for readers - accustomed to applying the word in a more restrictive sense. - + accustomed to applying the word in a more restrictive sense.

-

The TEI also identifies two further groupings derived from these three: - - elements such as lists, notes, quotations, etc. which can appear either between +

The TEI also identifies two further groupings derived from these three: elements such as lists, notes, quotations, etc. which can appear either between chunks (as children of a div) or within them; these elements populate the class model.inter. Note that this class is not a superset of the model.phrase and model.divPart classes but rather a distinct grouping of elements which are - both chunk-like and phrase-like. However, the classes model.phrase, model.pLike, and model.inter are all disjoint. - - elements which can appear directly within texts or text divisions; this is a + both chunk-like and phrase-like. However, the classes model.phrase, model.pLike, and model.inter are all disjoint.elements which can appear directly within texts or text divisions; this is a combination of the inter- and chunk- level elements defined above. These elements populate the class model.common, which is defined as a superset of the classes model.divPart, model.inter, and (when the dictionary module is included in a schema) - model.entryLike. - Broadly speaking, the front, body, and back of a text each comprises a series of + model.entryLike. Broadly speaking, the front, body, and back of a text each comprises a series of components, optionally grouped into divisions.

As noted above, some elements do not belong to any model class, and some model classes are not readily associated with any of the above informal groupings. However, over @@ -1150,7 +825,7 @@ one, or vice versa, should be done with care.

- + @@ -1187,18 +862,11 @@ entities in the XML DTD fragments.-->

Standard Content Models

As far as possible, the TEI schemas use the following set of frequently-encountered content - models to help achieve consistency among different elements. - - - - - - - + models to help achieve consistency among different elements.

- +

The present version of the TEI Guidelines includes some different elements. shows, in descending order of frequency, the seven most commonly used content models.

@@ -1223,21 +891,13 @@ entities in the XML DTD fragments.-->

TEI datatype includes additional usage constraints which cannot be enforced by existing schema languages, although a TEI-compliant processor should attempt to validate them (see further discussion in chapter ).

-

The following element is used to define a TEI datatype: - - +

The following element is used to define a TEI datatype:

TEI-defined datatypes may be grouped into those which define normalized values for numeric quantities, probabilities, or temporal expressions, those which define various kinds of shorthand codes or keys, and those which define pointers or links.

The following datatypes are used for attributes which are intended to hold normalized - values of various kinds. First, expressions of quantity or probability: - - - - - - + values of various kinds. First, expressions of quantity or probability:

Examples of attributes using the teidata.probability datatype include degree on damage or certainty; examples of @@ -1253,17 +913,7 @@ entities in the XML DTD fragments.-->

Next, the datatypes used for attributes which are intended to hold normalized dates or - times, durations, truth values, and language identifiers: - - - - - - - - - - + times, durations, truth values, and language identifiers:

Note that in each of these cases the values used are those recommended by existing international standards: ISO 8601 as @@ -1282,19 +932,7 @@ entities in the XML DTD fragments.-->

-

The following datatypes have more specialized uses: - - - - - - - - - - - - +

The following datatypes have more specialized uses:

@@ -1311,16 +949,7 @@ entities in the XML DTD fragments.-->

By far the largest number of TEI attributes take values which are coded values or names of some kind. These values may be constrained or defined in a number of different ways, each of - which is given a different name, as follows: - - - - - - - - - + which is given a different name, as follows:

Attributes of type teidata.word, such as age on person, are used to supply an identifier expressed as any kind of single token or @@ -1374,7 +1003,7 @@ entities in the XML DTD fragments.-->

which case the list is advisory), or closed (in which case it determines the range of legal values). In this latter case, the datatype will not be teidata.enumerated, but an explicit list of the possible values.

- + @@ -1389,11 +1018,7 @@ entities in the XML DTD fragments.-->

than as a distinct datatype, and is provided by the minOccurs or maxOccurs attribute. See further .

In a small number of cases, an attribute may take a value of either one datatype or - another. These cases are considered as distinct datatypes: - - - - + another. These cases are considered as distinct datatypes:

@@ -1408,15 +1033,7 @@ entities in the XML DTD fragments.-->

of any TEI schema. It provides declarations for all datatypes, and initial declarations for the attribute classes, model classes, and macros used by other modules in the TEI scheme. Its components are listed below in alphabetical order: - - TEI Infrastructure - Declarations for classes, datatypes, and macros available to all TEI modules - Infrastructure de la TEI - 所有TEI模組可用的元素集、資料類型、巨集指令之宣告 - Dichiarazione di classi, tipi di dati (datatype)e macro disponibili in tutti i moduli TEI - Declaraçoes de classes, tipos de dados, e macros disponíveis em todos os módulos TEI - 全TEIモジュールで使用可能なデータ型，クラス，マクロ。 - + TEI InfrastructureDeclarations for classes, datatypes, and macros available to all TEI modulesInfrastructure de la TEI所有TEI模組可用的元素集、資料類型、巨集指令之宣告Dichiarazione di classi, tipi di dati (datatype)e macro disponibili in tutti i moduli TEIDeclaraçoes de classes, tipos de dados, e macros disponíveis em todos os módulos TEI 全TEIモジュールで使用可能なデータ型，クラス，マクロ。

The order in which declarations are made within the infrastructure module is critical, since several class declarations refer to others, which must therefore precede them. Other diff --git a/P5/Source/Guidelines/en/TC-CriticalApparatus.xml b/P5/Source/Guidelines/en/TC-CriticalApparatus.xml index 94d9059057..92d680bd69 100644 --- a/P5/Source/Guidelines/en/TC-CriticalApparatus.xml +++ b/P5/Source/Guidelines/en/TC-CriticalApparatus.xml @@ -1,11 +1,5 @@ - +

Critical Apparatus @@ -21,7 +15,6 @@ $Id$ notes at the bottom of each page. TEI’s critical apparatus module allows variation to be encoded so that such notes may be generated, but it also models the variation so that, for example, interactive editions in which readers can choose which witness readings to display are possible.

-

Information about variant readings (whether or not represented by a critical apparatus in the source text) may be recorded in a series of apparatus entries, each entry documenting one variation, or set of readings, in the text. Elements for the @@ -32,36 +25,24 @@ $Id$ text of the edition, are described in section . Finally, several extra attributes for some tags of the core tag set, made available when the additional tag set for text criticism is selected, are documented in section .

-

Scholarly practice in representing critical editions differs widely across disciplines, time periods, and languages. The TEI does not make any recommendations as to which text-critical methods are best suited to any given text. Editors will wish to consider questions such as: - - What source documents will be used? Are there many witnesses, few, or one? Are the - sources relatively close copies or not? - Will there be a single base text? Or will witnesses be separately - transcribed? - If a single base text will be used, will it be that of a particular witness, or will the - editor attempt to reconstruct an ideal or original text? - Will each reading in an apparatus entry record every attestation (a positive + What source documents will be used? Are there many witnesses, few, or one? Are the + sources relatively close copies or not?Will there be a single base text? Or will witnesses be separately + transcribed?If a single base text will be used, will it be that of a particular witness, or will the + editor attempt to reconstruct an ideal or original text?Will each reading in an apparatus entry record every attestation (a positive apparatus), or merely witnesses that deviate from the base text (a negative - apparatus)? - Will the readings of most or all witnesses be represented in the apparatus, or only a - selection the editor deems relevant? - What level of variation will require distinguishing one witness reading from another? + apparatus)?Will the readings of most or all witnesses be represented in the apparatus, or only a + selection the editor deems relevant?What level of variation will require distinguishing one witness reading from another? For example, will the editor consider an abbreviated word in a witness as agreeing with the - base text, or not? - Will conjectures (variant readings suggested by an editor) be treated differently than - readings found in witnesses? - Will there be a need to distinguish different types of variation, for example - orthographic vs. morphological or lexical variants? -

- + base text, or not?Will conjectures (variant readings suggested by an editor) be treated differently than + readings found in witnesses?Will there be a need to distinguish different types of variation, for example + orthographic vs. morphological or lexical variants?

Different editorial methodologies will produce different answers to these questions, and those answers may influence choices of markup used in the edition. For example, if there will be multiple witness transcriptions and a single apparatus, then the double - end-point attachment method may be the best choice of apparatus linking style. The parallel segmentation method may present several advantages to editors + end-point attachment method may be the best choice of apparatus linking style. The parallel segmentation method may present several advantages to editors producing an edition with a single base text. Editors of single-source editions may care to note material aspects of the text (such as damage or unclear text). On the other hand, editors attempting to synthesize an ideal or original text from many witnesses may feel @@ -69,47 +50,33 @@ $Id$ distinguish witness readings from conjectures by modern editors may wish to use wit to indicate the former and source for the latter. Differences in types of variation might be marked using type or ana on the rdg element.

-

Many examples given in this chapter refer to the following texts of the opening (usually just line 1) of Chaucer's Wife of Bath's Prologue, as it appears in each of the four - different manuscripts - Ellesmere, Huntingdon Library 26.C.9 () + different manuscripts Ellesmere, Huntingdon Library 26.C.9 () - Hengwrt, National Library of Wales, Aberystwyth, Peniarth 392D () +To speke of wo that is in mariage; ...-->Hengwrt, National Library of Wales, Aberystwyth, Peniarth 392D () - British Library Lansdowne 851 () +To speke of wo that is in mariage; ...--> British Library Lansdowne 851 () - Bodleian Library Rawlinson Poetic 149 () +To speke of wo that is in mariage; ...-->Bodleian Library Rawlinson Poetic 149 () - -

- +

The Apparatus Entry, Readings, and Witnesses

This section introduces the fundamental markup methods used to encode textual variations: - - the app element for entries in the critical apparatus: see section . - elements for identifying individual readings: see section . - ways of grouping readings together: see section . - methods of identifying which witnesses support a particular reading, and for - describing the witnesses included in the apparatus: see section . - elements for indicating which portions of a text are covered by fragmentary witnesses: - see section . -

+ the app element for entries in the critical apparatus: see section .elements for identifying individual readings: see section .ways of grouping readings together: see section .methods of identifying which witnesses support a particular reading, and for + describing the witnesses included in the apparatus: see section .elements for indicating which portions of a text are covered by fragmentary witnesses: + see section .

The app element is in one sense a more sophisticated and complex version of the choice element introduced in as a way of marking points where the encoding of a passage in a single source may be carried out in more than one way. Unlike choice, however, the app element allows for the representation of many different versions of the same passage taken from different sources.

-
The Apparatus Entry

Individual textual variations are encoded using the app element, which groups @@ -117,9 +84,7 @@ To speke of wo that is in mariage; ...--> variations or apparatus entries is not a purely mechanical process; different editors will group readings differently. No rules are given here as to how to collect readings into apparatus entries.

-

The individual apparatus entry is encoded with the app element: - -

+

The individual apparatus entry is encoded with the app element:

The attributes loc, from, and to, are used to link the apparatus entry to the base text, if present. In such cases, several methods may be used for such linkage, each involving a slightly different usage for these attributes. Linkage @@ -129,25 +94,21 @@ To speke of wo that is in mariage; ...--> the rdg or other elements, as described in the next section. A very simple partial apparatus for the first line of the Wife of Bath's Prologue might take a form something like this: - - Experience though noon Auctoritee - Experiment thouh noon Auctoritee - Eryment though none auctorite - + Experience though noon AuctoriteeExperiment thouh noon AuctoriteeEryment though none auctorite Of course, in practice the apparatus will be somewhat more complex. Specifically, it may be desired to record more obviously that manuscripts El and La agree on the words noon Auctoritee, to indicate a preference for one reading, etc. The following sections on readings, subvariation, and witness information describe some of the more important complications which can arise.

- + + + +
Readings

Individual readings are the crucial elements in any critical apparatus of variants. The - following elements should be used to tag individual readings within an apparatus entry: - - - N.B. the term lemma is used here in the text-critical sense of + following elements should be used to tag individual readings within an apparatus entry: N.B. the term lemma is used here in the text-critical sense of the reading accepted as that of the original or of the base text. This sense differs from that in which the word is used elsewhere in the Guidelines, for example as in the attribute lemma where the intended sense is the root form of an inflected @@ -168,12 +129,10 @@ proposition; a helping theorem.-->

Readings may be encoded individually, or grouped for clarity using the rdgGrp element described in section .

As members of the attribute class att.textCritical, both of these elements - inherit the following attributes: . + inherit the following attributes: . rdg (but not rdgGrp) is also a member of att.witnessed: These elements also inherit the following attributes from the - att.global.responsibility class: - - As elsewhere, these attributes may be used to indicate the person responsible + att.global.responsibility class: As elsewhere, these attributes may be used to indicate the person responsible for the editorial decision being recorded, and also the degree of certainty associated with that decision by the person carrying out the encoding.

The wit attribute identifies the witnesses which have the reading in question. @@ -185,38 +144,20 @@ proposition; a helping theorem.-->

other methods of identifying the witnesses to a reading, see section .

The type attribute allows the encoder to classify readings in any convenient way, for example as substantive variants of the lemma: - - Experience - Experiment - Eryment - + ExperienceExperimentEryment or as orthographic variants: - - though - thouh -

+ thoughthouh

The varSeq and cause attributes may be used to convey information on the sequence and cause of variation. In the following apparatus fragment, the reading Eryment is tagged as sequential to (derived from) the reading Experiment, and the cause is given as loss of the abbreviation for per. - - Experiment - Eryment -

+ ExperimentEryment

If a manuscript is written in several hands, and it is desired to report which hand wrote a particular reading, the hand attribute should be used. For example, in the Munich manuscript containing the Carmina Burana, the word - alle has been changed to allen: Swaz hi gât umbe -daz sint alle megede, -die wellent ân man - - - alle - allen - -disen sumer gân. - + alle has been changed to allen: Swaz hi gât umbedaz sint alle megede,die wellent ân manalleallen +disen sumer gân.

@@ -228,12 +169,7 @@ disen sumer gân. Zupitza and Chambers:For the sake of legibility in the example, long marks over vowels are omitted. se ðe on - - hea(um) h(æþ)e - heaðo hlæwe - heaum hope - -hord beweotode, + hea(um) h(æþ)eheaðo hlæweheaum hopehord beweotode,

Because the hand attribute indicates a particular manuscript hand, it is intelligible only on a reading from a single witness. If an encoder wishes to indicate that a particular @@ -245,14 +181,11 @@ disen sumer gân. can be attached to the apparatus in a note.

The note element may also be used to record the specific wording of notes in the apparatus of the source edition, as here in a transcription of Friedrich Klaeber's note on - Beowulf 2207a: syððan Beowulfe -Fol. 179a beowulfe. + Beowulf 2207a: syððan BeowulfeFol. 179a beowulfe. Folio 179, with the last page (Fol. 198b), is the worst part of the entire MS. It has been freshened up by a later hand, but not always correctly. Information on doubtful readings is in the notes of - Zupitza and Chambers. -brade rice - + Zupitza and Chambers.brade rice Notes providing details of the reading of one particular witness should be encoded using the specialized witDetail element described in section .

@@ -270,16 +203,17 @@ disen sumer gân. transcription of primary sources in section , the division of layers of responsibility through various scholars for particular aspects of a particular reading may require the more complex mechanisms for assigning responsibility described in chapter .

- + + + +
Indicating Subvariation in Apparatus Entries

The rdgGrp element may be used to group readings, either because they have identical values on one or more attributes, or because they are seen as forming a self-contained variant sequence, or for some other reason. This grouping of readings is - entirely optional: no such grouping of readings is required. - -

+ entirely optional: no such grouping of readings is required.

The rdgGrp element is a member of class att.textCritical and therefore can carry the type, cause, varSeq, hand, and resp attributes described in the preceding section. When values for any of these attributes are given on a @@ -290,13 +224,7 @@ disen sumer gân. both readings rdg type='orthographic', as shown in the preceding section. This fact can be expressed more perspicuously, however, by grouping their readings into a rdgGrp, thus: - - though - - thogh - thouh - -

+ thoughthoghthouh

Similarly, rdgGrp may be used to organize the substantive variants of an apparatus entry. Editors may need to indicate that each of a group of witnesses may be taken as all supporting a particular reading, even though there may be variation concerning the exact @@ -316,20 +244,7 @@ disen sumer gân.

In this example, the different subvariants on Experience, Experiment, and Eriment are held within three rdgGrp elements nested within the enclosing app element: - - - Experience - Experiens - - - Experiment - Eximent - - - Eriment - Eryment - - + ExperienceExperiensExperimentEximentErimentEryment From this, one may deduce that the regularized reading Experience is supported by all three manuscripts El Hg Ha4, although the spelling differs in Ha4, and that the regularized reading Eriment is supported by Ra2, even though the @@ -343,26 +258,7 @@ disen sumer gân. depth. Because apparatus entries may also nest, the app element might also be used to group readings in the same way. The example above is substantially identical to the following, which uses app instead of rdgGrp: - - - - Experience - Experiens - - - - - Experiment - Eximent - - - - - Eriment - Eryment - - - + ExperienceExperiensExperimentEximentErimentEryment This expresses even more clearly than the previous encoding of this material that at the highest level of classification (apparatus entry A1), this variation has three normalized readings, and that the first of these is supported by manuscripts El, Hg, and Ha4; the @@ -375,23 +271,10 @@ disen sumer gân. experiment to eriment says nothing about the relative priority of experiment and experience: - - - Experience - Experiens - - - - Experiment - Eximent - - - Eriment - Eryment - - -

- + ExperienceExperiensExperimentEximentErimentEryment

+ + +
Witness Information @@ -411,22 +294,14 @@ disen sumer gân. witnesses for that reading. The link to the reading may be inferred from witDetail's position or made explicit by the target attribute which witDetail inherits from the attribute class - att.pointing; the link to the witness, by the wit attribute. - - -

+ att.pointing; the link to the witness, by the wit attribute.

Because it annotates an attribute value, witDetail cannot be included in the text at the point of attachment; without a target attribute, it refers to the closest preceding lem or rdg. But if there is any ambiguity or if the witDetail refers to multiple readings, target must be used to point to the reading(s) being annotated. To indicate that the Ellesmere manuscript has an ornamental capital in the word Experience, for example, one might write: - - Experience - Ornamental capital. - Experiens - - + ExperienceOrnamental capital.Experiens This encoding makes clear that the ornamental capital mentioned is in the Ellesmere manuscript, and not in Hengwrt or Ha4.

Like note, witDetail may be used to record the specific wording of @@ -434,26 +309,18 @@ disen sumer gân. formal way elsewhere. The example from the Carmina Burana above (section ), for example, might be extended thus, to record the wording of the note explaining that the variant reading adds n to the original - in a second hand: Swaz hi gât umbe -daz sint alle megede, -die wellent ân man - - - alle - allen - - n nachgetragen. - - -disen sumer gân. - + in a second hand: Swaz hi gât umbedaz sint alle megede,die wellent ân manalleallenn nachgetragen. + +disen sumer gân.

Feature structures containing information about the text in a witness (whether retroversion, regularization, or other) can also be linked to specific lem and rdg instances. See chapter .

- + + +
Witness Information in the Source @@ -466,32 +333,21 @@ disen sumer gân. future reference the exact form in which the source edition records the witnesses to a particular reading; this is particularly important in cases of ambiguity in the information, or uncertainty as to the correct interpretation. The wit element may - be used to transcribe such lists of witnesses to a particular reading. - - The wit list may appear following a rdg, rdgGrp, or + be used to transcribe such lists of witnesses to a particular reading. The wit list may appear following a rdg, rdgGrp, or lem element in any apparatus entry. wit may be used in a way functionally equivalent to wit if the sigla therein are wrapped in refs with target attributes pointing to a predefined witness. For example - - Nondum - nundum - corr. G1 - - + Nondumnundumcorr. G1 which indicates that the reading nundum for nondum is to be found in MSS G (although it is corrected to nondum in the primary hand) and P, might be written: - - Nondum - nundum - G(corr. G1)P - - + NondumnundumG(corr. G1)P This is somewhat more verbose, but accomplishes the same goal. Because wit is more succinct, and because it makes the automated verification of correct witness references easier, using wit (with witDetail when needed) is almost always to be preferred.

- + + +
The Witness List @@ -507,47 +363,21 @@ disen sumer gân.

Whether information about a particular witness is supplied by means of a bibl, msDesc, or witness element, a unique siglum for this source should always be supplied, using the global xml:id attribute. This identifier can then - be used elsewhere to refer to this particular witness. - - - - - -

+ be used elsewhere to refer to this particular witness.

The minimal information provided by a witness list is thus the set of sigla for all the witnesses named in the apparatus. For example, the witnesses referenced by the examples of this chapter might simply be listed thus: - - - - - - - - - - - - - - - -

+

It is more helpful, however, for witness lists to be somewhat more informative: each witness element should contain at least a brief prose description of the witness, perhaps including a bibliographic citation, as in the following examples: - - Ellesmere, Huntingdon Library 26.C.9 - Hengwrt, National Library of Wales, - Aberystwyth, Peniarth 392D - Bodleian Library Rawlinson Poetic 149 -(see further ) - + Ellesmere, Huntingdon Library 26.C.9Hengwrt, National Library of Wales, + Aberystwyth, Peniarth 392DBodleian Library Rawlinson Poetic 149 +(see further ) As the last example shows, the witness description here may be complemented by a reference to a full description of the manuscript supplied elsewhere, typically as the content of an msDesc or bibl element. Alternatively, it may contain a whole - paragraph of commentary for each witness: - die sog. Kleine (oder alte) + paragraph of commentary for each witness: die sog. Kleine (oder alte) Heidelberger Liederhandschrift. Universitätsbibliothek Heidelberg col. pal. germ. 357. Pergament, 45 Fll. 18,5 × 13,5 cm. @@ -560,11 +390,8 @@ disen sumer gân. genannte Dichter. Zu den Vorzügen von A gehört, daß sie kaum je bewußt geändert hat, so daß sie für manche Dichter ... oft den besten Text liefert (so wohl mit - Recht v. Kraus). - Bezeichnung Lachmann - s für die von einer 2. Hand auf bl. 40–43 - geschriebenen Strophen der Hs. A. - die Weingartner (Stuttgarter) + Recht v. Kraus).Bezeichnung Lachmanns für die von einer 2. Hand auf bl. 40–43 + geschriebenen Strophen der Hs. A.die Weingartner (Stuttgarter) Liederhandschrift. Württembergische Landesbibliothek Stuttgart, HB XIII poetae germanici 1. Pergament, 156 Bll. 15 × 11,5 cm; 25 teils ganzseitig, @@ -572,26 +399,19 @@ disen sumer gân. geschrieben. Sie enthält Lieder von 25 namentlich genannten Dichtern. (Dazu kommen Gedichte von einigen ungenannten bzw. unbekannten Dichtern, ein Marienlobpreis und eine - Minnelehre.) - + Minnelehre.)

It would however generally be preferable to represent such detailed information using an appropriately structured msDesc element, as discussed in chapter . Note also that if the witnesses being recorded are not manuscripts but printed works, it may be preferable to document them using the standard bibl or biblStruct elements described in , as in this example: - - -T. Kempis, De la imitació de Jesuchrist e del + T. Kempis, De la imitació de Jesuchrist e del menyspreu del món (trad. Miquel Peres); Barcelona, 1482, Pere -Posa. Editio princeps. -T. Kempis, Del menyspreu del món (trad. Miquel -Peres); València, 1491. -T. Kempis, Libre del menysprey del món e de la +Posa. Editio princeps.T. Kempis, Del menyspreu del món (trad. Miquel +Peres); València, 1491.T. Kempis, Libre del menysprey del món e de la imitació de nostre senyor Déu Jesucrist, (trad. Miquel Peres); -Barcelona, 1518, Carles Amorós. - - +Barcelona, 1518, Carles Amorós.

In text-critical work it is customary to refer to frequently occurring groups of witnesses by means of a single common siglum. Such sigla may be documented as @@ -600,71 +420,24 @@ Barcelona, 1518, Carles Amorós. the group in its optional child head element, before listing the other witnesses contained by the group. For example, the Constant Group C of manuscripts comprising witnesses Cp, La, and S12, - might be represented as follows: - -Ellesmere, Huntingdon Library 26.C.9 - - - Constant Group C - Corpus Christi Oxford MS 198 - British Library Lansdowne 851 - British Library Sloane MS 1686 - - + might be represented as follows: Ellesmere, Huntingdon Library 26.C.9Constant Group CCorpus Christi Oxford MS 198British Library Lansdowne 851British Library Sloane MS 1686 That the reading Experiment occurs in all three manuscripts can now be indicated simply as follows: Experiment

The more elaborate example below shows both multiple levels of nesting and a strategy for mapping the the xml:id of the witness to the siglum which will be displayed to the reader of a derived visualisation: Servius (Σ) = ΔΓ - - Δ - J = Metens. Bibl. mun. 292, s. IX - L = Leid. Bibl. der Rijksuniv. B.P.L. 52, s. VIII / IX - - Γ - θ - A = Caroliruh. Bad. Landesbibl. Aug. CXVI, s. IX2 (Reichenau); de codice A derivati: - - S = Sangall. Stiftsbibl. 861 + 862, s. IX / X - Guelf. = Guelf. HAB 2546 (44.23 Aug. fol.), s. XV - - - O = Oxon. Bodl. Laud lat. 117, s. XI2 - - τ - - Pa = Paris. BnF lat. 7959, s. IX (Tours) - Pc = Paris. BnF lat. 7961, s. X / XI - Q Flor. BML Plut. 45.14, s. IX - Lb = corrector cod. L (sup.) - - - γ - E = Escorial. Bibl. S. Lorenzo T.II.17, s. IX2 (Ital. septentrion.) - Pb Paris. BnF lat. 16236, s. X / XI - Y = Trident. Bib. com. 3388 (olim Vind. 72), s. - IX2 - M = Monac. Bay. Staatsbibl. Clm 6394, s. XI - - - σ - W = Guelf. HAB 2091, s. XIIIex. - N = Neap. Bibl. naz. lat. 5 (olim Vind. 27), s. - X1 - U = Berolin. Staatsbibl. lat. quart. 219, s. XII - - º classis codicum de Γ defluentium quibus lectiones faciliores in contextum contaminatione inferre valde placuit (= PaPcγσ in A. 9.1-10.190, 10.397-12.162; PaPcγU in A. 12.162-320; PaPcγ in A. 12.320-522); cf. praef. n. 30. - - - + ΔJ = Metens. Bibl. mun. 292, s. IX L = Leid. Bibl. der Rijksuniv. B.P.L. 52, s. VIII / IXΓθA = Caroliruh. Bad. Landesbibl. Aug. CXVI, s. IX2 (Reichenau); de codice A derivati: + S = Sangall. Stiftsbibl. 861 + 862, s. IX / XGuelf. = Guelf. HAB 2546 (44.23 Aug. fol.), s. XV + O = Oxon. Bodl. Laud lat. 117, s. XI2τPa = Paris. BnF lat. 7959, s. IX (Tours)Pc = Paris. BnF lat. 7961, s. X / XIQ Flor. BML Plut. 45.14, s. IXLb = corrector cod. L (sup.)γE = Escorial. Bibl. S. Lorenzo T.II.17, s. IX2 (Ital. septentrion.) Pb Paris. BnF lat. 16236, s. X / XIY = Trident. Bib. com. 3388 (olim Vind. 72), s. + IX2M = Monac. Bay. Staatsbibl. Clm 6394, s. XI + σW = Guelf. HAB 2091, s. XIIIex.N = Neap. Bibl. naz. lat. 5 (olim Vind. 27), s. + X1U = Berolin. Staatsbibl. lat. quart. 219, s. XIIº classis codicum de Γ defluentium quibus lectiones faciliores in contextum contaminatione inferre valde placuit (= PaPcγσ in A. 9.1-10.190, 10.397-12.162; PaPcγU in A. 12.162-320; PaPcγ in A. 12.320-522); cf. praef. n. 30. Here we have a summary of the witnesses, with their sigla, used in an edition, as is generally found in the conspectus siglorum in the front matter of a critical edition. Families are indicated with Greek letters and manuscript witnesses with Latin letters. The siglum for display is always contained in the abbr with type siglum child of each witness, so it is always easy to retrieve the display siglum for a given identifier reference.

- -

Situations commonly arise where there are many more or less fragmentary witnesses, such that there may be quite distinct groups of witnesses for different parts of a text or collection of texts. One may treat this with distinct listWit elements for each @@ -680,7 +453,10 @@ Barcelona, 1518, Carles Amorós. overlapping lemma) and thence calculate all the manuscripts agreeing with the base text. In practice, encoders may find it less error-prone to list all witnesses explicitly in each apparatus entry.

- + + + +
@@ -689,72 +465,47 @@ Barcelona, 1518, Carles Amorós. relatively complete text with one or more lacunae), it is usually desirable to record explicitly where its preserved portions begin and end. The following empty tags, which may occur within any lem or rdg element, indicate the beginning or end of a - fragmentary witness or of a lacuna within a witness: - - - - - These elements constitute the class model.rdgPart, + fragmentary witness or of a lacuna within a witness: These elements constitute the class model.rdgPart, members of which are permitted within the elements lem and rdg when the module defined by this chapter is included in a schema.

Suppose a fragment of a manuscript X of the Wife of Bath's Prologue has a physical lacuna, and the text of the manuscript begins with auctorite. In an apparatus this might appear thus, distinguished from the reading of other manuscripts by the presence of the lacunaEnd element: - - Auctoritee - auctorite - auctorite - + Auctoriteeauctoriteauctorite Alternatively, it may be clearer to record this as - - Auctoritee - auctorite - + Auctoriteeauctorite since this shows more clearly that the lacuna and the reading of auctorite both appear in witness X. In some cases, the apparatus in the source may commence recording the readings for a particular witness without its being clear whether the previous absence of readings for this witness is due to a lacuna, or to some other reason. The witStart element may be used in this circumstance: - - Auctoritee - auctorite - auctorite -

- - + Auctoriteeauctoriteauctorite

+ + + + + +
Linking the Apparatus to the Text -

Three different methods may be used to link a critical apparatus to the text: - the location-referenced method, - the double-end-point-attached method, and - the parallel segmentation method. -

+

Three different methods may be used to link a critical apparatus to the text: the location-referenced method,the double-end-point-attached method, andthe parallel segmentation method.

Both the location-referenced and the double end-point methods may be used with either in-line or external apparatus, the former dispersed within the base text, the latter held in some separate location, within or outside the document containing the base text. The parallel segmentation method may only be used for in-line apparatus.

- - - +

Where an external apparatus is used, the listApp element provides a useful means of grouping together a series of app elements of a specific type, or from a particular source: - - - - + listApp elements would normally appear in the back of a document, but they may also be placed in any other convenient location.

-

Any document containing app elements requires a variantEncoding declaration - in the encodingDesc element of its TEI header, thus: - -

- + in the encodingDesc element of its TEI header, thus:

The Location-referenced Method

The location-referenced method of encoding apparatus provides a convenient method for @@ -766,53 +517,27 @@ Barcelona, 1518, Carles Amorós. text, the TEI header must have the declaration:

In the body of the document, the base text (here El) will appear: - - -

- The Prologe of the Wyves Tale of Bathe - Experience though noon Auctoritee - Were in this world ... -
- -

+
The Prologe of the Wyves Tale of BatheExperience though noon AuctoriteeWere in this world ...

Elsewhere in the document, or in a separate file, the apparatus will appear. On each app element, the loc attribute should be specified to indicate where the variant occurs in the base text. - - Experiment - Eryment -

+ ExperimentEryment

If the same text is encoded using in-line storage, the apparatus is dispersed through the base text block to which it refers. In this case, the location of the variant can be read from the line in which it occurs. - - -Experience - - Experiment - Eryment - - though noon Auctoritee -Were in this world ...

+ Experience + ExperimentEryment + though noon AuctoriteeWere in this world ...

Since the location is not required to be exact, the apparatus for a line might also appear at the end of the line: Experience though noon Auctoritee - - Experiment - Eryment - -Were in this world ...

+ Experiment ErymentWere in this world ...

When the apparatus is linked to the text by means of location references, as shown here, it is not possible to find automatically the precise portion of text varied by the readings. In order to show explicitly what portion of the base text is replaced by the variant readings, the lem element may be used: Experience though noon Auctoritee - - Experience - Experiment - Eryment - -Were in this world ... + ExperienceExperimentErymentWere in this world ... Often the lemma will have no attributes, being simply the base text reading and requiring no qualification, but it may optionally carry the normal attributes, as shown here. Some text critics prefer to abbreviate or elide the lemma, in @@ -845,19 +570,9 @@ Barcelona, 1518, Carles Amorós. the latter case, the base text (here El) will appear with anchor elements inserted at every place where a variant begins or ends (unless some element with an identifier already begins or ends at that point): - - - -

The Prologe ... - Experience though noon Auctoritee - Were in this world ... -
- +
The Prologe ... Experience though noon AuctoriteeWere in this world ...
 The apparatus will be separately encoded: - - Experiment - Eryment - + ExperimentEryment No anchor element is needed at the beginning of the line, since the from attribute can use the identifier for the line as a whole; the lemma is assumed to run from the beginning of the element indicated by the from attribute, to the end of that @@ -867,15 +582,9 @@ Barcelona, 1518, Carles Amorós.

When the apparatus is encoded in-line, it is dispersed through the base text. Only the beginning of the lemma need be marked with an anchor, since the app is inserted at the end of the lemma, and itself therefore marks the end of the lemma. - - -Experience - - Experiment - Eryment - - though noon Auctoritee -Were in this world ...

+ Experience + ExperimentEryment + though noon AuctoriteeWere in this world ...

The lemma need not be repeated within the app element in this method, as it may be extracted reliably from the base text. If an exhaustive list of witnesses is available, it will also not be necessary to specify just which manuscripts agree with the base text to @@ -886,21 +595,10 @@ Barcelona, 1518, Carles Amorós.

Alternatively, if it is desired to make an explicit record of the attestation of the base text, the lem element may be embedded within app, carrying the witnesses to the base. Thus - - Experience - Experiment - Eryment -

+ ExperienceExperimentEryment

This method is designed to cope with overlapping lemmata. For example, at line 117 of the Wife of Bath's Prologue, the manuscripts Hg (Hengwrt), El (Ellesmere), - and Ha4 (British Library Harleian 7334) read: - - And of so parfit wys a wight ywroght - - And for what profit was a wight ywroght - - And in what wise was a wight ywroght -

+ and Ha4 (British Library Harleian 7334) read: And of so parfit wys a wight ywroghtAnd for what profit was a wight ywroghtAnd in what wise was a wight ywroght

In this case, one might wish to record in what wise was in Ha4 as a single variant for of so parfit wys in Hg, and was a wight in El and Ha4 as a variant on wys a wight in Hg. @@ -911,14 +609,8 @@ Barcelona, 1518, Carles Amorós. wys a wight ywroght - - of so parfit wys - in what wise was - - - wys a wight - was a wight - + of so parfit wysin what wise was + wys a wightwas a wight The parallel segmentation method, to be discussed next, cannot handle overlaps among variants, and would require the individual variants to be split into pieces.

Because creation and interpretation of double end-point attachment apparatus will be @@ -943,52 +635,20 @@ Barcelona, 1518, Carles Amorós. variation needs to be modeled.

In the parallel segmentation method, each segment of text on which there is variation is marked by an app element. If there is a preferred (or base) reading it is tagged - with lem; each reading is given in a rdg element: - - - Experience - Experiment - Eryment though noon Auctoritee - Were in this world ...

+ with lem; each reading is given in a rdg element: ExperienceExperimentEryment though noon AuctoriteeWere in this world ...

This method cannot be used with external apparatus: it must be used in-line. Note that apparatus encoded with this method may be translated into the double end-point attachment method and back without loss of information. Where double-end-point-attachment encodings have no overlapping lemmata, translation of these to the parallel segmentation encoding and back will also be possible without loss of information.

-

As noted, apparatus entries may nest in this method: if an imaginary fifth manuscript of the text read Auctoritee, though none experience, the variation on - the individual words of the line would nest within that for the line as a whole: - - Auctoritee, though none experience - - - Experience - Experiment - Eryment - - - though - thogh - thouh - - - noon Auctorite - none auctorite - - - -

+ the individual words of the line would nest within that for the line as a whole: Auctoritee, though none experienceExperienceExperimentErymentthoughthoghthouhnoon Auctoritenone auctorite

Parallel segmentation cannot, however, deal very gracefully with variants which overlap without nesting: such variants must be broken up into pieces in order to keep all witnesses synchronized.

- -
Other Linking Methods

When an apparatus is provided it does not need to be given at the location in the @@ -1009,28 +669,9 @@ Barcelona, 1518, Carles Amorós. thus contains a URI as a value. This means that it can point directly to an xml:id, an xml:id in another local file, or indeed a file identified by any URL or URN. - - Experience though noon Auctoritee - - - - - Experiment - Eryment - - + Experience though noon AuctoriteeExperimentEryment This could also be encoded as: - - though noon Auctoritee - - - - - Experience - Experiment - Eryment - - + though noon AuctoriteeExperienceExperimentEryment However, this should be considered more fragile since a full reading of the lem is not provided in the source file.

In addition, URLs can contain XPointer schemes including xpath(), range(), and @@ -1039,17 +680,7 @@ Barcelona, 1518, Carles Amorós. used, as in the double end-point attachment method, to identify the starting and ending location for an apparatus using XPointer schemes described in section to more precisely identify this location where beneficial. - - Experience though noon Auctoritee - - - - - Experience - Experiment - Eryment - - + Experience though noon AuctoriteeExperienceExperimentEryment

If only the from attribute is provided then it should be understood that this supplies the location of the textual variance that the apparatus documents. If the @@ -1057,12 +688,7 @@ Barcelona, 1518, Carles Amorós. elements) then this is understood to record the starting and ending of the range as in the double end-point attachment method. In such a case a @to attribute is unnecessary.

-
- - - -
Using Apparatus Elements in Transcriptions

It is often desirable to record different transcriptions of one stretch of text. These @@ -1084,11 +710,7 @@ Barcelona, 1518, Carles Amorós. u. This information may be held within an app structure, as follows: Virginite is grete - - perfectio - perfectioun - perfectioun - +perfectioperfectiounperfectioun This example uses special purpose elements am and ex used to represent abbreviation marks and editorial expansion respectively; these elements are provided by the transcr module documented in chapter , which @@ -1121,11 +743,7 @@ not for those for elements nested within.-->

Editorial notes may also be attached to app structures within transcriptions. Here, editorial preference for Ruggiers' expansion and an explanation of that preference is given: Virginite is grete - - perfecti - perfectioun - perfectioun - +perfectiperfectiounperfectioun Furnivall's expansion implies that the bar is an abbreviation for 'u'. There are no certain instances of @@ -1148,7 +766,6 @@ not for those for elements nested within.-->

join element or the next and prev attributes defined by chapter .

-
Strategies for Encoding Variation

Textual variation may manifest itself in many ways. Variation most frequently occurs at the phrase level, @@ -1161,10 +778,7 @@ not for those for elements nested within.-->

Phenomena such as omissions and transpositions in witnesses will require some encoding strategies that differ from those in the examples above. An editor wishing to signal an omission in one witness should encode the omission using an empty rdg, thus: - - Hypsipyle uacuo constitit in thalamo: - - + Hypsipyle uacuo constitit in thalamo: Notice that in this example, the variation occurs at the unit of the verse line. The scribe of MS J has skipped line 18 (probably by mistake) because, like line 19, it begins with the name "Hypsipyle." If a witness contains an interpolation that the editor does not wish to show in the base text, an empty @@ -1175,61 +789,32 @@ not for those for elements nested within.-->

For example, in his edition of Propertius 1.16, Housman printed lines 25-6 after line 32, Heyworth prints them in place. We might encode Heyworth's edition, which records Housman's conjecture despite disagreeing with it, as follows: - - - desine iam reuocare tuis periuria verbis, - Cynthia, et oblitos parce movere deos; - - and then, after line 32: - - - - - - Housman put these lines after 32. - + desine iam reuocare tuis periuria verbis,Cynthia, et oblitos parce movere deos; and then, after line 32: + Housman put these lines after 32. Note that both apps are linked via the exclude attribute, because they are mutually exclusive: if one reading is chosen for display in a reading interface, for example, the other must disappear and vice versa. To avoid repetition, the second pair of lines can make use of the copyOf attribute. If they were both transposed and somewhat different, then both sets should be written in full.

Apparatus entries may nest when there is variation at both higher and lower structural levels, e.g.: - - - utetac perhapsquam formosa nouo quae parat ire uiro. - atet non sic, Ithaci digressu motaimmota, Calypso - desertis olim fleuerat aequoribus: - multos illa dies incomptis maesta capillis - - omits lines 8-11 because of homoeoteleuton. - + utetacperhapsquam formosa nouo quae parat ire uiro.atet non sic, Ithaci digressu motaimmota, Calypsodesertis olim fleuerat aequoribus:multos illa dies incomptis maesta capillisomits lines 8-11 because of homoeoteleuton. Here, MS C omits lines 8-11, but there are variations the editor wishes to record in the other witnesses which do have these lines. Therefore, an outer app gives the lines in the lem and the omission in a rdg. Further variation is encoded for lines 8 and 9 using nested apps.

-
Module for Critical Apparatus

The module described in this chapter makes available the following components: - - Text Criticism - Critical Apparatus - Apparat critique - 學術編輯註解 - Apparato critico - Critical Apparatus - 校勘モジュール - + Text CriticismCritical ApparatusApparat critique學術編輯註解Apparato criticoCritical Apparatus校勘モジュール The selection and combination of modules to form a TEI schema is described in .

- - - - - - + + + + + @@ -1240,5 +825,4 @@ not for those for elements nested within.-->
-
diff --git a/P5/Source/Guidelines/en/TD-DocumentationElements.xml b/P5/Source/Guidelines/en/TD-DocumentationElements.xml index b610ee20ff..7f7dbccd92 100644 --- a/P5/Source/Guidelines/en/TD-DocumentationElements.xml +++ b/P5/Source/Guidelines/en/TD-DocumentationElements.xml @@ -1,16 +1,7 @@ - + -
+
Documentation Elements

This chapter describes a module which may be used for the documentation of the XML elements and element classes which make up any markup scheme, in particular that described by the TEI Guidelines, and also for @@ -23,22 +14,16 @@ $Id$ be helpful. In the remainder of this chapter we refer to software which provides such a processing environment as an ODD processor.ODD is short for One Document Does it all, and was the name invented by the original TEI Editors for the predecessor of the system - currently used for this purpose. See further and . Like any other piece of XML software, an ODD processor may be instantiated in many ways: the + currently used for this purpose. See further and . Like any other piece of XML software, an ODD processor may be instantiated in many ways: the current system uses a number of XSLT stylesheets which are freely available from the TEI, but this specification makes no particular assumptions about the tools which will be used to provide an ODD processing environment.

As the name suggests, an ODD processor uses a single XML document to generate multiple outputs. These - outputs will include: - formal reference documentation for elements, attributes, element classes, patterns, etc. such as - those provided in below; - detailed descriptive documentation, embedding some parts of the formal reference documentation, - such as the tag description lists provided in this and other chapters of these Guidelines; - declarative code for one or more XML schema languages, such as RELAX NG, W3C Schema, ISO - Schematron, or DTD. - - + outputs will include: formal reference documentation for elements, attributes, element classes, patterns, etc. such as + those provided in below;detailed descriptive documentation, embedding some parts of the formal reference documentation, + such as the tag description lists provided in this and other chapters of these Guidelines;declarative code for one or more XML schema languages, such as RELAX NG, W3C Schema, ISO + Schematron, or DTD.

The input required to generate these outputs consists of running prose, and special purpose elements documenting the components (elements, classes, etc.) which are to be declared in the chosen schema @@ -77,30 +62,20 @@ an XML Document Type Declaration. Phrase Level Terms

In any kind of technical documentation, the following phrase-level elements may be found useful for marking up strings of text which need to be distinguished from the running text because they come from - some formal language: - - - Like other phrase-level elements used to indicate the semantics of a typographically + some formal language: Like other phrase-level elements used to indicate the semantics of a typographically distinct string, these are members of the model.emphLike class. They are available anywhere that running prose is permitted when the module defined by this chapter is included in a schema.

The code and ident elements are intended for use when citing brief passages in some formal language such as a programming language, as in the following example: - -

If the variable z has a value of zero, a statement such as x=y/z will - usually cause a fatal error.

- +

If the variable z has a value of zero, a statement such as x=y/z will + usually cause a fatal error.

If the cited phrase is a mathematical or chemical formula, the more specific formula element defined by the figures module () may be more appropriate.

A further group of similar phrase-level elements is also defined for the special case of representing - parts of an XML document: - - - - - These elements constitute the model.phrase.xml class, which is + parts of an XML document: These elements constitute the model.phrase.xml class, which is also a subclass of model.phrase. They are also available anywhere that running prose is permitted when the module defined by this chapter is included in a schema.

As an example of the recommended use of these elements, we quote from an imaginary TEI working paper: @@ -112,10 +87,7 @@ an XML Document Type Declaration.

Within technical documentation, it is also often necessary to provide more extended examples of usage or to present passages of markup for discussion. The following special elements are provided for these - purposes: - - - + purposes:

Like the code element, the egXML element is used to mark strings of formal code, or passages of XML markup. The eg element may be used to enclose any kind of example, which will @@ -133,26 +105,13 @@ an XML Document Type Declaration. Element and Attribute Descriptions

Within the body of a document using this module, the following elements may be used to reference parts of the specification elements discussed in section , in particular - the brief prose descriptions these provide for elements and attributes. - - - + the brief prose descriptions these provide for elements and attributes.

TEI practice recommends that a specList listing the elements under discussion introduce each subsection of a module's documentation. The source for the present section, for example, begins as follows: - -

- Element and Attribute Descriptions -

Within the body of a document using this module, the … the brief prose descriptions these provide for elements and attributes. - - - -

-

TEI practice recommends that a specList listing the elements under …

- -
- +
Element and Attribute Descriptions

Within the body of a document using this module, the … the brief prose descriptions these provide for elements and attributes. +

TEI practice recommends that a specList listing the elements under …

When formatting the ptr element in this example, an ODD processor might simply generate the section number and title of the section referred to, perhaps additionally inserting a link to the @@ -187,33 +146,19 @@ an XML Document Type Declaration.

Modules and Schemas

As mentioned above, the primary purpose of this module is to facilitate the documentation and creation - of an XML schema derived from the TEI Guidelines. The following elements are provided for this purpose: - - - - - - - - + of an XML schema derived from the TEI Guidelines. The following elements are provided for this purpose: A module is a convenient way of grouping together element and other declarations, and of associating an externally-visible name with the resulting group. A specification group performs essentially the same function, but the resulting group is not accessible outside the scope of the ODD document in which it is defined, whereas a module can be accessed by name from any TEI schema specification. Elements, and their attributes, element classes, and - patterns are all individually documented using further elements described in section below; part of that specification includes the name of the module to which the + patterns are all individually documented using further elements described in section below; part of that specification includes the name of the module to which the component belongs.

An ODD processor generating XML DTD or schema fragments from a document marked up according to the recommendations of this chapter will generate such fragments for each moduleSpec element found. For example, the chapter documenting the TEI module for names and dates contains a module specification like the following: - - - Names and Dates - Additional elements for names and dates - - + Names and DatesAdditional elements for names and dates together with specifications for all the elements, classes, and patterns which make up that module, expressed using elementSpec, classSpec, or macroSpec elements as appropriate. (These elements are discussed in section below.) Each of those @@ -223,9 +168,7 @@ an XML Document Type Declaration. (etc.) which reference it.

In most realistic applications, it will be desirable to combine more than one module together to form a complete schema. A schema consists of references to one or more modules or specification - groups, and may also contain explicit declarations or redeclarations of elements (see further ). Any combination of modules can be used to create a schema The distinction between base and additional tagsets in earlier versions of the TEI scheme has not + groups, and may also contain explicit declarations or redeclarations of elements (see further ). Any combination of modules can be used to create a schema The distinction between base and additional tagsets in earlier versions of the TEI scheme has not been carried forward into P5.

A schema can combine references to TEI modules with references to other (non-TEI) modules using @@ -245,27 +188,13 @@ an XML Document Type Declaration.

An ODD processor will generate a piece of schema code corresponding with the declarations contained by a specGrp element in the documentation being output, and a cross-reference to such a piece of schema code when processing a specGrpRef. For example, if the input text reads -

This module contains three red elements: - - - - and two blue ones: - - -

- +

This module contains three red elements: and two blue ones:

then the output documentation will replace the two specGrp elements above with a - representation of the schema code declaring the elements beetroot, east, and rose and that declaring the elements sky and bayou respectively. Similarly, if the + representation of the schema code declaring the elements beetroot, east, and rose and that declaring the elements sky and bayou respectively. Similarly, if the input text contains elsewhere a passage such as -
- An overview of the imaginary module -

The imaginary module contains declarations for coloured things: +

An overview of the imaginary module

The imaginary module contains declarations for coloured things: -

-
+

then the specGrpRef elements may be replaced by an appropriate piece of reference text such as The RED elements were declared in section 4.2 above, or even by a copy of the relevant declarations. As stated above, the order of declarations within the imaginary module described above @@ -287,12 +216,7 @@ an XML Document Type Declaration.
Specification Elements -

The following elements are used to specify elements, classes, patterns, and datatypes: - - - - - +

The following elements are used to specify elements, classes, patterns, and datatypes:

Unlike most elements in the TEI scheme, each of these specification elements has a fairly rigid internal structure consisting of a large number of child elements which are always @@ -303,8 +227,7 @@ an XML Document Type Declaration. common to all the specification elements, and then those which are specific to a particular type.

Specification elements may appear at any point in an ODD document, both between and within paragraphs as well as inside a specGrp element, but the specification element for any particular component - may only appear once (except in the case where a modification is being defined; see further ). The order in which they appear will not affect the order in which they are + may only appear once (except in the case where a modification is being defined; see further ). The order in which they appear will not affect the order in which they are presented within any schema module generated from the document. In documentation mode, however, an ODD processor will output the schema declarations corresponding with a specification element at the point in the text where they are encountered, provided that they are contained by a specGrp element, @@ -343,24 +266,11 @@ element -->

The gloss element may be used to provide a brief explanation for the name of the object if this is not self-explanatory. For example, the specification for the element ab used to mark arbitrary blocks of text begins as follows: - - anonymous block - - + anonymous block A gloss may also be supplied for an attribute name or an attribute value in similar circumstances: - - - suspension - the abbreviation provides the first letter(s) of the word or phrase, omitting the - remainder. - - - contraction - the abbreviation omits some letter(s) in the middle. - - - + suspensionthe abbreviation provides the first letter(s) of the word or phrase, omitting the + remainder.contractionthe abbreviation omits some letter(s) in the middle.

Note that the gloss element is needed to explain the significance of the identifier for an item only when this is not apparent, for example because it is abbreviated, as in the above example. @@ -371,37 +281,27 @@ element -->

The contents of the desc element provide a brief characterization of the intended function of the object being documented in a form that permits its quotation out of context, as in the following example: - - - identifies a word or phrase as belonging to some - language other than that of the surrounding text. - - + identifies a word or phrase as belonging to some + language other than that of the surrounding text. By convention, a desc element begins with a verb such as contains, indicates, specifies, etc. and contains a single clause.

-

Both the gloss and desc elements (in +

Both the gloss and desc elements (in addition to exemplum, remarks, and - valDesc) are members of att.translatable, and thus carry the + valDesc) are members of att.translatable, and thus carry the versionDate attributre. Where specifications are supplied in multiple languages, these elements may be repeated as often as needed. Each such element should carry both an xml:lang and a versionDate attribute to indicate the language used and the date on which the translated text was last checked against its source.

- +

The equiv element is used to document equivalencies between the concept represented by this object and the same concept as described in other schemes or ontologies. The uri attribute is used to supply a pointer to some location where such external concepts are defined. For example, to indicate that the TEI death element corresponds to the concept defined by the CIDOC CRM category E69, the declaration for the former might begin as follows: - - - - - - +

The equiv element may also be used to map newly-defined elements onto existing constructs in the TEI, using the filter and name attributes to point to an implementation of @@ -409,63 +309,33 @@ element --> shortcuts for convenience of data entry or markup readability. For example, suppose that in some TEI customization an element bo has been defined which is conceptually equivalent to the standard markup construct hi rend='bold'. The - following declarations would additionally indicate that instances of the bo element can be converted to canonical TEI by obtaining a filter from the URI specified, and + following declarations would additionally indicate that instances of the bo element can be converted to canonical TEI by obtaining a filter from the URI specified, and running the procedure with the name bold. The mimeType attribute specifies the language (in this case XSL) in which the filter is written: - - - - bold - contains a sequence of characters rendered in a bold face. - - - + boldcontains a sequence of characters rendered in a bold face.

The altIdent element is used to provide an alternative name for an object, for example using a different natural language. Thus, the following might be used to indicate that the abbr element should be identified using the German word Abkürzung: - - Abkürzung - + Abkürzung In the same way, the following specification for the graphic element indicates that the attribute url may also be referred to using the alternate identifier href: - - - - href - - - - - + href

By default, the altIdent of a component is identical to the value of its ident attribute.

The remarks element contains any additional commentary about how the item concerned may be used, details of implementation-related issues, suggestions for other ways of treating related information etc., as in the following example: - - - -

This element is intended for use only where no other element is available to mark the phrase +

This element is intended for use only where no other element is available to mark the phrase or words concerned. The global xml:lang attribute should be used in preference to - this element where it is intended to mark the language of the whole of some text element.

-

The distinct element may be used to identify phrases belonging to sublanguages or - registers not generally regarded as true languages.

- - - + this element where it is intended to mark the language of the whole of some text element.

The distinct element may be used to identify phrases belonging to sublanguages or + registers not generally regarded as true languages.

A specification element will usually conclude with a list of references, each tagged using the standard ptr element, and grouped together into a listRef element: in the case of the foreign element discussed above, the list is as follows: - - - - - + where the value COHQF is the identifier of the section in these Guidelines where this element is fully documented.

@@ -484,7 +354,7 @@ element -->

The source attribute may be used on either element to indicate the source from which an example is taken, typically by means of a pointer to an entry in an associated bibliography, as in the following example: -

L'element foreign s'applique également aux termes considerés étrangers.

@@ -527,23 +397,16 @@ to mark any technical term, thus:
Classification of Components

In the TEI scheme elements are assigned to one or more classes, which may themselves - have subclasses. The following elements are used to indicate class membership: - - - + have subclasses. The following elements are used to indicate class membership:

The classes element appears within either the elementSpec or classSpec element. It specifies the classes of which the element or class concerned is a member by means of one or more memberOf child elements. Each such element references a class by means of its key attribute. Classes themselves are defined by the classSpec element described in section below.

-

For example, to show that the element gi is a member of the class model.phrase.xml, the elementSpec which documents this element contains the +

For example, to show that the element gi is a member of the class model.phrase.xml, the elementSpec which documents this element contains the following classes element: - - - - +

@@ -561,41 +424,28 @@ to mark any technical term, thus:

The elementSpec element is used to document an element type, together with its associated attributes. In addition to the elements listed above, it may contain the following subcomponents: - - - - - - +

These subcomponents are discussed in the following sections.

Defining Content Models -

As described in and , the content of the element being +

As described in and , the content of the element being defined — that is, what elements are allowed inside it, and in what order they are permitted — is described by its content model. The content model is defined by the content child of elementSpec. There are three distinctly different ways of specifying a content model: - - The content model can be described using TEI elements - defined by this chapter, as discussed in immediately below. Two such TEI elements + The content model can be described using TEI elements + defined by this chapter, as discussed in immediately below. Two such TEI elements that may be used to define a content model are dataRef and valList. But because these are most often used to define attribute values, they are discussed - separately near the beginning and towards the end of , respectively. - Alternatively, and primarily for backwards + separately near the beginning and towards the end of , respectively.Alternatively, and primarily for backwards compatibility, the content model may be expressed using a - RELAX NG pattern. This is discussed in , below. - Lastly, content models may be expressed using a schema + RELAX NG pattern. This is discussed in , below.Lastly, content models may be expressed using a schema language other than TEI or RELAX NG, but no further recommendations on doing so are provided by these - Guidelines. -

+ Guidelines.

Defining Content Models: TEI

In the simplest case, the content model of an element may @@ -606,48 +456,34 @@ to mark any technical term, thus: would still be allowed to contain comments or processing instructions, as these are not considered part of the content model. - - - +

-

More commonly, one or more of the following elements are used +

More commonly, one or more of the following elements are used to define a content model: - - - - - - +

-

An elementRef provides the name of an element which +

An elementRef provides the name of an element which may appear at a certain point in a content model. An anyElement also asserts that an element may appear at a certain point in a content model, but rather than providing the name of a particular element type that may appear, any element regardless of its name may appear (and may have any attributes). A classRef provides the name of a model class, members - of which may appear at a certain point in content model.The classRef element may be used to + of which may appear at a certain point in content model.The classRef element may be used to refer to attribute classes, but this should not be done within a content. A macroRef provides the name of a predefined macro, the expansion of which is to be inserted at a certain point in a content model.

-

These three elements are all members of an attribute class +

These three elements are all members of an attribute class which provides attributes that further modify their significance as follows: - - - +

-

Additionally, two wrapper elements are provided to indicate +

Additionally, two wrapper elements are provided to indicate whether the components listed as their children form a sequence or an alternation: - - - - - These two wrapper elements are also members of att.repeatable. References listed as + + These two wrapper elements are also members of att.repeatable. References listed as children of sequence must appear in the order and cardinality specified. Only one of the references listed as children of alternate may appear, although the @@ -657,105 +493,53 @@ to mark any technical term, thus: ref elements (except zero); at least one element must be present, but having both a ptr and a ref would be invalid. - - - - - - - - + However, the following content model permits any number of either ptr or ref elements (except zero); one element must be present, and having both ptr elements and ref elements (even intermixed) would be valid. - - - - - - - - +

-

The sequence and alternate elements may be +

The sequence and alternate elements may be used in combination with great expressive power. For example, in the following example, which might be imagined as a clean replacement for the content of the choice element, one and only one of the element pairs sic and corr, orig and reg, or abbr and expan is allowed. - - - - - - - - - - - - - - - - - - + In the following example, which might be imagined as a clean replacement for the content of the address element, the encoder is given a choice of either: - - a single street followed by a single + a single street followed by a single placeName followed by a single postCode - followed by an optional country, or - 2, 3, or 4 - addrLine elements. - - - - - - - - - - - - - - + followed by an optional country, or2, 3, or 4 + addrLine elements. +

-

In addition to expressing where certain elements, members of +

In addition to expressing where certain elements, members of a class of elements, or constructs matching a predefined macro may occur inside an element, a content model may permit a string of zero or more Unicode characters to occur at a certain point in the content model. This is indicated by supplying the element textNode within the content element. - - - + If nothing but a textNode element is present inside a content element, valid instances of the element being defined may contain a sequence of zero or more Unicode - characters, but may not contain any elements.This content model is not used very often in the + characters, but may not contain any elements.This content model is not used very often in the TEI scheme. Because only Unicode characters are permitted, there is no way to record characters that are not (yet) represented in Unicode. Thus in TEI instead of textNode we often use a reference to macro.xtext which permits both Unicode characters and the g element.

-
-
- Defining Content Models: RELAX NG -

Element content models may also be defined using RELAX NG +

+
+ Defining Content Models: RELAX NG +

Element content models may also be defined using RELAX NG patterns. Here is a very simple example - - - - + The element within whose specification element this content element appears will have a content model which is expressed in RELAX NG as text, using the RELAX @@ -763,31 +547,19 @@ to mark any technical term, thus: when RELAX NG schemas are being generated. When an XML DTD is being generated, an equivalent declaration (in this case (#PCDATA)) will be output.

-

Here is a more complex example: - - - - - - - - - - - - +

Here is a more complex example: + This is the content model for the teiHeader element, expressed in the RELAX NG syntax, which again is copied unchanged to the output during schema generation. The equivalent DTD notation generated from this is (fileDesc, (%model.teiHeaderPart;)*, revisionDesc?).

-

The RELAX NG language does not formally distinguish element names, attribute names, class names, or +

The RELAX NG language does not formally distinguish element names, attribute names, class names, or macro names: all names are patterns which are handled in the same way, as the above example shows. Within the TEI scheme, however, different naming conventions are used to distinguish amongst the objects being named. Unqualified names (fileDesc, revisionDesc) are always - element names. Names prefixed with model. or att. (e.g. model.teiHeaderPart and att.typed) are always class names. In + element names. Names prefixed with model. or att. (e.g. model.teiHeaderPart and att.typed) are always class names. In DTD language, classes are represented by parameter entities (%model.teiHeaderPart; in the above example); see further .

-

The RELAX NG pattern names generated by an ODD processor by default include a special prefix, the +

The RELAX NG pattern names generated by an ODD processor by default include a special prefix, the default value for which is set using the prefix attribute on schemaSpec. The purpose of this is to ensure that the pattern name @@ -801,14 +573,9 @@ to mark any technical term, thus: For example, suppose that we wish to define a content model for term which permits either a TEI ident or the ident defined by some other vocabulary. A suitable content model would be generated from the following content element: - - - - - - +

-
+
Additional Constraints @@ -822,8 +589,7 @@ to mark any technical term, thus: simple XML vocabulary for an assertion language which provides a powerful way of expressing constraints on the content of any XML document in addition to those provided by other schema languages. Such constraints can be embedded within a TEI schema specification — including - a TEI customization specification — using the methods exemplified in this chapter.Indeed, these Guidelines themselves include many additional constraints + a TEI customization specification — using the methods exemplified in this chapter.Indeed, these Guidelines themselves include many additional constraints which are expressed in the ISO Schematron language using this mechanism. A conformant TEI document should respect these constraints, although automatic validation of them may not be possible for all processors. @@ -839,105 +605,39 @@ to mark any technical term, thus: passive may be supplied only if the attribute active is supplied.. In the current version of the Guidelines, constraint specifications expressed as Schematron rules have been added, as follows: - - - - One of the - attributes 'name', 'ref' or 'key' must be supplied - - - - - Only one of the - attributes @active and @mutual may be supplied - - - - - the - attribute 'passive' may be supplied only if the attribute 'active' is supplied - - - + One of the + attributes 'name', 'ref' or 'key' must be suppliedOnly one of the + attributes @active and @mutual may be suppliedthe + attribute 'passive' may be supplied only if the attribute 'active' is supplied

The constraints in the preceding example all related to attributes in the empty namespace, and the - Schematron rules did not therefore need to define a TEI namespace prefix. The Schematron language ns element should be used to do this when a constraint needs to refer to a + Schematron rules did not therefore need to define a TEI namespace prefix. The Schematron language ns element should be used to do this when a constraint needs to refer to a TEI element, as in the following example, which models the constraint that a TEI div must contain either no subdivisions or at least two of them: - - - - - - if it contains any subdivisions, a - division must contain at least two of them - - - - + if it contains any subdivisions, a + division must contain at least two of them Schematron rules are also useful where an application needs to enforce rules on attribute values, as in the following examples which check that various types of title are provided: - - - - an introductory component - of the title is expected - - - - - a main title must be supplied - - - - + an introductory component + of the title is expected a main title must be supplied +

As a further example, Schematron may be used to enforce rules applicable to a TEI document which is going to be rendered into accessible HTML, for example to check that some sort of content is available from which the alt attribute of an HTML img can be created: - - - - - - - You should provide information in a figure from - which we can construct an alt attribute in HTML - - - - - + You should provide information in a figure from + which we can construct an alt attribute in HTML Schematron rules can also be used to enforce other HTML accessibility rules about tables; note here the use of a report and an assertion within one pattern: - - - - - - - A <table> should have a caption, using a <head> - element - Do not use tables to lay out the document body - - - - - + A <table> should have a caption, using a <head> + elementDo not use tables to lay out the document body

Constraints can be expressed using any convenient language. The following example uses a pattern matching language called SPITBOL to express the requirement that title and author should be different. - - - (output = leq(title,author) "title and author cannot be the same") - - + (output = leq(title,author) "title and author cannot be the same") Note that the value of scheme is SPITBOL. In order to properly constrain and document the values of scheme used in their @@ -963,29 +663,10 @@ to mark any technical term, thus: to be made available, or whether only one of them may be used. For example, the attribute list for the element moduleRef contains a nested attribute list to indicate that either the include or the except attribute may be supplied, but not both: - - - - - - - - - - - - +

The attDef element is used to document a single attribute, using an appropriate selection - from the common elements already mentioned and the following : - - - - - - - - + from the common elements already mentioned and the following :

The attList within an elementSpec is used to specify only the attributes which are specific to that particular element. Instances of the element may carry other attributes which are @@ -996,30 +677,22 @@ to mark any technical term, thus: Datatypes

The datatype (i.e. the kind of value) for an attribute may be specified using the elements datatype and dataRef. A datatype may be defined in any of the - following three ways: - by reference to an existing TEI datatype definition, itself defined by a dataSpec; - by use of its name in XML Schema + following three ways: by reference to an existing TEI datatype definition, itself defined by a dataSpec;by use of its name in XML Schema Part 2: Datatypes Second Edition, the widely used datatype library maintained by the W3C as part of - the definition of its schema language; - by referencing its URI within some other datatype library. - The TEI defines a number of datatypes, each with an identifier beginning + the definition of its schema language;by referencing its URI within some other datatype library. The TEI defines a number of datatypes, each with an identifier beginning teidata., which are used in preference to the datatypes available natively from a target schema such as RELAX NG or W3C Schema since the facilities provided by different schema - languages vary so widely. The TEI datatypes available are described in section above. Note that each is, of necessity, mapped eventually to an externally defined datatype such + languages vary so widely. The TEI datatypes available are described in section above. Note that each is, of necessity, mapped eventually to an externally defined datatype such as W3C Schema's text or name, possibly combined to give more expressivity, or constrained to a particular defined usage.

It is possible to reference a W3C schema datatype directly using name. In this case, the child dataFacet can be used instead of restriction to set W3C schema compliant restrictions on the datatype. A dataFacet is particularly useful for restrictions that can be difficult to impose and to read as a regular expression pattern. - - - - + Note that restrictions are either expressed with restriction or dataFacet, never both.

-

A datatype may be used to constrain the textual content of +

A datatype may be used to constrain the textual content of an element, rather than the value of an attribute. But because they are intended for use in defining ranges of attribute values, datatypes may not contain elements or attributes.

@@ -1029,22 +702,11 @@ to mark any technical term, thus: specified. For example, the columns attribute of the layout element can have one or two non-negative integers as its value: - - - columns - specifies the number of columns per page - - - - -

If a single number is given, all pages referenced + columnsspecifies the number of columns per page

If a single number is given, all pages referenced have this number of columns. If two numbers are given, the number of columns per page varies between the values supplied. Where columns is omitted - the number is assumed to be 1.

- - - + the number is assumed to be 1.

indicating that the target attribute may take any number of values, each being of the same datatype, namely the TEI data specification teidata.pointer. As is usual in XML, multiple values for a single attribute are separated by one or more white space characters. Hence, @@ -1069,39 +731,17 @@ to mark any technical term, thus: example, to specify that an imaginary attribute ageAtDeath must take positive integer values less than 150, the datatype teidata.numeric might be used in combination with a constraintSpec such as the following: - - - age in years at death - - - - age at death must be an integer less than 150 - - - - + age in years at death age at death must be an integer less than 150

The elements altIdent, equiv, gloss and desc may all be used in the same way as they are elsewhere to describe fully the meaning of a coded value, as in the following example: - - - dou - - dubious - used when the application of this element is doubtful or uncertain - - + doudubiousused when the application of this element is doubtful or uncertain

Where all the possible values for an attribute can be enumerated, the datatype teidata.enumerated should be used, together with a valList element specifying the values and their significance, as in the following example: - - required - recommended - optional - - + requiredrecommendedoptional Note the use of the gloss element here to explain the otherwise less than obvious meaning of the codes used for these values. Since this value list specifies that it is of type closed, only the values enumerated are legal, and an ODD processor will typically @@ -1109,28 +749,8 @@ to mark any technical term, thus:

The valList element can also be used to provide illustrative examples of the kinds of values expected without listing all of them. In such cases the type attribute will have the value open, as in the following example: - - characterizes the movement, for example as an - entrance or exit. - 예를 들어 입장 또는 퇴장과 같은, 이동의 특성을 기술한다. - - - - - - character is entering the stage. - 등장인물이 무대에 등장하고 있다. - - - character is exiting the stage. - 등장인물이 무대에서 퇴장하고 있다. - - - character moves on stage - 등장인물이 무대에서 이동한다. - - - + characterizes the movement, for example as an + entrance or exit.예를 들어 입장 또는 퇴장과 같은, 이동의 특성을 기술한다.character is entering the stage.등장인물이 무대에 등장하고 있다.character is exiting the stage.등장인물이 무대에서 퇴장하고 있다.character moves on stage등장인물이 무대에서 이동한다. The datatype will be teidata.enumerated in either case.

The valList or dataRef elements may also be used (as a child of the content element) to put constraints on the permitted content of an element, as noted at @@ -1212,11 +832,7 @@ xmlns="http://www.tei-c.org/ns/Examples"> one or more possible models for such processing, both to clarify the intentions of the encoder, and to provide default behaviours for a software engineer to implement when documents conforming to a particular TEI customization are processed. To that end, the following elements may be used to - document one or more processing models for a given element. - - - - + document one or more processing models for a given element.

One or more of these elements may appear directly within an element specification to define the processing anticipated for that element, more specifically how it should be processed to produce the @@ -1231,8 +847,7 @@ xmlns="http://www.tei-c.org/ns/Examples"> high-level formatting concepts familiar to software engineers and web designers, such as block or inline. As such, it has a different purpose from existing TEI mechanisms for documenting the appearance of source materials, such as the global - attributes rend, rendition and style, described in sections and . It does not necessarily describe anything present in + attributes rend, rendition and style, described in sections and . It does not necessarily describe anything present in the original source, nor does it necessarily represent its original structure or semantics. A processing model is a template description, which may be used to simplify the task of producing or customizing the stylesheets needed by a formatting engine or any other form of processor.

@@ -1240,10 +855,7 @@ xmlns="http://www.tei-c.org/ns/Examples"> The TEI processing model

The model element is used to document the processing model intended for a particular element in an abstract manner, independently of its implementation in whatever processing language - is chosen. This is achieved by means of the following attributes and elements: - - - The mandatory behaviour attribute defines in broad terms how an element + is chosen. This is achieved by means of the following attributes and elements: The mandatory behaviour attribute defines in broad terms how an element should be processed, for example as a block or as an inline element. The optional predicate attribute may be used to specify a subset of contexts in which this model should be applicable: for example, an element might be treated as a block element in some contexts, @@ -1262,33 +874,21 @@ xmlns="http://www.tei-c.org/ns/Examples">

Here is a simple example of a processing model which might be included in the specification for an element such as hi or foreign. The intent is that these elements should be presented inline using an italic font. - - - font-style: italic; - - + font-style: italic; If the rendition element, or the attributes style, rend, or rendition have already been used in the source document to indicate elements that were originally rendered in italic, and we wish simply to follow this in our processing, then there is no need to include an outputRendition element, and the attribute useSourceRendition could be used as follows: - - - + Any rendition information present in the source document will be ignored unless the useSourceRendition attribute has the value true. If that is the case, then such information will be combined with any rendition information supplied by the outputRendition element. For example, using CSS, an element which appears in the source as follows - - this is in bold - + this is in bold would appear in bold and italic if processed by the following model - - - font-style: italic; - - + font-style: italic;

@@ -1300,26 +900,12 @@ xmlns="http://www.tei-c.org/ns/Examples"> models. For example, supposing that the associated CSS stylesheet includes a CSS class called labeled-list, the following processing model might be used to request it be used for list elements containing a child label element: - - - - - - - +

In the following example, a table will be formatted using renditional information provided in the source if that is available, or by an external stylesheet, using one of the CSS classes specified, if it is not: - - - - - - - - +

As discussed further below, the input data available to a processing model is by default the content of the element being processed, together with its child nodes.

@@ -1358,14 +944,7 @@ xmlns="http://www.tei-c.org/ns/Examples"> appears inside a p element, but as an indented block when it appears elsewhere. To achieve this, we need to change the specification for the quote element to include two model elements as follows: - - - font-style: italic; - - - left-margin: 2em; - - + font-style: italic;left-margin: 2em; As noted above, these two models are mutually exclusive. The first processing model will be used only for quote elements which match the XPath expression given as value for the predicate attribute. All other element occurrences will use the second processing @@ -1379,24 +958,7 @@ xmlns="http://www.tei-c.org/ns/Examples"> technical specialist.

The modelGrp element can be used to group together all the processing models which have in common a particular intended output, as in the following example: - - - - font-size: 7pt; - - - text-color: red; - - - - - font-size: 12pt; - - - text-align: center; - - - + font-size: 7pt;text-color: red;font-size: 12pt;text-align: center;

@@ -1409,11 +971,7 @@ xmlns="http://www.tei-c.org/ns/Examples"> arguments of a function in many programming languages: they provide names which can be used to distinguish particular parts of the input data available to the process used to implement the behaviour in question.

-

The following elements are used to represent and to define parameters: - - - -

+

The following elements are used to represent and to define parameters:

By default, a processor implementing the TEI processing model for a particular element has available to it as input data the content of the element itself, and all of its children. One or more param elements may be supplied within a model element to specify @@ -1432,13 +990,7 @@ xmlns="http://www.tei-c.org/ns/Examples"> to provide the former, while the latter is provided by the content of the ref element itself: - - - - - - - + The value attribute of a param element supplies an XPath expression that indicates where the required value may be found. The context for this XPath is the element which is being processed; hence in this example, the uri parameter takes the value of the @@ -1451,13 +1003,7 @@ xmlns="http://www.tei-c.org/ns/Examples"> behaviour itself, as further discussed in section below.

As a further example, the TEI choice element requires a different behaviour for which the name alternate is proposed as in the following example: - - - - - - - + The processing model shown here will be selected for processing a choice element which has both sic and corr child elements. The names default and alternate here are provided for convenience. The default parameter provides the value of the child corr element, and the alternate @@ -1467,35 +1013,13 @@ xmlns="http://www.tei-c.org/ns/Examples">

A choice element might contain multiple corrections, each with differing values for their cert attribute. In the following processing model, we will accept as value of the default attribute only those child corr elements which have a value high for that attribute: - - - - - - - +

A choice element might contain several different pairs of alternate elements (abbr and expan, orig and reg, etc.) We might wish to group together a set of processing models for these, for example to determine which of the possible alternatives is displayed by default whenever a choice element is processed for output to the web: - - - - - - - - - - - - - - - - - +

If nothing matches the XPath defining the value of a particular parameter (e.g. if in the above example there is no correction with cert=high) then the default @@ -1546,18 +1070,7 @@ xmlns="http://www.tei-c.org/ns/Examples"> different behaviour (here called footnote) should be used to display the content of the element at a specified place, given by the parameter place. Because both of these actions are required, the two models are grouped by a modelSequence element: - - - - - - - - - - - - +

The value of the parameter called place above is an XPath expression supplying an arbitrary string (foot), which is therefore quoted. It is left to implementors to validate or @@ -1574,39 +1087,15 @@ xmlns="http://www.tei-c.org/ns/Examples"> grouped together in a paramList element. This paramList is supplied within the valItem used to document and name the behaviour. Here for example is the valItem which defines the link behaviour presented above: - - - create a hyperlink - - - supplies the location of some content describing the link - - - supplies the location of the intended hyperlink - - - - + create a hyperlinksupplies the location of some content describing the linksupplies the location of the intended hyperlink

Similarly the valItem which defines the behaviour named alternate includes specifications for two parameters: one also called alternate and the other called default - - - support display of alternative visualisations, for + support display of alternative visualisations, for example by displaying the preferred content, by displaying both in parallel, or by toggling - between the two. - - - supplies the location of the preferred - content - - - supplies the location of the alternative - content - - - - + between the two.supplies the location of the preferred + contentsupplies the location of the alternative + content

The suggested behaviours provided by the model element are informally defined using commonly understood terminology, but specific details of how they should be implemented are left to @@ -1623,47 +1112,30 @@ xmlns="http://www.tei-c.org/ns/Examples"> free standing pipeline, or to extract and process them dynamically during document processing. However, although implementors are generally free to interpret the processing model documentation according to their own requirements, some general assumptions underlie the - recommendations made here: - If a model element has no child param elements, the action specified by + recommendations made here: If a model element has no child param elements, the action specified by its behaviour should be applied to the whole element node concerned, including its child nodes of whatever type. If that behaviour requires distinguishing particular parts of the input, an - implementation may choose either to make those distinctions itself, or to raise an error. - If a model element has no predicate or output attribute then + implementation may choose either to make those distinctions itself, or to raise an error.If a model element has no predicate or output attribute then it is assumed to apply to all instances of the element defined in its parent elementSpec for all outputs. Otherwise its applicability depends on these - attributes. - Only one of the models is to be applied for a particular instance of the element, except when they appear + attributes.Only one of the models is to be applied for a particular instance of the element, except when they appear within a modelSequence - - A matching model is one where the element to be processed satisfies the XPath in the + A matching model is one where the element to be processed satisfies the XPath in the predicate attribute of the model or modelSequence and the current output method matches the method specified in the output attribute of the model, modelSequence, or a containing modelGrp. A model or modelSequence without a predicate always matches the element to be processed. A model, - modelGrp, or modelSequence without an output attribute matches any output method. - Processing Model implementations must execute only the first matching model or - modelSequence in document order. - If there are two or more model elements provided for an elementSpec but + modelGrp, or modelSequence without an output attribute matches any output method.Processing Model implementations must execute only the first matching model or + modelSequence in document order.If there are two or more model elements provided for an elementSpec but they have different output attributes then the implementation should choose the - model appropriate to the desired output. - If there are two or more model elements provided for an elementSpec but + model appropriate to the desired output. If there are two or more model elements provided for an elementSpec but they have different predicate attributes then the implementation should choose the model whose predicate provides the most specific context (where specific is understood in the same way as in XSLT) - - In the following example, which shows part of the element specification for the head + In the following example, which shows part of the element specification for the head element, there are two model elements, one with and one without a predicate attribute: - - - Model for list headings - - - - Default model for all headings. - - - + Model for list headingsDefault model for all headings. In this example, an implementation should use the first processing model only for head elements with a list element as parent; for all other head elements, the second processing model should be used.

@@ -1695,31 +1167,17 @@ xmlns="http://www.tei-c.org/ns/Examples"> Class Specifications

The element classSpec is used to document either an attribute class or a model class, as defined in section . A corresponding - classRef element may be used to select a specific named class from those available. - - - - + classRef element may be used to select a specific named class from those available.

A model class specification does not list all of its members. Instead, its members declare that they belong to it by means of a classes element contained within the relevant elementSpec. This will contain a memberOf element for each class of which the relevant element is a member, supplying the name of the relevant class. For example, the elementSpec for the element hi contains the following: - - - - - This indicates that the hi element is a member of the class with identifier model.hiLike. The classSpec element that documents this class contains + + This indicates that the hi element is a member of the class with identifier model.hiLike. The classSpec element that documents this class contains the following declarations: - - groups phrase-level elements related to highlighting that have no specific semantics - - - - - + groups phrase-level elements related to highlighting that have no specific semantics which indicate that the class model.hiLike is actually a member (or subclass) of the class model.highlighted.

The function of a model class declaration is to provide another way of referring to a group of @@ -1733,33 +1191,18 @@ xmlns="http://www.tei-c.org/ns/Examples"> classRef element within the content of an elementSpec), its meaning will depend on the value of its expand attribute.

If this attribute is not specified, the classRef is interpreted to mean an alternated list of - all the current members of the class named. For example, suppose that the members of the class model.hiLike are elements hi, it, and bo. Then a content model such as - - - + all the current members of the class named. For example, suppose that the members of the class model.hiLike are elements hi, it, and bo. Then a content model such as + would be equivalent to the explicit content model: - - - - - - - + (or, to use RELAX NG compact syntax, - ( hi | it | bo )). + ( hi | it | bo )). However, a content model of <classRef - expand="sequence"/> would be equivalent to the + expand="sequence"/> would be equivalent to the following explicit content model: - - - - - - + (or, in RELAX NG compact syntax, - ( hi, it, bo )).

+ ( hi, it, bo )).

-

The specification elements, and some of their children, are all members of the att.identified class, from which they inherit the following attributes: - - This attribute class is a subclass of the att.combinable class - from which it (and some other elements) inherits the following attribute: - - This attribute class, in turn, is a subclass of the att.deprecated class, from which it inherits the following attribute: - - The validUntil attribute may be used to signal an intent to remove a construct +

The specification elements, and some of their children, are all members of the att.identified class, from which they inherit the following attributes: This attribute class is a subclass of the att.combinable class + from which it (and some other elements) inherits the following attribute: This attribute class, in turn, is a subclass of the att.deprecated class, from which it inherits the following attribute: The validUntil attribute may be used to signal an intent to remove a construct from future versions of the schema being specified.

@@ -1886,9 +1317,7 @@ xmlns="http://www.tei-c.org/ns/Examples">

The elementSpec, attDef and schemaSpec specification elements also have an attribute which determines which namespace to which the object being created will belong. In the case of schemaSpec, this namespace is inherited by all the elements created in the schema, unless - they have their own ns. - - + they have their own ns.

These attributes are used by an ODD processor to determine how declarations are to be combined to form @@ -1904,10 +1333,7 @@ xmlns="http://www.tei-c.org/ns/Examples"> with existing ones, or to modify particular parts of existing declarations.

In the simplest case, a user-defined schema might just combine all the declarations from two nominated modules: - - - - + An ODD processor, given such a document, should combine the declarations which belong to the named modules, and deliver the result as a schema of the requested type. It may also generate documentation for the elements declared by those modules. No source is specified for the modules, and the schema @@ -1942,75 +1368,36 @@ most recent version of the Guidelines would be used instead.-->

that module. This may be modified by means of the attributes include and except which allow the encoder to supply an explicit lists of elements from the stated module which are to be included or excluded respectively. For example: - - - - + The schema specified here will include all the elements supplied by the core module except for add, del, orig, and reg. It will also include only the linkGrp and link elements from the linking module.

Alternatively, the element elementRef may be used to indicate explicitly which elements are to be included in a schema. The same effect as the preceding example might thus be achieved by the following: - - - - - + Note that in this last case, there is no need to specify the name of the module from which the two element declarations are to be found; in the TEI scheme, element names are unique across all modules. The module is simply a convenient way of grouping together a number of related declarations.

In the same way, a schema may select a subset of the attributes available in a specific class, using the classRef element to point to an attribute class: - - - - - - + Here, only the corresp attribute is included; the other attributes in the class are not available. The same effect can be achieved using except: - - - - - - +

A schema may also include declarations for new elements, as in the following example: - - - - - - - + A declaration for the element soundClip, which is not defined in the TEI scheme, will be added to the output schema. This element will also be added to the existing TEI class model.pPart.data, and will thus be available in TEI conformant documents. Attributes from existing TEI classes could be added to the new element using attRef: - - - - - - - - - - + This will provide the source attribute from the att.global.source class on the new soundClip element.

A schema might also include re-declarations of existing elements, as in the following example: - - - - - - - - + The effect of this is to redefine the content model for the element head as plain text, by over-riding the content child of the selected elementSpec. The attribute specification mode="change" has the effect of over-riding only those children elements of @@ -2023,72 +1410,18 @@ most recent version of the Guidelines would be used instead.-->

mode attribute is used to determine exactly how the second declaration (and its constituents) should be combined with the first. The following table summarizes how a processor should resolve duplicate declarations; the term identifiable refers to those elements which can - have a mode attribute: - - mode value - existing declaration - effect - - - add - no - add new declaration to schema; process its children in add mode - - - add - yes - raise error - - - replace - no - raise error - - - replace - yes - retain existing declaration; process new children in replace mode; ignore existing - children - - - change - no - raise error - - - change - yes - process identifiable children according to their modes; process unidentifiable children in - replace mode; retain existing children where no replacement or change is provided - - - delete - no - raise error - - - delete - yes - ignore existing declaration and its children - -
+ have a mode attribute: mode valueexisting declarationeffectaddnoadd new declaration to schema; process its children in add modeaddyesraise errorreplacenoraise errorreplaceyesretain existing declaration; process new children in replace mode; ignore existing + childrenchangenoraise errorchangeyesprocess identifiable children according to their modes; process unidentifiable children in + replace mode; retain existing children where no replacement or change is provided deletenoraise errordeleteyesignore existing declaration and its children

Combining TEI and Non-TEI Modules

In the simplest case, all that is needed to include a non-TEI module in a schema is to reference its RELAX NG source using the url attribute on moduleRef. The following specification, - for example, creates a schema in which declarations from the non-TEI module svg11.rng (defining Standard Vector Graphics) are included. To avoid any risk of name + for example, creates a schema in which declarations from the non-TEI module svg11.rng (defining Standard Vector Graphics) are included. To avoid any risk of name clashes, the schema specifies that all TEI patterns generated should be prefixed by the string "TEI_". - - - - - - - - +

This specification generates a single schema which might be used to validate either a TEI document (with the root element TEI), or an SVG document (with a root element svg:svg), but @@ -2096,19 +1429,10 @@ most recent version of the Guidelines would be used instead.-->

SVG language. For that to be possible, the svg:svg element must become a member of a TEI model class (), so that it may be referenced by other TEI elements. To achieve this, we modify the last moduleRef in the above example as follows: - - - - - - - - - +

This states that when the declarations from the svg11.rng module are - combined with those from the other modules, the declaration for the model class model.graphicLike in the TEI module should be extended to include the element + combined with those from the other modules, the declaration for the model class model.graphicLike in the TEI module should be extended to include the element svg:svg as an alternative. This has the effect that elements in the TEI scheme which define their content model in terms of that element class (notably figure) can now include it. A RELAX NG schema generated from such a specification can be used to validate documents in which the TEI @@ -2120,8 +1444,7 @@ most recent version of the Guidelines would be used instead.-->

Linking Schemas to XML Documents

Schemas can be linked to XML documents by means of the ?xml-model? processing instruction described in the W3C Working Group Note Associating Schemas with XML - documents (). ?xml-model? can be used for any type of schema, and may be used for multiple schemas: + documents (). ?xml-model? can be used for any type of schema, and may be used for multiple schemas: ]]> This example includes a standard RELAX NG schema, a Schematron schema which might be used for checking @@ -2134,29 +1457,16 @@ most recent version of the Guidelines would be used instead.-->

Module for Documentation Elements

The module described in this chapter makes available the following components: - - Documentation Elements - Documentation of TEI and other XML markup languages - Éléments de déclaration d’un modèle - TEI模組說明 - Documentazione dei moduli TEI - Documentação dos módulos TEI - タグ定義モジュール - + Documentation ElementsDocumentation of TEI and other XML markup languagesÉléments de déclaration d’un modèleTEI模組說明Documentazione dei moduli TEIDocumentação dos módulos TEIタグ定義モジュール The selection and combination of modules to form a TEI schema is - described in .

The elements described - in this chapter are all members of one of three classes: model.oddDecl, model.oddRef, or model.phrase.xml, with the exceptions of - schemaSpec (a member of model.divPart) and both eg and egXML - (members of model.common and model.egLike). All of these classes are + described in .

+

The elements described + in this chapter are all members of one of three classes: model.oddDecl, model.oddRef, or model.phrase.xml, with the exceptions of + schemaSpec (a member of model.divPart) and both eg and egXML + (members of model.common and model.egLike). All of these classes are declared along with the other general TEI classes, in the basic - structure module documented in .

-

In addition, some elements are members of the att.identified class, which is documented in + structure module documented in .

+

In addition, some elements are members of the att.identified class, which is documented in above.

diff --git a/P5/Source/Guidelines/en/TS-TranscriptionsofSpeech.xml b/P5/Source/Guidelines/en/TS-TranscriptionsofSpeech.xml index c6385f2a2e..89bb0a0c24 100644 --- a/P5/Source/Guidelines/en/TS-TranscriptionsofSpeech.xml +++ b/P5/Source/Guidelines/en/TS-TranscriptionsofSpeech.xml @@ -1,16 +1,9 @@ - +
-Transcriptions of Speech - -

The module described in this chapter is intended for use with a + Transcriptions of Speech +

The module described in this chapter is intended for use with a wide variety of transcribed spoken material. It should be stressed, however, that the present proposals are not intended to support unmodified every variety of research undertaken upon spoken material @@ -21,7 +14,7 @@ their transcriptions. Speech regarded as a purely acoustic phenomenon may well require different methods from those outlined here, as may speech regarded solely as a process of social interaction.

-

This chapter begins with a discussion of some of the problems +

This chapter begins with a discussion of some of the problems commonly encountered in transcribing spoken language (section ). Section documents some additional TEI header elements which may be used to document the recording or other source from which transcribed text is taken. @@ -30,10 +23,9 @@ provided by this module. Finally, section of this chapter reviews further problems specific to the encoding of spoken language, demonstrating how mechanisms and elements discussed elsewhere in these Guidelines may be applied to them.

- - -
General Considerations and Overview -

There is great variation in the ways different researchers have +

+ General Considerations and Overview +

There is great variation in the ways different researchers have chosen to represent speech using the written medium.For a discussion of several of these see ; ; and . This @@ -56,7 +48,7 @@ recording and making public what was produced in a private setting and intended for a limited audience are more frequently encountered in dealing with spoken texts than with written ones.

-

Speech also poses difficult structural problems. Unlike a written +

Speech also poses difficult structural problems. Unlike a written text, a speech event takes place in time. Its beginning and end may be hard to determine and its internal composition difficult to define. Most researchers agree that the utterances or turns of @@ -75,15 +67,14 @@ into units defined by phonological, prosodic, or syntactic phenomena; no clear agreement exists, however, even as to appropriate names for such segments.

- -

Spoken texts transcribed according to the guidelines presented here +

Spoken texts transcribed according to the guidelines presented here are organized as follows. The overall structure of a TEI spoken text is identical to that of any other TEI text: the TEI element for a spoken text contains a teiHeader element, followed by a text element. Even texts primarily composed of transcribed speech may also include conventional front and back matter, and may even be organized into divisions like printed texts.

-

We may say, therefore, that these Guidelines regard transcribed +

We may say, therefore, that these Guidelines regard transcribed speech as being composed of arbitrary high-level units called texts.textsas organizing unit for spoken material A spoken text might typically be a conversation between a small number @@ -99,8 +90,7 @@ described below (). Details concerning additional elements which may be used for the documentation of participant and contextual information are given in .

- -

Defining the bounds of a spoken text is frequently a matter of +

Defining the bounds of a spoken text is frequently a matter of arbitrary convention or convenience. In public or semi-public contexts, a text may be regarded as synonymous with, for example, a lecture, a broadcast item, a meeting, etc. In informal or private @@ -108,14 +98,10 @@ contexts, a text may be simply a conversation involving a specific group of participants. Alternatively, researchers may elect to define spoken texts solely in terms of their duration in time or length in words. By default, these Guidelines assume of a text only that: - -it is internally cohesive, -it is describable by a single header, and -it represents a single stretch of time with no significant +it is internally cohesive,it is describable by a single header, andit represents a single stretch of time with no significant discontinuities.

- -

Within a text it may be necessary to identify subdivisions +

Within a text it may be necessary to identify subdivisions of various kinds, if only for convenience of handling. The neutral div element discussed in section is recommended for this purpose. It may be found useful also for @@ -125,24 +111,16 @@ are hierarchically well-behaved. Where they are not, as is often the case, the mechanisms discussed in chapters and may be used.

- -

A spoken text may contain any of the following components: - -utterances -pauses -vocalized but non-lexical phenomena such as coughs -kinesic (non-verbal, non-lexical) phenomena such as gestures -entirely non-linguistic incidents occurring during and possibly -influencing the course of speech -writing, regarded as a special class of incident in that it can +

A spoken text may contain any of the following components: +utterancespausesvocalized but non-lexical phenomena such as coughskinesic (non-verbal, non-lexical) phenomena such as gesturesentirely non-linguistic incidents occurring during and possibly +influencing the course of speechwriting, regarded as a special class of incident in that it can be transcribed, for example captions or overheads displayed during -a lecture -shifts or changes in vocal quality +a lectureshifts or changes in vocal quality

-

Elements to represent all of these features of spoken language are +

Elements to represent all of these features of spoken language are discussed in section below.

-

An utterance (tagged u) may contain lexical items +

An utterance (tagged u) may contain lexical items interspersed with pauses and non-lexical vocal sounds; during an utterance, non-linguistic incidents may occur and written materials may be presented. The u element can thus contain any of the other @@ -151,8 +129,7 @@ of the utterance; the other elements may all appear between utterances or next to each other, but except for writing they do not contain any other elements nor any data.

- -

A spoken text itself may be without substructure, that is, it may +

A spoken text itself may be without substructure, that is, it may consist simply of units such as utterances or pauses, not grouped together in any way, or it may be subdivided. If the notion of what constitutes a text in spoken discourse is @@ -168,7 +145,7 @@ complete text. Examples might include provided only that the set of all such divisions is coextensive with the text.

-

Each such division of a spoken text should be represented by the +

Each such division of a spoken text should be represented by the numbered or unnumbered div elements defined in chapter . For some detailed kinds of analysis a hierarchy of such divisions may be found useful; nested div elements may be used for this purpose, as in the following example showing how a @@ -176,43 +153,31 @@ collection made up of transcribed sound bites taken from speeches given by a politician on different occasions might be encoded. Each extract is regarded as a distinct div, nested within a single composite div as -follows:

-
-
-
-
-
-
-
+follows:
+
+
+

-

As a member of the class att.declaring, the +

As a member of the class att.declaring, the div element may also carry a decls attribute, for use where the divisions of a text do not all share the same set of the contextual declarations specified in the TEI header. (See further section ). -

- -
- -
Documenting the Source of Transcribed Speech -

Where a computer file is derived from a spoken text rather than a +

+
+
+ Documenting the Source of Transcribed Speech +

Where a computer file is derived from a spoken text rather than a written one, it will usually be desirable to record additional information about the recording or broadcast which constitutes its source. Several additional elements are provided for this purpose within the source description component of the TEI header: - - - - - - + As a member of the att.duration class, the recording element inherits the following attribute: - - - +

-

Note that detailed information about the participants or setting of +

Note that detailed information about the participants or setting of an interview or other transcript of spoken language should be recorded in the appropriate division of the profile description, discussed in chapter , rather than as part of the source @@ -223,24 +188,16 @@ recording was produced. If the source was a previously-created transcript, it should be treated in the same way as any other source text.

-

The scriptStmt element should be used where it is known that +

The scriptStmt element should be used where it is known that one or more of the participants in a spoken text is speaking from a previously prepared script. The script itself should be documented in the same way as any other written text, using one of the three citation tags mentioned above. Utterances or groups of utterances may be linked to the script concerned by means of the decls attribute, described in section . - - - - CNN Network News - News headlines - 12 Jun 91 - - - +CNN Network NewsNews headlines12 Jun 91

-

The recordingStmt is used to group together information +

The recordingStmt is used to group together information relating to the recordings from which the spoken text was transcribed. The element may contain either a prose description or, more helpfully, one or more recording elements, each corresponding with a @@ -248,58 +205,27 @@ particular recording. The linkage between utterances or groups of utterances and the relevant recording statement is made by means of the decls attribute, described in section .

-

The recording element should be used to provide a +

The recording element should be used to provide a description of how and by whom a recording was made. This information may be provided in the form of a prose description, within which such items as statements of responsibility, names, places, and dates may be identified using the appropriate phrase-level tags. Alternatively, a selection of elements from the model.recordingPart class may be provided. This element class makes available the following elements: - - - - - - - +

-

Specialized +

Specialized collections may wish to add further sub-elements to these major components. These elements should be used only for information relating to the recording process itself; information about the setting or participants (for example) is recorded elsewhere: see sections and . - - -

U-matic recording made by college audio-visual department staff, - available as PAL-standard VHS transfer or sound-only cassette

- - - - - Location recording by - Sound Services Ltd. - - -

Multiple close microphones mixed down to stereo Digital - Audio Tape, standard play, 44.1 KHz sampling frequency

- - 12 Jan 1987 - - - - -14 Feb 2001 - - -17 Feb 2001 - - -22 Feb 2001 - - -

-

When a recording has been made from a public broadcast, details of +

U-matic recording made by college audio-visual department staff, + available as PAL-standard VHS transfer or sound-only cassette

+Location recording bySound Services Ltd.

Multiple close microphones mixed down to stereo Digital + Audio Tape, standard play, 44.1 KHz sampling frequency

12 Jan 1987 +14 Feb 200117 Feb 200122 Feb 2001

+

When a recording has been made from a public broadcast, details of the broadcast itself should be supplied within the recording element, as a nested broadcast element. A broadcast is closely analogous to a publication and the broadcast element should @@ -310,57 +236,39 @@ author, while other participants (for example interviewers, interviewees, script writers, directors, producers, etc.) should be specified using the respStmt or editor element with an appropriate resp (see further section ). - -

Recorded from FM Radio to digital tape

- - - Interview on foreign policy BBC Radio 5 - interviewerRobin Day - intervieweeMargaret Thatcher - The World Tonight - First broadcast on 27 Nov 1989 - - -

-

When a broadcast contains several distinct recordings (for example a +

Recorded from FM Radio to digital tape

Interview on foreign policyBBC Radio 5interviewerRobin DayintervieweeMargaret ThatcherThe World TonightFirst broadcast on 27 Nov 1989

+

When a broadcast contains several distinct recordings (for example a compilation), additional recording elements may be further nested within the broadcast element. - - - - - - + +

-

The transcriptionDesc element can be used to document the particular transcription conventions (use of space, +

The transcriptionDesc element can be used to document the particular transcription conventions (use of space, punctuation, special characters etc.) used in making the transcription. A number of sets of such conventions have been defined within particular research communities, or by users of particular transcription tools. The attributes ident and version may be used to refer to such conventions in a machine tractable way, where this is appropriate. - - - +

- - - - - - - - - -
- -
Elements Unique to Spoken Texts -

The following elements characterize spoken texts, transcribed + + + + + + + + +

+
+ Elements Unique to Spoken Texts +

The following elements characterize spoken texts, transcribed according to these Guidelines:

-

The u element may appear directly within a spoken text, +

The u element may appear directly within a spoken text, and may contain any of the others; the others may also appear directly (for example, a vocal may appear between two utterances) but cannot contain a u element. In terms of the basic TEI model, @@ -370,31 +278,20 @@ elements, but with the important difference that they can exist either as siblings or as children of utterances. The class model.divPart.spoken provides the u element; the class model.global.spoken provides the six other elements listed above.

- -

As members of the att.ascribed class, +

As members of the att.ascribed class, all of these elements share the following attributes: As members of the att.typed, att.timed and att.duration classes, all of these elements except shift share the following attribute: - - - - - +

-

Each of these elements is further discussed and specified in +

Each of these elements is further discussed and specified in sections to .

-

We can show the relationship between four of these constituents of +

We can show the relationship between four of these constituents of speech using the features eventive, communicative, anthropophonic (for sounds produced by the human vocal apparatus), and lexical: - - eventivecommunicativeanthropophoniclexical -incident+--- -kinesic++-- -vocal+++- -utterance++++ -
+ eventivecommunicativeanthropophoniclexicalincident+---kinesic++--vocal+++-utterance++++
The differences are not always clear-cut. Among incidents might be included actions like slamming the door, which can certainly be communicative. Vocals include coughing and sneezing, which arevocal eventsin @@ -406,7 +303,7 @@ may differ in the way borderlines are drawn and should declare their definitions in the editorialDecl element of the header (see ).

-

The following short extract exemplifies several of these elements. It +

The following short extract exemplifies several of these elements. It is recoded from a text originally transcribed in the CHILDES format.The original is a conversation between two children and their parents, recorded in 1987, and discussed in @@ -420,37 +317,20 @@ either with orthographic transcriptions or with the vocal element, and entirely non-linguistic but significant incidents such as the sound of the toy cat are represented by the incident elements (see section ). - - - - - - - - -you +you never take this cat for show and tell - meow meow -yeah well I dont want to -toy cat has bell in tail which continues to make a tinkling sound -meows -because it is so old -how boutabout + meow meowyeah well I dont want totoy cat has bell in tail which continues to make a tinkling soundmeowsbecause it is so oldhow boutabout your cat yours is new - shows Father the cat -thats darling -no mine isnt old -mine is just um a little dirty - + shows Father the cat thats darlingno mine isnt oldmine is just um a little dirty

-

This example also uses some elements common to all TEI texts, +

This example also uses some elements common to all TEI texts, notably the reg tag for editorial regularization. Unusually stressed syllables have been encoded with the emph element. The seg element has also been used to segment the last utterance. Further discussion of all of such options is provided in section .

-

Contextual information is of particular importance in spoken texts, +

Contextual information is of particular importance in spoken texts, and should be provided by the TEI header of a text. In general, all of the information in a header is understood to be relevant to the whole of the associated text. The element u as a member of the @@ -458,13 +338,13 @@ of the associated text. The element u as a member of the different context by means of the decls attribute (see further section ).

-
Utterances -

Each distinct utterance in a spoken text is represented +

+ Utterances +

Each distinct utterance in a spoken text is represented by a u element, described as follows: - - +

-

Use of the who attribute to associate the utterance with a +

Use of the who attribute to associate the utterance with a particular speaker is recommended but not required. Its use implies as a further requirement that all speakers be identified by a person or personGrp element, typically in the TEI @@ -476,8 +356,7 @@ participants, the encoder may choose to create personGrp elements with xml:id attributes such as various or unknown, and perhaps give the root listPerson element an xml:id value of all, then point to those as appropriate using who.

- -

The trans attribute is provided as a means of +

The trans attribute is provided as a means of characterizing the transition from one utterance to the next at a simpler level of detail than that provided by the temporal alignment mechanism discussed in section . The value specified @@ -486,10 +365,7 @@ utterance bearing the attribute. For example:For the most part, the examples in this chapter use no sentence punctuation except to mark the rising intonation often found in interrogative statements; for further discussion, see section . -Have you heard the -the election results? yes -it's a disaster -it's a miracle +Have you heard thethe election results? yesit's a disasterit's a miracle In this example, utterance ts_b1 latches on to utterance ts_a1, while there is a marked pause between ts_b1 and ts_a2. ts_b2 and @@ -497,7 +373,7 @@ In this example, utterance ts_b1 latches on to utterance providing a more precise indication of the degree of overlap, see section .

-

An utterance may contain either running text, or text within which +

An utterance may contain either running text, or text within which other basic structural elements are nested. Where such nesting occurs, the who attribute is considered to be inherited for the elements pause, vocal, shift, and @@ -505,7 +381,7 @@ elements pause, vocal, shift, and is regarded as being produced by that speaker only, while a pause between utterances applies to all speakers.

-

Occasionally, an utterance may seem to contain other utterances, +

Occasionally, an utterance may seem to contain other utterances, for example where one speaker interrupts himself, or when another speaker produces a back-channel while they are still speaking. The present version of these @@ -522,14 +398,15 @@ Alternatively the incident element described in section So what could I have done tut-tutting about it anyway? Where this is not possible, it is simplest to regard the back-channel as a distinct utterance.

-
-
Pausing -

Speakers differ very much in their rhythm and in particular in the +

+
+ Pausing +

Speakers differ very much in their rhythm and in particular in the amount of time they leave between words. The following element is provided to mark occasions where the transcriber judges that speech has been paused, irrespective of the actual amount of silence: @@ -550,32 +427,32 @@ and discussed informally below should be used. Note that the trans attribute mentioned in the previous section may also be used to characterize the degree of pausing between (but not within) utterances. -

-
Vocal, Kinesic, Incident -

The presence of +

+
+
+ Vocal, Kinesic, Incident +

The presence of non-transcribed semi-lexical or non-lexical phenomena either between or within utterances may be indicated with the following three elements.

-

The who attribute should be used to specify the person or +

The who attribute should be used to specify the person or group responsible for a vocal, kinesic, or incident which is contained within an utterance, if this differs from that of the enclosing utterance. The attribute must be supplied for a vocal, kinesic, or incident which is not contained within an utterance.

-

The iterated attribute may be used to indicate that the +

The iterated attribute may be used to indicate that the vocal, kinesic, or incident is repeated, for example laughter as opposed to laugh. These should both be distinguished from laughing, where what is being encoded is a shift in voice quality. For this last case, the shift element discussed in section should be used.

-

A child desc element may be used to supply a conventional +

A child desc element may be used to supply a conventional representation for the phenomenon, for example: - -burp, click, cough, exhale, giggle, gulp, +burp, click, cough, exhale, giggle, gulp, inhale, laugh, sneeze, sniff, snort, sob, swallow, throat, yawn - -ah, aha, aw, eh, ehm, er, erm, hmm, huh, + ah, aha, aw, eh, ehm, er, erm, hmm, huh, mm, mmhm, oh, ooh, oops, phew, tsk, uh, uh-huh, uh-uh, um, urgh, yup Researchers may prefer to regard some semi-lexical phenomena as @@ -584,36 +461,21 @@ See further the discussion at section below. As for all basic categories, the definition should be made clear in the encodingDesc element of the TEI header.

-

Some typical examples follow: -This is just delicious -telephone rings -I'll get it -I used to cough smoke a lot -sniffsHe thinks he's tough -snorts - - - - - - - - - - +

Some typical examples follow: +This is just delicioustelephone ringsI'll get itI used to cough smoke a lotsniffsHe thinks he's toughsnorts Note that Ann's snorting could equally well be encoded as follows: - - snorts - +snorts

-

The extent to which encoding of incidents or kinesics is included in a +

The extent to which encoding of incidents or kinesics is included in a transcription will depend entirely on the purpose for which the transcription was made. As elsewhere, this will depend on the particular research agenda and the extent to which their presence is felt to be significant for the interpretation of spoken interactions. -

-
Writing -

Written text may also be encountered when speech is transcribed, for +

+
+
+ Writing +

Written text may also be encountered when speech is transcribed, for example in a television broadcast or cinema performance, or where one participant shows written text to another. The writing element may be used to distinguish such written elements from the spoken text in @@ -624,35 +486,26 @@ For example, if speaker A in the breakfast table conversation in section look at this - +look at this Government claims economic problems -over by June what nonsense! +over by Junewhat nonsense!

-

If the source of the writing being displayed is known, +

If the source of the writing being displayed is known, bibliographic information about it may be stored in a listBibl within the sourceDesc element of the TEI header, and then pointed to using the source attribute. For example, in the following imaginary example, a lecturer displays two different versions of the same passage of text: - - - -Shakespeare First Folio text -Shakespeare Second Folio text - - - -[...] now compare the punctuation of lines 12 and 14 in these two +Shakespeare First Folio textShakespeare Second Folio text[...] now compare the punctuation of lines 12 and 14 in these two versions of page 42... [...] [...] - -

-
-
Temporal Information -

As noted above, utterances, vocals, pauses, kinesics, incidents, +

+
+
+ Temporal Information +

As noted above, utterances, vocals, pauses, kinesics, incidents, and writing elements all inherit attributes providing information about their position in time from the classes att.timed and att.duration. These attributes can be used to link parts of the transcription very exactly with points on a @@ -661,16 +514,17 @@ timeline, or simply to indicate their duration. Note that if whose temporal distance from each other is specified in a timeline, then dur is ignored.

-

The anchor element (see ) may be used as +

The anchor element (see ) may be used as an alternative means of aligning the start and end of timed elements, and is required when the temporal alignment involves points within an element.

-

For further discussion of temporal alignment and synchronization +

For further discussion of temporal alignment and synchronization see below.

-
-
Shifts -

A common requirement in transcribing spoken language is to mark +

+
+ Shifts +

A common requirement in transcribing spoken language is to mark positions at which a variety of prosodic features change. Many paralinguistic features (pitch, prominence, loudness, etc.) characterize stretches of speech which are not co-extensive with utterances or any of @@ -685,222 +539,59 @@ utterances for the same speaker, unless changed by a new shift for the same feature in the same speaker. Intervening utterances by other speakers do not normally carry the same feature. For example: -Elizabeth -Yes -Come and try this - come on +ElizabethYesCome and try this come on In this example, the word Elizabeth is spoken loudly, the words Yes and Come and try this with normal volume, and the words come on very loudly.

-

The values proposed here for the feature attribute are +

The values proposed here for the feature attribute are based on those used by the Survey of English Usage (see further Boase 1990); this list may be revised or supplemented using the methods outlined in section .

-

The new attribute specifies the new state of the feature +

The new attribute specifies the new state of the feature following the shift. If this attribute has the special value normal, the implication is that the feature concerned ceases to be remarkable at this point.

-

A list of suggested values for each of the features proposed follows: - -tempo - - -allegro (fast) - -very fast -accelerando (getting faster) -lento (slow) -very slow -rallentando (getting slower) -loud (for loudness): - -forte (loud) -very loud -crescendo (getting louder) -piano (soft) -very soft -diminuendo (getting softer) -pitch (for pitch range): - -high pitch-range -low pitch-range -wide pitch-range -narrow pitch-range -ascending -descending -monotonous -scandent, each succeeding syllable higher than - the last, generally ending in a falling tone -tension: - -slurred -lax, a little slurred -tense -very precise -staccato, every stressed syllable being doubly - stressed -legato, every syllable receiving more or less equal - stress -rhythm: - -beatable rhythm -arrhythmic, particularly halting -spiky rising, with markedly higher unstressed - syllables -spiky falling, with markedly lower unstressed - syllables -glissando rising, like spiky rising but the +

A list of suggested values for each of the features proposed follows: +tempo +allegro (fast)very fastaccelerando (getting faster)lento (slow)very slowrallentando (getting slower)loud (for loudness): +forte (loud)very loudcrescendo (getting louder)piano (soft)very softdiminuendo (getting softer)pitch (for pitch range): +high pitch-rangelow pitch-rangewide pitch-rangenarrow pitch-rangeascendingdescendingmonotonousscandent, each succeeding syllable higher than + the last, generally ending in a falling tonetension: +slurredlax, a little slurredtensevery precisestaccato, every stressed syllable being doubly + stressedlegato, every syllable receiving more or less equal + stressrhythm: +beatable rhythmarrhythmic, particularly haltingspiky rising, with markedly higher unstressed + syllablesspiky falling, with markedly lower unstressed + syllablesglissando rising, like spiky rising but the unstressed syllables, usually several, also rise - in pitch relative to each other -glissando falling, like spiky falling but with the + in pitch relative to each otherglissando falling, like spiky falling but with the unstressed syllables also falling in pitch relative - to each other -voice (for voice quality): - -whisper -breathy -husky -creaky -falsetto -resonant -unvoiced laugh or giggle -voiced laugh -tremulous -sobbing -yawning - sighing + to each othervoice (for voice quality): +whisperbreathyhuskycreakyfalsettoresonantunvoiced laugh or gigglevoiced laughtremuloussobbingyawning sighing

-

A full definition of the sense of the values provided for each +

A full definition of the sense of the values provided for each feature may be provided either in the encoding description section of the text header (see section ) or as part of a TEI customization, as described in section .

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
-
Elements Defined Elsewhere -

This section describes the following features characteristic of + + + + + + + + + +

+
+
+ Elements Defined Elsewhere +

This section describes the following features characteristic of spoken texts for which elements are defined elsewhere in these Guidelines: - -segmentation below the utterance level -synchronization and overlap -regularization of orthography The elements +segmentation below the utterance levelsynchronization and overlapregularization of orthography The elements discussed here are not provided by the module for spoken texts. Some of them are included in the core module and others are contained in the modules for linking and for analysis respectively. The selection @@ -909,8 +600,9 @@ in section .

-
Segmentation -

For some analytic purposes it may be desirable to subdivide the +

+ Segmentation +

For some analytic purposes it may be desirable to subdivide the divisions of a spoken text into units smaller than the individual utterance or turn. Segmentation may be performed for a number of different purposes and in terms of a variety of speech phenomena. @@ -924,7 +616,7 @@ of segments which are internally connected by a network of syntactic relations and externally delimited by the absence of such relations with respect to neighbouring segments. Such a segment is a syntactic unit called a macrosyntagm (trans. S. Johansson).

-

These Guidelines propose that such analyses be performed in terms of +

These Guidelines propose that such analyses be performed in terms of neutrally-named segments, represented by the seg element, which is discussed more fully in section . This element may take a type attribute to specify the kind of @@ -932,7 +624,7 @@ segmentation applicable to a particular segment, if more than one is possible in a text. A full definition of the segmentation scheme or schemes used should be provided in the segmentation element of the editorialDecl element in the TEI header (see ).

-

In the first example below, an utterance has been segmented according +

In the first example below, an utterance has been segmented according to a notion of syntactic completeness not necessarily marked by the speech, although in this case a pause has been recorded between the two sentence-like units. In the second, the segments are defined @@ -940,60 +632,34 @@ prosodically (an acute accent has been used to mark the position immediately following the syllable bearing the primary accent or stress), and may be thought of as tone units. - - we went to the pub yesterday - - there was no one there - - - although its an old ide´a - it hasnt been on the mar´ket very long - +we went to the pub yesterdaythere was no one therealthough its an old ide´ait hasnt been on the mar´ket very long In either case, the segmentation element in the header of the text should specify the principles adopted to define the segments marked in this way.

-

When utterances are segmented end-to-end in the same way as the +

When utterances are segmented end-to-end in the same way as the s-units in written texts, the s element discussed in chapter may be used, either as an alternative or in addition to the more general purpose seg element. The s element is available without formality in all texts, but does not allow segments to nest within each other.

-

Where segments of different kinds are to be distinguished within the +

Where segments of different kinds are to be distinguished within the same stretch of speech, the type attribute may be used, as in the following example: - -I think -this chap was writing -and he said hello said -hello -and he said -I'm going to a gate - at twenty past seven -he said -ok -right away -and so on they went -and they were - writing there - +I think this chap was writing and he said hello said hello and he said I'm going to a gate + at twenty past seven he said ok right away and so on they went and they were + writing there In this example, recoded from a corpus of language-impaired speech prepared by Fletcher and Garman, the speaker's utterance has been fully segmented into clausal (type="C") -or minor (type="M") units.

- -

For some features, it may be +or minor (type="M") units.

+

For some features, it may be more appropriate or convenient to introduce a new element in a custom namespace: - - -and he said -I'm going to a +and he said I'm going to a gate -at twenty past seven - - +at twenty past seven Here, ext:paraphasia has been used to define a particular characteristic of this corpus for which no element exists in the TEI scheme. @@ -1001,28 +667,27 @@ See further chapter for a discussion of the way in which this kind of user-defined extension of the TEI scheme may be performed and chapter for the mechanisms on which it depends.

-

This example also uses the core elements gap and +

This example also uses the core elements gap and del to mark editorial decisions concerning matter completely omitted from the transcript (because of inaudibility), and words which have been transcribed but which the transcriber wishes to exclude from the segment because they are repeated, respectively. See section for a discussion of these and related elements.

-

It is often the case that the desired segmentation does not respect +

It is often the case that the desired segmentation does not respect utterance boundaries; for example, syntactic units may cross utterance boundaries. For a detailed discussion of this problem, and the various methods proposed by these Guidelines for handling it, see chapter . Methods discussed there include these: - -milestone tags may be used; +milestone tags may be used; the special-purpose shift tag discussed -in section is an extension of this method -where several discontinuous segments are to be grouped +in section is an extension of this methodwhere several discontinuous segments are to be grouped together to form a syntactic unit (e.g. a phrasal verb with interposed -complement), the join element may be used -

-
Synchronization and Overlap -

A major difference between spoken and written texts is the importance +complement), the join element may be used

+
+
+ Synchronization and Overlap +

A major difference between spoken and written texts is the importance of the temporal dimension to the former. As a very simple example, consider the following, first as it might be represented in a playscript: @@ -1030,18 +695,12 @@ playscript: Stig: Yes Lou: (nods vigorously) To encode this, we first define the participants: - - - - - + Let us assume that Stig and Lou respond to Jane's question before she has finished asking it—a fairly normal situation in spontaneous speech. The simplest way of representing this overlap would be to use the trans attribute previously discussed: -have you read Vanity Fair -yes - +have you read Vanity Fairyes However, this does not allow us to indicate either the extent to which Stig's utterance is overlapped, nor does it show that there are in fact three things which are synchronous: the end of Jane's utterance, @@ -1051,22 +710,20 @@ alignment discussed in detail in section , are needed. If the module for linking has been enabled (as described in section above), one way to represent the simple example above would be as follows: -have you read Vanity Fair -yes -nods head vertically

-

For a full discussion of this and related mechanisms, section should be consulted. The rest of the present +have you read Vanity Fairyesnods head vertically

+

For a full discussion of this and related mechanisms, section should be consulted. The rest of the present section, which should be read in conjunction with that more detailed discussion, presents a number of ways in which these mechanisms may be applied to the specific problem of representing temporal alignment, synchrony, or overlap in transcribing spoken texts.

-

In the simple example above, the first utterance (that with +

In the simple example above, the first utterance (that with identifier utt1) contains an anchor element, the function of which is simply to mark a point within it. The synch attribute associated with this anchor point specifies the identifiers of the other two elements which are to be synchronized with it: specifically, the second utterance (utt2) and the kinesic (k1). Note that one of these elements has content and the other is empty.

-

This example demonstrates only a way of indicating a point within one +

This example demonstrates only a way of indicating a point within one utterance at which it can be synchronized with another utterance and a kinesic. For more complex kinds of alignment, involving possibly multiple synchronization points, an additional element is provided, @@ -1075,13 +732,8 @@ known as a timeline. This consists of a series of attributes which indicate its exact temporal position relative to other elements in the same timeline, in addition to the sequencing implied by its position within it.

-

For example: - - - - - - +

For example: + This timeline represents four points in time, named TS-P1, TS-P2, TS-P6, and TS-P3 (as with all attributes named xml:id in the TEI scheme, the names must be unique within the document but have no other @@ -1091,7 +743,7 @@ at some unspecified time later than TS-P2 and previous to TS-P3 (this is implied by its position within the timeline, as no attribute values have been specified for it). The fourth point, TS-P3, is 1.5 seconds later than TS-P6.

-

One or more such timelines may be specified within a spoken text, to +

One or more such timelines may be specified within a spoken text, to suit the encoder's convenience. If more than one is supplied, the origin attribute may be used on each to specify which other timeline element it follows. The unit attribute @@ -1100,58 +752,37 @@ contained by the alignment map. Alternatively, to avoid the need to specify times explicitly, the interval attribute may be used to indicate that all the when elements in a time line are a fixed distance apart.

-

Three methods are available for aligning points or elements within a +

Three methods are available for aligning points or elements within a spoken text with the points in time defined by the timeline: - -The elements to be synchronized may specify the identifier +The elements to be synchronized may specify the identifier of a when element as the value of one of the start, -end, or synch attributes -The when +end, or synch attributesThe when element may specify the identifiers of all the elements to be -synchronized with it using the synch attribute -A +synchronized with it using the synch attributeA free-standing link element may be used to associate the when element and the elements synchronized with it by specifying their identifiers as values for its target attribute.

-

For example, using the timeline given above: This is my turn The start of utterance +

For example, using the timeline given above: This is my turn The start of utterance TS-U1 is aligned with TS-P2 and its end with TS-P3. The transition between the words my and turn occurs at point TS-P6A, which is synchronous with point TS-P6 on the timeline.

-

The synchronization represented by the preceding examples could +

The synchronization represented by the preceding examples could equally well be represented as follows: - - - - - - -This is my turn +This is my turn Here, the whole of the object with identifier ts-u1 (the utterance) has been aligned with two different points, ts-p2 and ts-p3. This is interpreted to mean that the utterance spans at least those two points.

-

Finally, a linkGrp may be used as an alternative to the +

Finally, a linkGrp may be used as an alternative to the synch attribute: - - - - - - - - + This is my turn - - - - - -

-

As a further example of the three possibilities, consider the +

+

As a further example of the three possibilities, consider the following dialogue, represented first as it might appear in a conventional playscript: Tom: I used to smoke - - @@ -1169,64 +800,41 @@ to extend beyond the very simple case presented here. Their reliance on the accidentals of physical layout may also make them difficult to transport and to process computationally. These Guidelines recommend the following mechanisms to encode this.

-

Where the whole of one or another utterance is to be synchronized, +

Where the whole of one or another utterance is to be synchronized, the start and end attributes may be used: I used to smoke a lot more than this -but I never inhaled the smoke -You used to smoke +but I never inhaled the smokeYou used to smoke Note that the second utterance above could equally well be encoded as follows with exactly the same effect: You used to smoke

-

If synchronization with specific timing information is required, a +

If synchronization with specific timing information is required, a timeline must be included: - - - - -I used to smoke +I used to smoke a lot more than this - but I never inhaled the smoke - - You used to smoke + but I never inhaled the smokeYou used to smoke (Note that If only the ordering or sequencing of utterances is needed, then specific timing information shown here in unit, absolute and interval does not need to be provided.)

-

As above, since the whole of Bob's utterance is to be aligned, the +

As above, since the whole of Bob's utterance is to be aligned, the start and end attributes may be used as an alternative to the second pair of anchor elements: You used to smoke

-

An alternative approach is to mark the synchronization by pointing +

An alternative approach is to mark the synchronization by pointing from the timeline to the text: - - - - -I used to smoke +I used to smoke a lot more than this - but I never inhaled the smoke -You used to smoke + but I never inhaled the smokeYou used to smoke To avoid deciding whether to point from the timeline to the text or vice versa, a linkGrp may be used: - - - - - - I used to smoke +I used to smoke a lot more than this - but I never inhaled the smoke - You used to smoke - - - - -

-

Note that in each case, although Bob's utterance follows Tom's + but I never inhaled the smokeYou used to smoke

+

Note that in each case, although Bob's utterance follows Tom's sequentially in the text, it is aligned temporally with its middle, without any need to disrupt the normal syntax of the text.

-

As a final example, consider the following exchange, first as it +

As a final example, consider the following exchange, first as it might be represented using a musical-score-like notation, in which points of synchronization are represented by vertical alignment of the text: @@ -1238,17 +846,11 @@ All three speakers are simultaneous at the words my, simultaneous at the words turn and it's. This could be encoded as follows, using pointers from the alignment map into the text: - - - - - -this is my turn -balderdash - no it's mine -

-
Regularization of Word Forms -

When speech is transcribed using ordinary orthographic notation, as +this is my turnbalderdash no it's mine

+
+
+ Regularization of Word Forms +

When speech is transcribed using ordinary orthographic notation, as is customary, some compromise must be made between the sounds produced and conventional orthography. Particularly when dealing with informal, dialectal, or other varieties of language, the transcriber will @@ -1259,7 +861,7 @@ vocabulary item from kind of, isn'tis not; for some purposes, the regional variant isnae might also be worth distinguishing in the same way.

-

One rule of thumb might be to allow such variation only where a +

One rule of thumb might be to allow such variation only where a generally accepted orthographic form exists, for example, in published dictionaries of the language register being encoded; this has the disadvantage that such dictionaries may not exist. Another is to @@ -1273,19 +875,21 @@ or V A T) and where it is pronounced as a single word (VAT or RADA). Similar considerations might apply to pronunciation of foreign words (e.g. Monsewer vs. Monsieur).

-

In general, use of punctuation, capitalization, etc., in spoken +

In general, use of punctuation, capitalization, etc., in spoken transcripts should be carefully controlled. It is important to distinguish the transcriber's intuition as to what the punctuation should be from the marking of prosodic features such as pausing, intonation, etc.

-

Whatever practice is adopted, it is essential that it be clearly and +

Whatever practice is adopted, it is essential that it be clearly and fully documented in the editorial declarations section of the header. It may also be found helpful to include normalized forms of non-conventional spellings within the text, using the elements for simple editorial changes described in section (see -further section ).

-
Prosody -

In the absence of conventional punctuation, the marking of prosodic +further section ).

+
+
+ Prosody +

In the absence of conventional punctuation, the marking of prosodic features assumes paramount importance, since these structure and organize the spoken message. Indeed, such prosodic features as points of primary or secondary stress may be represented by specialized @@ -1296,8 +900,7 @@ can be indicated by the segmentation tag discussed in section . The shift element discussed in section may also be used to encode some prosodic features, for example where all that is required is the ability to record shifts in voice quality.

- -

In a more detailed phonological transcript, it is common practice +

In a more detailed phonological transcript, it is common practice to include a number of conventional signs to mark prosodic features of the surrounding or (more usually) preceding speech. Such signs may be used to record, for example, particular intonation patterns, @@ -1311,51 +914,26 @@ further chapters and ). For representation of phonemic information, the use of the International Phonetic Alphabet, which can be represented in Unicode characters, is recommended.

-

In the following example, special characters have been defined as +

In the following example, special characters have been defined as follows within the encodingDesc of the TEI header - - low fall intonation - low rise intonation - fall rise intonation - rise fall intonation - lengthened syllable - shortened syllable - - +low fall intonationlow rise intonationfall rise intonationrise fall intonationlengthened syllableshortened syllable These declarations might additionally provide information about how the characters concerned should be rendered, their equivalent IPA form, etc. In the transcript itself references to them can then be included as follows: - - - -

Customer WN

-

Assistant K

 - - -
- C is with a friend - - Excuse me You dont have some +

Customer WN

Assistant K

C is with a friendExcuse me You dont have some aesthetic specially on early - aesthetics terminology - + aesthetics terminology No No I'm - afraid - + afraid No Well thanks Oh you couldnt can we kind of - I mean ask you to order it for us - - Yes if you know the title Yeah - - - + I mean ask you to order it for us + Yes if you know the title Yeah Yes thats fine. just as soon as it comes in we'll send - you a postcard -
 + you a postcard

-

This example, which is taken from a corpus of bookshop service +

This example, which is taken from a corpus of bookshop service encounters, also demonstrates the use of the unclear and gap elements discussed in section . Where words are so @@ -1364,9 +942,7 @@ element may be used; where the encoder can identify the words but wishes to record a degree of uncertainty about their accuracy, the unclear element may be used. More flexible and detailed methods of indicating uncertainty are discussed in chapter .

- - -

For more detailed work, involving a detailed phonological transcript +

For more detailed work, involving a detailed phonological transcript including representation of stress and pitch patterns, it is probably best to maintain the prosodic description in parallel with the conventional written transcript, rather than attempt to embed detailed @@ -1374,11 +950,10 @@ prosodic information within it. The two parallel streams may be aligned with each other and with other streams, for example an acoustic encoding, using the general alignment mechanisms discussed in section .

- - -
-
Speech Management -

Phenomena of speech management include disfluencies such +

+
+ Speech Management +

Phenomena of speech management include disfluencies such as filled and unfilled pauses, interrupted or repeated words, corrections, and reformulations as well as interactional devices asking for or providing feedback. Depending on the importance attached to such @@ -1392,44 +967,41 @@ Guidelines recommend the use of the tags for simple editorial intervention discussed in section , to make explicit the extent of regularization or normalization performed by the transcriber.

-

For example, false starts, repetition, and truncated words might all +

For example, false starts, repetition, and truncated words might all be included within a transcript, but marked as editorially deleted, in the following way: ssee you you you know it's he's crazy

-

As previously noted, the gap element may be used to mark +

As previously noted, the gap element may be used to mark points within a transcript where words have been omitted, for example because they are inaudible, as in the following example in which 5 seconds of speech is drowned out by an external event:

-

The unclear element may be used to mark words which have +

The unclear element may be used to mark words which have been included although the transcriber is unsure of their accuracy: ...and then marbled queen

-

Where a transcriber is believed to have incorrectly identified a +

Where a transcriber is believed to have incorrectly identified a word, the elements corr or sic embedded within a choice element may be used to indicate both the original and a corrected form of it: - -SCSIskuzzy - +SCSIskuzzy These elements are further discussed in section .

-

Finally phenomena such as code-switching, where a +

Finally phenomena such as code-switching, where a speaker switches from one language to another, may easily be represented in a transcript by using the foreign element provided by the core tagset: - -I proposed that wir können +I proposed that wir können vielleicht go to warsaw -and vienna - +and vienna

-
-
Analytic Coding -

The recommendations made here only concern the establishment of a +

+
+ Analytic Coding +

The recommendations made here only concern the establishment of a basic text. Where a more sophisticated analysis is needed, more sophisticated methods of markup will also be appropriate, for example, using stand-off markup to indicate multiple segmentation of the @@ -1442,34 +1014,22 @@ type of speech act (imperative, concessive, etc.), or information status the general purpose analytic tools discussed in chapters , , and may be used to advantage.

-

The general-purpose annotationBlock element may be used to group together a transcription and multiple layers of annotation. It also serves +

The general-purpose annotationBlock element may be used to group together a transcription and multiple layers of annotation. It also serves to divide a transcribed text up into meaningful analytic sections. - - - +

- -
-
- -
- Module for Transcribed Speech -

The module described in this chapter makes available the following components: - - Transcribed Speech - Transcribed Speech - Transcriptions de la parole - 轉錄的言詞 - Trascrizione del parlato - Transcrição do discurso - 発話モジュール - +

+
+
+ Module for Transcribed Speech +

The module described in this chapter makes available the following components: + Transcribed SpeechTranscribed SpeechTranscriptions de la parole轉錄的言詞Trascrizione del parlatoTranscrição do discurso発話モジュール The selection and combination of modules to form a TEI schema is described in .

- - - - - -
+ + + + + +
diff --git a/P5/Source/Guidelines/en/TitlePageVerso.xml b/P5/Source/Guidelines/en/TitlePageVerso.xml index bdd294ef10..c0c8132c36 100644 --- a/P5/Source/Guidelines/en/TitlePageVerso.xml +++ b/P5/Source/Guidelines/en/TitlePageVerso.xml @@ -1,27 +1,18 @@ - - - + -
- Releases of the TEI Guidelines - - - 1990, C.M. Sperberg-McQueen and Lou Burnard - - 1992, C.M. Sperberg-McQueen and Lou Burnard - - 1994, C.M. Sperberg-McQueen and Lou Burnard - - 2001, Lou Burnard, Syd Bauman, and Steven DeRose - - 2007, Lou Burnard and Syd Bauman - -
+ Releases of the TEI Guidelines + + + 1990, C.M. Sperberg-McQueen and Lou Burnard + + 1992, C.M. Sperberg-McQueen and Lou Burnard + + 1994, C.M. Sperberg-McQueen and Lou Burnard + + 2001, Lou Burnard, Syd Bauman, and Steven DeRose + + 2007, Lou Burnard and Syd Bauman + +
diff --git a/P5/Source/Guidelines/en/USE.xml b/P5/Source/Guidelines/en/USE.xml index acd43c1eb8..64c2c96dfd 100644 --- a/P5/Source/Guidelines/en/USE.xml +++ b/P5/Source/Guidelines/en/USE.xml @@ -1,16 +1,8 @@ - +
Using the TEI - -

This section discusses some technical topics concerning the deployment of the TEI markup schema documented elsewhere in these Guidelines. TEI - Extension. Since the ODD markup description language defined in chapter is fundamental to the way conformance and customization are handled in the TEI + Extension. Since the ODD markup description language defined in chapter is fundamental to the way conformance and customization are handled in the TEI system, these two definitional sections are followed by a section () which describes the intended behaviour of an ODD processor.

-
@@ -41,7 +31,6 @@ that practice. --> media type application/tei+xml to enable and encourage automated recognition and processing of TEI files by external applications.

-
Obtaining the TEI

As discussed in chapter , all components of the TEI schema are generated @@ -55,15 +44,9 @@ that practice. --> repository at ; versions are also available in other formats, along with copies of these Guidelines and related materials, from the TEI web site at .

-
- - -
- Customization -

These Guidelines provide an encoding schema suitable for encoding a very wide range of texts, and capable of supporting a wide variety of applications. For this reason, the TEI schema supports a variety of different approaches to solving similar problems, and also defines a @@ -71,13 +54,11 @@ that practice. --> the TEI schema may be extended in well-defined and documented ways for texts that cannot be conveniently or appropriately encoded using what is provided. For these reasons, it is almost impossible to use the TEI schema without customizing it in some way.

-

This section describes how the TEI encoding schema may be customized, and should be read in conjunction with chapter , which describes how a specific application of the TEI encoding schema should be documented. The documentation system described in that chapter is, like the rest of the TEI schema, independent of any particular schema or document type definition language.

-

Formally speaking, these Guidelines provide both syntactic rules about how elements and attributes may be used in valid documents and semantic recommendations about what interpretation should be attached to a given syntactic construct. In this sense, they provide @@ -112,7 +93,6 @@ that practice. --> will inevitably be cases where the intention of the contributors has not been conveyed with sufficient clarity to prevent users of these Guidelines from extending them in the sense of attaching slightly variant semantics to them.

-

Beyond this unintentional semantic extension, some of the elements described can intentionally be used in a variety of ways; for example, the element note has an attribute type which can take on arbitrary string values, depending on how it is @@ -122,14 +102,11 @@ that practice. --> this way would no longer necessarily regard as valid the same set of documents as the corresponding unmodified TEI schema, but would remain faithful to the same conceptual model.

- -

This section explains how the TEI schema can be customized by suppressing elements, modifying classes of elements, or adding elements. Documents which validate against an application of the TEI schema which has been customized in this way may or may not be considered TEI-conformant, as further discussed in section .

-

The TEI system is designed to support modification and customization in a documented way that can be validated by an XML processor. This is achieved by writing a small TEI-conformant document, known informally as an ODD (One Document Does it all), from which an appropriate @@ -144,43 +121,26 @@ that practice. --> This indirection makes it simpler to implement customization of the TEI system in an accessible and human-readable way.

-

As further discussed in section , the TEI encoding schema comprises a set of class and macro declarations, and a number of modules. Each module is made up of element and attribute declarations, and a schema is made by combining a particular set of modules together. In the absence of any other kind of customization, when modules are combined - together: - all the elements defined by the module (and described in the corresponding section of - these Guidelines) are included in the schema; - each such element is identified by the canonical name given it in these - Guidelines; - the content model of each such element is as defined by these Guidelines; - the names, datatypes, and permitted values declared for each attribute associated with - each such element are as given in these Guidelines; - the elements comprising element classes and the meaning of macro declarations + together: all the elements defined by the module (and described in the corresponding section of + these Guidelines) are included in the schema;each such element is identified by the canonical name given it in these + Guidelines;the content model of each such element is as defined by these Guidelines;the names, datatypes, and permitted values declared for each attribute associated with + each such element are as given in these Guidelines;the elements comprising element classes and the meaning of macro declarations expressed in terms of element classes is determined by the particular combination of - modules selected. - The TEI customization mechanisms allow the user to control this behaviour as follows: - - particular elements may be suppressed, removing them from any classes in which they - are members, and also from any generated schema; - new elements may be added to an existing class, thus making them available in macros - or content models defined in terms of those classes; - additional attributes, or attribute values, may be specified for an individual element - or for classes of elements; - within certain limits, attributes, or attribute values, may also be removed either - from an individual element or for classes of elements; - the characteristics inherited by one class from another class may be modified by + modules selected. The TEI customization mechanisms allow the user to control this behaviour as follows: + particular elements may be suppressed, removing them from any classes in which they + are members, and also from any generated schema; new elements may be added to an existing class, thus making them available in macros + or content models defined in terms of those classes;additional attributes, or attribute values, may be specified for an individual element + or for classes of elements; within certain limits, attributes, or attribute values, may also be removed either + from an individual element or for classes of elements; the characteristics inherited by one class from another class may be modified by modifying its class membership: all members of the class then inherit the changed - characteristics; - the set of values legal for an attribute or attribute class may be constrained or - relaxed by supplying or modifying a value list, or by modifying its datatype. - within certain limits, the name (generic identifier) associated with an element may be - changed, without changing the semantic or syntactic properties of the element; - - The modification mechanisms presented in this section are quite general, and may be + characteristics;the set of values legal for an attribute or attribute class may be constrained or + relaxed by supplying or modifying a value list, or by modifying its datatype.within certain limits, the name (generic identifier) associated with an element may be + changed, without changing the semantic or syntactic properties of the element; The modification mechanisms presented in this section are quite general, and may be used to make all the types of changes just listed.

-

The recommended way of implementing and documenting all such modifications is by means of the ODD system described in chapter ; in the remainder of this section we give specific examples to illustrate how that system may be applied. An ODD processor, such as the @@ -191,20 +151,9 @@ that practice. --> information about the methods used for XML DTD and RELAX NG schema generation is however provided in section . Several example ODD files are also provided as part of the standard TEI release: see further section below.

-
Kinds of Modification -

For ease of discussion, we distinguish the following different kinds of modification: - deletion of elements; - modification of content models; - modification of attribute and attribute-value lists; - modification of class membership; - addition of new elements. - renaming of elements; - - Each of these is described in the following sections.

- +

For ease of discussion, we distinguish the following different kinds of modification: deletion of elements;modification of content models;modification of attribute and attribute-value lists;modification of class membership;addition of new elements.renaming of elements; Each of these is described in the following sections.

Each kind of modification changes the set of documents that will be considered valid according to the resulting schema. A schema derived from any combination of unmodified TEI declarations (an "unmodified schema") may be thought of as defining a certain set of @@ -220,40 +169,27 @@ that practice. --> terminology, unclean modifications are not particularly deprecated, and their use may often be vital to the success of a project. The concept is introduced solely to distinguish the effects of different kinds of modification.

- -
Deletion of Elements -

The simplest way to modify the supplied modules is to suppress one or more of the supplied elements. This is simply done by setting the mode attribute to delete on an elementSpec for the element concerned.

-

For example, if the note element is not to be used in a particular application, but has been included via one of the supplied modules, then the schema specification - concerned will contain a declaration like the following: The ident attribute here supplies the + concerned will contain a declaration like the following: The ident attribute here supplies the canonical name of the element to be deleted and the mode attribute specifies what is to be done with it. There is no need to specify the module concerned, since element names are unique across all TEI modules. The full specification for a schema in - which this modification is applied would thus be something like the following: - - - - + which this modification is applied would thus be something like the following:

-

In most cases, deletion is a clean modification, since most elements are optional. Documents that are valid with respect to the modified schema are also valid according to TEI-All. To say this another way, the set of documents matching the new schema is contained by the set of documents matching the original schema.

-

There are however some elements in the TEI schema which have mandatory children; for example, the element listPerson must contain at least one element from the model.personLike class. If that class has no members because all of its @@ -262,12 +198,10 @@ that practice. --> would therefore be regarded as unclean. So long as at least one member of the class remains available, however, deleting other members would not have this effect, and would therefore be regarded as a clean modification.

-

In general, whenever the element deleted by a modification is mandatory within the content model of some other (undeleted) element, the result is an unclean modification, and may also break the TEI Abstract Model (). However, the parent of a mandatory child can be safely removed if it is itself optional.

-

To determine whether or not an element is mandatory in a given context, the user must inspect the content model of the element concerned. In most cases, content models are expressed in terms of model classes rather than elements; hence, removing an element will @@ -275,39 +209,22 @@ that practice. --> class available. If a class is completely depopulated by a modification, then the cleanliness of the modification will depend upon whether or not the class reference is mandatory or optional, in the same way as for an individual element.

-
- -
Modification of Content Models -

The content model for an element in the TEI schema is defined by means of a content element within the elementSpec which specifies it. For example, the specification for the element term provided by these Guidelines - contains a content element like the following: - - - - This content model consists of a reference to a macro called macro.phraseSeq. Further examination shows that this macro in turn expands to + contains a content element like the following: This content model consists of a reference to a macro called macro.phraseSeq. Further examination shows that this macro in turn expands to an optional repeatable alternation of text (textNode) with references to three - other classes (model.gLike, model.phrase, or model.global). For some particular + other classes (model.gLike, model.phrase, or model.global). For some particular application it might be preferable to insist that term elements should only contain plain text, excluding these other possibilities.Excluding model.gLike is generally inadvisable however, since without it the resulting schema has no way of referencing non-Unicode characters. This could be achieved simply by supplying a specification for term like the - following: - - - - + following:

-

This is a clean modification which does not change the meaning of a TEI element; there is therefore no need to assign the element to some other namespace than that of the TEI, though it may be considered good practice; see further below.

@@ -315,7 +232,6 @@ that practice. --> its model to one of its existing components, is always clean, because the set of documents matched by the resulting schema is a subset of the set of documents which would have been matched by TEI-All.

-

Note that content models are generally defined (as far as possible) in terms of references to model classes, rather than to explicit elements. This means that the need to modify content models is greatly reduced: if an element is deleted or modified, for @@ -323,17 +239,14 @@ that practice. --> references that element via its class, as well as those which reference it explicitly. For this reason it is not (in general) good practice to replace class references by explicit element references, since this may have unintended side effects.

-

An unqualified reference to an element class within a content model generates a content model which is equivalent to an alternation of all the members of the class referenced. - Thus, a content model which refers to the model class model.phrase will generate a content model in which any one of the members of + Thus, a content model which refers to the model class model.phrase will generate a content model in which any one of the members of that class is equally acceptable. The classRef element used to reference a class has an expand attribute which may be used to vary this behaviour, for example to require an optional repeatable alternation of all members of a class, a sequence containing no more than one of each member of the class, etc. as described further in .

-

Content model changes which are not simple restrictions on an existing model should be undertaken with caution. The set of documents matching the schema which results from such changes is unlikely to be contained by the set of documents matching TEI-All, and such @@ -344,13 +257,9 @@ that practice. --> also include members of the class model.pLike such as p or ab. Although syntactically feasible, such a modification would not be regarded as TEI-conformant because it breaks the TEI Abstract Model.

-
- -
Modification of Attribute and Attribute Value Lists -

The attributes applicable to a given element may be specified in two ways: they may be given explicitly, by means of an attList element within the corresponding elementSpec, or they may be inherited from an attribute class, as specified in @@ -360,35 +269,21 @@ that practice. --> the element in question a member of that class, as further discussed below. If this is not possible, then a new attDef element must be added to the existing attList for the element in question.

-

Whichever method is adopted, the modification capabilities are the same as those available for elements. Attributes may be added or deleted from the list, using the mode attribute on attDef in the same way as on elementSpec. The content of an attribute is defined by means of the datatype, valList, or valDesc elements within the attDef element. Any of these elements may be changed.

-

Suppose, for example, that we wish to add two attributes to the eg element (used to indicate examples in a text), type to characterize the example in some way, and valid to indicate whether the example is considered valid or not. A quick - glance through the Guidelines indicates that the attribute class att.typed could be used to provide the type attribute, but there is + glance through the Guidelines indicates that the attribute class att.typed could be used to provide the type attribute, but there is no comparable class which will provide a valid attribute. The existing eg element in fact has no local attributes defined for it at all: we will therefore need to add not only an attDef element to define the new attribute, but also an attList to hold it.

-

We begin by adding the new valid attribute: - - - indicates whether or not the example is considered to be valid - - - - - - +

We begin by adding the new valid attribute: indicates whether or not the example is considered to be valid

The value supplied for the mode attribute on the attDef element is add; if this attribute already existed on the element we are modifying this @@ -397,61 +292,30 @@ that practice. --> declaration by supplying replace as the value for mode; alternatively, we can change some parts of an existing declaration only by supplying just the new parts, and setting change as the value for mode.

-

Because the new attribute is not defined by the TEI, it is good practice to specify a namespace for it on the attDef; see further .

- -

As noted above, adding the new type attribute involves changing this element's - class membership; we therefore discuss that in the next section ().

- + class membership; we therefore discuss that in the next section ().

The canonical name for the new attribute is valid, and is supplied on the ident attribute of the attDef element. In this simple example, we supply only a description and datatype for the new attribute; the former is given by the desc element, and the latter by the datatype element. (There are of - course many other pieces of information which could be supplied, as documented in ). The content of the datatype + course many other pieces of information which could be supplied, as documented in ). The content of the datatype element is a dataRef element which references an existing TEI data specification.

-

It is often desirable to constrain the possible values for an attribute to a greater extent than is possible by simply supplying a TEI datatype for it. This facility is provided by the valList element, which can also appear as a child of the attDef element. Suppose for example that, rather than simply indicating whether or not the example is considered valid by means of the values true and false we wish to provide a more nuanced indication, using encoded values such - as A, B, and C. A declaration like the following might be appropriate: - - - - indicates the validity of the example by supplying one of three predefined - codes for it. - - - - - - validity is of the highest class - - - validity is of the second highest class - - - validity is of the lowest class - - - - - + as A, B, and C. A declaration like the following might be appropriate: indicates the validity of the example by supplying one of three predefined + codes for it.validity is of the highest classvalidity is of the second highest classvalidity is of the lowest class

-

The same technique may be used to replace or extend the valList supplied as part of any attribute in the TEI schema.

-
Class Modification -

The concept of element classes was introduced in ; an understanding of it is fundamental to successful use of the TEI system. As noted there, we distinguish model classes, the members of which all have structural @@ -471,108 +334,62 @@ that practice. --> this, using a memberOf element for each.

To add an element to a class in which it is not already a member, all that is needed is to supply a new memberOf element within the classes element for the - element concerned. For example, to add an element to the att.typed class, we include a declaration like the following: - - - - Any existing class memberships for the element being changed are + element concerned. For example, to add an element to the att.typed class, we include a declaration like the following: Any existing class memberships for the element being changed are not affected because the mode attribute of the classes element is set to change (rather than its default value of replace). Consequently, - in this case, the eg element retains its membership of the two classes (model.common and model.graphicLike) to + in this case, the eg element retains its membership of the two classes (model.common and model.graphicLike) to which it already belongs.

Equally, to remove the attributes which an element inherits from its membership in some class, all that is needed is to remove the relevant memberOf element. For example, the element term defined in the core module is a member of two attribute - classes, att.typed and att.declaring. It inherits the attributes type and + classes, att.typed and att.declaring. It inherits the attributes type and subtype from the former, and the attribute decls from the latter. To remove the last of these attributes from this element, we need to remove it from that - class: - - - - + class:

If the intention is to change the class membership of an element completely, rather than simply add or remove it to or from one or more classes, the value of the mode attribute of classes can be set to replace (which is the default if no value is specified), indicating that the memberships indicated by its child memberOf elements are the only ones applicable. Thus the following declaration: - - - - - would have the effect of removing the element term from - both its existing attribute classes, and adding it to the att.interpLike class.

+ would have the effect of removing the element term from + both its existing attribute classes, and adding it to the att.interpLike class.

If however the mode attribute is set to change, the implication is that the memberships indicated by its child memberOf elements are to be combined with the existing memberships for the element.

-

To change or remove attributes inherited from an attribute class for all members of the class (as opposed to specific members of that class), it is also possible to modify the - class specification itself. For example, the class att.global.rendition defines several attributes which are available for all + class specification itself. For example, the class att.global.rendition defines several attributes which are available for all elements, namely rend, style, and rendition. If we decide that we never wish to use the rend attribute, the simplest way of removing it - is to supply a modified class specification for att.global.rendition as follows: - - - - - Because the mode attribute on the classSpec defining the + is to supply a modified class specification for att.global.rendition as follows: Because the mode attribute on the classSpec defining the attributes inherited through membership of this class has the value change, any of its existing identifiable components not specified in the modification above will remain unchanged. The only effect will therefore be to delete the rend attribute from the class, and hence from all elements which are members of the class.

-

The classes used in the TEI schema are further discussed in chapter . Note in particular that classes are themselves classified: the attributes inherited by a member of attribute class A may come to it directly from that class, or from another class - of which A is itself a member. For example, the class att.global is itself a member of the classes att.global.linking and att.global.analytic. By - default, these two classes are predefined as empty. However, if (for example) the linking module is included in a schema, a number of attributes - (corresp, sameAs, etc.) are defined as members of the att.global.linking class. All elements which are members of att.global will then inherit these new attributes (see further + of which A is itself a member. For example, the class att.global is itself a member of the classes att.global.linking and att.global.analytic. By + default, these two classes are predefined as empty. However, if (for example) the linking module is included in a schema, a number of attributes + (corresp, sameAs, etc.) are defined as members of the att.global.linking class. All elements which are members of att.global will then inherit these new attributes (see further section ). A new attribute may thus be added to the global class in two ways: either by adding it to the attList defined within the class specification for att.global; or by defining a new attribute class, and changing the class membership of the att.global class to reference it.

- -

Such global changes should be undertaken with caution: in general removing existing non-mandatory attributes from a class will always be a clean modification, in the same way as removing non-mandatory elements. Adding a new attribute to a class however can be a clean modification only if the new attribute is labelled as belonging to some namespace other than the TEI.

-

The same mechanisms are available for modification of model classes. Care should be taken when modifying the model class membership of existing elements since model class membership is what determines the content model of most elements in the TEI schema, and a small change may have unintended consequences.

- -
- -
Addition of New Elements -

To add a completely new element into a schema involves providing a complete element specification for it. It is recommended that the classes element of this new declaration should include a reference to at least one TEI model class. Without such a @@ -581,26 +398,16 @@ that practice. --> possible to modify the content models of one or more existing elements to refer to the new element explicitly, as discussed in but this will generally be less convenient.

-

For example, the three elements bibl, biblFull, and biblStruct are all defined as members of the class model.biblLike. To add a fourth member (say myBibl) to this class, we need to include in the elementSpec defining our new element a memberOf element which - nominates the intended class: - - - - - The other parts of this declaration will typically include a + nominates the intended class: The other parts of this declaration will typically include a description for the new element and information about its content model, its attributes, etc., as further described in .

-
Renaming of Elements -

Every element and other named markup construct in the TEI schema has a canonical name, usually composed of English language words or syllables: this name is supplied as the value of the ident attribute on the elementSpec, attDef, @@ -611,16 +418,11 @@ that practice. --> identifiers for the same markup construct, and an ODD processor may choose which of them to use for a given purpose. Each such alternative name is supplied by means of an altIdent element within the specification element concerned.

-

For example, the following declaration converts note to nt: - nt - Note that the mode attribute on the +

For example, the following declaration converts note to nt: nt Note that the mode attribute on the elementSpec now takes the value change to indicate that those parts of the element specification not supplied are to be inherited from the standard definition. The content of the altIdent element is now available for use in place of the canonical ident value in the schema generated.

-

Renaming in this way is is an inherently unclean modification (because the set of documents matched by the resulting schema is not contained by the set matched by TEI-All), even though the process of @@ -632,15 +434,10 @@ that practice. --> avoid the risk of name collision between the new name and all existing TEI names as well as for reasons of conformance (see further ).

-
-
-
Modification and Namespaces - -

All the elements defined by the TEI schema are labelled as belonging to a single namespace, maintained by the TEI and with the URI http://www.tei-c.org/ns/1.0.This is not strictly the case, @@ -651,42 +448,24 @@ that practice. -->

-

This implies that any other modification must either specify a different namespace or, equivalently, specify no namespace at all. The ns attribute is provided on elements schemaSpec, elementSpec, and attDef for this purpose.

-

Suppose, for example, that we wish to add a new attribute topic to the existing TEI element p. In the absence of namespace +

Suppose, for example, that we wish to add a new attribute topic to the existing TEI element p. In the absence of namespace considerations, this would be an unclean modification, since p does not currently have such an attribute. The most appropriate action is to explicitly attach the new - attribute to a new namespace by a declaration such as the following: - - - - indicates the topic of a TEI paragraph - - - - + attribute to a new namespace by a declaration such as the following: indicates the topic of a TEI paragraph

Document instances using a schema derived from this ODD can now indicate clearly the status - of this attribute: -

- -

Flopsy, Mopsy, Cottontail, and Peter...

-

- + of this attribute:

Flopsy, Mopsy, Cottontail, and Peter...

Since topic is explicitly labelled as belonging to something other than the TEI namespace, we regard the modification which introduced it as clean. A namespace-aware processor will be able to validate those elements in the TEI namespace against the unmodified schema.Full namespace support does not exist in the DTD language, and therefore these techniques are available only to users of more modern schema languages such as RELAX NG or W3C Schema.

-

Similar considerations apply when modification is made to the content model or some other aspect of an element, or when a new element is declared. schemaSpec. This can be useful if it is desired simply to avoid namespace processing. For example, the following schema specification results in a schema called noName which has no namespace, even though it comprises declarations from - the TEI header module: - - - + the TEI header module:

In addition to the TEI canonical namespace mentioned above, the TEI may also define namespaces for approved translations of the TEI schema into other languages. @@ -712,14 +486,11 @@ that practice. --> used as appropriate to indicate that a customization uses a standardized set of renamings.--> The namespace for such translations is the same as that for the canonical namespace, suffixed by the appropriate ISO language identifier (). A schema - specification using the Chinese translation, for example, would use the namespace http://www.tei-c.org/ns/1.0/zh + specification using the Chinese translation, for example, would use the namespace http://www.tei-c.org/ns/1.0/zh

-
Documenting the Modification -

The elements used to define a TEI customization (schemaSpec, moduleRef, elementSpec, etc.) will typically be used within a TEI document which supplies further information about the intended use of the new schema, the meaning and application of @@ -737,9 +508,7 @@ that practice. --> the remarks element may contain discussions of matters irrelevant to the project. These elements may therefore be replaced or deleted within an elementSpec as necessary.

- -

Radical revision is also possible. It is feasible to produce a modification in which the teiHeader or text elements are not required, or in which any other rule stated in these Guidelines is either not enforced or not enforceable. In fact, the @@ -749,31 +518,19 @@ that practice. --> mechanism in this way. We discuss exactly what is meant by the concept of TEI conformance in the next section, .

- - -
Examples of Modification -

Several examples of customizations of the TEI are provided as part of the standard release. - They include the following: - - The schema generated from this customization is the minimum needed for TEI - Conformance. It provides only a handful of elements. - - The schema generated from this customization combines all available TEI modules, - providing elements. - - The schema generated from this customization combines all available TEI modules with - three other non-TEI vocabularies, specifically MathML, SVG, and XInclude. - + They include the following: The schema generated from this customization is the minimum needed for TEI + Conformance. It provides only a handful of elements. The schema generated from this customization combines all available TEI modules, + providing elements.The schema generated from this customization combines all available TEI modules with + three other non-TEI vocabularies, specifically MathML, SVG, and XInclude.

It is unlikely that any project would wish to use any of these extremes unchanged. However, they form a useful starting point for customization, whether by removing modules from tei_all or tei_allPlus, or by replacing elements deleted from tei_bare. They also demonstrate how an ODD document may be constructed to provide a basic reference manual to accompany schemas generated from it.

-

Shortly after publication of the first edition of these Guidelines, as a demonstration of how the TEI encoding schema might be adopted to meet 90% of the needs of 90% of the TEI user community, the TEI editors produced a brief tutorial defining one specific @@ -784,8 +541,7 @@ that practice. --> provided with TEI P5.

An updated and expanded version of this schema known as TEI simplePrint was added to the Exemplars at release 3.1.0. The elements it defines have been modified to take - advantage of the processing model features (see further ) introduced to the Guidelines at release 3.0.0.

+ advantage of the processing model features (see further ) introduced to the Guidelines at release 3.0.0.

The exemplars provided with TEI P5 also include a customization file from which a schema for the validation of other customization files may be generated. This ODD, called tei_odds, combines the four basic modules with the tagdocs, dictionaries, gaiji, linking, and figures @@ -795,47 +551,23 @@ that practice. --> enables schemas derived from this customization file to validate examples contained within them in a number of ways, further described within the document.-->

- - - -
- - -
- Conformance -

The notion of TEI Conformance is intended to assist in the description of the format and contents of a particular XML document instance or set of documents. It may be found - useful in such situations as: - interchange or integration of documents amongst different researchers or users; - software specifications for TEI-aware processing tools; - agreements for the deposit of texts in, and distribution of texts from, archives; - specifying the form of documents to be produced by or for a given project. - It is not intended to provide any other evaluation, for example of scholarly merit, + useful in such situations as: interchange or integration of documents amongst different researchers or users; software specifications for TEI-aware processing tools; agreements for the deposit of texts in, and distribution of texts from, archives; specifying the form of documents to be produced by or for a given project. It is not intended to provide any other evaluation, for example of scholarly merit, intellectual integrity, or value for money. A document may be of major intellectual importance and yet not be TEI-conformant; a TEI-conformant document may be of no scholarly value whatsoever.

-

In this section we explore several aspects of conformance, and in particular attempt to define how the term TEI-conformant should be used. The terminology defined here should be considered normative: users and implementors of the TEI Guidelines should use the phrases TEI-conformant and TEI Extension only in the senses given and with the usages described.

- -

A document is TEI-conformant if it: - is a well-formed XML document () - can be validated against a TEI Schema, that is, a schema derived from the - TEI Guidelines () - conforms to the TEI Abstract Model () - uses the TEI namespace (and other namespaces where relevant) correctly - () - is documented by means of a TEI-conformant ODD file () which refers to the TEI Guidelines - Each of these criteria is discussed in more detail below.

- +

A document is TEI-conformant if it: is a well-formed XML document ()can be validated against a TEI Schema, that is, a schema derived from the + TEI Guidelines () conforms to the TEI Abstract Model () uses the TEI namespace (and other namespaces where relevant) correctly + () is documented by means of a TEI-conformant ODD file () which refers to the TEI Guidelines Each of these criteria is discussed in more detail below.

TEI-conformant; the terms algorithmically conformant or TEI-conformable are provided in order to distinguish documents exhibiting these kinds of conformance from others.

--> -

A document is said to use a TEI Extension if it is a well-formed XML document which is valid against a TEI Schema which contains additional distinctions, representing concepts not present in the TEI Abstract Model, and therefore not documented in these @@ -854,26 +585,20 @@ that practice. --> extension which is expressed by means of the recommended mechanisms is also a TEI-conformant document provided that those parts of it which are not extensions are TEI-conformant.

-

A TEI-conformant document is said to follow TEI Recommended Practice if, wherever these Guidelines prefer one encoding practice to another, the preferred practice is used.

-
- Well-formedness Criterion -

These Guidelines mandate the use of well-formed XML as representation format. Documents must conform to the World Wide Web Consortium recommendation of the Extensible Markup - Language (XML) 1.0 (Fourth Edition) or successor editions found at . Other ways of + Language (XML) 1.0 (Fourth Edition) or successor editions found at . Other ways of representing the concepts of the TEI Abstract Model are possible, and other representations may be considered appropriate for use in particular situations (for example, for data capture, or project-internal processing). But such alternative representations should not be considered in any way TEI-conformant.

-

Previous versions of these Guidelines used SGML as a representation format. With the release of P5, the only representation format supported by these Guidelines became valid XML; legacy documents in SGML format should therefore be converted using appropriate @@ -886,7 +611,6 @@ that practice. --> no special interchange format is therefore proposed by these Guidelines. For discussion of encoding issues that may arise in the processing of special character sets or non-standard writing systems, see further chapter .

-

In addition to the well-formedness criterion, the W3C defines the notion of a valid document, as being a well-formed document which matches a specific set of rules or syntactic constraints, defined by a schema. As noted above, TEI @@ -895,17 +619,13 @@ that practice. --> components which these Guidelines define.

-
Validation Constraint -

All TEI-conformant documents must validate against a schema file that has been derived from the published TEI Guidelines, combined and documented in the manner described in section . We call the formal output of this process a TEI Schema.

- -

The TEI does not mandate use of any particular schema language, only that this schemaHere and elsewhere we use the word schema to refer +

The TEI does not mandate use of any particular schema language, only that this schemaHere and elsewhere we use the word schema to refer to any formal document grammar language, irrespective of the formalism used to represent it. should have been generated from a TEI ODD file that references the TEI Guidelines. Currently available tools permit the expression of schemas in any or all of @@ -919,18 +639,12 @@ that practice. -->

-

As noted in section , many varieties of TEI schema are possible and not all of them are necessarily TEI-conformant; derivation from an ODD is a necessary but not a sufficient condition for TEI Conformance.

- -
-
- Conformance to the TEI Abstract Model -

The TEI Abstract Model is the conceptual schema instantiated by the TEI Guidelines. These Guidelines define, both formally and informally, a set of abstract concepts such as paragraph or heading, and their structural relationships, for @@ -941,22 +655,17 @@ that practice. --> TEI element cannot therefore be changed without changing the model. Elements can however be removed from a class by deletion, and new non-TEI elements within their own namespaces can be added to existing TEI classes.

- -
Semantic Constraints -

It is an important condition of TEI conformance that elements defined in the TEI Guidelines as having one specific meaning should not be used with another. For example, the element l is defined in the TEI Guidelines as containing a line of verse. A schema in which it is redefined to mean a typographic line, or an ordered queue of objects of some kind, cannot therefore be TEI-conformant, whatever its other properties.

-

The semantics of elements defined in the TEI Guidelines are conveyed in a number of ways, ranging from formally verifiable datatypes to informal descriptive prose. In addition, a mapping between TEI elements and concepts in other conceptual models may be provided by the equiv element where this is available.

-

A schema which shares equivalent concepts to those of the TEI conceptual model may be mappable to the TEI Schema by means of such a mechanism. For example, the concept of paragraph expressed in the TEI schema by the p element is probably the same @@ -967,7 +676,6 @@ that practice. --> interchange because elements from one namespace may be readily integrated with those from another, but do not affect the definition of conformance.

-

A document is said to conform to the TEI Abstract Model if features for which an encoding is proposed by the TEI Guidelines are encoded within it using the markup and other syntactic properties defined by means of a valid TEI-conformant @@ -982,43 +690,25 @@ that practice. --> implicitly by examples of usage. Any inconsistency between, for example, the text of these Guidelines and a part of a specification should be considered an error and reported to the TEI Council for correction.

-
-
Mandatory Components of a TEI Document -

It is a long-standing requirement for any TEI-conformant document that it should contain a teiHeader element. To be more specific a - TEI-conformant document must contain - a single teiHeader element followed by one or more elements from the - model.resource class; or - in the case of a corpus or collection, a single overall teiHeader + TEI-conformant document must contain a single teiHeader element followed by one or more elements from the + model.resource class; or in the case of a corpus or collection, a single overall teiHeader element followed by a series of TEI elements each with its own - teiHeader - All teiHeader elements in a TEI-conformant document must - include elements for: - - This should include the title of the TEI document expressed using a - titleStmt element. - - This should include the place and date of publication or distribution of the TEI - document, expressed using the publicationStmt element. - - For a document derived from some previously existing document, this must include a + teiHeader All teiHeader elements in a TEI-conformant document must + include elements for: This should include the title of the TEI document expressed using a + titleStmt element.This should include the place and date of publication or distribution of the TEI + document, expressed using the publicationStmt element.For a document derived from some previously existing document, this must include a bibliographic description of that source. For a document not so derived, this must include a brief statement that the document has no pre-existing source. In either - case, this will be expressed using the sourceDesc element. -

- + case, this will be expressed using the sourceDesc element.

-
- -
Use of the TEI Namespace -

The Namespaces Recommendation of the W3C () provides a way for an XML document to combine markup from different vocabularies without risking name collision and consequent processing difficulties. While the scope of the TEI is large, there are many @@ -1028,39 +718,32 @@ that practice. --> documents using TEI markup with their own system. To meet these objectives without compromising the reliability of its encoding, a TEI-conformant document is required to make appropriate use of the TEI namespace.

-

Essentially all elements in a TEI Schema which represents concepts from the TEI Abstract Model belong to the TEI namespace, http://www.tei-c.org/ns/1.0, maintained by the TEI. A TEI-conformant document is required to declare the namespace for all the elements it contains whether these come from the TEI namespace or from other schemas.

-

A TEI Schema may be created which assigns TEI elements to some other namespace, or to no namespace at all. A document using such a schema cannot be considered TEI-conformant. A document which places non-TEI elements or attributes within the TEI namespace cannot be considered TEI-conformant; such practices are strongly deprecated as they may lead to serious difficulties for processing or interchange.

-
-
Documentation Constraint -

As noted in above, a TEI Schema can only be generated from a TEI ODD, which also serves to document the semantics of the elements defined by it. A TEI-conformant document should therefore always be accompanied by (or refer to) a valid TEI ODD file specifying which modules, elements, classes, etc. are in use together with any modifications applied, and from which a TEI Schema can be generated to validate the document. The TEI supplies a number of predefined TEI Customization - exemplar ODD files and the schemas already generated from them (see ), but most projects will typically need to customize the TEI beyond + exemplar ODD files and the schemas already generated from them (see ), but most projects will typically need to customize the TEI beyond what these examples provide. It is assumed, for example, that most projects will customize the TEI schema by removing those elements that are not needed for the texts they are encoding, and by providing further constraints on the attribute values and element content models the TEI provides. All such customizations must be specified by means of a valid TEI ODD file.

-

As different sorts of customization have different implications for the interchange and interoperability of TEI documents, it cannot be assumed that every customization will necessarily result in a schema that validates only TEI-conformant documents. The ODD @@ -1068,7 +751,6 @@ that practice. --> observing this model is a requirement for TEI Conformance. The ODD language can in fact be used to describe many kinds of markup schema, including schemas which have nothing to do with the TEI at all.

-

Equally, it is possible to construct a TEI Schema which is identical to that derived from a given TEI ODD file without using the ODD schema. A schema can constructed simply by combining the predefined schema language fragments corresponding with the required set of @@ -1077,125 +759,31 @@ that practice. --> general be easily determined; it may therefore be impractical to determine whether such a schema represents a clean modification or an extension. This is one reason for making the presence of a TEI ODD file a requirement for conformance.

-
- - - -
Varieties of TEI Conformance -

The conformance status of a given document may be assessed by answering the following - questions, in the order indicated: - Is it a valid XML document, for which a TEI Schema exists? If not, then the document - cannot be considered TEI-conformant in any sense. - Is the document accompanied by a TEI-conformant ODD specification describing its + questions, in the order indicated: Is it a valid XML document, for which a TEI Schema exists? If not, then the document + cannot be considered TEI-conformant in any sense.Is the document accompanied by a TEI-conformant ODD specification describing its markup schema and intended semantics? If not, then the document can only be considered TEI-conformant if it validates against a predefined TEI Schema and conforms to the TEI - abstract model. - Does the markup in the document correctly represent the TEI abstract model? Though - difficult to assess, this is essential to TEI conformance. - Does the document claim that all of its elements come from some namespace other than - the TEI (or no namespace)? If so, the document cannot be TEI-conformant. - If the document claims to use the TEI namespace, in part or wholly, do the elements + abstract model.Does the markup in the document correctly represent the TEI abstract model? Though + difficult to assess, this is essential to TEI conformance.Does the document claim that all of its elements come from some namespace other than + the TEI (or no namespace)? If so, the document cannot be TEI-conformant.If the document claims to use the TEI namespace, in part or wholly, do the elements associated with that namespace in fact belong to it? If not, the document cannot be TEI-conformant; if so, and if all non-TEI elements and attributes are correctly - associated with other namespaces, then the document may be TEI-conformant. - Is the document valid according to a schema made by combining all TEI modules as + associated with other namespaces, then the document may be TEI-conformant.Is the document valid according to a schema made by combining all TEI modules as well as valid according to the schema derived from its associated ODD specification? If - so, the document is TEI-conformant. - Is the document valid according to the schema derived from its associated ODD + so, the document is TEI-conformant. Is the document valid according to the schema derived from its associated ODD specification, but not according to tei_all? If so, the - document uses a TEI extension. - Is it possible automatically to transform the document into a document which is + document uses a TEI extension. Is it possible automatically to transform the document into a document which is valid according to tei_all, using only information supplied in the accompanying ODD and without loss of information? If so, the document is - TEI-conformant. - + TEI-conformant.

-

In the following table, we examine more closely some specific, though imaginary, cases: - - - - A - B - C - D - E - F - G - H - - - Conforms to TEI Abstract Model - Y - N - Y - Y - ? - Y - N - ? - - - Valid ODD present - Y - Y - Y - Y - Y - Y - Y - N - - - Uses only non-TEI namespace(s) or none - N - N - N - N - Y - N - Y - N - - - Uses TEI and other namespaces correctly - Y - Y - N - Y - N - Y - N - Y - - - Document is valid as a subset of tei_all - Y - N - Y - N - N - Y - N - Y - - - Document can be converted automatically to a form which is valid as a subset of - tei_all - Y - N - Y - N - N - Y - N - ? - -
+ AB CDE FGHConforms to TEI Abstract ModelYNYY?YN?Valid ODD presentYYYYYYYNUses only non-TEI namespace(s) or noneNNNNYNYNUses TEI and other namespaces correctlyYYNYNYNYDocument is valid as a subset of tei_allYNYNNYNYDocument can be converted automatically to a form which is valid as a subset of + tei_allYNYNNYN?

We assume firstly that each sample document assessed here is a well-formed XML document, and that it is valid against some schema.

@@ -1206,7 +794,6 @@ that practice. --> documents exactly how it uses the TEI. All the TEI-defined elements and attributes in the document are placed in the TEI namespace. The schema against which it is valid is a clean subset of the tei_all schema.

-

The document in column B is not a TEI document. Although it is accompanied by a valid TEI ODD, the resulting schema includes some unclean modifications, and represents some concepts from the TEI Abstract Model using non-TEI elements; for example, it @@ -1216,13 +803,11 @@ that practice. --> ODD. It uses the TEI namespace correctly to identify the TEI elements it contains, but the ODD does not contain enough information automatically to convert its non-TEI elements into TEI equivalents.

-

The document in column C is TEI conformant. It is almost the same as the document in column A, except that the names of the elements used are not those specified for the TEI namespace. Because the ODD accompanying it contains an exact mapping for each element name (using the altIdent element) and there are no name conflicts, it is possible to make an automatic conversion of this document.

-

The document in column D is a TEI Extension. It combines elements from its own namespace with unmodified TEI elements in the TEI namespace. Its usage of TEI elements conforms to the TEI Abstract Model. Its ODD defines a new blort element which @@ -1230,7 +815,6 @@ that practice. --> its schema is not a clean subset of tei_all. If the associated ODD provided a way of mapping this element to an existing TEI element, then this would be TEI-conformant.

-

The document in column E is superficially similar to document D, but because it does not use any namespace declarations (or, equivalently, it assigns unmodified TEI elements to its own namespace), it may contain name collisions; there is no way of knowing whether a @@ -1242,19 +826,15 @@ that practice. --> to represent a concept not in the TEI Abstract Model but in the abstract model of some other system, whose namespace has been removed as well) cannot be reliably resolved. By our current definition therefore, this is not a TEI document.

-

The document in column F is TEI-conformant. The difference between it and that in column D is that the new element blort which is used in this document is a specialization of an existing TEI element, and the ODD in which it is defined specifies the mapping (a my:blort may be automatically converted - to a tei:seg type="blort", for example). For this to work, however, the blort must observe the same syntactic constraints as the + to a tei:seg type="blort", for example). For this to work, however, the blort must observe the same syntactic constraints as the seg; if it does not, this would also be a case of TEI Extension.

-

The document in column G is not a TEI document. Its structure is fully documented by a valid TEI ODD, but it does not claim to represent the TEI Abstract Model, does not use the TEI namespace, and is not intended to validate against any TEI schema.

-

The document in column H is very like that in column A, but it lacks an accompanying ODD. Instead, the schema used to validate it is produced simply by combining TEI schema fragments in the same way as an ODD processor would, given the ODD. If the resulting schema is a clean @@ -1262,53 +842,36 @@ that practice. --> TEI-conformant one, but there is no way of determining (without inspection) whether this is the case if any modification or extension has been applied. Its status is therefore, like that of Text E, impossible to determine.

-
- -
- - - - -
Implementation of an ODD System

This section specifies how a processing system may take advantage of the markup specification elements documented in chapter of these Guidelines in order to produce project specific user documentation, schemas in one or more schema languages, and validation tools for other processors.

-

The specifications in this section are illustrative but not normative. Its function is to further illustrate the intended scope and application of the elements documented in chapter , since it is believed that these may have application beyond the areas directly addressed by the TEI.

-

An ODD processing system has to accomplish two main tasks. A set of selections, deletions, changes, and additions supplied by an ODD customization (as described in ) must first be merged with the published TEI P5 ODD specifications. Next, the resulting unified ODD must be processed to produce the desired outputs.

-

An ODD processor is not required to do these two stages in sequence, but that may well be the simplest approach; the ODD processing tools currently provided by the TEI Consortium, which are also used to process the source of these Guidelines, adopt this approach.

-
Making a Unified ODD

An ODD customization must contain a single schemaSpec element, which defines the - schema to be constructed. - - Amongst other attributes inherited from the att.identified class, this element also carries a required ident + schema to be constructed. Amongst other attributes inherited from the att.identified class, this element also carries a required ident attribute. This provides a name for the generated schema, which other components of the processing system may use to refer to the schema being generated, e.g. in issuing error messages or as part of the generated output schema file or files. The ns attribute may be used to specify the default namespace within which elements valid against the resulting schema belong, as discussed in .

The schemaSpec element contains an unordered series of specialized elements, each - of which is of one of the following four types: - - elements from the class model.oddDecl (by default + of which is of one of the following four types: elements from the class model.oddDecl (by default elementSpec, classSpec, moduleSpec, and macroSpec); these must have a mode attribute which determines how they will be processed.An ODD processor should recognize as @@ -1317,9 +880,7 @@ that practice. --> in an imported module. If the value of mode is add, then the object is simply copied to the output, but if it is change, delete, or replace, then it will be looked at by other parts of - the process. - - specGrpRef elements refer to specGrp elements that occur elsewhere + the process.specGrpRef elements refer to specGrp elements that occur elsewhere in this, or another, document. A specGrp element, in turn, groups together a set of ODD specifications (among other things, including further specGrpRef elements). The use of specGrp and specGrpRef permits the ODD markup to @@ -1328,9 +889,7 @@ that practice. --> be followed, and the elementSpec, classSpec, and macroSpec, elements in the corresponding specGrp should be processed as described in the previous item; specGrpRef elements should be processed as described - here. - - moduleRef elements with key attributes refer to components of + here.moduleRef elements with key attributes refer to components of the TEI. The value of the key attribute matches the ident attribute of the moduleSpec element defining a TEI module. The key must be dereferenced by some means, such as reading an XML file with the TEI ODD @@ -1339,119 +898,63 @@ that practice. --> should return a stream of XML containing the element, class, and macro specifications collected together in the specified module. These specification elements are then processed in the same way as if they had been supplied directly within the - schemaSpec being processed. - - - a moduleRef element may also refer to a compatible external module by means + schemaSpec being processed.a moduleRef element may also refer to a compatible external module by means of its url attribute; the content of such modules, which must be available in the RELAX NG XML syntax, are passed directly and without modification to the output - schema when that is created. - + schema when that is created.

-

Each object obtained from the TEI ODD specification using moduleRef by means of the key attribute must be checked against objects in the customization - schemaSpec according to the following rules: - if there is an object in the ODD customization with the same value for the + schemaSpec according to the following rules: if there is an object in the ODD customization with the same value for the ident attribute, and a mode value of delete, then the - object from the module is ignored; - if there is an object in the ODD customization with the same value for the + object from the module is ignored; if there is an object in the ODD customization with the same value for the ident attribute, and a mode value of replace, then the object from the module is ignored, and the one from the ODD customization is used in - its place; - if there is an object in the ODD customization with the same value for the + its place; if there is an object in the ODD customization with the same value for the ident attribute, and a mode value of change, then the - two objects must be merged, as described below; - if there is an object in the ODD customization with the same value for the + two objects must be merged, as described below; if there is an object in the ODD customization with the same value for the ident attribute, and a mode value of add, then an - error condition should be raised; - - otherwise, the object from the module is copied to the result. - + error condition should be raised; otherwise, the object from the module is copied to the result.

-

To merge two objects with the same ident, their component attributes and child elements must be looked at recursively. Each component may fall into one of the following - four categories: - - Some components may occur only once within the merged object (for example + four categories: Some components may occur only once within the merged object (for example attributes, and altIdent, content, or classes elements). If such a component is found in the ODD customization, it will be copied to the output; if it is not found there, but is present in the TEI ODD specification, then that will be - copied to the output. - - Some components are grouping objects (attList, valList, for + copied to the output. Some components are grouping objects (attList, valList, for example); these are always copied to the output, and their children are then processed - following the rules given in this list. - - Some components are identifiable: this means that they are + following the rules given in this list.Some components are identifiable: this means that they are members of the att.identified class from which they inherit the ident attribute; examples include attDef and valItem. A component of this type will be processed according to its mode attribute, - following the rules given above. - - Some components may occur multiple times, but are neither grouped nor identifiable. + following the rules given above.Some components may occur multiple times, but are neither grouped nor identifiable. Examples include the desc, exemplum, remarks, listRef, datatype and defaultVal elements, and the members of model.identSynonyms, i.e., the equiv, altIdent, and gloss, elements. These should be copied from both the TEI - ODD specification and the ODD customization, and all occurrences included in the output. - + ODD specification and the ODD customization, and all occurrences included in the output.

-

A special problem arises with elements which are members of attribute classes, as they are permitted to override attributes inherited from a class. For example, consider this simple - modification: - - - - - - - The effect of its membership in the att.typed class is + modification: The effect of its membership in the att.typed class is to provide p with a type attribute and a subtype attribute. If we wish p to not have subtype, we could extend the - customization in our schema as follows: - - - - - - - - - - This means that when memberOf key="att.typed"/ is processed, that class + customization in our schema as follows: This means that when memberOf key="att.typed"/ is processed, that class is looked up, each attribute which it defines is examined in turn, and the customization is searched for an override. If the modification is of the attribute class itself, work proceeds as usual; if, however, the modification is at the element level, the class reference is deleted and a series of attRef elements is added to the element, one for each attribute inherited from the class. Since attribute classes can themselves be members of other attribute classes, membership must be followed recursively.

-

The effect of the concatenation of unidentifiable components should be considered - carefully. An original may have - - marks paragraphs in prose. - - - which would usefully be extended with this: - - marca párrafos en prosa. - - - to provide an alternate description in another language. Nothing prevents the user + carefully. An original may have marks paragraphs in prose. which would usefully be extended with this: marca párrafos en prosa. to provide an alternate description in another language. Nothing prevents the user from supplying desc several times in the same language, and subsequent applications will have to decide what that may mean.

-

Similar considerations apply to multiple example elements, though these are less likely to cause problems in documentation. Note that existing examples can only be deleted by supplying a completely new elementSpec in replace mode, since the exemplum element is not identifiable.

-

In the processing of the content models of elements and the content of macros, deleted elements may require special attention.The carthago program behind the Pizza Chef application, written by Michael Sperberg-McQueen for TEI P3 and P4, went to @@ -1476,48 +979,16 @@ that practice. --> --> - - - - - - - - - - - - - - - requires no special treatment because everything is expressed in terms of model + requires no special treatment because everything is expressed in terms of model classes; if the class model.personPart is deleted explicitly, or - removed because all of its members have been deleted, then model.global is left as the only child of the inner alternate. An ODD - processor may or may not elect to simplify the resulting choice between nothing and model.global by removing the wrapper alternate element. + removed because all of its members have been deleted, then model.global is left as the only child of the inner alternate. An ODD + processor may or may not elect to simplify the resulting choice between nothing and model.global by removing the wrapper alternate element. However, such simplification may be considerably more complex in the general case and an ODD processor is therefore likely to be more successful in carrying out such simplification as a distinct stage during processing of ODD sources.

-

If an element refers directly to an element child, like this: - - - - - - - - - - - - - - - and figDesc has been deleted,Note that deletion of +

If an element refers directly to an element child, like this: and figDesc has been deleted,Note that deletion of required elements will cause the schema specification to accept as valid documents which cannot be TEI-conformant, since they no longer conform to the TEI Abstract Model; conformance topics are addressed in more detail in . it will be @@ -1525,52 +996,35 @@ that practice. --> invalid.

-

The result of the work carried out should be a new schemaSpec which contains a complete and internally consistent set of element, class, and macro specifications, possibly also including moduleRef elements with url attributes identifying external modules.

-
-
Generating Schemas

Assuming that any modifications have been resolved, as outlined in the previous section, - making a schema is now a four stage process: - all datatype and other macro specifications must be collected together and declared - at the start of the output schema; - all classes must be declared in the right order (order is significant because since - some classes reference others); - all elements are declared; - any moduleRef elements with a url attribute identifying an - external schema must be processed. - Working in this order gives the best chance of successfully supporting all the + making a schema is now a four stage process: all datatype and other macro specifications must be collected together and declared + at the start of the output schema; all classes must be declared in the right order (order is significant because since + some classes reference others);all elements are declared;any moduleRef elements with a url attribute identifying an + external schema must be processed. Working in this order gives the best chance of successfully supporting all the schema languages. However, there are a number of obstacles to overcome along the way.

-

An ODD processor may choose to use any desired schema language or languages for its schema output, since ODD specifications are expressed as far as possible in a form independent of any schema language. The current TEI ODD processing system produces schema output in the three main schema - languages as follows: - A RELAX NG (XML) schema is generated by converting content models, datatypes, and + languages as follows: A RELAX NG (XML) schema is generated by converting content models, datatypes, and macro specifications provided within the ODD specification; a version re-expressed in the RELAX NG compact syntax is generated using James Clark's trang - application. - - A DTD schema is generated by converting the RELAX NG content models to DTD language, - often simplifying it to allow for the less-sophisticated output language. - - A W3C Schema schema is created by generating a RELAX NG schema and then using James - Clark's trang application. - Note that the method used to generate W3C Schema means that a processor must ensure + application.A DTD schema is generated by converting the RELAX NG content models to DTD language, + often simplifying it to allow for the less-sophisticated output language.A W3C Schema schema is created by generating a RELAX NG schema and then using James + Clark's trang application. Note that the method used to generate W3C Schema means that a processor must ensure that the RELAX NG it generates follows the subset which trang is able to translate properly (see further below)—this may involve simple trial and error.

-

Other projects may decide to follow a different route, perhaps implementing a direct ODD to W3C Schema translator.

-

Secondly, it is possible to create two rather different styles of schema. On the one hand, the schema can try to maintain all the flexibility of ODD by using the facilities of the schema language for parameterization; on the other, it can remove all customization features @@ -1579,33 +1033,8 @@ that practice. --> RELAX NG languages, which can be included as modules in other schemas, and customized further; the second as the output from a processor such as Roma, in which many of the parameterization features have been removed.

-

The difference between the schema styles may be illustrated by considering this ODD - specification: - - - - - - - - - - - - - - - - - - - - - - - - A simple rendering to RELAX NG produces this: + specification: A simple rendering to RELAX NG produces this: att.global.linking.attribute.prev, att.global.linking.attribute.exclude, att.global.linking.attribute.select -}]]> In the above, a subsequent redefinition of the attribute class (such as att.global) would have no effect, since references to such classes have been +}]]> In the above, a subsequent redefinition of the attribute class (such as att.global) would have no effect, since references to such classes have been expanded to reference their constituent attributes.

The equivalent parameterized version might look like this: Here, the attribut parameterized schema are used to distinguish the two schema types. An ODD processor is not required to support both, though the simple schema output is generally preferable for most applications.

-

Thirdly, the problem of missing components must be resolved. For example, consider this - (fictitious) model for sp: - - - - - - - - - - - - - - This proposes anything from the class model.global, - followed optionally by a speaker element followed by anything from the model.global class. What happens if speaker is removed from - the schema? The following would result: - - - - - - - - - - - which is illegal in DTD and W3C schema languages, since for a given member of + (fictitious) model for sp: This proposes anything from the class model.global, + followed optionally by a speaker element followed by anything from the model.global class. What happens if speaker is removed from + the schema? The following would result: which is illegal in DTD and W3C schema languages, since for a given member of model.global it is impossible to be sure which rule is being used. This situation is not detected when RELAX NG is used, since the language is able to cope with non-deterministic content models of this kind and does not require that only a single rule be used.

- - +

Finally, an application will need to have some method of associating the schema with document instances that use it. The TEI does not mandate any particular method of doing this, since different schema languages and processors vary considerably in their @@ -1690,7 +1088,6 @@ performance.attributes = att.global.attributes, empty]]> Here, the attribut method, but does suggest that those which are already part of XML (the DOCTYPE declaration for DTDs) and W3C Schema (the xsi:schemaLocation attribute) be supported where possible.

-

In order for the xsi:schemaLocation attribute to be valid when a document is validated against either a DTD or a RELAX NG schema, ODD processors may wish to add declarations for this attribute and its namespace to the root element, even though these are @@ -1702,150 +1099,73 @@ performance.attributes = att.global.attributes, empty]]> Here, the attribut "http://www.w3.org/2001/XMLSchema-instance"]]> and inside the root element declaration.

-

Note that declaration of the xsi:schemaLocation attribute in a W3C Schema schema is not permitted. Therefore, if W3C Schemas are being generated by converting the RELAX NG schema (for example, with trang), it may be necessary to perform that conversion prior to adding the xsi:schemaLocation declaration to the RELAX NG.

-

It is recognized that this is an unsatisfactory solution, but it permits users to take advantage of the W3C Schema facility for indicating a schema, while still permitting documents to be validated using DTD and RELAX NG processors without any conflict.

-
-
Names and Documentation in Generated Schemas

When processing class, element, or macro specifications, there are three general rules: - - If a RELAX NG pattern or DTD parameter entity is being created, its name is the + If a RELAX NG pattern or DTD parameter entity is being created, its name is the value of the corresponding ident attribute, prefixed by the value of any prefix attribute on schemaSpec. This allows for elements from an external schema to be mixed in without risk of name clashes, since all TEI elements can - be given a distinctive prefix such as tei_. Thus - - - - - - may generate a RELAX NG (compact syntax) pattern like this: + be given a distinctive prefix such as tei_. Thus may generate a RELAX NG (compact syntax) pattern like this: References to these patterns (or, in DTDs, parameter entities) also need to be prefixed - with the same value. - - If an element or attribute is being created, its default name is the value of the + with the same value. If an element or attribute is being created, its default name is the value of the ident attribute, but if there is an altIdent child, its content is - used instead. - - Where appropriate, the documentation strings in gloss and desc + used instead. Where appropriate, the documentation strings in gloss and desc should be copied into the generated schema. If there is only one occurrence of either of these elements, it should be used regardless, but if there are several, local processing rules will need to be applied. For example, if there are several with different values of xml:lang, a locale indication in the processing environment might be used - to decide which to use. For example, - - - heading - en-tête - encabezamiento - titolo - - - might generate a RELAX NG schema fragment like the following, if the locale is + to decide which to use. For example, headingen-têteencabezamientotitolo might generate a RELAX NG schema fragment like the following, if the locale is determined to be French: - - Alternatively, a selection might be made on the basis of the value of the - version attribute which these elements carry as members of the att.translatable class.

+ Alternatively, a selection might be made on the basis of the value of the + version attribute which these elements carry as members of the att.translatable class.

In addition, there are three conventions about naming patterns relating to classes; ODD processors need not follow them, but those reading the schemas generated by the TEI project - will find it necessary to understand them: - when a pattern for an attribute class is created, it is named after the attribute + will find it necessary to understand them: when a pattern for an attribute class is created, it is named after the attribute class identifier (as above) suffixed by .attributes (e.g. - att.editLike.attributes); - when a pattern for an attribute is created, it is named after the attribute class + att.editLike.attributes); when a pattern for an attribute is created, it is named after the attribute class identifier (as above) suffixed by .attribute. and then the identifier of - the attribute (e.g. att.editLike.attribute.resp); - - - when a parameterized schema is created, each element generates patterns for its + the attribute (e.g. att.editLike.attribute.resp);when a parameterized schema is created, each element generates patterns for its attributes and its contents separately, suffixing respectively .attributes - and .contents to the element name. - + and .contents to the element name.

-
Making a RELAX NG Schema -

To create a RELAX NG schema, the processor processes every macroSpec, classSpec, and elementSpec in turn, creating a RELAX NG pattern for each, using the naming conventions listed above. The order of declaration is not important, and a processor may well sort them into alphabetical order of identifier.

-

A complete RELAX NG schema must have an rng:start element defining which elements can occur as the root of a document. The ODD schemaSpec has an optional start attribute, containing one or more patterns, which can be used to construct the rng:start. A pattern normally corresponds to an element name, but if a prefix (see above, ) is supplied for an element, the pattern consists of the prefix name with the element name.

-
Macros

An ODD macro generates a corresponding RELAX NG pattern by processing the body of the - content element in the same way as elsewhere. Thus - - - - - - - - - - - produces the following - - - - - - - - - - - + content element in the same way as elsewhere. Thus produces the following

-
Classes

An ODD model class always generates a RELAX NG pattern definition listing all the members - of the class in alternation. For example - - - - will produce something like the following: - - - - - - - - assuming that the elements num, measure, and + of the class in alternation. For example will produce something like the following: assuming that the elements num, measure, and measureGrp are all defined in the schema concerned as members of that class. A model declaration may also generate a number of other patterns corresponding with sequences or alternations of the class members: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - where the pattern name is created by appending an underscore and the name of the + where the pattern name is created by appending an underscore and the name of the generation type to the class name.

When classes are referenced using the classRef element, it is possible to indicate which of the available patterns is required by means of the expand attribute.

Attribute classes work by producing a pattern containing definitions of the appropriate - attributes. So - - - - - indicates whether the end of a verse line is marked by enjambement. - - - - - - - the line is end-stopped - - - - the line in question runs on into the next - - - - the line is weakly enjambed - - - - the line is strongly enjambed - - - - - - produces - - - - - - - - (enjambement) indicates whether the end of a verse line is marked by + attributes. So indicates whether the end of a verse line is marked by enjambement.the line is end-stopped the line in question runs on into the next the line is weakly enjambed the line is strongly enjambed produces (enjambement) indicates whether the end of a verse line is marked by enjambement. Sample values include: 1] no; 2] yes; 3] weak; 4] - strong - - - - - Since the processor may have expanded the attribute classes already, separate + strong Since the processor may have expanded the attribute classes already, separate patterns are generated for each attribute in the class as well as one for the class itself. This allows an element to refer directly to a member of a class. Notice that the desc element is used to add an a:documentation element to the schema, @@ -1957,56 +1190,16 @@ xsi:schemaLocation { list { teidata.namespace, teidata.pointer }+ }]]> insi include: 1] no; 2] yes; 3] weak; 4] strong Naturally, this behaviour is not mandatory; and other ODD processors may create documentation in other ways, or ignore those parts of the ODD specifications when creating schemas.

-

An individual attribute consists of an rng:attribute with a name - attribute derived according to the naming rules described above (). In addition, the ODD model supports a defaultVal, which is transformed to a - defaultValue attribute in the namespace http://relaxng.org/ns/compatibility/annotations/1.0 on the + attribute derived according to the naming rules described above (). In addition, the ODD model supports a defaultVal, which is transformed to a + defaultValue attribute in the namespace http://relaxng.org/ns/compatibility/annotations/1.0 on the rng:attribute. The body of the attribute is taken from the datatype child, unless there is a supporting valList with a type value of closed. In that case an rng:choice is created, listing the allowed - values. Thus the following attribute definition - - yes - - - the name component is spelled out in full. - - - abbreviated - the name component is given in an abbreviated form. - - - initial letter - the name component is indicated only by one initial. - - - - may generate this RELAX NG code: - - - - - yes - the name component is spelled out in full. - abb - the name component is given in an abbreviated form. - init - the name component is indicated only by one initial. - - - - - - Note the use of the http://relaxng.org/ns/compatibility/annotations/1.0 namespace to provide + values. Thus the following attribute definition yesthe name component is spelled out in full.abbreviatedthe name component is given in an abbreviated form.initial letterthe name component is indicated only by one initial. may generate this RELAX NG code: yes the name component is spelled out in full. abb the name component is given in an abbreviated form. init the name component is indicated only by one initial. + Note the use of the http://relaxng.org/ns/compatibility/annotations/1.0 namespace to provide default values and documentation.

-
Elements

An elementSpec produces a RELAX NG specification in two parts; firstly, it must @@ -2018,43 +1211,19 @@ xsi:schemaLocation { list { teidata.namespace, teidata.pointer }+ }]]> insi content element; ; the attributes are processed in the same way as those from attribute classes, described above.

-
- -
Making a DTD

Generation of DTDs largely follows the same pattern as RELAX NG generation, with one important exception—the order of declaration matters. A DTD may not refer to an entity which has not yet been declared. Since both macros and classes generate DTD parameter entities, the TEI Guidelines are constructed so that they can be declared in the right - order. A processor must therefore work in the following order: - declare all model classes which have a predeclare value of - true - declare all macros which have a predeclare value of - true - declare all other classes - declare the modules (if DTD fragments are being constructed) - declare any remaining macros - declare the elements and their attributes - + order. A processor must therefore work in the following order: declare all model classes which have a predeclare value of + truedeclare all macros which have a predeclare value of + truedeclare all other classesdeclare the modules (if DTD fragments are being constructed)declare any remaining macrosdeclare the elements and their attributes

-

Let us consider a complete example, a simple element with no attributes of its own: - - specifies the faith, religion, or belief set of a person. - - - - - - - - - - If DTD fragments are being generated (for use as described in ), this will result in the following: +

Let us consider a complete example, a simple element with no attributes of its own: specifies the faith, religion, or belief set of a person. If DTD fragments are being generated (for use as described in ), this will result in the following:

%att.global.attributes; %att.editLike.attributes; %att.datable.attributes; > -]]]]>]]> Here the whole stanza is contained in a marked section (for use as described in ), the element name is parameterized (see ), and +]]]]>]]> Here the whole stanza is contained in a marked section (for use as described in ), the element name is parameterized (see ), and the class attributes are entity references derived from the memberOf records in - classes. Note the additional attribute which provides a default xmlns declaration for the element; the effect of this is that if the document is + classes. Note the additional attribute which provides a default xmlns declaration for the element; the effect of this is that if the document is processed by a DTD-aware XML processor, the namespace declaration will be present automatically without the document author even being aware of it.

-

A simpler rendition for a flattened DTD generated from a customization will result in the following, with no containing marked section, and no parameterized name: @@ -2101,28 +1267,21 @@ will come to grief.-->

%att.datable.w3c.attribute.notAfter; %att.datable.w3c.attribute.from; %att.datable.w3c.attribute.to;>]]> Here the attributes from classes have been expanded into individual entity references.

- - -
-
Generating Documentation

In Donald Knuth's literate programming terminology (), the previous sections have dealt with the tangle process; to generate documentation, we now turn to the weave process.

-

An ODD customization may consist largely of general documentation and examples, requiring no ODD-specific processing. It will normally however also contain a schemaSpec element and possibly some specGrp fragments.

-

The generated documentation may be of two forms. On the one hand, we may document the customization itself, that is, only those elements (etc.) which differ in their specification from that provided by the TEI reference documentation. Alternatively, we may generate reference documentation for the complete subset of the TEI which results from applying the customization. The TEI Roma tools take the latter approach, and operate on the result of the first stage processing described in .

-

Generating reference documentation for elementSpec, classSpec, and macroSpec elements is largely dependent on the design of the preferred output. Some applications may, for example, want to turn all names of objects into hyperlinks, show @@ -2136,28 +1295,22 @@ will come to grief.-->

Example reference documentation for faith -
- - -
Using TEI Parameterized Schema Fragments

The TEI parameterized DTD and RELAX NG fragments make use of parameter entities and patterns for several purposes. In this section we describe their interface for the user. In general we recommend use of ODD instead of this technique, which has been retained only for compatability reasons.

-
Selection of Modules -

Special-purpose parameter entities are used to specify which modules are to be combined into a TEI DTD. They take the form TEI.xxxxx where xxxx is the name of the module as given in table in . @@ -2166,18 +1319,13 @@ will come to grief.-->

parameter entities are declared by default with the value IGNORE: to select a module, therefore, the encoder declares the appropriate parameter entities with the value INCLUDE.

-

For XML DTD fragments, note that some modules generate two DTD fragments: for example the - analysis module generates fragments called analysis-decl and analysis. This is + analysis module generates fragments called analysis-decl and analysis. This is because the declarations they contain are needed at different points in the creation of an XML DTD.

-

The parameter entity named for the module is used as the keyword controlling a - conditional marked section in the DTD fragment generated by the tei module. The declarations for each DTD fragment constituting the module are - contained within such marked sections. For example, the parameter entity TEI.linking appears twice in tei.dtd, once for the + conditional marked section in the DTD fragment generated by the tei module. The declarations for each DTD fragment constituting the module are + contained within such marked sections. For example, the parameter entity TEI.linking appears twice in tei.dtd, once for the linking-decl schema fragment:

%file.linking;]] >]]> If TEI.linking has its default value of IGNORE, neither declaration has any effect. If however it has the value INCLUDE, then the content of each marked section is acted upon: - the parameter entities file.linking and file.linking-decl are referenced, which has the effect of embedding the content + the parameter entities file.linking and file.linking-decl are referenced, which has the effect of embedding the content of the files they represent at the appropriate point in the DTD.

-

The RELAX NG schema fragments can be combined in a wrapper schema using the standard mechanism of rng:include in that language.

-
- -
Inclusion and Exclusion of Elements -

The TEI DTD fragments also use marked sections and parameter entity references to allow users to exclude the definitions of individual elements, in order either to make the elements illegal in a document or to allow the element to be redefined. The parameter @@ -2208,7 +1350,6 @@ will come to grief.-->

element concerned. The default definition for these parameter entities is INCLUDE but they may be changed to IGNORE in order to exclude the standard element and attribute definition list declarations from the DTD.

-

The declarations for the element p, for example, are preceded by a definition for a parameter entity with the name p and contained within a marked section whose keyword is given as %p;: @@ -2217,22 +1358,18 @@ will come to grief.-->

]]]]>

These parameter entities are defined immediately preceding the element whose declarations they control; because their names are completely regular, they are not documented further.

-

To define a DTD in which the element p is excluded therefore, the entity p needs to be redefined as IGNORE by +

To define a DTD in which the element p is excluded therefore, the entity p needs to be redefined as IGNORE by ensuring that a declaration such as ]]> is added earlier in the DTD than the default (see further ).

-

Similarly, in the parameterized RELAX NG schemas, every element is defined by a pattern named after the element. To undefine an element therefore all that is necessary is to add a declaration like the following:

-
Changing the Names of Generic Identifiers -

In the TEI DTD fragments, elements are not referred to directly by their generic identifiers; instead, the DTD fragments refer to parameter entities which expand to the standard generic identifiers. This allows users to rename elements by redefining the @@ -2245,9 +1382,7 @@ will come to grief.-->

]]> Note that since all names are case-sensitive, the specific mix of uppercase and lowercase letters in the standard generic identifier must be preserved in the entity name.

-

These declarations are generated by an ODD processor when TEI DTD fragments are created.

-

In the RELAX NG schemas, all elements are normally defined using a pattern with the same name as the element (as described in ): for example The easiest way of renaming the element is thus simply to rewrite the pattern with a @@ -2256,45 +1391,29 @@ will come to grief.-->

pattern abbr.content) or its attributes (defined by the pattern abbr.attributes) can be accomplished in a similar way, using the features of the RELAX NG language. The recommended method of carrying out such - modifications is however to use the ODD language as further described in section .

+ modifications is however to use the ODD language as further described in section .

- -
Embedding Local Modifications (DTD only) -

Any local modifications to a DTD (i.e. changes to a schema other than simple inclusion or exclusion of modules) are made by declarations stored in one of two local extension files, one containing modifications to the TEI parameter entities, and the other new or changed declarations of elements and their attributes. Entity declarations must be made which associate the names of these two files with the appropriate parameter entity so that the declarations they contain can be embedded within the TEI DTD at an appropriate point.

-

The following entities are referred to by the main tei.dtd - file to embed portions of the TEI DTD fragments or locally developed extensions. - - identifies a local file containing extensions to the TEI parameter entities - - identifies a local file containing extensions to the TEI module -

-

For example, if the relevant files are called project.ent and project.dtd, then + file to embed portions of the TEI DTD fragments or locally developed extensions. identifies a local file containing extensions to the TEI parameter entitiesidentifies a local file containing extensions to the TEI module

+

For example, if the relevant files are called project.ent and project.dtd, then declarations like the following would be appropriate: ]]>

-

When an entity is declared more than once, the first declaration is binding and the others are ignored. The local modifications to parameter entities should therefore be - handled before the standard parameter entities themselves are declared in tei.dtd. The entity TEI.extensions.ent is + handled before the standard parameter entities themselves are declared in tei.dtd. The entity TEI.extensions.ent is referred to before any TEI declarations are handled, to allow the user's declarations to take priority. If the user does not provide a TEI.extensions.ent entity, the entity will be expanded to the empty string.

-

For example the encoder might wish to add two phrase-level elements it and bd, perhaps as synonyms for - hi rend='italics' and hi rend='bold'. As described in chapter , this involves two distinct steps: one to define the new elements, and +

For example the encoder might wish to add two phrase-level elements it and bd, perhaps as synonyms for + hi rend='italics' and hi rend='bold'. As described in chapter , this involves two distinct steps: one to define the new elements, and the other to ensure that they are placed into the TEI document structure at the right place.

Creating the new declarations is done in the same way for user-defined elements as for @@ -2312,9 +1431,6 @@ will come to grief.-->

|'>]]> and this declaration will take precedence over the default when the declaration for macro.phraseSeq is evaluated.

-
-
-
diff --git a/P5/Source/Guidelines/en/VE-Verse.xml b/P5/Source/Guidelines/en/VE-Verse.xml index ede8b26788..40221ff91e 100644 --- a/P5/Source/Guidelines/en/VE-Verse.xml +++ b/P5/Source/Guidelines/en/VE-Verse.xml @@ -1,43 +1,31 @@ - +
- Verse -

This module is intended for use when encoding texts which are entirely or predominantly in + Verse +

This module is intended for use when encoding texts which are entirely or predominantly in verse, and for which the elements for encoding verse structure already provided by the core module are inadequate.

-

The tags described in section include elements for the encoding of verse +

The tags described in section include elements for the encoding of verse lines and line groups such as stanzas: these are available for any TEI document, irrespective of the module it uses. Like the modules for prose and for drama, the module for verse additionally makes use of the module defined in chapter to define the basic formal structure of a text, in terms of front, body and back elements and the text-division elements into which these may be subdivided.

-

The module for verse extends the facilities provided by these modules in the following ways: - - a special purpose caesura element is provided, to allow for segmentation of - the verse line (see section ) - a set of attributes is provided for the encoding of rhyme scheme and metrical - information (see sections and ) - a special purpose rhyme element is provided to support simple analysis of - rhyming words (see section ) -

- - -
- Structural Divisions of Verse Texts -

Like other kinds of text, texts written in verse may be of widely differing lengths and +

The module for verse extends the facilities provided by these modules in the following ways: + a special purpose caesura element is provided, to allow for segmentation of + the verse line (see section )a set of attributes is provided for the encoding of rhyme scheme and metrical + information (see sections and )a special purpose rhyme element is provided to support simple analysis of + rhyming words (see section )

+
+ Structural Divisions of Verse Texts +

Like other kinds of text, texts written in verse may be of widely differing lengths and structures. A complete poem, no matter how short, may be treated as a free-standing text, and encoded in the same way as a distinct prose text. A group of poems functioning as a single unit may be encoded either as a group or as a text, depending on the encoder's view of the text. For further discussion, including an example encoding for a verse anthology, see chapter .

-

Many poems consist only of ungrouped lines. +

Many poems consist only of ungrouped lines. @@ -61,203 +49,79 @@ $Id$ This short poem by Emily - Dickinson is a simple case: - - 1755 - - - To make a prairie it takes a clover and one bee, - One clover, and a bee, - And revery. - The revery alone will do, - If bees are few. - - + Dickinson is a simple case: 1755To make a prairie it takes a clover and one bee,One clover, and a bee,And revery.The revery alone will do,If bees are few.

-

Often, however, lines are grouped, formally or informally, into stanzas, verse paragraphs, +

Often, however, lines are grouped, formally or informally, into stanzas, verse paragraphs, etc. The lg element defined in the core tag set (in section ) may be used for all such groupings. It may thus serve for informal groupings of lines such - as those of the following example from Allen Ginsberg: - - My Alba - - Now that I've wasted - five years in Manhattan - life decaying - talent a blank - - - talking disconnected - patient and mental - sliderule and number - machine on a desk - - - + as those of the following example from Allen Ginsberg: My AlbaNow that I've wastedfive years in Manhattanlife decayingtalent a blanktalking disconnectedpatient and mentalsliderule and numbermachine on a desk

-

It may also be used to mark the verse paragraphs into which longer poems are often divided, +

It may also be used to mark the verse paragraphs into which longer poems are often divided, as in the following example from Samuel Taylor Coleridge's Frost at - Midnight: - The Frost performs its secret ministry, - Unhelped by any wind. ... - Whose puny flaps and freaks the idling Spirit - By its own moods interprets, every where - Echo or mirror seeking of itself, - And makes a toy of Thought. - - - But O! how oft, - How oft, at school, with most believing mind - Presageful, have I gazed upon the bars, - To watch that fluttering stranger! ... - - - Dear Babe, that sleepest cradled by my side, - + Midnight: The Frost performs its secret ministry,Unhelped by any wind. ...Whose puny flaps and freaks the idling SpiritBy its own moods interprets, every whereEcho or mirror seeking of itself,And makes a toy of Thought.But O! how oft,How oft, at school, with most believing mindPresageful, have I gazed upon the bars,To watch that fluttering stranger! ... Dear Babe, that sleepest cradled by my side, Note, in the above example, the use of the part attribute on the l element, where a verse line is broken between two line groups, as discussed in section .

-

Most typically, however, the lg element is used to mark the highly regular line +

Most typically, however, the lg element is used to mark the highly regular line groups which characterize stanzaic and similar verse forms, as in the following example - from Chaucer: - Sire Thopas was a doghty swayn; - White was his face as payndemayn, - His lippes rede as rose; - His rode is lyk scarlet in grayn, - And I yow telle in good certayn, - He hadde a semely nose. - - - His heer, his ber was lyk saffroun, - That to his girdel raughte adoun; - + from Chaucer: Sire Thopas was a doghty swayn;White was his face as payndemayn,His lippes rede as rose;His rode is lyk scarlet in grayn,And I yow telle in good certayn,He hadde a semely nose.His heer, his ber was lyk saffroun,That to his girdel raughte adoun;

-

Like other text-division elements, lg elements may be nested hierarchically. For +

Like other text-division elements, lg elements may be nested hierarchically. For example, one particularly common English stanzaic form consists of a quatrain or sestet followed by a couplet. The lg element may be used to encode both the stanza and - its components, as in the following example from Byron: - - In the first year of Freedom's second dawn - Died George the Third; although no tyrant, one - Who shielded tyrants, till each sense withdrawn - Left him nor mental nor external sun: - A better farmer ne'er brushed dew from lawn, - A worse king never left a realm undone! - - - He died — but left his subjects still behind, - One half as mad — and t'other no less blind. - - + its components, as in the following example from Byron: In the first year of Freedom's second dawnDied George the Third; although no tyrant, oneWho shielded tyrants, till each sense withdrawnLeft him nor mental nor external sun:A better farmer ne'er brushed dew from lawn,A worse king never left a realm undone!He died — but left his subjects still behind,One half as mad — and t'other no less blind.

-

Note the use of the type attribute to name the type of unit encoded by the +

Note the use of the type attribute to name the type of unit encoded by the lg element; this attribute is common to all members of the att.divLike class (see section ).For discussion of other attributes of this class, see . When used on lg, the type attribute is intended solely for conventional names of different classes of text block. For systematic analysis of metrical and rhyme schemes, use the met and rhyme attributes, for which see below, section .

-

As a further example, consider the Shakespearean sonnet. This may be divided into two +

As a further example, consider the Shakespearean sonnet. This may be divided into two parts: a concluding couplet, and a body of twelve lines, itself subdivided into three quatrains: - - - - - My Mistres eyes are nothing like the Sunne, - Currall is farre more red, then her lips red - If snow be white, why then her brests are dun: - If haires be wiers, black wiers grown on her head: - - - I have seene Roses damaskt, red and white, - But no such Roses see I in her cheekes, - And in some perfumes is there more delight, - Then in the breath that from my Mistres reekes. - - - I love to heare her speake, yet well I know, - That Musicke hath a farre more pleasing sound: - I graunt I never saw a goddesse goe, - My Mistres when shee walkes treads on the ground. - - - - And yet by heaven I think my love as rare, - As any she beli'd with false compare. - - - + My Mistres eyes are nothing like the Sunne,Currall is farre more red, then her lips redIf snow be white, why then her brests are dun:If haires be wiers, black wiers grown on her head:I have seene Roses damaskt, red and white,But no such Roses see I in her cheekes,And in some perfumes is there more delight,Then in the breath that from my Mistres reekes.I love to heare her speake, yet well I know,That Musicke hath a farre more pleasing sound:I graunt I never saw a goddesse goe,My Mistres when shee walkes treads on the ground.And yet by heaven I think my love as rare,As any she beli'd with false compare.

-

Particularly lengthy poetic texts are often subdivided into units larger than stanzas or +

Particularly lengthy poetic texts are often subdivided into units larger than stanzas or paragraphs, which may themselves be subdivided. Spenser's Faery Queene, for example, consists of twelve books each of which contains a prologue followed by twelve cantos. Each prologue and each canto consists of nine-line stanzas, each of which follows the same regular pattern. Other examples in the same tradition are easy to find.

- -

Large structures of this kind are most conveniently represented by div or +

Large structures of this kind are most conveniently represented by div or div1 elements, as described in section . Thus the start - of the Faerie Queene might be encoded as follows: -

-
- - A Gentle Knight was pricking on the plain - Y cladd in mightie armes and silver shielde, - -
-
- The encoder must choose at which point in the hierarchy of structural + of the Faerie Queene might be encoded as follows:
A Gentle Knight was pricking on the plainY cladd in mightie armes and silver shielde,
 The encoder must choose at which point in the hierarchy of structural units to introduce lg elements rather than a yet smaller div element: it - would (for example) also be possible to encode the above example as follows: -
-
-
- A gentle knight was pricking on the plain - Ycladd in mightie armes and silver shielde, -
-
-
-

- -

One reason for using div rather than lg elements is that the former may + would (for example) also be possible to encode the above example as follows:

A gentle knight was pricking on the plainYcladd in mightie armes and silver shielde,

+

One reason for using div rather than lg elements is that the former may contain non-metrical elements, such as epigraphs or dedications and other members of the model.divTop class, whereas lg elements may contain only headings or metrical lines.

-
-
- Components of the Verse Line -

It is often convenient for various kinds of analysis to encode subdivisions of verse lines. +

+
+ Components of the Verse Line +

It is often convenient for various kinds of analysis to encode subdivisions of verse lines. The general purpose seg element defined in the tag set for segmentation and - alignment (section ) is provided for this purpose: - -

-

To use this element together with the module for verse, the module for segmentation and + alignment (section ) is provided for this purpose:

+

To use this element together with the module for verse, the module for segmentation and alignment must also be enabled as further described in section .

-

In Old and Middle English alliterative verse, individual verse lines are typically split +

In Old and Middle English alliterative verse, individual verse lines are typically split into half lines. The seg element may be used to mark these explicitly, as in the following example from Langland's Piers Plowman: In a somer - seson, - whan softe was the sonne, - I shoop me into shroudes - as I a sheep were, - In habite as an heremite - unholy of werkes, - Went wide in this world - wondres to here. - + seson,whan softe was the sonne,I shoop me into shroudesas I a sheep were,In habite as an heremite unholy of werkes,Went wide in this world wondres to here.

-

The seg element can be nested hierarchically, in the same way as the lg +

The seg element can be nested hierarchically, in the same way as the lg element, down to whatever level of detailed structure is required. In the following example, the line has been divided into feet, each of which has been further subdivided into syllables.As elsewhere in these Guidelines, this @@ -267,138 +131,80 @@ $Id$ this example will still require additional processing, since whitespace should be retained for the lower level seg elements (those of type syll) but not for the higher level one (those of type foot). - - Arma vi - rumque ca - no Tro - iae qui - primus ab - oris - -

-

The seg element may be used to identify any subcomponent of a line which has + Arma virumque cano Troiae qui primus ab oris

+

The seg element may be used to identify any subcomponent of a line which has content; its type attribute may characterize such units in any way appropriate to the needs of the encoder. For the specific case of labeling each foot with its formal type (dactyl, spondee, etc.), and each syllable with its metrical or prosodic status (syllables bearing primary or secondary stress, long syllables, short syllables), however, the specialized attributes met and real are defined, which provide a more systematic framework than the type attribute; see section below.

-

In classical verse, a hexameter like that above may also be formally divided into two +

In classical verse, a hexameter like that above may also be formally divided into two cola or hemistiches. This example provides a typical case, in that the boundary of the first colon falls in the middle of one of the feet (between the syllables no and Tro). If both kinds of segmentation are required, the part attribute might be used to mark the overlapping structure as - follows. - - - Ar - ma - vi - - - rum - que - ca - - - no - - - - - Tro - - - iae - qui - - - + follows. Arma virumque cano Troiae qui

-

Instead of using the part attribute on the seg element, it might be +

Instead of using the part attribute on the seg element, it might be simpler just to mark the point at which the caesura occurs. An additional element is provided for analyses of this kind, in which what is to be marked are points between the - words, which have some significance within a verse line: - - In classical prosody, the caesura, which occurs within a foot, is + words, which have some significance within a verse line: In classical prosody, the caesura, which occurs within a foot, is distinguished from a diaeresis, which occurs on a foot boundary (not to be confused with the division of a diphthong into two syllables, or the diacritic symbol used to indicate such division, each of which is also termed diaeresis). This distinction is rarely made nowadays, the term caesura being used for any division irrespective of foot boundaries. No special-purpose diaeresis element is therefore provided.

-

As an example of the caesura element, we refer again to the example from Langland. +

As an example of the caesura element, we refer again to the example from Langland. An encoder might choose simply to record the location of the caesura within each line, rather than encoding each half-line as a segment in its own right, as follows: In a somer seson, - whan softe was the sonne, - I shoop me into shroudes as I a sheep were, - In habite as an heremite unholy of werkes, - Went wide in this world wondres to here. + whan softe was the sonne, I shoop me into shroudes as I a sheep were, In habite as an heremite unholy of werkes, Went wide in this world wondres to here.

-

Logically, the opposite of caesura might be considered to be enjambement. When +

Logically, the opposite of caesura might be considered to be enjambement. When the verse module is included in a schema, an additional class - called att.enjamb is defined as follows: - - The following lines demonstrate the use of the enjamb attribute to + called att.enjamb is defined as follows: The following lines demonstrate the use of the enjamb attribute to mark places where there is a discrepancy between the boundaries of the l elements and the syntactic structure of the verse (a discrepancy of some significance in some - schools of verse): Un astrologue, un jour, se laissa choir - Au fond d'un puits. + schools of verse): Un astrologue, un jour, se laissa choirAu fond d'un puits.

-
-
- Encoding Textual Structures Across Verses -

It is possible that certain textual structures may span multiple lines of verse, either by +

+
+ Encoding Textual Structures Across Verses +

It is possible that certain textual structures may span multiple lines of verse, either by incorporating more than one, or by crossing line hierarchy. This is common, for example, when lines contain reported thought or speech (i.e. said), or other forms of quotation (i.e. q). For these cases, it is recommended practice to fragment and reconstruct the elements representing the textual structures.

-

The following example from Margaret Cavendish's Nature's Pictures shows speech +

The following example from Margaret Cavendish's Nature's Pictures shows speech encoded across two lines reconstructed by chaining elements with prev and - next attributes: - - Our lives, ſaid he, + next attributes: Our lives, ſaid he, wee'll give before we yield, - - - Wee'll win your battles, or dye in the field. - - + Wee'll win your battles, or dye in the field. +

-

Alternatively, the elements may be reconstructed with stand-off markup using the element join: - - - Our lives, ſaid he, +

Alternatively, the elements may be reconstructed with stand-off markup using the element join: + Our lives, ſaid he, wee'll give before we yield, - - - Wee'll win your battles, or dye in the field. - - - -

- -

- + Wee'll win your battles, or dye in the field. +

-

+

A more general discussion of these and other strategies to deal with fragmentation and reconstruction appears in section .

-
-
- Rhyme and Metrical Analysis -

When the module for verse is in use, the following additional attributes are available to - record information about rhyme and metrical form: - - +

+
+ Rhyme and Metrical Analysis +

When the module for verse is in use, the following additional attributes are available to + record information about rhyme and metrical form:

-

These attributes may be attached to the lg element, or to the higher-level +

These attributes may be attached to the lg element, or to the higher-level text-division elements div, div1, etc. In general, the attributes should be specified at the highest level possible; they may not however be specifiable at the highest level if some of the subdivisions of a text are in prose and others in verse. All @@ -407,35 +213,28 @@ $Id$ on l or seg. The value for these attributes may take any form desired by the encoder, but the nature of the notation used will determine how well the attribute values can be processed by automatic means.

-

The primary function of the metrical attributes is to encode the conventional metrical or +

The primary function of the metrical attributes is to encode the conventional metrical or rhyming structure within which the poet is working, rather than the actual prosodic realization of each line; the latter can be recorded using the real attribute, as further discussed below. A simple mechanism is also provided for recording the actual realization of a rhyme pattern; see .

-
- Sample Metrical Analyses -

As a simple example of the use of these attributes, consider the following lines from - Pope's Essay on Criticism:

- - 'Tis hard to say, if greater Want of Skill - Appear in Writing or in Judging ill; - But, of the two, less dang'rous is th'Offence, - To tire our Patience, than mis-lead our Sense: - -
+
+ Sample Metrical Analyses +

As a simple example of the use of these attributes, consider the following lines from + Pope's Essay on Criticism:

'Tis hard to say, if greater Want of SkillAppear in Writing or in Judging ill;But, of the two, less dang'rous is th'Offence,To tire our Patience, than mis-lead our Sense:

-

This text is written entirely in heroic couplets; each line is an iambic +

This text is written entirely in heroic couplets; each line is an iambic pentameter (which, using a common notation, can be described with the formula -+|-+|-+|-+|-+/, each - denoting a metrically unstressed syllable, each + a metrically stressed one, each | a foot boundary, and the / a line-end), and the couplets rhyme (which can be represented with the conventional formula aa).

-

Because both rhyme pattern and metrical form are consistent throughout the poem, they +

Because both rhyme pattern and metrical form are consistent throughout the poem, they may be conveniently specified on the div element; the values given for the attributes will be inherited by any metrical unit contained within the div elements of this poem, and must be interpreted in the appropriate way.

-

Since the notation used in the met, real, and rhyme +

Since the notation used in the met, real, and rhyme attributes is user-defined, no binding description can be given of its details or of how its interpretation must proceed. (A default notation is provided for the rhyme attribute, which however the encoder can replace with another; see @@ -452,7 +251,7 @@ $Id$ sophisticated software, segments within the line might even be understood as inheriting precisely that portion of the formula which applies to the segment in question; this will, however, be easier to accomplish for some languages than for others.

-

The rhyme attribute in this example uses the default notation to specify a +

The rhyme attribute in this example uses the default notation to specify a rhyme scheme applicable only to pairs of lines. As elsewhere, the default notation for the rhyme attribute has no meaning for metrical units at the line level or below. In verse forms where line-internal rhyme is structurally significant, e.g. in @@ -461,18 +260,18 @@ $Id$ line. In such cases, a user-specified rhyme notation must be substituted for the default notation, or else the rhyme pattern must be described using some alternative method (e.g. by using the link mechanism described below).

-

The precise semantics of the met attribute and the inferences which software +

The precise semantics of the met attribute and the inferences which software is expected or able to draw from it, are implementation-dependent; so are the semantics and processing of the rhyme attribute, when user-specified notations are used.

-

A formal definition of the significance of each component of the pattern given as the +

A formal definition of the significance of each component of the pattern given as the value of the met attribute may be provided in the metDecl element within the encodingDesc element in the TEI header (see section ). The encoder is free to invent any notation appropriate to his or her analytic needs, provided that it is adequately documented in this element. The notation may define metrical components using invented or traditional names (such as iamb or hexameter) or in terms of basic units such as codes for stressed or unstressed syllables, or a combination of the two.

-

The real (for realization) attribute may optionally be specified to +

The real (for realization) attribute may optionally be specified to indicate any deviation from the pattern defined by the met attribute which the encoder wishes to record. By default, the real attribute has the same value as the met attribute on the same element; it is only necessary to @@ -482,43 +281,28 @@ $Id$ stress the word But at the beginning of the third line rather than the word of following it, as the metrical pattern would normally require. This variation might be encoded as follows: - - But, of the two, ... - + But, of the two, ...

-

Where the real attribute is used to over-ride the default or conventional +

Where the real attribute is used to over-ride the default or conventional metrical pattern, it applies only to the element on which it is specified. The default pattern for any subsequent lines is unaffected.

-

As it happens, this particular kind of variation is very common in the English iambic +

As it happens, this particular kind of variation is very common in the English iambic pentameter—it even has a name: trochaic substitution—an encoder might therefore choose to regard this not as an instance of a variant realization, but as an instance of a variant metrical form: - - But, of the two, ... - Alternatively, a different metrical notation might be defined, in + But, of the two, ... Alternatively, a different metrical notation might be defined, in which this kind of variation was permitted throughout the text.

-

In choosing whether to over-ride a metrical specification in this way or by using the +

In choosing whether to over-ride a metrical specification in this way or by using the real attribute, the encoder is required to determine whether the change is a systematic or conventional one (as in this example) or an occasional variation, perhaps for local effect. In the following example, from Goethe's Auf dem See, the variation is a matter of local realization: - - - Und frische Nahrung, neues Blut - Saug' ich aus freier Welt; - Wie ist Natur so hold und gut, - Die mich am Busen hält! - Die Welle wieget unsern Kahn - Im Rudertakt hinauf, - Und Berge, wolkig himmelan, - Begegnen unserm Lauf. - On the other hand, the famous inserted alexandrine in Pope's Essay + Und frische Nahrung, neues Blut Saug' ich aus freier Welt; Wie ist Natur so hold und gut, Die mich am Busen hält! Die Welle wieget unsern Kahn Im Rudertakt hinauf, Und Berge, wolkig himmelan, Begegnen unserm Lauf. On the other hand, the famous inserted alexandrine in Pope's Essay on Criticism, might be encoded as follows: A - needless alexandrine ends the song, - That, like a wounded + needless alexandrine ends the song, That, like a wounded snake, drags its slow length along. Here the @@ -526,19 +310,17 @@ $Id$ alexandrine) is in force, while the real attribute indicates that there is a variation from that convention. As with many other aspects of metrical analysis, however, this is of necessity an entirely interpretive judgment.

-
-
- Segment-Level versus Line-level Tagging -

The examples given so far have encoded information about the realization of metrical +

+
+ Segment-Level versus Line-level Tagging +

The examples given so far have encoded information about the realization of metrical conventions at the level of the whole verse-line. This has obvious advantages of simplicity, but the disadvantage that any deviation from metrical convention is not marked at its precise point of occurrence in the text. Greater precision may be achieved, but only at the cost of marking deviant metrical units explicitly. This may be done with the seg element, giving the variant realization as the value of the real attribute on that element. Using this method, the example given - immediately above might be encoded as follows: A needless alexandrine ends the song, - - That, like a wounded snake, + immediately above might be encoded as follows: A needless alexandrine ends the song, That, like a wounded snake, drags its slow length along. The marking of the foot boundaries with the symbol | in the met attribute value of @@ -555,94 +337,64 @@ $Id$ is not sufficiently intelligent to scan lines without aid from the markup. Human readers who are interested in prosody may well be able to exploit the markup in useful ways even with less sophisticated software.

-

There are circumstances where it may also be useful to use the met attribute +

There are circumstances where it may also be useful to use the met attribute of seg. If we wish to identify the exact location of the different types of foot in the first line of Virgil's Aeneid, the text could be encoded as - follows (for simplicity's sake the caesura has been omitted): Arma vi - rumque ca - no Tro - iae qui - primus ab - oris - An appropriate value of the met attribute might also be + follows (for simplicity's sake the caesura has been omitted): Arma virumque cano Troiae qui primus ab oris An appropriate value of the met attribute might also be supplied on the enclosing div element, to indicate that each foot may be made up of a dactyl or a spondee, so that the values given here for met at the level of the foot may be considered a series of local variations on this fundamental pattern; in cases like this, of course, the local variations may also be considered aspects of realization rather than of convention, in which case the real attribute may be used instead of met, if desired.

-
-
- Metrical Analysis of Stanzaic Verse -

The method described above may be used to encode quite complex verse forms, for instance +

+
+ Metrical Analysis of Stanzaic Verse +

The method described above may be used to encode quite complex verse forms, for instance various kinds of fixed-form stanzas. Let us take one of Dante's canzoni, in which each stanza except the last has the same combination of eleven-syllable and seven-syllable - lines, and the same rhyme scheme:

- - Doglia mi reca nello core ardire - -
+ lines, and the same rhyme scheme:
Doglia mi reca nello core ardire

-

Here the met attribute specifies a metrical pattern for each of the +

Here the met attribute specifies a metrical pattern for each of the twenty-one lines making up a stanza of the canzone. Each stanza inherits this definition from the parent div element. The rhyme attribute specifies a rhyme scheme for each stanza, in the same way.

-

In the metrical notation used here, the letter E represents a line containing +

In the metrical notation used here, the letter E represents a line containing nine syllables which may or may not be metrically prominent, a tenth which is prominent and an optional non-prominent eleventh syllable. The letter S is used to represent a line containing five syllables which may or may not be metrically prominent, a sixth which is prominent and an optional non-prominent seventh syllable. A suitable definition for this notation might be given by a metDecl element like the following: - - - xxxxxxxxx+o - xxxxx+o - metrically prominent or non-prominent - metrically prominent - optional non prominent - line division - - + xxxxxxxxx+oxxxxx+ometrically prominent or non-prominentmetrically prominentoptional non prominentline division

-

As noted above, the metrical pattern specified on the div applies to each +

As noted above, the metrical pattern specified on the div applies to each lg (stanza) element contained within the div. In fact however, after seven stanzas of this type, there is a final stanza, known as a commiato or envoi, which follows a different metrical and rhyming scheme. The solution to this problem is simply to specify a new met attribute on the eighth stanza itself, which will override the default value inherited from parent - div, as follows:

- - ... - - - Canzone, presso di qui è une donna - -

-

Note that, in the same way as for the real attribute, over-riding of this + div, as follows:

... Canzone, presso di qui è une donna

+

Note that, in the same way as for the real attribute, over-riding of this kind does not affect subsequent elements at the same hierarchic level. Any lg element following the commiato above would be assumed to use the same metrical and rhyming scheme as the one preceding the commiato. Moreover, although it is quite regular (in the sense that the last stanza of each canzone is a commiato), the over-riding must be specified for each case.

-
-
-
- Rhyme - -

The rhyme attribute is used to specify the rhyme pattern of a verse form. It +

+
+
+ Rhyme +

The rhyme attribute is used to specify the rhyme pattern of a verse form. It should not be confused with the rhyme element, which is used to mark the actual - rhyming word or words: - -

- -

Like the met attribute, the rhyme attribute can be used with a + rhyming word or words:

+

Like the met attribute, the rhyme attribute can be used with a user-specified notation documented by the metDecl element in the TEI header. Unlike met, however, the rhyme attribute has a default notation; if this default notation is used, no metDecl element need be given.

-

The default notation for rhyme offers the ability to record patterns of rhyming lines, +

The default notation for rhyme offers the ability to record patterns of rhyming lines, using the traditional notation in which distinct letters stand for rhyming lines. For a work in rhyming couplets, like the Pope example above, the rhyme attribute simply specifies aa, indicating that pairs of adjacent lines rhyme with each @@ -651,108 +403,56 @@ $Id$ abab. The traditional Spenserian stanza has the pattern ababbcbcc, indicating that within each nine line stanza, lines 1 and 3 rhyme with each other, as do lines 2, 4, 5 and 7, and lines 6, 8 and 9.

-

Non-rhyming lines within such a group may be represented using a hyphen or an x, as in the - following example: - - Why, all the Saints and Sages who discuss'd - Of the Two Worlds so learnedly, are thrust - Like foolish Prophets forth; their Words to Scorn - Are scatter'd, and their Mouths are stopt with Dust. - -

-

The rhyme element may be used to mark the words (or parts of words) which rhyme - according to a predefined pattern: - Outside in the distance a wildcat did growl - Two riders were approaching and the wind began to howl - - +

Non-rhyming lines within such a group may be represented using a hyphen or an x, as in the + following example: Why, all the Saints and Sages who discuss'dOf the Two Worlds so learnedly, are thrustLike foolish Prophets forth; their Words to ScornAre scatter'd, and their Mouths are stopt with Dust.

+

The rhyme element may be used to mark the words (or parts of words) which rhyme + according to a predefined pattern: Outside in the distance a wildcat did growlTwo riders were approaching and the wind began to howl

-

The label attribute is used to specify which parts of a rhyme scheme a given set - of rhyming words represent: - I wander thro' each charter'd street, - Near where the charter'd Thames does flow, - And mark in every face I meet - Marks of weakness, marks of woe. - - In every cry of every Man - In every Infant's cry of fear, - In every voice, in every ban, - The mind-forg'd manacles I hear. - -

-

Within a given scope, all rhyme elements with the same value for their +

The label attribute is used to specify which parts of a rhyme scheme a given set + of rhyming words represent: I wander thro' each charter'd street,Near where the charter'd Thames does flow,And mark in every face I meetMarks of weakness, marks of woe.In every cry of every ManIn every Infant's cry of fear,In every voice, in every ban,The mind-forg'd manacles I hear.

+

Within a given scope, all rhyme elements with the same value for their label attribute are assumed to rhyme with each other: thus, in the above example, the two rhymes labelled a in the first stanza rhyme with each other, but not necessarily with those labelled a in the second stanza. The scope is defined by the nearest ancestor element for which the rhyme attribute has been supplied.

- -

The rhyme element can appear anywhere within a verse line, and not necessarily +

The rhyme element can appear anywhere within a verse line, and not necessarily around a single word. It can thus be used to mark quite complex internal rhyming schemes, - as in the following example: - The sunlight on the garden - Hardens and grows cold, - We cannot cage the minute - Within its nets of gold - When all is told - We cannot beg for pardon. - + as in the following example: The sunlight on the gardenHardens and grows cold,We cannot cage the minuteWithin its nets of goldWhen all is toldWe cannot beg for pardon.

-

This mechanism, although reasonably simple for simple cases, may not be appropriate for +

This mechanism, although reasonably simple for simple cases, may not be appropriate for more complex applications. In general, rhyme may be considered as a special form of correspondence, and hence encoded using the mechanisms defined for that purpose in section . Similar considerations apply to other metrical features such as alliteration or assonance.

-

To use the correspondence mechanisms to represent the complex rhyming pattern of the above - example, each rhyme element must be given a unique identifier, as follows: - The sunlight on the garden - Hardens and grows cold, - We cannot cage the minute - Within its nets of gold - When all is told - We cannot beg for pardon. - - Now that each rhyming word, or part-word, has been tagged and allocated an +

To use the correspondence mechanisms to represent the complex rhyming pattern of the above + example, each rhyme element must be given a unique identifier, as follows: The sunlight on the gardenHardens and grows cold,We cannot cage the minuteWithin its nets of goldWhen all is toldWe cannot beg for pardon. Now that each rhyming word, or part-word, has been tagged and allocated an arbitrary identifier, the general purpose link element may be used to indicate - which of the rhyme elements share the same rhyme, as follows: - - - - - + which of the rhyme elements share the same rhyme, as follows:

-

For further discussion of the link and linkGrp element, see section .

-

The rhyme and caesura phrase level elements are made available by the +

For further discussion of the link and linkGrp element, see section .

+

The rhyme and caesura phrase level elements are made available by the model.lPart class when the module defined by this chapter is included in a schema.

-
- -
- Metrical Notation Declaration -

When the module defined in this chapter is included in a schema, a specialized element is +

+
+ Metrical Notation Declaration +

When the module defined in this chapter is included in a schema, a specialized element is optionally available in the encodingDesc element of the TEI header to document the - metrical notation used in marking up a text. - - -

-

As with other components of the header, metrical notation may be specified either formally + metrical notation used in marking up a text.

+

As with other components of the header, metrical notation may be specified either formally or informally. In a formal specification, every symbol used in the metrical notation must be documented by a corresponding metSym element; in an informal one, only a brief prose description of the way in which the notation is used need be given. In either case, the optional pattern attribute may be used to supply a regular expression which a processor can use to validate expressions in the intended notation. The following - constraints apply: - if pattern is supplied, any notation used which does not conform to it - should be regarded as invalid - if any metSym is defined, then any notation using undefined symbols - should be regarded as invalid - if both pattern and symbol are defined, then every symbol appearing explicitly - within pattern must be defined - symbols which are not matched by pattern may be defined within a - metDecl element -

-

As a simple example, consider the case of the notation in + constraints apply: if pattern is supplied, any notation used which does not conform to it + should be regarded as invalidif any metSym is defined, then any notation using undefined symbols + should be regarded as invalidif both pattern and symbol are defined, then every symbol appearing explicitly + within pattern must be definedsymbols which are not matched by pattern may be defined within a + metDecl element

+

As a simple example, consider the case of the notation in which metrical prominence, metrical feet, and line boundaries are all to be encoded. Legal specifications in this notation may be written for any sequence of metrically prominent or @@ -763,30 +463,18 @@ $Id$ | for foot boundary and / for line boundary, then the following declaration achieves this objective: - - - metrical prominence - metrical non-prominence - foot boundary - metrical line boundary - - + metrical prominencemetrical non-prominencefoot boundarymetrical line boundary

-

The same notation might also be specified less formally, as follows: - - -

Metrically prominent syllables are marked '1' and other +

The same notation might also be specified less formally, as follows: +

Metrically prominent syllables are marked '1' and other syllables '0'. Foot divisions are marked by a vertical bar, - and line divisions with a solidus.

-

This notation may be applied to any metrical unit, of any + and line divisions with a solidus.

This notation may be applied to any metrical unit, of any size (including, for example, individual feet as well as - groups of lines).

- - + groups of lines).

Note that in this case, because the pattern attribute has not been supplied, no processor can validate met attribute values within the text which use this metrical notation.

-

For more complex cases, it will often be more convenient to +

For more complex cases, it will often be more convenient to define a notation incrementally. The terminal attribute should be used to indicate for a given symbol whether or not it may be re-defined in terms of other symbols used @@ -795,22 +483,10 @@ $Id$ most common types of foot. These symbols are themselves documented within the same notation, in terms of more primitive long and short syllables: - - - -oo - -o - o- - -- - ooo - oo- - short syllable - long syllable - - + -oo-oo---ooooo-short syllablelong syllable Note here the use of the global n attribute to supply an additional name for the symbols being documented.

- -

Where an encoder wishes to use more than one different +

Where an encoder wishes to use more than one different pattern for metrical notation, multiple metDecl elements may be included in the encodingDesc, each supplied with an xml:id. The decls @@ -821,47 +497,16 @@ $Id$ pattern. In the body of the document, there are two div elements, one declaring the English pattern and one the French: - - - - - stressed syllable - unstressed syllable - metrical line boundary - - - syllabe tonique - syllabe atone - pause métrique - - - - - -

- - - - -
-
- - - - -
- - + stressed syllableunstressed syllablemetrical line boundarysyllabe toniquesyllabe atonepause métrique

- - - - -
- -
- Encoding Procedures for Other Verse Features -

A number of procedures that may be of particular concern to encoders of verse texts are + + + + +

+
+ Encoding Procedures for Other Verse Features +

A number of procedures that may be of particular concern to encoders of verse texts are dealt with elsewhere in these guidelines. Some aspects of layout and physical appearance, especially important in the case of free verse, are dealt with in chapter . Some initial recommendations for the encoding of phonetic or prosodic transcripts, which may be helpful in the analysis of sound structures in poetry, are to be found in @@ -869,8 +514,7 @@ $Id$ (those proposed for the International Phonetic Alphabet suggest themselves) to mark positions of suprasegmentals such as primary and secondary stress, or other aspects of accentual structure.

- -

As already indicated, chapter contains much which will be found useful +

As already indicated, chapter contains much which will be found useful for the aligning of multiple levels of commentary and structure within verse analysis. Encoders of verse (as of other types of literary text) will frequently wish to attach identifying labels to portions of text that are not part of a system of hierarchical @@ -882,7 +526,7 @@ $Id$ means of encoding a wide variety of aspects of verse literature, including not only the metrical structures discussed above, but also such stylistic and rhetorical features as metaphor.

-

For other features it must for the time being be left to encoders to devise their own +

For other features it must for the time being be left to encoders to devise their own terminology. Elements such as metaphor tenor="..." vehicle="..." ... /metaphor might well suggest themselves; but given the problems of definition involved, and the great richness of modern metaphor theory, it is clear that any such @@ -893,29 +537,20 @@ $Id$ definitions on which they rest. Where no formal elements are currently proposed, such information may readily be given as simple prose description within the encodingDesc element defined in section .

-
- -
- Module for Verse -

The module described in this chapter makes available the +

+
+ Module for Verse +

The module described in this chapter makes available the following components: - - Verse - Verse structures - Poésie - 韻文結構 - Strutture poetiche - Estrutura dos versos - 韻文モジュール - + VerseVerse structuresPoésie韻文結構Strutture poeticheEstrutura dos versos韻文モジュール The selection and combination of modules to form a TEI schema is described in .

- - - - - - -
-
\ No newline at end of file + + + + + + +
+
diff --git a/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml b/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml index ba3c5ce0c0..518e3ea19e 100644 --- a/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml +++ b/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml @@ -1,17 +1,10 @@ - +
-Characters, Glyphs, and Writing Modes - - -

Chapter introduced the fundamental notions of + Characters, Glyphs, and Writing Modes + +

Chapter introduced the fundamental notions of language identification and character representation in an encoded TEI document. In this chapter we discuss some additional issues relating to the way that written language is represented in a TEI document. In @@ -27,11 +20,9 @@ section we discuss ways of documenting the writing mode used in a source text, that is, the directionality of the script, the orientation of individual characters, and related questions.

- - - -
Is Your Journey Really Necessary? -

Despite the availability of Unicode, text encoders still +

+ Is Your Journey Really Necessary? +

Despite the availability of Unicode, text encoders still sometimes find that the published repertoire of available characters is inadequate to their needs. This is particularly the case when dealing with ancient languages, for which encoding @@ -40,40 +31,33 @@ represent variant forms of a character or glyphs. The module defined by this chapter provides a mechanism to satisfy that need, while retaining compatibility with standards.

-

When encoders encounter some graphical unit in a document which is +

When encoders encounter some graphical unit in a document which is to be represented electronically, the first issue to be resolved should be Is this really a different character? To determine whether a particular graphical unit is a character or not, see .

-

If the unit is indeed determined to be a character, the next +

If the unit is indeed determined to be a character, the next question should be Has this character been encoded already? In order to determine whether a character has been encoded, encoders should follow the following steps: - -

Check the Unicode +

Check the Unicode web site at , in particular the page "Where is my Character?", and the associated character code charts. Alternatively, users can check the latest published version of The Unicode Standard (Unicode Consortium (2006)), though the web site is often more up to date than the printed version, and should be - checked for preference.

-

The pictures (glyphs) in the Unicode code + checked for preference.

The pictures (glyphs) in the Unicode code charts are only meant to be representative, not definitive. If a specific form of an already encoded character is required for a project, refer to the guidelines contained below under Annotating Characters. Remember that your encoded document may be rendered on a system which has different fonts from yours: if the specific form of a character is important to you, -then you should document it.

- Check the Proposed New Characters web page () to see whether - the character is in line for approval. - -Ask on the Unicode email list () to +then you should document it.

Check the Proposed New Characters web page () to see whether + the character is in line for approval.Ask on the Unicode email list () to see whether a proposal is pending, or to determine whether this character is considered eligible for addition -to the Unicode Standard. - -

-

Since there are now over 130,000 characters in Unicode, +to the Unicode Standard.

+

Since there are now over 130,000 characters in Unicode, chances are good that what you need is already there, but it might not be easy to find, since it might have a different name in Unicode. Editors working with East Asian writing systems should consult @@ -85,27 +69,25 @@ with those of the character you are looking for. For example, if your character is definitely a digit, but the properties of the best match you can find for it say that it is a letter, you may have a character not yet defined in Unicode.

-

In general, it is advisable to avoid Unicode characters generally +

In general, it is advisable to avoid Unicode characters generally described as presentation forms.Specifically, characters in the Unicode blocks Alphabetic Presentation Forms, Arabic Presentation Forms-A, Arabic Presentation Forms-B, Letterlike Symbols,and Number Forms. However, if the character you are looking for is being used in a notation (rather than as part of the orthography of a language) then it is quite acceptable to select characters from the Mathematical Operators block, provided that they have the appropriate properties (i.e. So: Symbol, Other; or Sm: Symbol, Math).

-

An encoded character may be precomposed or it may be formed +

An encoded character may be precomposed or it may be formed from base characters and combining diacritical marks. Either will suffice for a character to be "found" as an encoded character. If there are several possible Unicode characters to choose amongst, it is good practice to consult other colleagues and practitioners to see whether a consensus has emerged in favour of one or other of them.

-

If, however, no suitable form of your character seems to exist, the +

If, however, no suitable form of your character seems to exist, the next question will be: Does the graphical unit in question represent a variant form of a known character, or does it represent a completely unencoded character? If the character is determined to be missing from the Unicode Standard, it would be helpful to submit -the new character for inclusion (see ). For assistance +the new character for inclusion (see ). For assistance on writing or submitting a proposal, potential proposers can contact -the UC Berkeley Script Encoding Initiative ().

-

These guidelines will help you proceed once you have +the UC Berkeley Script Encoding Initiative ().

+

These guidelines will help you proceed once you have identified a given graphical unit as either a variant or an unencoded character. Determining this will require knowledge of the contents of the document that you have. The first case will @@ -115,13 +97,13 @@ target="http://linguistics.berkeley.edu/sei/"/>).

will be discussed below () while the problem of representing new characters will be dealt with in section .

-

While there is some overlap between these requirements, +

While there is some overlap between these requirements, distinct specialized markup constructs have been created for each of these cases. These constructs are presented in section below.

-
-
- -Markup Constructs for Representation of Characters and Glyphs -

An XML document can, in principle, contain any defined Unicode + Markup Constructs for Representation of Characters and Glyphs +

An XML document can, in principle, contain any defined Unicode character. The standard allows these characters to be represented either directly, using an appropriate encoding (UTF-8 by default), or indirectly by means of a numeric character reference (NCR), such as @@ -148,7 +130,7 @@ part of it) by adding a suitable encoding declaration. For example, if a document begins with the declaration <?xml encoding="iso-8859-1"?> any Unicode characters which are not in the ISO-8859-1 character set must be represented by NCRs.

-

The gaiji module defined by this +

The gaiji module defined by this chapter adds a further way of representing specific characters and glyphs in a document. (Gaiji is from Japanese 外字, meaning external characters.) This allows the encoder to distinguish @@ -156,20 +138,17 @@ in the ISO-8859-1 character set must be represented by NCRs.

new nonstandard characters or glyphs, and to represent Unicode characters not available in the document encoding by an alternative means.

-

The mechanism provided here consists functionally of two parts: - - an element g, which serves as a proxy for new - characters or glyphs - elements char and glyph, providing information about such characters or glyphs; these elements are stored in the - charDecl element in the header. - +

The mechanism provided here consists functionally of two parts: + an element g, which serves as a proxy for new + characters or glyphselements char and glyph, providing information about such characters or glyphs; these elements are stored in the + charDecl element in the header.

-

When the gaiji module is included in a schema, the +

When the gaiji module is included in a schema, the charDecl element is added to the model.encodingDescPart class, and the g element is added to the phrase class. These elements and their components are documented in the rest of this section.

-

The Unicode standard defines properties for all the characters it +

The Unicode standard defines properties for all the characters it defines in the Unicode Character Database , knowledge of which is usually built into text processing systems. If the character represented by the g element does not exist in Unicode at all, its properties are not available. If the character represented is @@ -178,21 +157,18 @@ character set recognized by a given text processing system, it may also be convenient to have access to its properties in the same way. The char element makes it possible to store properties for use by such applications in a standard way.

-

The list of attributes (properties) for characters is modelled on +

The list of attributes (properties) for characters is modelled on those in the Unicode Character Database, which distinguishes normative and informative character properties. The Unicode Consortium also maintains a separate set of character properties specific to East Asian characters in the Unihan database which TEI fully supports. Lastly, non-Unicode properties may also be supplied. Since the list of properties will vary with different versions of the Unicode Standard, there may not be an exact correspondence between them and the list of properties defined in these Guidelines.

- -

Usage examples for these elements are given below at and . The gaiji module + +

Usage examples for these elements are given below at and . The gaiji module itself is formally defined in section below. It declares the following additional elements: - - - - + The charDecl element is a member of the class model.encodingDescPart, and thus becomes available within encodingDesc when this module is included in a schema. The g element is the only member of the class @@ -201,15 +177,11 @@ an alternative to plain text in almost every element which contains plain text, thus permitting the g element also to appear at such places when this module is included in a schema.

-

The following elements may appear within a charDecl +

The following elements may appear within a charDecl element: - - - - - +

-

The char and glyph elements have similar contents +

The char and glyph elements have similar contents and are used in similar ways, but their functions are different. The char element is provided to define a character which is not available in the current document character set, for whatever reason, @@ -221,7 +193,7 @@ original document. This is necessary since Unicode code points refer not to a single, specific glyph shape of a character, but rather to a set of glyphs, any of which may be used to render the code point in question; in some cases they can differ considerably.

-

The glyph element is provided for cases where the encoder +

The glyph element is provided for cases where the encoder wants to specify a specific glyph (or family of glyphs) out of all possible glyphs. Unfortunately, due to the way Unicode has been defined, there are cases where several glyphs that logically belong @@ -230,24 +202,14 @@ defining East Asian characters. In such cases, glyph elements can also be used to express the view that these apparently distinct characters are to be regarded as instances of the same character (see further ).

-

The Unicode Standard recommends naming conventions which should be +

The Unicode Standard recommends naming conventions which should be followed strictly where the intention is to annotate an existing Unicode character, and which may also be used as a model when creating new names for characters or glyphsIt should be noted, however, that this naming convention cannot meaningfully be applied to East Asian characters; the typical Unicode descriptions for these characters take the form CJK Unified Ideograph U+4E00, where U+4E00 is simply the Unicode code point value of the character in question. In cases where no Unicode code point exists, there is little hope of finding a name that helps to identify the character. Names should therefore be constructed in a way meaningful to local practice, for example by using a reference number from a well-known character dictionary or a project-specific serial number.:

-

Within both char and glyph, the following elements are available: - - - - - - - - - - +

Within both char and glyph, the following elements are available: +

- -

Four of these elements (gloss, desc, +

Four of these elements (gloss, desc, figure, and note) are defined by other TEI modules, and their usage here is no different from their usage elsewhere. The figure element, however, is used here only to @@ -259,7 +221,7 @@ resolution, or in different formats, or may itself be repeated. As elsewhere, the mimeType attribute of graphic should be used to specify the format of the image.

-

The mapping element is similar to the standard TEI +

The mapping element is similar to the standard TEI equiv element. While the latter is used to express correspondence relationships between TEI concepts or elements and those in other systems or ontologies, the former is used to express @@ -274,31 +236,18 @@ characters. The type of association is indicated by the uppercase equivalences, lowercase for lowercase equivalences, standard for standardized forms, and simplified for simplified characters, etc., as in the -following example: - - - -a - - - +following example: a

-

The mapping element may also be used to represent a mapping of the +

The mapping element may also be used to represent a mapping of the character or (more likely) glyph under discussion onto a character from the private use area as in this example: - - - -Z -U+E304 - - - +ZU+E304

-

A more precise documentation of the properties of any character or +

A more precise documentation of the properties of any character or glyph may be supplied using one of the three property elements: localProp, unicodeProp, or unihanProp; these are described in the next section.

-
Character Properties -

The Unicode Standard documents ideal +

+ Character Properties +

The Unicode Standard documents ideal characters, defined by reference to a number of properties (or attribute-value pairs) which they are said to possess. For example, a lowercase letter is said to have the value @@ -312,17 +261,13 @@ currently assigned to certain properties. When making such modifications, great care should be taken not to override standard informative properties for characters which already exist in the Unicode Standard, as documented in Freytag (2006).

- -

The unicodeProp, unihanProp, and + +

The unicodeProp, unihanProp, and localProp elements allow a TEI encoder to record information about a character or glyph: - - - - - +

-

Where the information concerned relates to a property which has +

Where the information concerned relates to a property which has already been identified in the Unicode Standard, use of the appropriate Unicode property name with unicodeProp is strongly encouraged. The use of available Unihan property names with @@ -330,90 +275,27 @@ strongly encouraged. The use of available Unihan property names with property names according to Unicode conventions are incorporated into the TEI schemas. Where neither of these standards suffices use localProp.

- -

The three elements for recording Unicode or locally defined properties belong to the att.gaijiProp class. This class defines two required attributes for record key-value pairs for character properties: + +

The three elements for recording Unicode or locally defined properties belong to the att.gaijiProp class. This class defines two required attributes for record key-value pairs for character properties: - - - + For each property, the encoder must supply both a name and a value. In cases of boolean properties TEI requires an explict true or false value attribute: - - - +

-

For convenience, we list here some of the normative character +

For convenience, we list here some of the normative character properties and their values. For full information, refer to chapter 4 of The Unicode Standard, or the online documentation of the Unicode Character Database. - - The general +The general category (described in the Unicode Standard chapter 4 section 5) is an assignment to some major classes and subclasses of characters. Suggested values for this property are listed here: - -LuLetter, uppercase -LlLetter, lowercase -LtLetter, titlecase -Lm Letter, modifier -LoLetter, other -MnMark, nonspacing -McMark, spacing combining -MeMark, enclosing -NdNumber, decimal digit -NlNumber, letter -NoNumber, other -PcPunctuation, connector -PdPunctuation, dash -PsPunctuation, open -PePunctuation, close -PiPunctuation, initial quote -PfPunctuation, final quote -PoPunctuation, other -SmSymbol, math -ScSymbol, currency -SkSymbol, modifier -SoSymbol, other -ZsSeparator, space -ZlSeparator, line -ZpSeparator, paragraph -CcOther, control -CfOther, format -CsOther, surrogate -CoOther, private use -CnOther, not assigned -
- - -This property applies to all Unicode characters. It governs the +LuLetter, uppercaseLlLetter, lowercaseLtLetter, titlecaseLm Letter, modifierLoLetter, otherMnMark, nonspacingMcMark, spacing combiningMeMark, enclosingNdNumber, decimal digitNlNumber, letterNoNumber, otherPcPunctuation, connectorPdPunctuation, dashPsPunctuation, openPePunctuation, closePiPunctuation, initial quotePfPunctuation, final quotePoPunctuation, otherSmSymbol, mathScSymbol, currencySkSymbol, modifierSoSymbol, otherZsSeparator, spaceZlSeparator, lineZpSeparator, paragraphCcOther, controlCfOther, formatCsOther, surrogateCoOther, private useCnOther, not assigned
+ This property applies to all Unicode characters. It governs the application of the algorithm for bi-directional behaviour, as further specified in Unicode Annex 9, The Bidirectional Algorithm. The following 21 different values are currently defined for this property: - -LLeft-to-Right -RRight-to-Left -ALRight-to-Left Arabic -ENEuropean Number -ESEuropean Number Separator -ETEuropean Number Terminator -ANArabic Number -CSCommon Number Separator -NSMNonspacing Mark -BNBoundary Neutral -BParagraph Separator -SSegment Separator -WSWhitespace -ONOther Neutrals -LRELeft-to-Right Embedding -LROLeft-to-Right Override -RLERight-to-Left Embedding -RLORight-to-Left Override -PDFPop Directional Format -LRILeft-to-Right Isolate -RLIRight-to-Left Isolate -FSIFirst Strong Isolate -PDIPop Directional Isolate -
 - This +LLeft-to-RightRRight-to-LeftALRight-to-Left ArabicENEuropean NumberESEuropean Number SeparatorETEuropean Number TerminatorANArabic NumberCSCommon Number SeparatorNSMNonspacing MarkBNBoundary NeutralBParagraph SeparatorSSegment SeparatorWSWhitespaceONOther NeutralsLRELeft-to-Right EmbeddingLROLeft-to-Right OverrideRLERight-to-Left EmbeddingRLORight-to-Left OverridePDFPop Directional FormatLRILeft-to-Right IsolateRLIRight-to-Left IsolateFSIFirst Strong IsolatePDIPop Directional Isolate
This property exists for characters that are not used independently, but in combination with other characters, for example the strokes making up CJK (Chinese, Japanese, and Korean) characters. It @@ -421,76 +303,27 @@ defined for this property: determine how they interact typographically. The following values are defined in the Unicode Standard: (see Unicode Character Database: Canonical Combining Class Values); these were taken from version 12.1: - -0Spacing, split, enclosing, reordrant, and Tibetan subjoined -1Overlays and interior -7Nuktas -8Hiragana/Katakana voicing marks -9Viramas -10Start of fixed position classes -199End of fixed position classes -200Below left attached -202Below attached -204Below right attached -208Left attached (reordrant around single base character) -210Right attached -212Above left attached -214Above attached -216Above right attached -218Below left -220Below -222Below right -224Left (reordrant around single base character) -226Right -228Above left -230Above -232Above right -233Double below -234Double above -240Below (iota subscript) -
 - - This property is defined for characters, +0Spacing, split, enclosing, reordrant, and Tibetan subjoined 1Overlays and interior 7Nuktas 8Hiragana/Katakana voicing marks 9Viramas 10Start of fixed position classes 199End of fixed position classes 200Below left attached 202Below attached 204Below right attached 208Left attached (reordrant around single base character) 210Right attached 212Above left attached 214Above attached 216Above right attached 218Below left 220Below 222Below right 224Left (reordrant around single base character) 226Right 228Above left 230Above 232Above right 233Double below 234Double above 240Below (iota subscript)
This property is defined for characters, which may be decomposed, for example to a canonical form plus a typographic variation of some kind. For such characters the Unicode standard specifies both a decomposition type and a decomposition mapping (i.e. another Unicode character to which this one may be mapped in the way specified by the decomposition type). The following types of mapping are defined in the Unicode Standard: - -fontA font variant (e.g. a blackletter form) -noBreakA no-break version of a space or hyphen -initialAn initial presentation form (Arabic) -medialA medial presentation form (Arabic) -finalA final presentation form (Arabic) -isolatedAn isolated presentation form (Arabic) -circleAn encircled form -superA superscript form -subA subscript form -verticalA vertical layout presentation form -wideA wide (or zenkaku) compatibility character -narrowA narrow (or hankaku) compatibility character -smallA small variant form (CNS compatibility) -squareA CJK squared font variant -fractionA vulgar fraction form -compatOtherwise-unspecified compatibility character -
- - This property applies for +fontA font variant (e.g. a blackletter form)noBreakA no-break version of a space or hypheninitialAn initial presentation form (Arabic)medialA medial presentation form (Arabic)finalA final presentation form (Arabic)isolatedAn isolated presentation form (Arabic)circleAn encircled formsuperA superscript formsubA subscript formverticalA vertical layout presentation formwideA wide (or zenkaku) compatibility characternarrowA narrow (or hankaku) compatibility charactersmallA small variant form (CNS compatibility)squareA CJK squared font variantfractionA vulgar fraction formcompatOtherwise-unspecified compatibility character
+This property applies for any character which expresses any kind of numeric value. Its - value is the intended value in decimal notation. - The mirrored + value is the intended value in decimal notation.The mirrored character property is used to properly render characters such as U+0028, OPENING PARENTHESIS independent of the text direction: it has the value Y -(character is mirrored) or N (code is not mirrored). -

-

The Unicode Standard also defines a set of informative (but non-normative) properties for Unicode characters. If encoders wish to provide such properties, they should be included using the Unicode name. If a Unicode name exists for a given character this should always be used, however encoders may also supply locally defined names. To tag a Unicode name, use unicodeProp name="Name" (or unihanProp name="Name"). For names specified elsewhere or specified locally use localProp.

-
-
-
-Annotating Characters -

Annotation of a character becomes necessary when it is desired +(character is mirrored) or N (code is not mirrored).

+

The Unicode Standard also defines a set of informative (but non-normative) properties for Unicode characters. If encoders wish to provide such properties, they should be included using the Unicode name. If a Unicode name exists for a given character this should always be used, however encoders may also supply locally defined names. To tag a Unicode name, use unicodeProp name="Name" (or unihanProp name="Name"). For names specified elsewhere or specified locally use localProp.

+
+
+
+ Annotating Characters +

Annotation of a character becomes necessary when it is desired to distinguish it on the basis of certain aspects (typically, its graphical appearance) only. In a manuscript, for example, where distinctly different forms of the letter r can be recognized, it @@ -505,54 +338,28 @@ as described here provides a solution to this problem. It s encoding is an abstraction and an interpretation of the text at hand, which will not necessarily be useful in reproducing an exact facsimile of the appearance of a manuscript.

- -

Assuming that we wish to distinguish the variant glyphs from the +

Assuming that we wish to distinguish the variant glyphs from the standard representation for the character concerned, we will need to define distinct glyph elements, one for each of the forms of -the letter we wish to distinguish: - - - -

- - - - -
- - +the letter we wish to distinguish:
With these definitions in place, occurrences of these two special rs in the text can be represented using the element g: - -

Words in this +

Words in this manuscript are sometimes - written in a funny way.

-

+ written in a funny way.

+

As can be seen in this example, the glyph element pointed to from the g element will be interpreted as an annotation on the content of the element g. This mechanism can be used to represent common manuscript abbreviations or ligatures, as in the following examples: -

... Filthy riches...

- - - -
- - -

... per ardua

- - - -
- - - +

... Filthy riches...

 +

... per ardua

 (In fact the Unicode Standard does provide a character to represent the Fi ligature; the encoder may however prefer not to use it in order to simplify other text processing operations, such as indexing).

-

With this +

With this markup in place, it will be possible to write programs to analyze the distribution of the different letters r as well as produce more faithful renderings of the original. It @@ -562,7 +369,7 @@ the letter we wish to distinguish: r' > r' >]]> @@ -570,19 +377,20 @@ which would enable the same material to be encoded as follows: Wo&r1;ds in this manusc&r2;ipt are sometimes written in a funny way.

]]>

-

The same technique may be used to represent particular +

The same technique may be used to represent particular abbreviation marks as well as to represent other characters or glyphs. For example, if we believe that the r-with-one-funny-stroke is being used as an abbreviation for receipt, this might be represented as follows:&r1;]]>

-

Note however that this technique employs markup objects to + +

Note however that this technique employs markup objects to provide a link between a character in the document and some annotation on that character. Therefore, it cannot be used in places where such markup constructs are not allowed, notably in attribute values.

- -

Since the need to use these constructs to annotate or define + +

Since the need to use these constructs to annotate or define characters occurs frequently in Chinese, Korean, and Japanese documents, here are some issues that are specific to these documents. There are two slightly different versions of the @@ -594,14 +402,7 @@ normalizer (for search or indexing operations) could take advantage of this information. To achieve this, we simply define within a charDecl element a glyph that has two mapping elements, as shown here: - - - - 說 - 説 - - - +說説 The first of these mappings, of type Unicode, simply maps our glyph to the code point where Unicode defined it. The other one, of type standard, encodes the fact that @@ -609,34 +410,21 @@ in our view, this glyph is a variation of the standard character given in the content of the element. We could then use this glyph element's unique identifier u8aaa to refer to it from within a text as follows. - - 說 - + 說

-

A slightly different, but related problem occurs when we have +

A slightly different, but related problem occurs when we have multiple variants, none of which has been defined in Unicode. In this case, we need to define one as a new character using char, and the others as glyphs using glyph. - - - - - - - - - - - + The char defines a new character, while the glyph element then defines a variant glyph of this newly defined character. Additional properties should be specified in order to make these both identifiable.

- -
-Adding New Characters -

The creation of additional characters for use in text encoding +

+ Adding New Characters +

The creation of additional characters for use in text encoding is quite similar to the annotation of existing characters. The same element g is used to provide a link from the character instance in the text to a character definition provided @@ -647,7 +435,7 @@ the Private Use Area (PUA) of the Unicode Standard, which is an area set aside for the very purpose of privately adding new characters to a document. Recommendations on how to use such PUA characters are given in the following section.

-

In some circumstances, it may be desirable to provide a single +

In some circumstances, it may be desirable to provide a single precomposed form of a character that is encoded in Unicode only as a sequence of code points. For example, in Medieval Nordic material, a character looking like a lowercase letter Y with a @@ -668,12 +456,7 @@ Therefore, the recommended representation is to use the g element defined by the module defined in this chapter: . This makes it possible for the encoder to provide useful documentation for the particular character or glyph so referenced: - - - - &#x0079;&#x0307;&#x0301; - U+E0A4 This +&#x0079;&#x0307;&#x0301;U+E0A4 This definition specifies the mapping between this composed character and the individual Unicode-defined code points which make it up. It also supplies a single locally-defined property @@ -681,43 +464,31 @@ provide useful documentation for the particular character or glyph so referenced purpose of which is to supply a recommended character entity name for the character.

-

The composition rules for ideographic characters typically require more complex rules than the &ydotacute; above. For these cases Unicode provides dedicated symbols to capture the composition in Ideographic Description Sequences (IDS). Encoders are strongly encouraged to provide IDS for each variant ideograph in the header component of the gaiji module to faciliated greater human and machine readability of rare or unencoded characters, as in the following example: - - - - ⿻人為 - 偽 - - +

The composition rules for ideographic characters typically require more complex rules than the &ydotacute; above. For these cases Unicode provides dedicated symbols to capture the composition in Ideographic Description Sequences (IDS). Encoders are strongly encouraged to provide IDS for each variant ideograph in the header component of the gaiji module to faciliated greater human and machine readability of rare or unencoded characters, as in the following example: +⿻人為偽 The composition rules and further examples appear in Chapter 18.2: Ideographic Description Characters of the Unicode Standard. Editors should be aware that different sequences can accurately describe the same character. In the example, the character "人" (U+4EBA) could have been substituted with "亻" (U+4EBB). Local preferences about how sequences are constructed should be documented in the encodingDesc of the corresponding TEI header (see ). Additionally, a number of online services, such as CHISE, offer querying and retrieving characters via IDS, which facilitates a greater degree of stability across different applications.

-

Under certain circumstances, Chinese Han characters can be written +

Under certain circumstances, Chinese Han characters can be written within a circle. Rather than considering this as simply an aspect of the rendering, an encoder may wish to treat such circled characters as entirely distinct derived characters. For a given character (say that represented by the numeric-character reference &#x4EBA;) the circled variant might conveniently be represented as - , which references a +, which references a definition such as the following: - - - - - + &#x4EBA; - - + &#xE000; - -

-

In this example, the circled ideograph +

+

In this example, the circled ideograph character has been defined with two mappings, and with two properties. The two properties are the Unicode-defined character-decomposition which specifies that this is a circled character, using the appropriate terminology (see above) and a locally defined property known as daikanwa. The two mappings indicate firstly that the standard form of this character is the character &#x4EBA;, and secondly that the character used to represent this character locally is the PUA character &#xE000;. For convenience of local processing this PUA character may in fact appear as content of the g element. In general, however, the g element will be empty.

-
-
-How to Use Code Points from the Private Use Area -

The developers of the Unicode Standard have set aside an +

+
+ How to Use Code Points from the Private Use Area +

The developers of the Unicode Standard have set aside an area of the codespace for the private use of software vendors, user groups, or individuals. As of this writing (Unicode 12.1), there are around 137,000 code points available in this area, which @@ -732,7 +503,7 @@ entity references should be used. This will make it easier for receiving parties to find out what PUA characters are used in a document and where possible code point clashes with local use on the receiving site might occur.-->

-

In the two previous examples, we mentioned that the variant +

In the two previous examples, we mentioned that the variant characters concerned might well be assigned specific code points from the PUA. This might, for example, facilitate the use of a particular font which displays the desired character at this code point in the @@ -750,13 +521,13 @@ local processing environment at the receiving site will be necessary to handle such characters, during which variant letters can be converted to hitherto unused code points on the basis of the information provided in the char element.

-

This mechanism is rather weak in cases where DOM trees or +

This mechanism is rather weak in cases where DOM trees or parsed XML fragments are exchanged, which may increasingly be the case. The best an application can do here is to treat any occurrence of a PUA character only in the context of the local document and use the properties provided through the char element as a handle to the character in other contexts.

-

In the fullness of time, a character may become standardized, and +

In the fullness of time, a character may become standardized, and thus assigned a specific code point outside the PUA. Documents which have been encoded using the mechanism must at the least ensure that this changed code point is recorded within the relevant char @@ -764,14 +535,11 @@ element; it will however normally be simpler to remove the char element and replace all occurrences of g elements which reference it by occurrences of the newly coded character.

-
- - -
- +
+
+ Writing Modes - -

The scripts used for writing human languages vary not only in the +

The scripts used for writing human languages vary not only in the glyphs they use, but also in the way (or ways) that those glyphs are arranged on the writing surface. For the majority of modern languages, writing is arranged as a series of lines which are to be read from top @@ -795,8 +563,7 @@ scripts written with lines running left to right, each line being read top to bottom (Ancient Uighur, classical Mongolian and Manchu), or scripts such as Ogham where the writing direction may start from the bottom left and run around the edge of an inscribed object.

- -

When different languages are combined, it is possible that +

When different languages are combined, it is possible that different writing modes will be needed: for example, in Hebrew text, running right to left, sequences of Latin digits still run left to right. When different writing modes are available for the same @@ -816,8 +583,7 @@ complex table, where column or row labels may be written vertically or diagonally to make the most effective use of available space, just as it may vary in response to the size and shape of the carrier in the case of a monumental inscription.

- -

For many, perhaps most, TEI documents there may be no need to +

For many, perhaps most, TEI documents there may be no need to encode the writing mode explicitly, even in so-called "mixed mode" texts containing passages written in languages which use different writing modes. Modern printed texts in most European languages, for @@ -829,22 +595,17 @@ are explicitly stated in the markup using the attribute default writing mode. Even where this attribute is not used, passages in different scripts will use different Unicode characters, and will thus imply a particular default writing mode.

- -

Consider the case of an English text containing a few Arabic words: +

Consider the case of an English text containing a few Arabic words: The Arabic term قلم رصاص means "pencil". A correct TEI encoding might read as follows: - - The Arabic term - قلم رصاص means "pencil". - +The Arabic term + قلم رصاص means "pencil". We might assume that it is the presence of the xml:lang attribute with value ar that causes processing software to display the Arabic from right to left, but in fact, this is not the case. The order in which the Arabic characters appear when rendered would be the same, even if the markup were not present: - - The Arabic term قلم رصاص means "pencil". - +The Arabic term قلم رصاص means "pencil". This is because Arabic glyphs are always displayed right to left, even when they appear within a left-to-right English sentence. Like most other codepoints in the Unicode standard, they have a specific @@ -855,8 +616,7 @@ Hebrew א (alef) is strongly right-to-left. Of course, some glyphs (common punctuation marks such as the period or comma for example) have weak or neutral settings because they may appear in several contexts.

- -

The Unicode Bidirectional Algorithm (Unicode +

The Unicode Bidirectional Algorithm (Unicode Consortium, 2017) defines a number of rules enabling software to render sequences of characters which have @@ -874,8 +634,7 @@ irrespective of the order in which the characters making up a sequence should be displayed or rendered. For example, in a RTL language such as Hebrew, the first character in a file will be that which is displayed at the rightmost end of the first line of text.

- -

An encoder wishing to document or to control the order in which +

An encoder wishing to document or to control the order in which sequences of characters in a TEI document are displayed will usually do so by segmenting the text into sequences presented in the desired order and specifying an appropriate language code for each. In @@ -900,8 +659,7 @@ and text-orientation (mixed, upright, as well as properties affecting the behaviour of the unicode-bidi (bidirectional) algorithm. We discuss and exemplify how these properties may be used below.

- -

The global TEI style attribute applies to the element on +

The global TEI style attribute applies to the element on which it is specified (and in most cases, its descendants). Rather than specify it on every element, it will often be more efficient to express sets of commonly-used styling rules as rendition @@ -910,18 +668,16 @@ global rendition attribute, as further discussed in - Examples of Different Writing Modes -

The CSS recommendations provides several properties which can be used to encode aspects of the "writing mode". The most useful of these is the property "writing-mode" which may be used to specify a reading-order for both characters within a single line and lines within a single block of text. The property "text-orientation" may also used to indicate the orientation of individual characters with respect to the line, and the property "direction" to determine the reading order of characters within a line only. We give some examples of each below.

-
- Vertical Writing Modes -

The writing-mode property is particularly useful for languages +

+
+ Examples of Different Writing Modes +

The CSS recommendations provides several properties which can be used to encode aspects of the "writing mode". The most useful of these is the property "writing-mode" which may be used to specify a reading-order for both characters within a single line and lines within a single block of text. The property "text-orientation" may also used to indicate the orientation of individual characters with respect to the line, and the property "direction" to determine the reading order of characters within a line only. We give some examples of each below.

+
+ Vertical Writing Modes +

The writing-mode property is particularly useful for languages which can be written in different writing modes, such as Chinese and Japanese. Its possible values include horizontal-tb, vertical-rl and vertical-lr. Each value has @@ -932,36 +688,38 @@ of a document will probably include many other properties of course.

which lines and paragraphs are arranged from top to bottom on a page), from right to left (as in the case of Japanese written vertically), or left-to-right (as in the case of Mongolian).

-

The following example shows three versions of the same poem: first in +

The following example shows three versions of the same poem: first in Japanese, written top to bottom; next in romaji (Japanese in Latin script); and finally in an English translation.

-

-

- - Taken from p.42 of Haiku: Japanese Art and Poetry. Judith Patt, Michiko Warkentyne (calligraphy) and Barry Till. 2010. -
-

-

-

We might encode this as follows:

-
- - 古池や - 蛙 - 飛び込む - 水の音 - - - furu ike ya - kawazu tobikomu - mizu no oto - - - Old pond, - and a frog dives in— - "Splash"! - -
 -

For the sake of simplicity, we have not attempted to capture in +

+

+ + Taken from p.42 of Haiku: Japanese Art and Poetry. Judith Patt, Michiko Warkentyne (calligraphy) and Barry Till. 2010. +
+

+

+

We might encode this as follows:

+ +
+ + 古池や + 蛙 + 飛び込む + 水の音 + + + furu ike ya + kawazu tobikomu + mizu no oto + + + Old pond, + and a frog dives in— + "Splash"! + +
+ +

For the sake of simplicity, we have not attempted to capture in this encoding such aspects as the indenting of lines in the first Japanese version, or the central alignment of the other two versions, nor any other renditional features such as font weight or @@ -973,11 +731,10 @@ of a document will probably include many other properties of course.

script. Its style attribute specifies a horizontal writing mode; this may seem superfluous, but vertically-written romaji is not unknown.

-
-
- Vertical Text with Embedded Horizontal Text - -

When Japanese is written vertically, the glyph orientation +

+
+ Vertical Text with Embedded Horizontal Text +

When Japanese is written vertically, the glyph orientation remains the same as when it is written horizontally. In other words, glyphs are not rotated (although as noted above some different glyphs may be used for some characters, in particular for @@ -990,99 +747,96 @@ of a document will probably include many other properties of course.

text runs, or are they rotated? Consider this fragment from a Japanese article about the Indonesian language, which takes the form of a glossary list:

-

-

- -Detail from p.62 of インドネシア語". 崎山理. 1985. 外国語との対照 II. 講座日本語学 11. -
-

- -

The text-orientation property allows us to indicate whether or +

+

+ + Detail from p.62 of インドネシア語". 崎山理. 1985. 外国語との対照 II. 講座日本語学 11. +
+

+

The text-orientation property allows us to indicate whether or not glyphs are rotated. In the following example, we have indicated that the list uses a vertical-rl writing mode, but that the orientation of individual glyphs may vary:

- - - - 「近い、ほとんど」 - - 「新しい、ばかい」 - - -

The rule text-orientation: mixed specifies that + + + + 「近い、ほとんど」 + + 「新しい、ばかい」 + + + +

The rule text-orientation: mixed specifies that characters from horizontal-only scripts are set sideways, i.e. 90° clockwise from their standard orientation in horizontal text. Characters from vertical scripts are set with their intrinsic - orientation (fantasai + orientation (fantasai 2014). Since the default value for text-orientation is mixed, this rule is not strictly required. However, if the Indonesian glyphs (which are roman characters) had been set vertically, like this:

-

-

- - Fragment of previous image with Indonesian glyphs upright. -
-

-

then an encoding like the following could be used to make this explicit:

- - - - 「近い、ほとんど」 - - 「新しい、ばかい」 - - - -

The rule text-orientation: upright specifies that +

+

+ + Fragment of previous image with Indonesian glyphs upright. +
+

+

then an encoding like the following could be used to make this explicit:

+ + + + 「近い、ほとんど」 + + 「新しい、ばかい」 + + + +

The rule text-orientation: upright specifies that characters from horizontal-only scripts are rendered upright, i.e. in their standard horizontal orientation. Characters from vertical scripts are set with their intrinsic orientation and - shaped normally (fantasai + shaped normally (fantasai 2014).

-
-
- Vertical Orientation in Horizontal Scripts -

It is not unusual to see text from horizontal languages +

+
+ Vertical Orientation in Horizontal Scripts +

It is not unusual to see text from horizontal languages written vertically even where no vertically-written script is involved. This example is a fragment from a table of information about agricultural development on Vancouver Island, written in 1855:

-

-

- - Enclosure with Despatch to London 10048, CO +

+

+ + Enclosure with Despatch to London 10048, CO 305/6, p. 131v from -
-

-

Four of the subheading cells in this fragment contain English text written vertically, +

+

+

Four of the subheading cells in this fragment contain English text written vertically, bottom-to-top, to conserve space on the page. To describe this sort of phenomenon, we can use the text-orientation property again:

- -

text-orientation: mixed | upright | sideways-right | sideways-left | sideways | use-glyph-orientation

- -

For full details on this property, we refer the reader to the CSS Writing Modes specification. +

+ text-orientation: mixed | upright | sideways-right | sideways-left | sideways | use-glyph-orientation +

+

For full details on this property, we refer the reader to the CSS Writing Modes specification. For the present example, we will make use only of the sideways-left value, which causes text to be set as if in a horizontal layout, but rotated 90° counter-clockwise. We might encode the third of the four cells containing vertical text like this:

- - - Cash Value + + Cash Value of Farms - -

The writing-mode property captures the fact that the script is written vertically, and + +

The writing-mode property captures the fact that the script is written vertically, and its lines are to be read from left to right (so the line containing of is to the right of that containing Cash value), while the text-orientation value encodes the orientation (rotated 90° counter-clockwise). We might also add text-align: center to the style, to express the fact that the text is centrally-aligned.

-
-
- Bottom-to-top Writing -

Of the rather small number of scripts which appear to be written +

+
+ Bottom-to-top Writing +

Of the rather small number of scripts which appear to be written bottom-to-top, perhaps the best-known is Ogham, an alphabet used mainly to write Archaic Irish. Ogham is typically found inscribed along the edge of a standing stone, starting at its base. The CSS Writing @@ -1098,19 +852,21 @@ of a document will probably include many other properties of course.

(such as Ogham running around the edge of a stone), a meticulous encoder might resort to the use of SVG to describe the path, rather than treating the phenomenon as a writing mode.

-
-
- Mixed Horizontal Directionality - -

Returning to our previous simple example

- The Arabic term قلم رصاص means "pencil". -

we could use the direction property to make directionality explicit:

-

direction: ltr | rtl

- - The Arabic term +
+
+ Mixed Horizontal Directionality + +

Returning to our previous simple example

+ The Arabic term قلم رصاص means "pencil". +

we could use the direction property to make directionality explicit:

+

+ direction: ltr | rtl +

+ + The Arabic term قلم رصاص means "pencil". - -

The use of the direction property to record the observed directionality + +

The use of the direction property to record the observed directionality of the text is unambiguous, even though it is (as we noted above) superfluous. The use of the unicode-bidi property here may require some explanation. By default this property has the value normal, the effect of which in this @@ -1120,8 +876,7 @@ of a document will probably include many other properties of course.

value is normal, because the element does not open an additional level of embedding with respect to the bidirectional algorithm.

- -

Mixed horizontal directionality is very common in languages such as Arabic +

Mixed horizontal directionality is very common in languages such as Arabic and Hebrew, particularly when numbers (which are always given LTR) or phrases from LTR languages are embedded. It is not impossible, though quite unusual, for ambiguities @@ -1131,16 +886,13 @@ not correspond to the natural reading order. A more detailed discussion of this issue from an HTML perspective is provided by a W3C Internationalization Working Group report Inline markup and bidirectional text in HTML.

- - - - - -
-
- + + +
+
+ Summary -

For most texts, information about text directionality need not be explicitly +

For most texts, information about text directionality need not be explicitly encoded in a TEI text, either because it follows unambiguously from xml:lang values, or because it can be expected to be handled unequivocally by the Unicode Bidi Algorithm. Where it is considered important @@ -1150,12 +902,12 @@ not correspond to the natural reading order. A more detailed attribute). Most phenomena can be well described in this way; of those which cannot, other approaches based on the CSS Transforms module are presented in the next section.

-
-
-
- +
+
+
+ Text Rotation -

In what follows, we examine a range of textual phenomena which +

In what follows, we examine a range of textual phenomena which in some ways appear very similar to those examined above, and even overlap with them. We can categorize these as text transformation features, and suggest some strategies for encoding them based on @@ -1164,14 +916,13 @@ not correspond to the natural reading order. A more detailed functions which can be used to rotate, skew, translate and otherwise transform textual and graphical objects. We can borrow this vocabulary in order to describe textual phenomena in a precise manner.

- -

We begin with a simple example of a rotational transform:

-

-

- -
-

-

Here a block of text has been rotated around its z-axis. This is clearly +

We begin with a simple example of a rotational transform:

+

+

+ +
+

+

Here a block of text has been rotated around its z-axis. This is clearly not a writing mode; the writing mode for this text is horizontal, left to right. Furthermore, even if we wished to treat this as a writing mode, we could not do so, because there is no way to use @@ -1182,13 +933,12 @@ not correspond to the natural reading order. A more detailed transform-origin. (Both of these properties have quite complex value sets, and we will not look at all of them here. See the specification for full details.)

- -

The transform property takes as its value one or more of the transform functions, +

The transform property takes as its value one or more of the transform functions, one of which is the function rotateZ():

- - TEI-C.ORG - -

Any rotation must take place clockwise around an axis positioned relative + + TEI-C.ORG + +

Any rotation must take place clockwise around an axis positioned relative to the element being rotated, and the transform-origin property can be used to specify the pivot point. By default, the value of transform-origin is 50% 50%, the point at the centre of the element, but these @@ -1196,41 +946,40 @@ not correspond to the natural reading order. A more detailed (The TEI zone element also bears an attribute rotate which can specify rotation in degrees around the z-axis, but it is not available for any other element.)

- -

A block of text may also be rotated about either of its other axes. For example, +

A block of text may also be rotated about either of its other axes. For example, this shows rotation around the Y (vertical) axis:

-

-

- -
-

- TEI-C.ORG - -

These are obviously trivial examples, but similar features do appear in historical texts. +

+

+ +
+

+ + TEI-C.ORG + +

These are obviously trivial examples, but similar features do appear in historical texts. George Herbert's The Temple includes two stanzas headed Easter Wings which are both normally printed in a rotated form so that they represent a pair of wings:

-

-

- - Page 35 of George Herbert's The Temple +

+

+ + Page 35 of George Herbert's The Temple (1633), from a copy in the Folger Library. -
-

- -

This could be encoded thus:

- - - My tender age in ſorrow did beginne: - And ſtill with ſickneſſes and ſhame - - -

We might also argue that this is in fact a vertical writing +

+

+

This could be encoded thus:

+ + + My tender age in ſorrow did beginne: + And ſtill with ſickneſſes and ſhame + + + +

We might also argue that this is in fact a vertical writing mode by supplying writing-mode: vertical-rl; text-orientation: sideways-right as the value for the style attribute in the preceding example.

- -

Rotation is also useful as a method of handling a true writing +

Rotation is also useful as a method of handling a true writing mode which is not covered by the CSS Writing Modes: boustrophedon. This is a writing mode common in inscriptions in Latin, Greek and other languages, in which @@ -1240,31 +989,28 @@ not correspond to the natural reading order. A more detailed lines in boustrophedon have another unexpected feature: their glyphs are reversed, so that these lines appear as mirror writing, as in the following ancient Greek inscription: -

- -Leaden plaque bearing an inquiry by Hermon from the oracular -precinct at Dodona. (L.H. Jeffery Archive) -
+
Leaden plaque bearing an inquiry by Hermon from the oracular +precinct at Dodona. (L.H. Jeffery Archive)

-

This might be transcribed as follows (ignoring word boundaries for the moment):

- - ΗΕΡΜΟΝΤΙΝA +

This might be transcribed as follows (ignoring word boundaries for the moment):

+ + ΗΕΡΜΟΝΤΙΝA ΚΑΘΕΟΝΠΟΤΘΕΜ ΕΝΟΣΥΕΝΕΑϜ ΟΙΥΕΝΟΙΤΙΕΚΚ ΡΕΤΑΙΑΣΟΝΑ ΣΙΜΟΣΟΤΤΑΙΕ ΑΣΣΑΙ - -

The 180-degree rotation around the Y (vertical) axis here + + +

The 180-degree rotation around the Y (vertical) axis here describes what is happening in the RTL line in boustrophedon; the order of glyphs is reversed, and so is their individual orientation (in fact, we see them from the back, as it were). seg elements have been used here because these are clearly not lines in the sense of poetic lines; the text is continuous prose, and linebreaks are incidental.

- -

There are obviously some unsatisfactory aspects of this manner of encoding +

There are obviously some unsatisfactory aspects of this manner of encoding boustrophedon. In the inscription above, some words run across linebreaks, so if we wished to tag both words and the right-to-left phenomena, one hierarchy would have to be privileged over the other. By using a transform @@ -1273,12 +1019,10 @@ precinct at Dodona. (L.H. Jeffery Archive) the CSS Writing Modes specification does not provide support for boustrophedon, because it is a rather obscure historical phenomenon; using a rotational transform is one practical alternative.

- -
-
- Caveat - -

As with other parts of the CSS specification, the intended +

+
+ Caveat +

As with other parts of the CSS specification, the intended effect of CSS Transforms properties and values is defined with reference to a specific Visual formatting model; the language is designed to describe how an HTML @@ -1299,36 +1043,26 @@ precinct at Dodona. (L.H. Jeffery Archive) resolve all ambiguities with regard to size, positioning, block status, etc. before any element undergoes a transform operation.

-
- - -
Formal Definition -

The gaiji module described in this chapter makes available the following +

+
+ Formal Definition +

The gaiji module described in this chapter makes available the following components: - - Character and Glyph Documentation - Character and glyph documentation - Représentation des caractères et des glyphes non standard - 文字與字體說明 - Documentazione di caratteri non standard e glifi - Documentação dos carateres - 外字モジュール - +Character and Glyph DocumentationCharacter and glyph documentationReprésentation des caractères et des glyphes non standard文字與字體說明Documentazione di caratteri non standard e glifiDocumentação dos carateres外字モジュール The selection and combination of modules to form a TEI schema is described in .

- - - - - - - - - - - - -
+ + + + + + + + + + + +
diff --git a/P5/Source/Specs/TEI.xml b/P5/Source/Specs/TEI.xml index a0fe94201b..bb59410921 100644 --- a/P5/Source/Specs/TEI.xml +++ b/P5/Source/Specs/TEI.xml @@ -1,11 +1,5 @@ - + TEI document @@ -53,7 +47,7 @@ $Id$ - + @@ -79,7 +73,9 @@ $Id$ gibt die Versionsnummer der TEI-Richtlinien an, gegen die dieses Dokument validiert wird. especifica el número de versión de las Directrices TEI frente a las cuales este documento es válido. versione dello schema TEI - + + +

Major editions of the Guidelines have long been informally referred to by a name made up of the letter P (for Proposal) followed by a digit. The current release is one of the many @@ -88,7 +84,9 @@ $Id$ of a more precise association provided by the source attribute on the associated schemaSpec.

 -

Durante mucho tiempo, se ha hecho referencia informalmente a las principales ediciones de las Directrices con un nombre compuesto por la letra P (de Propuesta) seguida de un dígito. El lanzamiento actual es uno de los muchos lanzamientos de la quinta edición principal de las Directrices, conocida como P5. Este atributo puede utilizarse para asociar un documento TEI con una publicación específica de las Directrices P5, en ausencia de una asociación más precisa proporcionada por el atributo fuente en el schemaSpec asociado.

 + +

Durante mucho tiempo, se ha hecho referencia informalmente a las principales ediciones de las Directrices con un nombre compuesto por la letra P (de Propuesta) seguida de un dígito. El lanzamiento actual es uno de los muchos lanzamientos de la quinta edición principal de las Directrices, conocida como P5. Este atributo puede utilizarse para asociar un documento TEI con una publicación específica de las Directrices P5, en ausencia de una asociación más precisa proporcionada por el atributo fuente en el schemaSpec asociado.

+

Hauptausgaben der TEI-Richtlinien werden seit langem informell mit einem Namen bezeichnet, der sich aus dem Buchstaben P (für proposal) und einer Ziffer zusammensetzt. Die aktuelle Ausgabe ist eine der vielen Ausgaben @@ -151,7 +149,6 @@ $Id$ - @@ -206,7 +203,9 @@ $Id$ it, for example: TEI version="4.4.0" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0".

 -

El elemento es obligatorio. Normalmente se especifica el espacio de nombres (namespace) de TEI en su interior http://www.tei-c.org/ns/1.0, utilizando el atributo xmlns

 + +

El elemento es obligatorio. Normalmente se especifica el espacio de nombres (namespace) de TEI en su interior http://www.tei-c.org/ns/1.0, utilizando el atributo xmlns

+

Cet élément est obligatoire.

 diff --git a/P5/Source/Specs/ab.xml b/P5/Source/Specs/ab.xml index 16bb2a91be..84206d4fe4 100644 --- a/P5/Source/Specs/ab.xml +++ b/P5/Source/Specs/ab.xml @@ -1,11 +1,5 @@ - + anonymous block @@ -57,7 +51,9 @@

The ab element may be used at the encoder's discretion to mark any component-level elements in a text for which no other more specific appropriate markup is defined. Unlike paragraphs, ab may nest and may use the type and subtype attributes.

 -

El elemento ab se puede utilizar a discreción del codificador para marcar cualquier elemento a nivel de componente en un texto para el que no se haya definido ningún otro marcado apropiado más específico.

 + +

El elemento ab se puede utilizar a discreción del codificador para marcar cualquier elemento a nivel de componente en un texto para el que no se haya definido ningún otro marcado apropiado más específico.

+

L'élément ab peut être utilisé à la discrétion de l'encodeur pour marquer dans un texte tout élément de niveau composant pour lequel aucune méthode appropriée de balisage plus spécifique n'est définie.

 @@ -67,4 +63,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/abbr.xml b/P5/Source/Specs/abbr.xml index 439640b430..52344077be 100644 --- a/P5/Source/Specs/abbr.xml +++ b/P5/Source/Specs/abbr.xml @@ -1,11 +1,5 @@ - + abbreviation @@ -14,7 +8,7 @@ abréviation abreviatura abbreviazione - Abkürzung + Abkürzung 省略形 contains an abbreviation of any sort. 어떤 종류의 약어를 포함한다. @@ -49,7 +43,9 @@ pemette al codificatore di classificare l'abbreviazione secondo una tipologia funzionale. erlaubt es, die Abkürzung nach einer geeigneten Typologie zu klassifizieren. - + + + suspension @@ -65,7 +61,7 @@ lettre du mot ou de l'expression et omet le reste. l'abbreviazione consiste delle prime lettere di una parola o sintagma, omettendo il restante. - die Abkürzung gibt nur den Anfang des Wortes oder der Phrase, der Rest wird weggelassen, z. B. H(ansestadt) H(amburg), u(nd) s(o) w(eiter). + die Abkürzung gibt nur den Anfang des Wortes oder der Phrase, der Rest wird weggelassen, z. B. H(ansestadt) H(amburg), u(nd) s(o) w(eiter). contraction @@ -93,7 +89,7 @@ spécial ou une marque. l'abbreviazione consiste di un simbolo o segno speciale. - die Abkürzung verwendet ein spezielles Zeichen für die ausgelassenen Buchstaben. + die Abkürzung verwendet ein spezielles Zeichen für die ausgelassenen Buchstaben. superscription @@ -123,7 +119,7 @@ des mots d'une expression. l'abbreviazione consiste delle lettere iniziali delle una parola di una frase. - die Abkürzung besteht aus den Anfangsbuchstaben mehrer Wörter. + die Abkürzung besteht aus den Anfangsbuchstaben mehrer Wörter. title @@ -138,7 +134,7 @@ sociale (Dr., Mme, M., …) labbreviazione si riferisce al titolo (Sig., Sig.ra ecc.) - eine Abkürzung für eine Anrede oder einen akademischen Titel (Dr., Hr., Fr., ...) + eine Abkürzung für eine Anrede oder einen akademischen Titel (Dr., Hr., Fr., ...) organization @@ -153,7 +149,7 @@ organisme. l'abbreviazione si riferisce al nome di un organizzazione. - eine Abkürzung für den Namen einer Organisation. + eine Abkürzung für den Namen einer Organisation. geographic @@ -167,7 +163,7 @@ géographique. l'abbreviazione si riferisce ad un toponimo - die Abkürzung steht für einen geografischen Namen. + die Abkürzung steht für einen geografischen Namen. @@ -199,7 +195,7 @@ いては、以下を参照のこと。

-

+

Das type-Attribute kann für die Klassifikation von Abkürzungen am Ort ihres Auftretens verwendet werden, was für einige Abkürzungen hilfreich sein kann, obwohl üblicherweise dieselbe Abkürzung in all ihren Vorkommen denselben Typ aufweist. Die Beispielswerte verdeutlichen, dass Abkürzungen auf verschiedene Arten typisiert werden können: nach der @@ -260,7 +256,7 @@ documented in the editorialDecl, either with a normalization element or a p.

 - +

Werden Abkürzungen stillschweigend aufgelöst, sollte diese Vorgehensweise im TEI-Header über das editorialDecl-Element dokumentiert werden, entweder in einem normalization- oder einem p-Element.

@@ -278,4 +274,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/abstract.xml b/P5/Source/Specs/abstract.xml index 7a1165a182..954e41230f 100644 --- a/P5/Source/Specs/abstract.xml +++ b/P5/Source/Specs/abstract.xml @@ -1,11 +1,5 @@ - + contains a summary or formal @@ -48,9 +42,13 @@ $Id$ should be encoded as a div within the front, as it should for a born-digital document.

-

Este elemento debe utilizarse solo en casos en los que el abstract no se encuentra disponible en la fuente original. Cualquier abstract presente en el documento fuente debe ser codificado como un div dentro del front, como corresponde en los casos de documentos de origen digital.

 -

この要素は、元資料で要約が利用できない場合にのみ使用されます。 元文書に既に存在する任意の要約は、ボーンデジタル文書の場合と同じように、front内のdivとして符号化する必要があります。

 + +

Este elemento debe utilizarse solo en casos en los que el abstract no se encuentra disponible en la fuente original. Cualquier abstract presente en el documento fuente debe ser codificado como un div dentro del front, como corresponde en los casos de documentos de origen digital.

+ + +

この要素は、元資料で要約が利用できない場合にのみ使用されます。 元文書に既に存在する任意の要約は、ボーンデジタル文書の場合と同じように、front内のdivとして符号化する必要があります。

+ - \ No newline at end of file + diff --git a/P5/Source/Specs/accMat.xml b/P5/Source/Specs/accMat.xml index ec4f558128..294857a5ef 100644 --- a/P5/Source/Specs/accMat.xml +++ b/P5/Source/Specs/accMat.xml @@ -1,11 +1,5 @@ - + accompanying material @@ -56,4 +50,4 @@ with the letter. It is not catalogued separately. - \ No newline at end of file + diff --git a/P5/Source/Specs/acquisition.xml b/P5/Source/Specs/acquisition.xml index 1a51d12679..b158b464e3 100644 --- a/P5/Source/Specs/acquisition.xml +++ b/P5/Source/Specs/acquisition.xml @@ -1,10 +1,7 @@ - + + + + acquisition adquisición acquisition @@ -28,35 +25,35 @@ institution. - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -80,4 +77,4 @@ institution. - \ No newline at end of file + diff --git a/P5/Source/Specs/activity.xml b/P5/Source/Specs/activity.xml index c0a3e3a5d4..3ae7c14167 100644 --- a/P5/Source/Specs/activity.xml +++ b/P5/Source/Specs/activity.xml @@ -1,10 +1,7 @@ - + + + + activity actividad activité @@ -44,7 +41,9 @@ language interaction is doing other than speaking, if anything. activities during a spoken text, the event element should be used.

-

Para una descripción más detallada de las acciones de los participantes durante los parlamentos, debe utilizarse el elemento event

 + +

Para una descripción más detallada de las acciones de los participantes durante los parlamentos, debe utilizarse el elemento event

+

Pour une description plus fine de toute activité survenant lors d'une communication orale transcrite, utilisez l'élément event.

@@ -58,4 +57,4 @@ be used.

- \ No newline at end of file + diff --git a/P5/Source/Specs/actor.xml b/P5/Source/Specs/actor.xml index e18aaff61f..a19474d3c2 100644 --- a/P5/Source/Specs/actor.xml +++ b/P5/Source/Specs/actor.xml @@ -1,11 +1,5 @@ - + contains the name of an actor appearing within a cast list. @@ -26,14 +20,18 @@ $Id$ specifies the sex of the actor. - + + +

Values for this attribute may be locally defined by a project, or may refer to an external standard.

 specifies the gender of the actor. - + + +

Values for this attribute may be locally defined by a project, or they may refer to an external standard.

 @@ -51,9 +49,9 @@ $Id$ - Mrs Saunders - la logeuse - Sylvia Marriott + Mrs Saunders + la logeuse + Sylvia Marriott @@ -72,7 +70,9 @@ $Id$ marking the components of names, and also of associating names with biographical information about a person.

-

Este elemento debe ser usado solo para marcar el nombre del actor tal como aparece en la fuente. El capítulo comenta/discute formas de marcar los componentes de los nombres, asi como también asociar nombre con información biográfica sobre una persona

 + +

Este elemento debe ser usado solo para marcar el nombre del actor tal como aparece en la fuente. El capítulo comenta/discute formas de marcar los componentes de los nombres, asi como también asociar nombre con información biográfica sobre una persona

+

Cet élément ne devrait être utilisé que pour encoder le nom de l'acteur tel qu'il est donné dans la source. Le chapitre diff --git a/P5/Source/Specs/add.xml b/P5/Source/Specs/add.xml index 46e8e60d50..83ebd4185d 100644 --- a/P5/Source/Specs/add.xml +++ b/P5/Source/Specs/add.xml @@ -1,11 +1,5 @@ - + addition @@ -83,13 +77,13 @@ $Id$

-

+

In einer diplomatischen Ausgabe, die auf eine genaue Wiedergabe der Vorlage zielt, sollte das add-Element nicht für jene Hinzufügungen genutzt werden, die von den Editoren oder Auszeichnenden zu der elektronischen TEI-Edition gemacht werden. In diesen Fällen wird empfohlen, entweder das corr-Element oder supplied-Element zu verwenden.

-

+

In der TEI-Edition eines historischen Textes mit bereits vorhandenen editorischen Korrekturen, in dem solche Ergänzungen oder Rekonstruktionen als Teil der Textvorlage betrachtet werden, kann - im Rahmen der Editionsgrundsätze eines Projekts - die Verwendung des add-Elements geeignet sein. @@ -98,4 +92,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/addName.xml b/P5/Source/Specs/addName.xml index b225c9b786..2bd53a697a 100644 --- a/P5/Source/Specs/addName.xml +++ b/P5/Source/Specs/addName.xml @@ -1,11 +1,5 @@ - + additional name @@ -63,4 +57,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/addSpan.xml b/P5/Source/Specs/addSpan.xml index 3053adcdc6..480b9fceca 100644 --- a/P5/Source/Specs/addSpan.xml +++ b/P5/Source/Specs/addSpan.xml @@ -1,11 +1,5 @@ - + added span of text @@ -35,7 +29,9 @@ $Id$ - + + + The @spanTo attribute of is required. @@ -79,7 +75,9 @@ $Id$ marked; the beginning by the addSpan element itself, the end by the spanTo attribute.

 -

Tanto el inicio como el final del material que se agrego debe ser marcado; el inicio con el mismo elemento addSpan y el final con el atributo spanTo.

 + +

Tanto el inicio como el final del material que se agrego debe ser marcado; el inicio con el mismo elemento addSpan y el final con el atributo spanTo.

+

Le début et la fin de la partie de texte ajoutée doivent être marqués ; le début, par l'élément addSpan lui-même, la fin, par l'attribut spanTo.

@@ -94,4 +92,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/additional.xml b/P5/Source/Specs/additional.xml index f2bb30769c..84a16575e8 100644 --- a/P5/Source/Specs/additional.xml +++ b/P5/Source/Specs/additional.xml @@ -1,11 +1,5 @@ - + additional @@ -26,9 +20,9 @@ it, with curatorial or administrative information. - - - + + + diff --git a/P5/Source/Specs/additions.xml b/P5/Source/Specs/additions.xml index 7c911618a1..9c58274831 100644 --- a/P5/Source/Specs/additions.xml +++ b/P5/Source/Specs/additions.xml @@ -1,11 +1,5 @@ - + additions diff --git a/P5/Source/Specs/addrLine.xml b/P5/Source/Specs/addrLine.xml index 43d72e9a37..4793135a49 100644 --- a/P5/Source/Specs/addrLine.xml +++ b/P5/Source/Specs/addrLine.xml @@ -1,11 +1,5 @@ - + address line @@ -22,7 +16,7 @@ contient une ligne d'adresse postale. contiene una línea de la dirección postal. contiene una riga di un indirizzo (postale). - enthält eine Zeile einer Postadresse. + enthält eine Zeile einer Postadresse. @@ -95,7 +89,7 @@

-

+

Adressen können entweder als eine Abfolge von Zeilen kodiert werden oder als eine beliebige Folge von Elementen der model.addrPart-Klasse. Andere, nicht-postalische Formen von Adressen, wie z. B. Telefonnummern oder E-Mail-Adressen, dürfen nicht direkt in ein address-Element eingeschlossen werden, @@ -108,4 +102,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/address.xml b/P5/Source/Specs/address.xml index c1c088b2ed..31fc091ed1 100644 --- a/P5/Source/Specs/address.xml +++ b/P5/Source/Specs/address.xml @@ -1,11 +1,5 @@ - + address @@ -29,16 +23,10 @@ - - - + - - - - - - + + @@ -108,13 +96,13 @@ TOURS

- - Lyon - 69002 - IIème - Perrache - 30, Cours de Verdun -
+ + Lyon + 69002 + IIème + Perrache + 30, Cours de Verdun + @@ -140,4 +128,4 @@ TOURS - \ No newline at end of file + diff --git a/P5/Source/Specs/adminInfo.xml b/P5/Source/Specs/adminInfo.xml index 29c7b2d1f6..8d19daafaf 100644 --- a/P5/Source/Specs/adminInfo.xml +++ b/P5/Source/Specs/adminInfo.xml @@ -1,11 +1,5 @@ - + administrative information @@ -32,19 +26,11 @@ description itself. - - - - - - - - - - - - - + + + + + @@ -102,4 +88,4 @@ Edgar Holden in 1993. Donor number: 1993-034.

- \ No newline at end of file + diff --git a/P5/Source/Specs/affiliation.xml b/P5/Source/Specs/affiliation.xml index 2940c7a37f..b01bc98245 100644 --- a/P5/Source/Specs/affiliation.xml +++ b/P5/Source/Specs/affiliation.xml @@ -1,10 +1,7 @@ - + + + + affiliation affiliation contains an informal description of a person's present or past affiliation with some @@ -34,48 +31,46 @@ - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + - + - - - - + + + + @@ -134,4 +129,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/age.xml b/P5/Source/Specs/age.xml index 51dbdc6bef..c26ae00ee1 100644 --- a/P5/Source/Specs/age.xml +++ b/P5/Source/Specs/age.xml @@ -1,10 +1,7 @@ - + + + + age âge specifies the age of a person. @@ -26,62 +23,60 @@ - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + - + - - - - - - in world - en el mundo - 物語世界 - age of a fictional character at the time the story + + + + + + in world + en el mundo + 物語世界 + age of a fictional character at the time the story takes place, rather than at the time the story is told - Edad de un personaje ficcional en el tiempo en el que la historia sucede (no en el tiempo en el cual es contada). - 物語を語る時点ではなく、物語の中の時点における架空の人物の年齢。 - - - - - + Edad de un personaje ficcional en el tiempo en el que la historia sucede (no en el tiempo en el cual es contada). + 物語を語る時点ではなく、物語の中の時点における架空の人物の年齢。 + + + + + @@ -95,12 +90,16 @@ o el intervalo de edad. assegna un codice numerico che rappresenta l'età o la fascia di età - + + +

This attribute may be used to complement a more detailed discussion of a person's age in the content of the element

 -

Este atributo debería ser usado para complementar un debate más detallado sobre la edad de la persona en el contenido del elemento

 + +

Este atributo debería ser usado para complementar un debate más detallado sobre la edad de la persona en el contenido del elemento

+

Cet attribut peut être utilisé pour compléter les détails sur l'âge d'une personne donnés dans l'élément.

@@ -140,4 +139,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/alt.xml b/P5/Source/Specs/alt.xml index e9535b5bb4..139812223e 100644 --- a/P5/Source/Specs/alt.xml +++ b/P5/Source/Specs/alt.xml @@ -1,5 +1,5 @@ - + alternation @@ -25,10 +25,14 @@ - + + + - + + + states whether the alternations gathered in this collection are exclusive or @@ -42,7 +46,9 @@ conjunto son exclusivas o inclusivas. dichiara se le alternative contenute nell'insieme sono esclusive o inclusive - + + + exclusive @@ -113,7 +119,9 @@ corrispondente; se l'attributo mode è incl ogni peso rappresenta la probabilità che compaia l'alternativa corrispondente a patto che compaia almeno un'altra delle possibili alternative - + + +

If mode is excl, the sum of weights must be 1. If mode is incl, the sum of weights must be in the diff --git a/P5/Source/Specs/altGrp.xml b/P5/Source/Specs/altGrp.xml index a98c9ddd05..9870a28217 100644 --- a/P5/Source/Specs/altGrp.xml +++ b/P5/Source/Specs/altGrp.xml @@ -1,5 +1,5 @@ - + alternation group @@ -26,11 +26,11 @@ - - - - - + + + + + @@ -46,7 +46,9 @@ conjunto son exclusivas o inclusivas. dichiara se le alternative contenute nell'insieme sono esclusive o inclusive - + + + excl @@ -149,4 +151,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/altIdent.xml b/P5/Source/Specs/altIdent.xml index cea06c3cac..1bf9ec24e8 100644 --- a/P5/Source/Specs/altIdent.xml +++ b/P5/Source/Specs/altIdent.xml @@ -1,11 +1,5 @@ - + alternate identifier @@ -34,7 +28,8 @@ $Id$ - + + diff --git a/P5/Source/Specs/altIdentifier.xml b/P5/Source/Specs/altIdentifier.xml index be5f44ec39..656823b583 100644 --- a/P5/Source/Specs/altIdentifier.xml +++ b/P5/Source/Specs/altIdentifier.xml @@ -1,10 +1,7 @@ - + + + + alternative identifier 대체 확인소 替換識別符碼 @@ -26,10 +23,9 @@ - - + @@ -39,35 +35,35 @@ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -113,4 +109,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/alternate.xml b/P5/Source/Specs/alternate.xml index ebe3bb05ce..1113981f98 100644 --- a/P5/Source/Specs/alternate.xml +++ b/P5/Source/Specs/alternate.xml @@ -1,11 +1,5 @@ - + indicates that the constructs referenced by its children form an alternation @@ -27,12 +21,13 @@ $Id$ - - - - - - + + + + + + +

This example content model permits either a name or a persName.

@@ -40,4 +35,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/am.xml b/P5/Source/Specs/am.xml index c1b8a5989b..17a32dbbd2 100644 --- a/P5/Source/Specs/am.xml +++ b/P5/Source/Specs/am.xml @@ -1,11 +1,5 @@ - + abbreviation marker @@ -33,13 +27,11 @@ l'abréviation - - - - - - - + + + + + @@ -55,20 +47,11 @@ l'abréviation - - - eu - - y - - - - sone + euysone ... - Le Dr. @@ -85,4 +68,4 @@ l'abréviation - \ No newline at end of file + diff --git a/P5/Source/Specs/analytic.xml b/P5/Source/Specs/analytic.xml index 7009b87082..56b9ed86bb 100644 --- a/P5/Source/Specs/analytic.xml +++ b/P5/Source/Specs/analytic.xml @@ -1,11 +1,5 @@ - + analytic level @@ -34,19 +28,17 @@ - - - - - - - - - - - - - + + + + + + + + + + + @@ -60,8 +52,8 @@ (December, 1991): - 25.6 - 377–380 + 25.6 + 377–380 @@ -86,4 +78,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/anchor.xml b/P5/Source/Specs/anchor.xml index 11733a1c20..00b231685d 100644 --- a/P5/Source/Specs/anchor.xml +++ b/P5/Source/Specs/anchor.xml @@ -1,5 +1,5 @@ - + anchor point @@ -23,7 +23,9 @@ - + + + The anchor is here somewhere. @@ -65,4 +67,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/annotation.xml b/P5/Source/Specs/annotation.xml index 5202a70f83..0928d0a7ae 100644 --- a/P5/Source/Specs/annotation.xml +++ b/P5/Source/Specs/annotation.xml @@ -1,14 +1,7 @@ - + - + represents an annotation following the Web Annotation Data Model. diff --git a/P5/Source/Specs/annotationBlock.xml b/P5/Source/Specs/annotationBlock.xml index ac877ca5bd..a0c3607ff1 100644 --- a/P5/Source/Specs/annotationBlock.xml +++ b/P5/Source/Specs/annotationBlock.xml @@ -1,9 +1,5 @@ - + @@ -47,4 +43,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/anyElement.xml b/P5/Source/Specs/anyElement.xml index dd469edd6f..14596a9b34 100644 --- a/P5/Source/Specs/anyElement.xml +++ b/P5/Source/Specs/anyElement.xml @@ -1,23 +1,19 @@ - + - indicates the presence + indicates the presence of any elements in a content model コンテンツモデル内のあらゆる要素の存在を示す。 - - - - - - + + + + + + + + supplies a list of namespaces to one of which the @@ -48,10 +44,11 @@ $Id$ must be declared using a namespace declaration on the parent or an ancestor element.

-

RELAX NG DTD互換モードが有効になっている場合、xml:idをanyNameネームクラスのコンテンツから除外する要素が必要。通常のTEIの目的では、これにはTEI名前空間と egXML要素のすべてが含まれる。除外されるデフォルトの要素と名前空間は、schemaSpecのdefaultExceptions属性で設定される。例外をローカルに指定する必要がある場合は、exceptを使用できる。要素接頭辞は、親要素または祖先要素の名前空間宣言を使用して宣言する必要がある。

 + +

RELAX NG DTD互換モードが有効になっている場合、xml:idをanyNameネームクラスのコンテンツから除外する要素が必要。通常のTEIの目的では、これにはTEI名前空間と egXML要素のすべてが含まれる。除外されるデフォルトの要素と名前空間は、schemaSpecのdefaultExceptions属性で設定される。例外をローカルに指定する必要がある場合は、exceptを使用できる。要素接頭辞は、親要素または祖先要素の名前空間宣言を使用して宣言する必要がある。

+ - @@ -61,7 +58,6 @@ $Id$

This content element permits one occurrence of any element which does not belong to the TEI namespace.

 - @@ -71,13 +67,12 @@ $Id$

This content element permits one or more elements which belong either to the MathML namespace or to the TEI examples namespace.

 - - + @@ -85,8 +80,7 @@ $Id$ either text nodes or elements from the TEI examples namespace. It is the equivalent of the content model ANY in an XML DTD using the TEI All schema.

 - - + - \ No newline at end of file + diff --git a/P5/Source/Specs/app.xml b/P5/Source/Specs/app.xml index a4e1356cdd..435d177909 100644 --- a/P5/Source/Specs/app.xml +++ b/P5/Source/Specs/app.xml @@ -1,11 +1,5 @@ - + apparatus entry @@ -29,15 +23,15 @@ lemma and usually one or more readings or notes on the relevant passage. - + - - + + @@ -52,7 +46,9 @@ some convenient typology. élément selon toute typologie adéquate. clasifica la variación contenida en tal elemento según una tipología funcional classifica la variazione contenuta in tale elemento secondo una tipologia funzionale - + + + identifies the beginning of the lemma in the base text. @@ -63,7 +59,9 @@ some convenient typology. lemme dans le texte de base. identifica, si es necesario, el inicio del lema en el texto base identifica, se necessario, l'inizio del lemma nel testo base - + + +

This attribute should be used when either the double-end point method of apparatus markup, or the location-referenced @@ -74,7 +72,9 @@ some convenient typology. l'apparat critique dite "double-end point", c'est-à-dire que l'on indique le début et la fin du bloc de texte balisé.

-

この属性は、校勘資料のマークアップの両端ポイント方式（double-end point method、または正規化された参照ではなくURLを使用する場所参照方式（location-referenced method）のいずれかを使用する場合に使用する必要がある。

 + +

この属性は、校勘資料のマークアップの両端ポイント方式（double-end point method、または正規化された参照ではなくURLを使用する場所参照方式（location-referenced method）のいずれかを使用する場合に使用する必要がある。

+ identifies the endpoint of the lemma in the base text. @@ -85,7 +85,9 @@ some convenient typology. dans le texte de base. identifica, si es necesario, el final del lema en el texto base identifica, se necessario, la fine del lemma nel testo base - + + +

This attribute is only used when the double-end point method of apparatus markup is used, when the encoded apparatus is not @@ -120,7 +122,9 @@ location-referenced method of apparatus markup is used. référencement des localisations. indica la posición de la variante en caso de usar el método de señalización de la posición de la variante en la codificación del aparato. indica la posizione della variante in caso di utilizzo del metodo di indicazione della posizione della variante nella codifica dell'apparato - + + +

This attribute is used only when the location-referenced encoding method is used. It supplies a string containing a canonical reference for the passage @@ -130,7 +134,9 @@ encoding method is used. It supplies a string containing a canonical reference

Cet attribut n'est utilisé que si l'on emploie la méthode de codage par référence à un emplacement ("location-referenced").

 -

当該属性は、場所参照（location-referenced）符号化方式が採られている場合にのみ使用される。バリエーションが適用される節のための正規化された参照を含む文字列を提供する。

 + +

当該属性は、場所参照（location-referenced）符号化方式が採られている場合にのみ使用される。バリエーションが適用される節のための正規化された参照を含む文字列を提供する。

+ @@ -140,7 +146,7 @@ encoding method is used. It supplies a string containing a canonical reference Experiment Eryment - + @@ -201,4 +207,4 @@ reading groups, each associated with witness specifications.

- \ No newline at end of file + diff --git a/P5/Source/Specs/appInfo.xml b/P5/Source/Specs/appInfo.xml index b14ddfacf0..6e636d300b 100644 --- a/P5/Source/Specs/appInfo.xml +++ b/P5/Source/Specs/appInfo.xml @@ -1,11 +1,5 @@ - + application information @@ -27,9 +21,7 @@ $Id$ - - - + @@ -44,4 +36,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/application.xml b/P5/Source/Specs/application.xml index 12606b8fab..fd4ae9d0cd 100644 --- a/P5/Source/Specs/application.xml +++ b/P5/Source/Specs/application.xml @@ -1,10 +1,7 @@ - + + + + provides information about an application which has acted upon the document. 문서에 사용한 애플리케이션에 관한 정보를 제시한다. proporciona información sobre la aplicación que ha @@ -22,54 +19,46 @@ $Id$ - - - + - - - - - - + + - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + supplies an identifier for the application, independent of its version number or display name. 버전 또는 표시명과 상관없이 애플리케이션의 확인소를 제공한다. @@ -80,7 +69,9 @@ $Id$ indépendamment de son numéro de version ou du nom affiché. indica un identificatore per l'applicazione, indipendentemente dal numero di versione o dal nome visualizzato - + + + supplies a version number for the application, independent of its identifier or display @@ -93,7 +84,9 @@ $Id$ indépendamment de son identifiant ou du nom affiché. indica un numero di versione per l'applicazione, indipendentemente dall'identificatore o dal nome visualizzato - + + + @@ -135,4 +128,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/arc.xml b/P5/Source/Specs/arc.xml index f2cdf06259..de802002f5 100644 --- a/P5/Source/Specs/arc.xml +++ b/P5/Source/Specs/arc.xml @@ -1,11 +1,5 @@ - + arc @@ -24,9 +18,7 @@ $Id$ - - - + @@ -39,7 +31,9 @@ $Id$ immédiatement cet arc. proporciona el identificador al nodo adyacente al nodo corriente. assegna un identificatore al nodo non adiacente all'arco - + + + gives the identifier of the node which is adjacent to this arc. @@ -50,7 +44,9 @@ $Id$ immédiatement cet arc. proporciona el identificador al nodo adyacente al nodo corriente. assegna un identificatore al nodo adiacente all'arco - + + + @@ -116,4 +112,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/argument.xml b/P5/Source/Specs/argument.xml index 88cf10e8b5..48d12eeda5 100644 --- a/P5/Source/Specs/argument.xml +++ b/P5/Source/Specs/argument.xml @@ -1,11 +1,5 @@ - + argument @@ -29,19 +23,13 @@ $Id$ - - - - - - + + + + - - - - - - + + @@ -75,4 +63,4 @@ Tubes formed by Lightning — House struck

- \ No newline at end of file + diff --git a/P5/Source/Specs/att.anchoring.xml b/P5/Source/Specs/att.anchoring.xml index 2981a19b9a..1387fc5de1 100644 --- a/P5/Source/Specs/att.anchoring.xml +++ b/P5/Source/Specs/att.anchoring.xml @@ -1,11 +1,5 @@ - + anchoring @@ -25,7 +19,9 @@ $Id$ riferimento della nota. 当該注釈がある場所への参照は、正確にその場所を示しているかどうか。 gibt an, ob eine Vorlage den exakten Referenzort der Anmerkung anzeigt. - + + + true

In modern texts, notes are usually anchored by means of explicit footnote or endnote @@ -74,7 +70,9 @@ $Id$ 当該注釈・コメントの終了点を示す。(当該注釈が注釈先の場所に埋め込 まれていない場合) verweist auf das Ende eines Bereichs, dem das note-Element angefügt ist, es sei denn die Anmerkung ist in den Text an diesem Punkt bereits eingebettet. - + + +

This attribute is retained for backwards compatibility; it may be removed at a subsequent release of the Guidelines. The recommended way of pointing to a span of elements is by @@ -94,21 +92,19 @@ $Id$ - -

(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses +

(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses necnon episcopum in duplicibus Quatuortemporibus totaliter expediui...

- - - - + + + Quatuor Tempora, so called dry fast days. - + Quatuor Tempora, tzw. Suche dni postne. - + diff --git a/P5/Source/Specs/att.ascribed.directed.xml b/P5/Source/Specs/att.ascribed.directed.xml index 41ded2db0a..1d76779908 100644 --- a/P5/Source/Specs/att.ascribed.directed.xml +++ b/P5/Source/Specs/att.ascribed.directed.xml @@ -1,57 +1,54 @@ - + - provides attributes for elements representing speech or action that can be directed at a + provides attributes for elements representing speech or action that can be directed at a group or individual. - - - - - - indicates the person, or group of people, to whom a speech act or action is directed. - - - -

In the following example from Mary Pix's The False Friend, speeches (sp) in the body of the play + + + + + + indicates the person, or group of people, to whom a speech act or action is directed. + + + + +

In the following example from Mary Pix's The False Friend, speeches (sp) in the body of the play are linked to castItem elements in the castList using the toWhom attribute, which is used to specify who the speech is directed to. Additionally, the stage includes toWhom to indicate the directionality of the action.

- - - Emilius. - - - Lovisa - - - A servant - - - - Emil. - My love! - - - Lov. - I have no Witness of my Noble Birth - Pointing to her Woman. - But that poor helpless wretch—— - - - -

To indicate the recipient of written correspondence, use the elements used in section , rather than a toWhom attribute.

 - - - - - - - \ No newline at end of file + + + Emilius. + + + Lovisa + + + A servant + + + + Emil. + My love! + + + Lov. + I have no Witness of my Noble Birth + Pointing to her Woman. + But that poor helpless wretch—— + + + + +

To indicate the recipient of written correspondence, use the elements used in section , rather than a toWhom attribute.

+ + + + + + + + diff --git a/P5/Source/Specs/att.ascribed.xml b/P5/Source/Specs/att.ascribed.xml index 086fc17c7b..982d2838cf 100644 --- a/P5/Source/Specs/att.ascribed.xml +++ b/P5/Source/Specs/att.ascribed.xml @@ -1,11 +1,5 @@ - + provides attributes for elements representing speech or action that can be ascribed to a @@ -31,7 +25,9 @@ $Id$ refiere el contenido del elemento. indica la persona o gruppo di persone alle quali viene attribuito il contenuto dell'elemento - + + +

In the following example from Hamlet, speeches (sp) in the body of the play are linked to role elements in the castList using the who @@ -55,16 +51,22 @@ $Id$ -

For transcribed speech, this will typically identify a participant or participant - group; in other contexts, it will point to any identified person element.

-

Pour un discours transcrit, identifiera typiquement un participant ou + +

For transcribed speech, this will typically identify a participant or participant + group; in other contexts, it will point to any identified person element.

+ + +

Pour un discours transcrit, identifiera typiquement un participant ou un groupe participant ; dans d'autres contextes, pointera vers n'importe quel élément - person identifié.

 -

転記された音声の場合、これは通常、参加者または参加者グループを識別する。他のコンテキストでは、識別されたperson要素を指し示す。

 + person identifié.

+ + +

転記された音声の場合、これは通常、参加者または参加者グループを識別する。他のコンテキストでは、識別されたperson要素を指し示す。

+ - \ No newline at end of file + diff --git a/P5/Source/Specs/att.breaking.xml b/P5/Source/Specs/att.breaking.xml index dd6de73bfb..22ad44e754 100644 --- a/P5/Source/Specs/att.breaking.xml +++ b/P5/Source/Specs/att.breaking.xml @@ -1,11 +1,5 @@ - + provides attributes to indicate whether or not the element @@ -24,7 +18,9 @@ le fait une espace. peut être considéré comme une espace blanc indiquant la fin d'un mot orthographique. この属性を持つ要素が空白と同じ方法で正字トークンの終わりを示すとみなされるべきかどうかを示す。 - + + + the element bearing this attribute is considered @@ -69,4 +65,4 @@ of any adjacent whitespace - \ No newline at end of file + diff --git a/P5/Source/Specs/att.cReferencing.xml b/P5/Source/Specs/att.cReferencing.xml index e090afd37a..cfdcaa4e5a 100644 --- a/P5/Source/Specs/att.cReferencing.xml +++ b/P5/Source/Specs/att.cReferencing.xml @@ -1,11 +1,5 @@ - + provides attributes that may be used to supply a @@ -35,27 +29,32 @@ specifica la destinazione di un puntatore usando un riferimento canonico a partire da uno schema definito in un elemento refsDecl nell'intestazione TEI - - + + + +

The value of cRef should be constructed so that when the algorithm for the resolution of canonical references (described in section ) is applied to it the result is a valid URI reference to the intended target.

-

The refsDecl to use may be indicated with the decls attribute.

+

The refsDecl to use may be indicated with the decls attribute.

Currently these Guidelines only provide for a single canonical reference to be encoded on any given ptr element.

 -

Le résultat de l’application de l'algorithme pour la résolution des +

Le résultat de l’application de l'algorithme pour la résolution des références canoniques (décrit à la section ). Ce sera une référence URI - valide pour la cible prévue.

La refsDecl à utiliser peut être indiquée à l'aide + valide pour la cible prévue.

+

La refsDecl à utiliser peut être indiquée à l'aide de l'attribut decls. Actuellement ces Principes directeurs ne permettent que l'encodage d'une unique référence canonique pour tout élément ptr donné.

 - -

節での正規化参照を解決するためのアルゴリズムが適用される時にその結果が対象への正しいURI参照となるように、 cRef の値は作られるべきである

refsDecl は decls 属性とともに示されてもよい。現行のガイドラインが ptr 要素に渡すのは、単一の符号化された正規化参照のみである。

 + +

節での正規化参照を解決するためのアルゴリズムが適用される時にその結果が対象への正しいURI参照となるように、 cRef の値は作られるべきである

+

refsDecl は decls 属性とともに示されてもよい。現行のガイドラインが ptr 要素に渡すのは、単一の符号化された正規化参照のみである。

+ - \ No newline at end of file + diff --git a/P5/Source/Specs/att.calendarSystem.xml b/P5/Source/Specs/att.calendarSystem.xml index c34014f4d0..457afadc56 100644 --- a/P5/Source/Specs/att.calendarSystem.xml +++ b/P5/Source/Specs/att.calendarSystem.xml @@ -1,11 +1,5 @@ - + provides attributes for indicating calendar systems to which a date belongs. @@ -38,7 +32,7 @@ $Id$ He was born on Feb. 22, 1732 (Feb. 11, 1731/32, O.S.). - + @@ -47,8 +41,7 @@ $Id$ - - Dienstag 7/19 + Dienstag 7/19 Mai. @@ -63,18 +56,17 @@ $Id$ as it appears on an original source. It does not modify the interpretation of the normalization attributes provided by att.datable.w3c, - att.datable.iso, or att.datable.custom. Attributes from those first two + att.datable.iso, or att.datable.custom. Attributes from those first two classes are always interpreted as Gregorian or proleptic Gregorian dates, as per the respective standards on which they are based. The - calender system used to interpret the last (att.datable.custom) may be specified with + calender system used to interpret the last (att.datable.custom) may be specified with datingMethod.

-

- calendar属性は(att.datable.customクラスで定義されるdatingMethod属性と異なり、 + +

calendar属性は(att.datable.customクラスで定義されるdatingMethod属性と異なり、 親要素によって定義される原資料の日付の暦日システムを定義するものであり、 - どの暦日に日付を正規化するかではない。

 + どの暦日に日付を正規化するかではない。

+ diff --git a/P5/Source/Specs/att.canonical.xml b/P5/Source/Specs/att.canonical.xml index f621566293..57aae63d34 100644 --- a/P5/Source/Specs/att.canonical.xml +++ b/P5/Source/Specs/att.canonical.xml @@ -1,11 +1,5 @@ - + provides attributes that can be used to associate a representation such as a name or title @@ -22,7 +16,9 @@ d'identifier l'entité (ou les entités) nommé(es), en utilisant une valeur codée d'un certain type. 何らかのコード化された値を用いて、名付けられたエンティティを識別する外部的に定義された手段を提供する。 - + + + @@ -40,7 +36,9 @@

La valeur peut être un identifiant unique dans une base de données, ou toute autre chaîne définie de façon externe identifiant le référent.

-

値はデータベースにおけるユニークな識別子や、外部で定義された指示対象を特定するなんらかの文字列であってよい。key属性の値に関してさだまった構文は提案されていない。なぜならば、それぞれのプロジェクトのやりかたに完全に依存するからである。同様の理由によって、データの相互交換においてこの属性は推奨されない。在るプロジェクトで用いられた値が他のプロジェクトの値と異なることを保証できないからである。そのような場面における魔法石的対処は、RFC4151に定義されるタグURIを値とするref属性を用いて、標準的なウェブにおける習慣にしたがってmagic tokenを使うことである。

 + +

値はデータベースにおけるユニークな識別子や、外部で定義された指示対象を特定するなんらかの文字列であってよい。key属性の値に関してさだまった構文は提案されていない。なぜならば、それぞれのプロジェクトのやりかたに完全に依存するからである。同様の理由によって、データの相互交換においてこの属性は推奨されない。在るプロジェクトで用いられた値が他のプロジェクトの値と異なることを保証できないからである。そのような場面における魔法石的対処は、RFC4151に定義されるタグURIを値とするref属性を用いて、標準的なウェブにおける習慣にしたがってmagic tokenを使うことである。

+ reference @@ -51,40 +49,35 @@ fournit un moyen explicite de localiser une définition complète de l'entité nommée au moyen d'un ou plusieurs URIs. 一つ以上のURIを用いて、名付けられたエンティティの完全な定義かIDを参照するための明確な手段を提供する。 - + + + Seamus Heaney - + -

The value must point directly to one or more XML elements or other resources by means of one or more URIs, separated by whitespace. If more than one is supplied the implication is that the name identifies several distinct entities.

+

The value must point directly to one or more XML elements or other resources by means of one or more URIs, separated by whitespace. If more than one is supplied the implication is that the name identifies several distinct entities.

La valeur doit pointer directement vers un ou plusieurs éléments XML au moyen d'un ou plusieurs URIs, séparés par un espace. Si plus d'un URI est fourni, cela implique que le nom identifie plusieurs entités distinctes.

 -

値は1つまたは複数のXML要素あるいは、空白によって区切られた1つまたは複数のURIを指し示すものでなければならない。1つ以上の値が与えられているときは、その名前が複数の異るエンティティに対応することを示唆する。

 + +

値は1つまたは複数のXML要素あるいは、空白によって区切られた1つまたは複数のURIを指し示すものでなければならない。1つ以上の値が与えられているときは、その名前が複数の異るエンティティに対応することを示唆する。

+

In this contrived example, a canonical reference to the same organisation is provided in four different ways.

- - - New Zealand Parliament, Legislative Council - -   - - New Zealand Parliament, Legislative Council - -   - - New Zealand Parliament, Legislative Council - -   - - New Zealand Parliament, Legislative Council - + New Zealand Parliament, Legislative Council +   + New Zealand Parliament, Legislative Council +   + New Zealand Parliament, Legislative Council +   + New Zealand Parliament, Legislative Council

The first presumes the availability of an internet connection and a processor that can resolve a URI (most can). The second diff --git a/P5/Source/Specs/att.citeStructurePart.xml b/P5/Source/Specs/att.citeStructurePart.xml index e25cca8223..303e4fa68b 100644 --- a/P5/Source/Specs/att.citeStructurePart.xml +++ b/P5/Source/Specs/att.citeStructurePart.xml @@ -1,11 +1,5 @@ - + provides attributes for selecting particular elements diff --git a/P5/Source/Specs/att.citing.xml b/P5/Source/Specs/att.citing.xml index a41f2441a8..b05f93b36c 100644 --- a/P5/Source/Specs/att.citing.xml +++ b/P5/Source/Specs/att.citing.xml @@ -1,11 +1,5 @@ - + provides attributes for specifying the specific part of a bibliographic item being cited. @@ -17,80 +11,82 @@ $Id$ identifie le type d'information que transmet l'élément, par exemple colonnes, pages, volume, inscription, etc. 当該要素が伝える情報の単位を特定する。たとえば、カラム (columns)、頁 (pages)、巻 (volume)、エントリ (entry) 等。 - + + + - - volume - 권 - volumen - the element contains a volume number. - 권수를 포함한다. - 該元素標記的內容為冊號。 - el elemento contiene el número de volumen. - 巻番号を含む。 - l'élément contient un numéro de volume. - l'elemento contiene il numero del volume. - - - the element contains an issue number, or volume and + + volume + 권 + volumen + the element contains a volume number. + 권수를 포함한다. + 該元素標記的內容為冊號。 + el elemento contiene el número de volumen. + 巻番号を含む。 + l'élément contient un numéro de volume. + l'elemento contiene il numero del volume. + + + the element contains an issue number, or volume and issue numbers. - 호, 또는 권과 호를 포함한다. - 該元素標記的內容為一期刊號或冊號與期刊號。 - el elemento contiene el número de la edición, o los números del volumen y de la edición. - 号番号かまたは巻と号の番号を含む。 - l'élément contient un numéro de + 호, 또는 권과 호를 포함한다. + 該元素標記的內容為一期刊號或冊號與期刊號。 + el elemento contiene el número de la edición, o los números del volumen y de la edición. + 号番号かまたは巻と号の番号を含む。 + l'élément contient un numéro de livraison ou bien un numéro de volume et de livraison. - l'elemento contiene l'indicazione del numero della pubblicazione - - - page - 페이지 - pagine - página - the element contains a page number or page range. - 페이지 번호 또는 페이지 범위를 포함한다. - 該元素標記的內容為一頁數或頁數範圍。 - el elemento contiene un número de página o un intervalo de páginas. - ページ番号またはページ範囲を含む。 - l'élément contient un nombre de pages + l'elemento contiene l'indicazione del numero della pubblicazione + + + page + 페이지 + pagine + página + the element contains a page number or page range. + 페이지 번호 또는 페이지 범위를 포함한다. + 該元素標記的內容為一頁數或頁數範圍。 + el elemento contiene un número de página o un intervalo de páginas. + ページ番号またはページ範囲を含む。 + l'élément contient un nombre de pages ou l'étendue de sélection des pages. - l'elemento contiene l'indicazione di pagina o pagine - - - the element contains a line number or line range. - 行番号か行範囲を含む。 - - - chapter - 장 - capítulo - chapitre - capitolo - the element contains a chapter indication (number + l'elemento contiene l'indicazione di pagina o pagine + + + the element contains a line number or line range. + 行番号か行範囲を含む。 + + + chapter + 장 + capítulo + chapitre + capitolo + the element contains a chapter indication (number and/or title) - 장 표시(숫자와/또는 제목)를 포함한다. - el elemento contiene la indicación del capítulo (número y/o el título) - 章の識別子(番号やタイトル)を含む。 - l'élément contient une indication de + 장 표시(숫자와/또는 제목)를 포함한다. + el elemento contiene la indicación del capítulo (número y/o el título) + 章の識別子(番号やタイトル)を含む。 + l'élément contient une indication de chapitre (le numéro et/ou le titre) - l'elemento contiene un'indicazione di capitolo (numero e/o titolo - - - the element identifies a part of a book or collection. - 책 또는 모음집의 부분을 식별한다. - 該元素標明的內容為單書或集合作品的一部份。 - el elemento identifica una parte de un libro o de una colección. - 書籍や叢書の部分を特定する。 - l'élément identifie une partie d'un + l'elemento contiene un'indicazione di capitolo (numero e/o titolo + + + the element identifies a part of a book or collection. + 책 또는 모음집의 부분을 식별한다. + 該元素標明的內容為單書或集合作品的一部份。 + el elemento identifica una parte de un libro o de una colección. + 書籍や叢書の部分を特定する。 + l'élément identifie une partie d'un livre ou une anthologie. - l'elemento identifica una parte di un libro o di una raccolta - - - the element identifies a column. - 一つのカラムを特定する。 - + l'elemento identifica una parte di un libro o di una raccolta + + + the element identifies a column. + 一つのカラムを特定する。 + - the element identifies an entry number or label in a list of entries. + the element identifies an entry number or label in a list of entries. エントリのリスト中の番号やラベルを特定する。 @@ -98,12 +94,16 @@ $Id$ specifies the starting point of the range of units indicated by the unit attribute. unit属性で指定された時間単位の幅における開始点を表す。 - + + + specifies the end-point of the range of units indicated by the unit attribute. unit属性で指定された時間単位の幅における終点を表す。 - + + + diff --git a/P5/Source/Specs/att.combinable.xml b/P5/Source/Specs/att.combinable.xml index a636a74c5d..41026a4d63 100644 --- a/P5/Source/Specs/att.combinable.xml +++ b/P5/Source/Specs/att.combinable.xml @@ -1,16 +1,10 @@ - + provides attributes indicating how multiple references to the same object in a schema should be combined - あるスキーマにおける同一オブジェクトに対する複数の参照をどのように統合すべきか示す属性を提供する。 + あるスキーマにおける同一オブジェクトに対する複数の参照をどのように統合すべきか示す属性を提供する。 @@ -87,74 +81,38 @@ $Id$ -

An ODD processor should handle the values for mode as follows: - - the object should be created (processing any children in add mode); raise an error if the object has an identifier and - an object with the same identifier (and namespace in the case of an element or attribute) already exists. - - use this object in preference to any existing object with the same identifier (and namespace in the case of an element or attribute), - and ignore any children of that object; process any new children in replace mode - - do not process this object or any existing object with the same identifier (and namespace in the case of an element or attribute); - the element carrying this attribute must be empty: raise an error if there are any children - - process this object and its children, replacing only those components of an existing object of the same type with the +

An ODD processor should handle the values for mode as follows: the object should be created (processing any children in add mode); raise an error if the object has an identifier and + an object with the same identifier (and namespace in the case of an element or attribute) already exists.use this object in preference to any existing object with the same identifier (and namespace in the case of an element or attribute), + and ignore any children of that object; process any new children in replace modedo not process this object or any existing object with the same identifier (and namespace in the case of an element or attribute); + the element carrying this attribute must be empty: raise an error if there are any childrenprocess this object and its children, replacing only those components of an existing object of the same type with the same identifier (and namespace in case of an element or attribute) that are explicitly specified. This will change only those existing attribute values and child elements that appear both in the original specification and in the new specification. - Other children from the original specification will be preserved. - + Other children from the original specification will be preserved.

Un processore ODD dovrebbe considerare i valori dell'attributo mode in questo modo: - - - l'oggetto dovrebbe essere creato, trattando tutti gli elementi figlio che hanno anch'essi il valore add. + l'oggetto dovrebbe essere creato, trattando tutti gli elementi figlio che hanno anch'essi il valore add. Se esistesse un oggetto con lo stesso nome (e namespace nel caso di un elemento o attributo) bisognerà dare un errore. - - - utilizzare questo oggetto al posto di qualsiasi atro oggetto esistente con lo stesso nome (e namespace nel caso di un elemento o attributo), + utilizzare questo oggetto al posto di qualsiasi atro oggetto esistente con lo stesso nome (e namespace nel caso di un elemento o attributo), e ignorare gli elementi figlio di quell'oggetto; trattare tutti gli elementi che hanno anch'essi il valore replace. - - - non trattare questo oggetto o qualsiasi altro oggetto con lo stesso nome (e namespace nel caso di un elemento o attributo); + non trattare questo oggetto o qualsiasi altro oggetto con lo stesso nome (e namespace nel caso di un elemento o attributo); l'elemento con questo valore deve essere vuoto: dare un error nel caso in cui contenesse elementi figlio. - - - trattare questo oggetto e tutti i suoi elementi figlio, sustituendo solo i componenti di un oggetto già esistente e + trattare questo oggetto e tutti i suoi elementi figlio, sustituendo solo i componenti di un oggetto già esistente e direttamente specificato dello stesso tipo e con lo stesso nome (e namespace nel caso di un elemento o attributo). Questa operazione cambierà solamente i valori di attributi già esistenti ed elementi figlio che sono presenti sia nella specificazione originale - che nella nuova specificazione. Gli altri elementi filgio che fanno parte della specificazione originale verranno mantenuti. - + che nella nuova specificazione. Gli altri elementi filgio che fanno parte della specificazione originale verranno mantenuti.

-

La signification informelle des valeurs de l'attribut mode est la suivante : - - l'objet doit être créé (traitement de tout enfant dans le mode add) ; - générer une erreur si un objet avec le même identifiant existe déjà. - - utiliser cet objet de préférence à tout autre portant le même identifiant et ignorer - tout enfant de cet objet ; traiter tout nouvel enfant dans le mode replace. - - ne pas traiter cet objet ou aucun autre portant le même identifiant ; générer une - erreur si de nouveaux enfants sont fournis. - - traiter cet objet, et ses enfants, et ceux de n'importe quel objet portant le même - identifiant, dans le mode change. - +

La signification informelle des valeurs de l'attribut mode est la suivante :l'objet doit être créé (traitement de tout enfant dans le mode add) ; + générer une erreur si un objet avec le même identifiant existe déjà.utiliser cet objet de préférence à tout autre portant le même identifiant et ignorer + tout enfant de cet objet ; traiter tout nouvel enfant dans le mode replace. ne pas traiter cet objet ou aucun autre portant le même identifiant ; générer une + erreur si de nouveaux enfants sont fournis.traiter cet objet, et ses enfants, et ceux de n'importe quel objet portant le même + identifiant, dans le mode change.

-

ODDプロセッサはmode属性値を次のように扱うべきである: - - オブジェクトを生成すべきである（子をすべてaddモードで処理する）。同一の識別子を持つオブジェクトがすでに存在するばあいはエラーを発生させる。 - - 同一の識別子を持つ先んじて存在するすべてのオブジェクトよりも当該のオブジェクトを優先して使用し、それらのオブジェクトの子を無視する。新しい子はすべてreplaceモードで処理する。 - - 当該の、あるいは先んじて存在するすべてのオブジェクトを処理してはならない。子が与えられたときはエラーを発生させる。 - - 当該のオブジェクトと子、また先んじて存在するすべてのオブジェクトの子をchangeモードで処理する。 -

+

ODDプロセッサはmode属性値を次のように扱うべきである: オブジェクトを生成すべきである（子をすべてaddモードで処理する）。同一の識別子を持つオブジェクトがすでに存在するばあいはエラーを発生させる。同一の識別子を持つ先んじて存在するすべてのオブジェクトよりも当該のオブジェクトを優先して使用し、それらのオブジェクトの子を無視する。新しい子はすべてreplaceモードで処理する。当該の、あるいは先んじて存在するすべてのオブジェクトを処理してはならない。子が与えられたときはエラーを発生させる。当該のオブジェクトと子、また先んじて存在するすべてのオブジェクトの子をchangeモードで処理する。

 diff --git a/P5/Source/Specs/att.coordinated.xml b/P5/Source/Specs/att.coordinated.xml index acafc0061e..8bab85b9b2 100644 --- a/P5/Source/Specs/att.coordinated.xml +++ b/P5/Source/Specs/att.coordinated.xml @@ -1,11 +1,5 @@ - + provides attributes that can be used to position their parent @@ -22,7 +16,9 @@ containing at least the start of the writing represented by this zone or surface. désigne l'élément qui, dans la transcription du texte, contient au moins le début de la section de texte représentée dans la zone ou surface. このzoneまたはsurface要素で示される記述の少なくとも開始点を含むようなテクストの翻刻内の要素を示す。 - + + + gives the x coordinate value for the upper left corner of a @@ -34,7 +30,9 @@ rectangular space. donne la valeur x de l'abscisse du coin supérieur gauche d'un rectangle. assegna il valore x all'angolo superiore sinistro di uno spazio rettangolare - + + + gives the y coordinate value for the upper left corner of a @@ -45,7 +43,9 @@ rectangular space. donne la valeur y de l'ordonnée du coin supérieur gauche d'un rectangle. assegna il valore y all'angolo superiore sinistro di uno spazio rettangolare - + + + gives the x coordinate value for the lower right corner of a @@ -56,7 +56,9 @@ rectangular space. donne la valeur x de l'abscisse du coin inférieur droit d'un rectangle. assegna il valore x all'angolo inferiore destro di uno spazio rettangolare - + + + gives the y coordinate value for the lower right corner of a @@ -67,12 +69,16 @@ rectangular space. donne la valeur y de l'ordonnée du coin inférieur droit d'un rectangle. assegna il valore y all'angolo inferiore destro di uno spazio rettangolare - + + + identifies a two dimensional area by means of a series of pairs of numbers, each of which gives the x,y coordinates of a point on a line enclosing the area. 当該の領域を取り囲む線上の点のXとY軸を与える一連の数値の組を持つ他の属性によって指定されたバウンディングボックス内の2次元の領域を特定する。 - + + + - \ No newline at end of file + diff --git a/P5/Source/Specs/att.damaged.xml b/P5/Source/Specs/att.damaged.xml index 1b45cc5be5..ba4d2d2af4 100644 --- a/P5/Source/Specs/att.damaged.xml +++ b/P5/Source/Specs/att.damaged.xml @@ -1,11 +1,5 @@ - + provides attributes describing the nature of any physical damage affecting a reading. @@ -45,7 +39,9 @@ $Id$ rintracciabile categoriza la causa del daño, si esta puede ser identificada. - + + + damage results from rubbing of the leaf edges @@ -102,7 +98,9 @@ $Id$ escala funcional; la etiqueta damage (daño) con el atributo degree (grado) deberán utilizarse sólo si el texto puede ser leído con una cierta certeza; los textos proporcionados por otras fuentes serán etiquetados como supplied (suplente) - + + +

The damage element is appropriate where it is desired to record the fact of damage although this has not affected the readability of the @@ -157,7 +155,9 @@ $Id$ physique assegna un numero arbitrario a ognuna delle porzioni di danneggiamento considerate parte dello stesso fenomeno fisico - + + + diff --git a/P5/Source/Specs/att.datable.custom.xml b/P5/Source/Specs/att.datable.custom.xml index 6cb24c7321..359d0fea2e 100644 --- a/P5/Source/Specs/att.datable.custom.xml +++ b/P5/Source/Specs/att.datable.custom.xml @@ -1,11 +1,5 @@ - + provides attributes for normalization of elements that contain datable events to a custom dating system @@ -16,7 +10,9 @@ supplies the value of a date or time in some custom standard form. 何らかの標準的な準形式で、日付や時刻の値を示す。 - + + +

The following are examples of custom date or time formats that are not valid ISO or W3C format normalizations, normalized to a different dating system

@@ -41,17 +37,23 @@ specifies the earliest possible date for the event in some custom standard form. 何らかの標準的な形式で、あるイベントに関して「この時点より前ではない」という日付を示す。 - + + + specifies the latest possible date for the event in some custom standard form. 何らかの標準的な形式で、あるイベントに関して「この時点より後ではない」という日付を示す。 - + + + indicates the starting point of the period in some custom standard form. 何らかの標準的な形式で期間の開始時点を示す。 - + + + @@ -65,19 +67,25 @@ indicates the ending point of the period in some custom standard form. 何らかの標準的な形式で期間の終了時点を示す。 - + + + supplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred ある時点につけた名前とその事柄が起きたとされる時間をともに定義している場所へのポインタを示す。たとえば、「令和改元」という日付をともなうID付きイベント要素を作成した場合にそのIDに対する参照を行う。 - + + + supplies a pointer to a calendar element or other means of interpreting the values of the custom dating attributes. ここで提供するポインタは、calendar 要素もしくは日付を示す属性の値を解釈する何らかの方式を指す。 - + + + Contayning the Originall, Antiquity, Increaſe, Moderne eſtate, and deſcription of that Citie, written in the yeare @@ -98,17 +106,21 @@ (in when) to the Gregorian date, but is also normalized (in when-custom) to a machine-actionable, numeric version of the date from the Creation.

 -

Note that the datingMethod attribute (unlike + +

Note that the datingMethod attribute (unlike calendar defined in att.datable) defines the calendar or dating system to which the date described by the parent element is normalized (i.e. in the when-custom or other X-custom attributes), not the calendar of the - original date in the element.

 -

（att.datableで定義されるcalendar 属性とは違って） + original date in the element.

+ + +

（att.datableで定義されるcalendar 属性とは違って） datingMethod属性が定義するのは、親要素で記述された日付を正規化した暦や暦法であり、 - 当該要素中のオリジナルの日付の暦ではない。

 + 当該要素中のオリジナルの日付の暦ではない。

+ - \ No newline at end of file + diff --git a/P5/Source/Specs/att.datable.iso.xml b/P5/Source/Specs/att.datable.iso.xml index 5b37e247cc..7ae8f43fe0 100644 --- a/P5/Source/Specs/att.datable.iso.xml +++ b/P5/Source/Specs/att.datable.iso.xml @@ -1,11 +1,5 @@ - + provides attributes for normalization of elements that contain datable events using the ISO 8601:2004 standard. @@ -28,7 +22,9 @@ précise une date exacte pour l'évènement selon la forme normalisée ISO 8601:2004, c'est-à-dire aaaa-mm-jj. indica il valore di una data o di un orario in un formato standard - + + +

The following are examples of ISO date, time, and date & time formats that are not valid W3C format normalizations.

@@ -86,7 +82,9 @@ specifica la prima data possibile per un evento nel formato standard aaaa-mm-gg indica la fecha más temprana posible para un evento en un formato estándard, p.ej. aaaa-mm-dd. - + + + specifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd. @@ -98,7 +96,9 @@ specifica l'ultima data possibile per un evento nel formato standard aaaa-mm-gg indica la fecha más tardana posible para un evento en un formato estándard, p.ej. aaaa-mm-dd. - + + + indicates the starting point of the period in standard form. @@ -108,7 +108,9 @@ indique le point de départ de la période sous une forme normalisée indica l'inizio del periodo nel formato standard indica el punto de inicio de un periodo de tiempo en formato estándard. - + + + indicates the ending point of the period in standard form. @@ -118,7 +120,9 @@ 当該時間幅の、終点を標準形で示す。 indique le point final de la période sous une forme normalisée indica la fine del periodo nel formato standard - + + + @@ -133,8 +137,8 @@

In providing a regularized form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading.

-

この属性の値は、グレゴリオ暦を用い、ISO8601:2004で定義されるいずれかの標準形式で正規化された日付や時刻、あるいはその組み合わせである。

- + +

この属性の値は、グレゴリオ暦を用い、ISO8601:2004で定義されるいずれかの標準形式で正規化された日付や時刻、あるいはその組み合わせである。

属性when-isoの値は、ISO8601:2004に従った、日付や時間、ま たはその組み合わせになる。属性calendarがある場合に は、要素内容の歴システムが示される。属calendarは、 属性when when-isoの歴システムを示すもので はない。これは普通はグレゴリオ暦になる。

diff --git a/P5/Source/Specs/att.datable.w3c.xml b/P5/Source/Specs/att.datable.w3c.xml index 09567b7fa4..01012f050d 100644 --- a/P5/Source/Specs/att.datable.w3c.xml +++ b/P5/Source/Specs/att.datable.w3c.xml @@ -1,11 +1,5 @@ - + provides attributes for normalization of elements that contain @@ -50,7 +44,9 @@ $Id$ une forme normalisée, par ex. aaaa-mm-jj. indica il valore di una data o di un orario in un formato standard proporciona el valor de una fecha o una hora en un formato estandard. - + + +

Examples of W3C date, time, and date & time formats.

@@ -87,7 +83,7 @@ $Id$ - Shakespeare meurt dix jours plus tard, à Stratford-on-Avon, + Shakespeare meurt dix jours plus tard, à Stratford-on-Avon, Warwickshire, dans l'Angleterre protestante et dans le calendrier julien, le mardi 23 avril ancien style, @@ -119,7 +115,9 @@ $Id$ l'événement sous une forme normalisée, par ex. aaaa-mm-jj specifica la prima data possibile per un evento nel formato standard aaaa-mm-gg especifica la fecha más temprana posible para un evento en un formato estándard, p.ej. aaaa-mm-dd. - + + + specifies the latest possible date for the event in @@ -131,7 +129,9 @@ $Id$ l'événement sous une forme normalisée, par ex. aaaa-mm-jj specifica l'ultima data possibile per un evento nel formato standard aaaa-mm-gg especifica la fecha más tardana posible para un evento en un formato estándard, p.ej. aaaa-mm-dd. - + + + indicates the starting point of the period in standard form, e.g. yyyy-mm-dd. @@ -142,7 +142,9 @@ $Id$ forme normalisée, par ex. aaaa-mm-jj indica l'inizio del periodo nel formato standard indica el punto de inicio del período en el formato estándard. - + + + indicates the ending point of the period in standard @@ -154,47 +156,50 @@ $Id$ normalisée, par ex. aaaa-mm-jj indica la fine del periodo nel formato standard indica el punto final de un periodo en formato estándard. - + + + - 28 May through 1 June 1863 - -

The value of these attributes should be a normalized + +

The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar.

-

The most commonly-encountered format for the date portion of +

The most commonly-encountered format for the date portion of a temporal attribute is yyyy-mm-dd, but yyyy, --mm, ---dd, yyyy-mm, or --mm-dd may also be used. For the time part, the form hh:mm:ss is used.

-

Note that this format does not currently permit use of the +

Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used.

- - -

La valeur de l'attribut when doit être une représentation normalisée de la date ou de l'heure, ou des deux, dans l'un des formats spécifiés par le XML Schema Part 2: Datatypes Second Edition, selon le calendrier grégorien.

-

Pour la date, le format le plus courant est yyyy-mm-dd, mais on trouve aussi yyyy, --mm, ---dd, yyyy-mm, ou --mm-dd. Pour l'heure, on utilise le format hh:mm:ss.

-

Il faut noter qu'actuellement ce format ne permet pas d'utiliser la valeur 0000 pour représenter l'année précédant le début de l'ère chrétienne ; on doit utiliser la valeur -0001.

- -

El valor del atributo cuando es una serie que representa una fecha o una hora, o ambas, en cualquiera de los siguientes formatos: una fecha en los formatos estándares descritos por la XML Schema Part 2: Datatypes Second Edition, p.ej. en el formato más común aaaa-mm-dd, pero también aaaa, --mm, ---dd, aaaa-mm, o --mm-dd; una hora en el formato estándar descrito en XML Schema Part 2: Datatypes Second Edition, es decir. hh: mm: ss; o una fecha y una hora combinadas en los formatos estándares descritos en XML Schema Part 2: Datatypes Second Edition, es decir. aaaa-mm-ddThh: mm: ss. Obligatoriamente el valor de cuando aparecerá en un formato de fecha, tiempo, o ambos formatos combinados, de los reconocidos por W3C XML Schema Part 2: Datatypes Second Edition. Esto se dará si el componente de la fecha (eventualmente) es una fecha gregoriana o proléptica gregoriana. A la hora de esta escritura, W3C no permite el año 0000, que sería utilizado normalmente para representar el año 1 antes de nuestra era. Usando el sistema actual de W3C, el año 1 a.C. se indica con -0001, el año 2 a.C. con -0002, etc. Es la intención del grupo de trabajo del esquema de XML permitir 0000 como la representación léxica de 1 a.C. (que es un año bisiesto), -0001 se convertiria en la representación léxica de 2 a.C., -0002 de 3 a.C., etc. Así en algunos casos puede ser ventajoso utilizar en su lugar el atributo cuando-ISO para indicar los años anteriores a nuestra era.

 - -

+ + +

La valeur de l'attribut when doit être une représentation normalisée de la date ou de l'heure, ou des deux, dans l'un des formats spécifiés par le XML Schema Part 2: Datatypes Second Edition, selon le calendrier grégorien.

+

Pour la date, le format le plus courant est yyyy-mm-dd, mais on trouve aussi yyyy, --mm, ---dd, yyyy-mm, ou --mm-dd. Pour l'heure, on utilise le format hh:mm:ss.

+

Il faut noter qu'actuellement ce format ne permet pas d'utiliser la valeur 0000 pour représenter l'année précédant le début de l'ère chrétienne ; on doit utiliser la valeur -0001.

+ + +

El valor del atributo cuando es una serie que representa una fecha o una hora, o ambas, en cualquiera de los siguientes formatos: una fecha en los formatos estándares descritos por la XML Schema Part 2: Datatypes Second Edition, p.ej. en el formato más común aaaa-mm-dd, pero también aaaa, --mm, ---dd, aaaa-mm, o --mm-dd; una hora en el formato estándar descrito en XML Schema Part 2: Datatypes Second Edition, es decir. hh: mm: ss; o una fecha y una hora combinadas en los formatos estándares descritos en XML Schema Part 2: Datatypes Second Edition, es decir. aaaa-mm-ddThh: mm: ss. Obligatoriamente el valor de cuando aparecerá en un formato de fecha, tiempo, o ambos formatos combinados, de los reconocidos por W3C XML Schema Part 2: Datatypes Second Edition. Esto se dará si el componente de la fecha (eventualmente) es una fecha gregoriana o proléptica gregoriana. A la hora de esta escritura, W3C no permite el año 0000, que sería utilizado normalmente para representar el año 1 antes de nuestra era. Usando el sistema actual de W3C, el año 1 a.C. se indica con -0001, el año 2 a.C. con -0002, etc. Es la intención del grupo de trabajo del esquema de XML permitir 0000 como la representación léxica de 1 a.C. (que es un año bisiesto), -0001 se convertiria en la representación léxica de 2 a.C., -0002 de 3 a.C., etc. Así en algunos casos puede ser ventajoso utilizar en su lugar el atributo cuando-ISO para indicar los años anteriores a nuestra era.

+ + +

この属性の値は、グレゴリオ暦を用い、XML Schema Part 2: Datatypes Second Editionで定義されるいずれかの標準形式で正規化された日付や時刻、あるいはその組み合わせである。時間の属性としてもっともよく使われる形式は、yyyy-mm-ddだが、yyyy、--mm、---dd、yyyy-mm、--mm-ddも用いてもよい。時間については、hh:mm:ssが用いられる。この形式は、紀元前1年を表現するのに0000という値を用いることは現在のところ許容していないことには注意されたい。代わりに-0001という値を用いる必要がある。

-

+

属性whenの値は、日付や時間またはその組み合わを、 XML Schema Part 2: Datatypes Second Editionに従って示される。 当該日付の値が、グレゴリオ暦またはそれ以前の前グレゴリオ暦シス テムの場合に真となる。

-

+

現時点では、W3Cは年号の値として0000を認めていない。 この場合、一般的には、1BCE(紀元前1世紀)と記される。 現行W3Cのシステムを採用すれば、1BCEは-0001、2BCEは、 @@ -207,9 +212,9 @@ $Id$ 従って、場合によっては、属性when-isoにより紀元前 を示した方が便利かもしれない。

- + - \ No newline at end of file + diff --git a/P5/Source/Specs/att.datable.xml b/P5/Source/Specs/att.datable.xml index f2f6276aea..c54ce4b167 100644 --- a/P5/Source/Specs/att.datable.xml +++ b/P5/Source/Specs/att.datable.xml @@ -1,11 +1,5 @@ - + provides attributes for normalization of elements diff --git a/P5/Source/Specs/att.datcat.xml b/P5/Source/Specs/att.datcat.xml index b23fde6e4d..734d8d5964 100644 --- a/P5/Source/Specs/att.datcat.xml +++ b/P5/Source/Specs/att.datcat.xml @@ -1,22 +1,13 @@ - + - + provides attributes that are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by an external taxonomy, in this way establishing the identity of information containers and values, and providing means of interpreting them. - datacat属性とValueDatacat属性を提供する。これらがXML要素や属性を連携させる日付分類は、国際標準ISO - 12620:2009で定義されるものであり、にあるISOCatと呼ばれるWebリポジトリに格納されている。 + datacat属性とValueDatacat属性を提供する。これらがXML要素や属性を連携させる日付分類は、国際標準ISO + 12620:2009で定義されるものであり、にあるISOCatと呼ばれるWebリポジトリに格納されている。 provides a pointer to a definition of, and/or general @@ -24,8 +15,7 @@ $Id$ information container (element content or attribute value), by referencing an external taxonomy or ontology. If valueDatcat is present in the immediate context, this attribute takes on role (a), while valueDatcat performs role (b). - 指定された要素をISOcatの適切なデータカテゴリ（または複数のデータカテゴリ）と対応付けるPID（永続的識別子）を含む。 + 指定された要素をISOcatの適切なデータカテゴリ（または複数のデータカテゴリ）と対応付けるPID（永続的識別子）を含む。 @@ -35,8 +25,7 @@ $Id$ information about a value of an information container (element content or attribute value), by reference to an external taxonomy or ontology. Used especially where a contrast with datcat is needed. - 指定された要素の内容または指定された属性の値を、ISOcatの適切かつ単純なデータカテゴリ（または複数のデータカテゴリ）と対応付けるPID（永続的識別子）を含む。 + 指定された要素の内容または指定された属性の値を、ISOcatの適切かつ単純なデータカテゴリ（または複数のデータカテゴリ）と対応付けるPID（永続的識別子）を含む。 @@ -53,17 +42,15 @@ $Id$ -

The example below presents the TEI encoding of the name-value pair +

The example below presents the TEI encoding of the name-value pair <part of speech, common - noun>, where the name (key) part + noun>, where the name (key) part of speech is abbreviated as POS, and the value, common noun is symbolized by NN. The entire name-value pair is encoded by means of the element f. In TEI XML, that element acts as the container, labeled with the name attribute. Its contents may be complex or simple. In the case at hand, the content is the symbol NN.

The datcat attribute relates the feature name (i.e., the key) to the data - category part of speech, while the attribute valueDatcat relates the feature value to the data category common noun. Both these data categories + category part of speech, while the attribute valueDatcat relates the feature value to the data category common noun. Both these data categories should be defined in an external and preferably open reference taxonomy or ontology.

@@ -73,17 +60,14 @@ $Id$ -

NN is the symbol for common noun used e.g. in the CLAWS-7 tagset defined by the +

NN is the symbol for common noun used e.g. in the CLAWS-7 tagset defined by the University Centre for Computer Corpus Research on Language at the University of Lancaster. The very same data category used for tagging an early version of the British National Corpus, and coming from the BNC Basic (C5) tagset, uses the symbol NN0 (rather than NN). Making these values semantically interoperable would be extremely difficult without a human expert if they were not anchored in a single point of an established reference taxonomy of morphosyntactic - data categories. In the case at hand, the string http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545 is both + data categories. In the case at hand, the string http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545 is both a persistent identifier of the data category in question, as well as a pointer to a shared definition of common noun.

While the symbols NN, NN0, and many others (often coming from languages other than @@ -95,19 +79,12 @@ $Id$ part of speech. The reference taxonomy in this example is the CLARIN Concept Registry.

-

If the feature structure markup exemplified above is to be repeated many times in a single document, it is much more efficient to gather the persistent identifiers in a single place and to only reference them, implicitly or directly, from feature structure markup. The following example is much more concise than the one above and relies on the concepts of feature structure declaration and feature value library, discussed in chapter . - - - - - -

- +

The assumption here is that the relevant feature values are collected in a place that the annotation document in question has access to — preferably, a single document per linguistic resource, for example an fsdDecl that is XIncluded as a sibling of text or a @@ -117,13 +94,7 @@ $Id$ (most of them omitted). At the same time, this example shows one way of encoding a tagset, i.e., an established inventory of values of (in the case at hand) morphosyntactic categories. - - - - - - -

+

Note that these Guidelines do not prescribe a specific choice between datcat and valueDatcat in such cases. The former is the generic way of referencing a data category, whereas the latter is more specific, in that it references a data category that @@ -138,8 +109,7 @@ $Id$ as in the case of the example of f name="POS" above.

- NN + NN

Efficiency of this type of interoperable markup demands that the references to the particular @@ -147,42 +117,10 @@ $Id$ place within the project), rather than being repeated inside every entry. For the container elements, this can be achieved at the level of tagUsage, although here, the valueDatcat attribute should be used, because it is not the tagUsage element that is associated with the relevant data category, but rather the element pos (or case, etc.) that is described by - tagUsage: - - - - Contains the part of speech. - Contains information about the grammatical case that the described form is inflected for. - - - - + tagUsage: Contains the part of speech.Contains information about the grammatical case that the described form is inflected for.

Another possibility is to shorten the URIs by means of the prefixDef mechanism, as illustrated below: - - - - - - - - -

- isotope -
- - adj - - -

+
isotope
adj

This mechanism creates implications that are not always wanted, among others, in the case at hand, suggesting that the identifiers pos and adj belong to a namespace associated with the CLARIN Concept Repository (CCR), whereas that is solely a shorthand @@ -216,24 +154,20 @@ $Id$ UD syntactic relations - - acl: Clausal modifier of noun (adjectival clause) + acl: Clausal modifier of noun (adjectival clause) - - acl:relcl: relative clause modifier + acl:relcl: relative clause modifier - - advcl: Adverbial clause modifier + advcl: Adverbial clause modifier -

The above fragment was excerpted from the GB subset of the ParlaMint project in April 2023, and +

The above fragment was excerpted from the GB subset of the ParlaMint project in April 2023, and enriched with att.datcat attributes for the purpose of illustrating the mechanism described here.

Note that, in the ideal case, the values of att.datcat attributes @@ -250,20 +184,18 @@ $Id$ att.pointing class, in that it describes the object that is being referenced, rather than the referencing object.

- + part of speech (morphosyntactic category) - - + + -

Above, the fDecl uses targetDatcat, because if it were to use + +

Above, the fDecl uses targetDatcat, because if it were to use datcat, it would be asserting that it is an instance of the container data category part of speech, whereas it is not — it models a container (f) that encodes a part of speech. Note also that it is the f that is modeled above, not @@ -274,12 +206,9 @@ $Id$

The att.datcat attributes can be used for any sort of taxonomies. The example below illustrates their usefulness for describing usage domain labels in dictionaries on the example of the Diccionario da Lingua Portugueza by - António de Morais Silva, retro-digitised in the MORDigital project.

+ António de Morais Silva, retro-digitised in the MORDigital project.

- - @@ -287,15 +216,18 @@ $Id$ Medical and Health Sciences Ciências Médicas e da Saúde - + Medicine - + + + Medicina - + + + @@ -303,20 +235,16 @@ $Id$ - Med. -

In the Morais dictionary, the relevant domain labels are in the header, getting referenced inside the dictionary, from usg elements. The vocabulary used for dictionary-internal - labelling is in turn anchored in the MorDigital controlled vocabulary + labelling is in turn anchored in the MorDigital controlled vocabulary service of the NOVA University of Lisbon – School of Social Sciences and Humanities (NOVA FCSH).

 -

The TEI Abstract Model can be expressed as a hierarchy of attribute-value matrices (AVMs) of various types and of various levels of complexity, nested or grouped in various ways. At @@ -327,8 +255,8 @@ $Id$ by the two tags that constitues the value. An analogous example is an attribute name and the value of that attribute.

In a TEI XML example of two equivalent serializations expressing the name-value pair - <part-of-speech,common-noun>, namely - <pos>commonNoun</pos> and + <part-of-speech,common-noun>, namely + <pos>commonNoun</pos> and pos="common-noun", one would classify the element pos and the attribute pos as containers (mapping onto the first member of the relevant name-value pair), while the character data @@ -344,19 +272,15 @@ $Id$

The value of the att.datcat attributes should be a PID (persistent identifier) that points to a specific — and, ideally, shared — taxonomy or ontology. Among the resources that can, to a lesser or greater extent, be used as inventories - of (more or less) standardized linguistic categories are the GOLD ontology, CLARIN CCR, OLiA, or TermWeb's DatCatInfo, and also the Universal Dependencies inventory, on the + of (more or less) standardized linguistic categories are the GOLD ontology, CLARIN CCR, OLiA, or TermWeb's DatCatInfo, and also the Universal Dependencies inventory, on the assumption that its URIs are going to persist. It is imaginable that a project may choose to address a local taxonomy store instead, but this risks losing the advantage of - interchangeability with other projects.

+ interchangeability with other projects.

Historically, datcat and valueDatcat originate from the (now obsolete) ISO 12620:2009 standard, describing the data model and procedures for a Data Category Registry (DCR). The current version of that standard, ISO 12620-1, does not standardize the serialization of pointers, merely mentioning the TEI att.datcat as - an example.

+ an example.

Note that no constraint prevents the occurrence of a combination of att.datcat attributes: the fDecl element, which is a natural bearer of the targetDatcat @@ -365,8 +289,7 @@ $Id$

ISO - 12620:2009は、データ分類のレジストリ（DCR）に関するデータモデルと手続きについての国際標準である。データ分類は、一つの言語の構造における基本的な記述子として定義される。DCRのデータモデルでは、個々のデータ分類には、ユニークな永続的識別子（PID)、つまり、URIが割り当てられる。DCRからデータ分類を利用する言語資源、あるいは、できることならそのスキーマは、このPIDを用いて参照すべきである。TEI文書のようなXMLベースの資源(にて参照可能)に関しては、ISO 12620:2009 付録 + 12620:2009は、データ分類のレジストリ（DCR）に関するデータモデルと手続きについての国際標準である。データ分類は、一つの言語の構造における基本的な記述子として定義される。DCRのデータモデルでは、個々のデータ分類には、ユニークな永続的識別子（PID)、つまり、URIが割り当てられる。DCRからデータ分類を利用する言語資源、あるいは、できることならそのスキーマは、このPIDを用いて参照すべきである。TEI文書のようなXMLベースの資源(にて参照可能)に関しては、ISO 12620:2009 付録 Aに、datcat属性とvalueDatcat属性を提供する小さなデータ分類参照のXML語彙がある。

 diff --git a/P5/Source/Specs/att.declarable.xml b/P5/Source/Specs/att.declarable.xml index 950e726ef4..ab5c5ec20b 100644 --- a/P5/Source/Specs/att.declarable.xml +++ b/P5/Source/Specs/att.declarable.xml @@ -1,11 +1,5 @@ - + provides attributes for those elements in the TEI header which @@ -32,7 +26,9 @@ its parent is selected. défaut quand son élément parent a été sélectionné. indica si el elemento es seleccionado automáticamente o no cuando es seleccionado el padre indica se l'elemento è selezionato automaticamente quando è selezionato il genitore - + + + false diff --git a/P5/Source/Specs/att.declaring.xml b/P5/Source/Specs/att.declaring.xml index d3e2c3489a..a37d82cdf9 100644 --- a/P5/Source/Specs/att.declaring.xml +++ b/P5/Source/Specs/att.declaring.xml @@ -1,11 +1,5 @@ - + provides attributes for elements which may be independently associated with a particular declarable element within the header, thus overriding the inherited default for that element. @@ -35,7 +29,9 @@ attribute and its content. identifica uno o más elementos declarables al interno del encabezado, los cuales son válidos para el elemento al cual es adscrito el atributo en cuestión y su contenido. identifica uno o più elementi dichiarabili all'interno dell'intestazione, i quali sono validi per l'elemento a cui è assegnato l'attributo in questione e il suo contenuto - + + + @@ -58,4 +54,4 @@ with individual parts of a TEI text are fully defined in chapter - \ No newline at end of file + diff --git a/P5/Source/Specs/att.deprecated.xml b/P5/Source/Specs/att.deprecated.xml index 652ed437fc..ed03cccdad 100644 --- a/P5/Source/Specs/att.deprecated.xml +++ b/P5/Source/Specs/att.deprecated.xml @@ -1,11 +1,5 @@ - + provides attributes indicating how a deprecated feature will be treated in future releases. @@ -32,10 +26,11 @@ $Id$ - - - - + + + + + @@ -65,7 +60,7 @@ $Id$ the future. E.g., the documentation for such a construct might include the phrase warning: deprecated in red.

- +

この属性の値は、（yyyy-mm-ddの形式で）日付を表し、属性がODDに追加された日付より後である必要がある。技術的には、この属性は、指定された日付まで定義されているマークアップ言語の将来のリリースで構造を残す意図のみを表明し、その日付以降に何が起こるかについて主張しない。実際には、validUntil日付の直後に定義されるマークアップ言語の将来のリリースからコンストラクトが削除されることが期待されます。

ODDプロセッサは、通常、validUntil日付が過去のものである仕様要素を処理しない。ODDプロセッサは、通常、validUntilの日付を持つコンストラクトについてユーザに警告する。例えば、そのような構造のドキュメントには、warning：deprecatedというフレーズが赤で表示される。

diff --git a/P5/Source/Specs/att.dimensions.xml b/P5/Source/Specs/att.dimensions.xml index 32c642bdbe..d73fe568e9 100644 --- a/P5/Source/Specs/att.dimensions.xml +++ b/P5/Source/Specs/att.dimensions.xml @@ -1,11 +1,5 @@ - + provides attributes for describing the size of physical objects. @@ -30,7 +24,9 @@ $Id$ noms des unités utilisées pour la mesure. especifica las unidades usadas para la medición. specifica le unità usate per la misurazione - + + + centimetres @@ -83,7 +79,9 @@ $Id$ 当該単位の大きさを示す。 spécifie la longueur dans les unités indiquées specifica la lunghezza nelle unità indicate - + + + indicates the size of the object concerned using a project-specific vocabulary combining @@ -92,7 +90,9 @@ $Id$ un vocabulaire spécifique à un projet qui combine la quantité et l'unité dans une chaîne seule de mots. 単一の文字列の数量と単位を組み合わせたプロジェクト固有の語彙を使用して、関連するオブジェクトのサイズを示す。 - + + + @@ -108,7 +108,9 @@ $Id$ characterizes the precision of the values specified by the other attributes. caractérise la précision des valeurs spécifiées par les autres attributs. 他の属性によって指定された値の精度を特徴付ける。 - + + + where the measurement summarizes more than one observation, specifies the applicability @@ -122,7 +124,9 @@ $Id$ casos en que se mida más de un objeto. indica l'applicabilità della misurazione, laddove venga misurato più di un oggetto - + + + measurement applies to all instances. @@ -161,4 +165,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/att.divLike.xml b/P5/Source/Specs/att.divLike.xml index c48a02c6c4..b1d7225c9d 100644 --- a/P5/Source/Specs/att.divLike.xml +++ b/P5/Source/Specs/att.divLike.xml @@ -1,11 +1,5 @@ - + provides attributes common to all elements which behave in the same way as divisions. @@ -36,7 +30,9 @@ $Id$ précise l'organisation du contenu de la division especifica cómo está organizado el contenido de una división textual. specifica come è organizzato il contenuto della partizione testuale - + + + uniform @@ -79,7 +75,9 @@ logique et doivent être traités dans l'ordre séquentiel la source originale et dans ce cas, de quelle partie. indica si la división es una muestra de la fuente original y, en ese caso, de que parte de este se trata indica se la partizione è un campione del testo originario e, in tal caso, da quale parte di questo è tratta - + + + complete diff --git a/P5/Source/Specs/att.docStatus.xml b/P5/Source/Specs/att.docStatus.xml index da32c21536..b8d0cf554b 100644 --- a/P5/Source/Specs/att.docStatus.xml +++ b/P5/Source/Specs/att.docStatus.xml @@ -1,11 +1,5 @@ - + provides attributes for use on metadata elements @@ -16,7 +10,9 @@ $Id$ describes the status of a document either currently or, when associated with a dated element, at the time indicated. 現在の、もしくは日時に関連づけられた要素にあっては、指定された時点における文書のステータスを記述する。 - + + + draft @@ -48,4 +44,4 @@ associated with a dated element, at the time indicated. - \ No newline at end of file + diff --git a/P5/Source/Specs/att.duration.iso.xml b/P5/Source/Specs/att.duration.iso.xml index 82d1ebdcf2..d0c7235169 100644 --- a/P5/Source/Specs/att.duration.iso.xml +++ b/P5/Source/Specs/att.duration.iso.xml @@ -1,11 +1,5 @@ - + provides attributes for recording normalized temporal durations. @@ -31,7 +25,9 @@ indique la longueur de cet élément dans le temps indica la durata nel tempo dell'elemento indica la longitud de este elemento en el tiempo. - + + + @@ -58,4 +54,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/att.duration.w3c.xml b/P5/Source/Specs/att.duration.w3c.xml index cb8d9d531d..7d46c66dc9 100644 --- a/P5/Source/Specs/att.duration.w3c.xml +++ b/P5/Source/Specs/att.duration.w3c.xml @@ -1,11 +1,5 @@ - + provides attributes for recording normalized temporal durations. @@ -34,7 +28,9 @@ $Id$ temps indica la durata nel tempo di tale elemento indica la longitud de este elemento en el tiempo. - + + + diff --git a/P5/Source/Specs/att.duration.xml b/P5/Source/Specs/att.duration.xml index 9b4682e57b..827b588e44 100644 --- a/P5/Source/Specs/att.duration.xml +++ b/P5/Source/Specs/att.duration.xml @@ -1,11 +1,5 @@ - + @@ -65,4 +59,4 @@ $Id$ アも存在する。

- \ No newline at end of file + diff --git a/P5/Source/Specs/att.editLike.xml b/P5/Source/Specs/att.editLike.xml index 92a0a4ab62..b50c0c97ab 100644 --- a/P5/Source/Specs/att.editLike.xml +++ b/P5/Source/Specs/att.editLike.xml @@ -1,11 +1,5 @@ - + provides attributes describing the nature of an encoded scholarly intervention or @@ -32,7 +26,9 @@ $Id$ fiabilidad o precisión de la intervención o interpretación. indica il carattere delle prove a sostegno dell'affidabilità o accuratezza dell'intervento o interpretazione - + + + there is internal evidence to support the intervention. @@ -76,7 +72,9 @@ $Id$ indicates whether this is an instant revision or not. これがにわか仕込みの修正か否かを示す。 - + + + false @@ -97,11 +95,13 @@ $Id$ intervención editorial en un texto, por ejemplo una corrección, una interpretación, la fecha o incluso la signatura de los manuscritos etc.

-

当該クラスは、あらゆる編集上の調整、例えば、原稿に対する修正や解釈、日時や場所の特定などを示すために、一般には使用される。

 + +

当該クラスは、あらゆる編集上の調整、例えば、原稿に対する修正や解釈、日時や場所の特定などを示すために、一般には使用される。

+ - - - - + + + + - \ No newline at end of file + diff --git a/P5/Source/Specs/att.edition.xml b/P5/Source/Specs/att.edition.xml index 39e2d8db4c..8401a16006 100644 --- a/P5/Source/Specs/att.edition.xml +++ b/P5/Source/Specs/att.edition.xml @@ -1,11 +1,5 @@ - + provides attributes identifying the source edition from which @@ -23,7 +17,9 @@ $Id$ fournit un identifiant arbitraire pour l'édition source dans laquelle la caractéristique associée (par exemple, une page, une colonne ou un saut de ligne) apparaît à ce point du texte. 関連する属性（ページ・段落・行の切れ目）がテキストのこの地点において発生するソースのエディションについての印やその他の任意の識別子を提供する。 - + + + edition reference @@ -32,7 +28,9 @@ $Id$ the associated feature (for example, a page, column, or line break) occurs at this point in the text. このポインタが示すのは、当該テキスト中に現れる（頁や段、行等の）関連する素性が生じる元の版である。 - + + + @@ -60,4 +58,4 @@ $Id$ con-sciousness;

 - \ No newline at end of file + diff --git a/P5/Source/Specs/att.enjamb.xml b/P5/Source/Specs/att.enjamb.xml index d502201125..88d2b29ebf 100644 --- a/P5/Source/Specs/att.enjamb.xml +++ b/P5/Source/Specs/att.enjamb.xml @@ -1,11 +1,5 @@ - + enjambement @@ -35,7 +29,9 @@ $Id$ 句またがりが起こる行末を示す。 indica que el final de un verso está caracterizada por un encabalgamiento. indica che la fine di un verso è caratterizzata da un enjambement - + + + the line is end-stopped @@ -92,7 +88,9 @@ enjambement is not of particular interest.

valeur par défaut no ; ceci permet d'omettre totalement l'attribut s'il n'est pas intéressant de noter un enjambement.

-

一般的には、句またがりが現れるとことで、当該属性に値yesが付 与される。または、その程度により、値weakかstrong が付与される。属性値が付与されていない場合でも、当該属性はデフォルト値として、値noを想定しない。従って、句またがりに関心を置かない場合には、当該属性を省略できる。

 + +

一般的には、句またがりが現れるとことで、当該属性に値yesが付 与される。または、その程度により、値weakかstrong が付与される。属性値が付与されていない場合でも、当該属性はデフォルト値として、値noを想定しない。従って、句またがりに関心を置かない場合には、当該属性を省略できる。

+ diff --git a/P5/Source/Specs/att.entryLike.xml b/P5/Source/Specs/att.entryLike.xml index 34db8ea57b..dde563fcb2 100644 --- a/P5/Source/Specs/att.entryLike.xml +++ b/P5/Source/Specs/att.entryLike.xml @@ -1,11 +1,5 @@ - + provides attributes used to distinguish @@ -36,7 +30,9 @@ $Id$ contienen de diferentes tipos. indica il tipo di voce, nei dizionari con tipi multipli. - + + + main @@ -167,4 +163,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/att.formula.xml b/P5/Source/Specs/att.formula.xml index 64257e3b07..ed06f9350e 100644 --- a/P5/Source/Specs/att.formula.xml +++ b/P5/Source/Specs/att.formula.xml @@ -1,34 +1,30 @@ - + provides attributes for defining a mathematical formula. A formula is provided to describe a mathematical calculation such as a conversion between measurement systems. - + + + - - - - - - - - - The stadium was a Roman unit of linear measurement equivalent to 625 pedes, or Roman feet. - - - - - + + + + + + + + + The stadium was a Roman unit of linear measurement equivalent to 625 pedes, or Roman feet. + + + + + diff --git a/P5/Source/Specs/att.fragmentable.xml b/P5/Source/Specs/att.fragmentable.xml index 0be8deabec..e14f294b55 100644 --- a/P5/Source/Specs/att.fragmentable.xml +++ b/P5/Source/Specs/att.fragmentable.xml @@ -1,11 +1,5 @@ - + provides attributes for representing @@ -20,7 +14,9 @@ $Id$ stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers. 通常は他の階層関係のオーバーラップなどに起因して、親要素が何らかの形で断片化されているかどうかを示す。例えば、二つ以上の韻文詩で分割された発話、頁区切りをまたぐ段落、二人の話者に分割された韻文の一行など。 - + + + N @@ -61,7 +57,9 @@ $Id$ should be used only where it is clear how the element may be reconstituted.

-

I、M、またはFという値は、要素の再構成方法が明らかな場合にのみ使用する。

 + +

I、M、またはFという値は、要素の再構成方法が明らかな場合にのみ使用する。

+ - \ No newline at end of file + diff --git a/P5/Source/Specs/att.gaijiProp.xml b/P5/Source/Specs/att.gaijiProp.xml index bccac95f5d..80eb63b18d 100644 --- a/P5/Source/Specs/att.gaijiProp.xml +++ b/P5/Source/Specs/att.gaijiProp.xml @@ -1,82 +1,77 @@ - + - - provides attributes for defining the properties of + + provides attributes for defining the properties of non-standard characters or glyphs. - liefert Attribute zur Definition der Eigenschaften + liefert Attribute zur Definition der Eigenschaften von nicht standardisierten Zeichen und Glyphen. - fornisce attributi per definire le proprietà di caratteri o glifi non standard - - - provides the name of the character or glyph + fornisce attributi per definire le proprietà di caratteri o glifi non standard + + + provides the name of the character or glyph property being defined. - - - - - - provides the value of the character or + + + + + + provides the value of the character or glyph property being defined. - - - - - - specifies the version number of the Unicode + + + + + + specifies the version number of the Unicode Standard in which this property name is defined. - gibt die Versionsnummer eines externen + gibt die Versionsnummer eines externen Standards an, in dem dieser Eigenschaftsname definiert ist. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

In this example a definition for the Unicode property Decomposition Mapping + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

In this example a definition for the Unicode property Decomposition Mapping is provided.

- - - -

All name-only attributes need an xs:boolean attribute value inside value.

- - - - + + + + + +

All name-only attributes need an xs:boolean attribute value inside value.

+ + + + diff --git a/P5/Source/Specs/att.global.analytic.xml b/P5/Source/Specs/att.global.analytic.xml index ae354ea3ff..2d31aa74f5 100644 --- a/P5/Source/Specs/att.global.analytic.xml +++ b/P5/Source/Specs/att.global.analytic.xml @@ -1,11 +1,5 @@ - + provides additional global attributes for associating specific analyses or @@ -37,9 +31,9 @@ element on which the ana attribute appears. indica uno o più elementi che contengono interpretazioni dell'elemento specificato dall'attributo ana - - - + + +

When multiple values are given, they may reflect either multiple divergent interpretations of an ambiguous text, or multiple @@ -64,4 +58,4 @@ contexts.

- \ No newline at end of file + diff --git a/P5/Source/Specs/att.global.change.xml b/P5/Source/Specs/att.global.change.xml index ce241257d7..77de760ff9 100644 --- a/P5/Source/Specs/att.global.change.xml +++ b/P5/Source/Specs/att.global.change.xml @@ -1,11 +1,5 @@ - + provides attributes allowing its member @@ -18,8 +12,10 @@ associated. a state or revision campaign to which the element bearing this attribute and its children have been assigned by the encoder. この属性とその子を持つ要素が符号化する人によって割り当てられた状態または改定を記述する1つまたは複数のchange要素を示す。 - + + + - \ No newline at end of file + diff --git a/P5/Source/Specs/att.global.facs.xml b/P5/Source/Specs/att.global.facs.xml index 1edcc4cdca..ccdfb25574 100644 --- a/P5/Source/Specs/att.global.facs.xml +++ b/P5/Source/Specs/att.global.facs.xml @@ -1,11 +1,5 @@ - + provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. @@ -41,4 +35,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/att.global.linking.xml b/P5/Source/Specs/att.global.linking.xml index ccc1a64726..96c94c4eb7 100644 --- a/P5/Source/Specs/att.global.linking.xml +++ b/P5/Source/Specs/att.global.linking.xml @@ -1,11 +1,5 @@ - + provides a set of attributes for hypertextual linking. @@ -33,8 +27,9 @@ $Id$ correspondance avec l'élément en question. señala los elementos que presentan una correspondencia con el elemento corriente. punta a elementi che hanno una qualche corrispondenza con l'elemento corrente - - + + + @@ -58,32 +53,29 @@ $Id$

In this example a group contains two texts, each containing the same document in a different language. The correspondence is indicated using corresp. The language is indicated using xml:lang, whose value is inherited; both the tag with the corresp and the tag pointed to by the corresp inherit the value from their immediate parent.

- - - - - London - The city of London... - - - - - London - -

Allegorical character representing the city of London.

- - - - London’s Genius - -

Personification of London’s genius. Appears as an + + + London + The city of London... + + + + London + +

Allegorical character representing the city of London.

+ + + + London’s Genius + +

Personification of London’s genius. Appears as an allegorical character in mayoral shows.

- - - + + +

In this example, a place element containing information about the city of London is linked with two person elements in a literary personography. This correspondence represents a slightly looser relationship than the one in the @@ -91,7 +83,6 @@ $Id$ substituted for the physical city, or vice versa, but there is obviously a correspondence between them.

 - synchronous @@ -108,7 +99,9 @@ $Id$ pointe vers des éléments qui sont synchrones avec l'élément en question. señala los elementos que son sincrónicos con el elemento corriente. punta a elementi sincroni rispetto all'elemento corrente - + + + points to an element that is the same as the current @@ -119,7 +112,9 @@ $Id$ pointe vers un élément identique à l'élément en question. señala el elementos que se corresponde exactamente con el elemento corriente. punta a un elemento che corrisponde esattamente all'elemento corrente - + + + points to an element of which the current element is a @@ -131,7 +126,9 @@ $Id$ est une copie. señala un elemento del que el elemento corriente es una copia. punta a un elemento di cui l'elemento corrente è una copia - + + +

Any content of the current element should be ignored. Its true content is that of the element being pointed at.

@@ -158,8 +155,12 @@ $Id$ virtuel dont l'élément en question est une partie. punta all'elemento seguente all'interno di un aggregazione virtuale di cui l'elemento corrente fa parte - -

It is recommended that the element indicated be of the same type as the element bearing this attribute.

 + + + + +

It is recommended that the element indicated be of the same type as the element bearing this attribute.

+

指定された要素も、この属性を持つ要素と同じ型であることが推奨される。

 @@ -181,8 +182,12 @@ $Id$ señala al elemento precedente de una adición virtual, de la cual el elemento corriente forma parte. punta all'elemento precedente all'interno di un aggregazione virtuale di cui l'elemento corrente fa parte - -

It is recommended that the element indicated be of the same type as the element bearing this attribute.

 + + + + +

It is recommended that the element indicated be of the same type as the element bearing this attribute.

+

指定された要素も、この属性を持つ要素と同じ型であることが推奨される。

 @@ -197,7 +202,9 @@ $Id$ exclusive à l'élément en question. señala los elementos que estan en relación de alternancia exclusiva con el elemento corriente. punta a elementi in relazione di alternanza esclusiva con l'elemento corrente - + + + selects one or more alternants; if one alternant is @@ -217,7 +224,9 @@ $Id$ sélectionnées. selecciona una o más alternativas; si se selecciona una de las alternativas, la ambigüidad o la incerteza se indica como resuelta; si se selecciona más de una alternativa, el grado de ambigüidad o incerteza se indica como reducido del número de las alternativas no seleccionadas. seleziona una o più alternative; se viene selezionata una delle alternative, l'ambiguità o incertezza è indicata come risolta; se viene selezionata più di un'alternativa, il grado di ambiguità o incertezza è indicato come ridotto dal numero delle alternative non selezionate - + + +

This attribute should be placed on an element which is superordinate to all of the alternants from which the @@ -238,4 +247,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/att.global.rendition.xml b/P5/Source/Specs/att.global.rendition.xml index 34340ef03f..1b09b3fe3a 100644 --- a/P5/Source/Specs/att.global.rendition.xml +++ b/P5/Source/Specs/att.global.rendition.xml @@ -1,22 +1,11 @@ - + provides rendering attributes common to all elements in the TEI encoding scheme. TEIの符号化スキーマにおけるすべての要素に共通するレンダリング属性を提供する。 - - - - - rendition 번역 @@ -34,7 +23,9 @@ $Id$ proporcionado en el texto fuente. indica come l'elemento in questione è stato reso o rappresentato nel testo originario - + + + To The Duchesse of Newcastle, @@ -76,14 +67,18 @@ $Id$ varía demasiado de proyecto a proyecto. Observar algunas convenciones que puedan resultar útiles en los puntos indicados en las guías de consulta.

 -

本ガイドラインでは、当該属性rendの値として推奨するものはない。活字化の特徴は様々であり、それらのどれを採用するかはプロジェクトごとでおそろしく異なるからである。当ガイドラインでは、有用な記述法があれば、その都度示すことになっている。rend属性の値は、空白によって区切られる順序不定の個々のトークンの集合である。

 + +

本ガイドラインでは、当該属性rendの値として推奨するものはない。活字化の特徴は様々であり、それらのどれを採用するかはプロジェクトごとでおそろしく異なるからである。当ガイドラインでは、有用な記述法があれば、その都度示すことになっている。rend属性の値は、空白によって区切られる順序不定の個々のトークンの集合である。

+ contains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text なんらかの形式的スタイル定義言語においてソーステキスト内の当該要素のレンダリングや表示を定義する際の表現を含む。 - + + + To The Duchesse of Newcastle, On Her @@ -103,7 +98,8 @@ the TEI header.

空白を区切り記号とするrendの属性値とは異なり、style属性は空白を含んでもよい。この属性は資料における行に埋め込まれたスタイル情報を記録するためのものであり、何らかの出力を対象とするものではない。

この属性の値を表現する形式言語はTEIヘッダにおいてstyleDefDecl要素を用いて指定されてもよい。

-

もしstyleとrenditionの両方が一つの要素に現れる場合、styleはrenditionを上書きもしくは補完する。styleはrendと同時に用いられるべきではない。後者は形式的なスタイル定義言語を採用しているわけではないから。

 +

もしstyleとrenditionの両方が一つの要素に現れる場合、styleはrenditionを上書きもしくは補完する。styleはrendと同時に用いられるべきではない。後者は形式的なスタイル定義言語を採用しているわけではないから。

+ points to a description of the rendering or presentation used for this element in the @@ -116,7 +112,9 @@ the TEI header.

présentation utilisés pour cet élément dans le texte source indica una descrizione della resa o della presentazione utilizzate per tale elemento nel testo di partenza - + + + To The Duchesse of Newcastle, On Her @@ -151,7 +149,8 @@ the TEI header.

属性renditionは、XHTMLの属性classと大変 似たように使用される。但し、重要な違いとして、当該属性は、元資 料の表現を記述するものであり、スクリーン上または紙上でどう表示 されているかを示すものではない。

もしrendition属性がCSSのような形式言語において定義されるスタイル定義を参照するのに用いられているなら、rend属性と同時に用いないことが推奨される。属性renditionと属性rendの両方が使用されている場合、後者の値が前者の値を上書きする、または補うと判断される。

-

当該属性値となるURIは、属性schemeで提示されているス タイル言語により、当該表現を定義する要素renditionを示すべきである。

 +

当該属性値となるURIは、属性schemeで提示されているス タイル言語により、当該表現を定義する要素renditionを示すべきである。

+

L'attribut rendition est employé à peu près de la même manière que l'attribut class défini pour XHTML mais avec cette sérieuse différence que sa fonction @@ -175,10 +174,8 @@ the TEI header.

indicado por el atributo scheme (esquema).

 - - - \ No newline at end of file + diff --git a/P5/Source/Specs/att.global.responsibility.xml b/P5/Source/Specs/att.global.responsibility.xml index 9003a64b4d..f794f0a61f 100644 --- a/P5/Source/Specs/att.global.responsibility.xml +++ b/P5/Source/Specs/att.global.responsibility.xml @@ -1,11 +1,5 @@ - + provides attributes indicating the agent @@ -56,7 +50,9 @@ $Id$ interpretación, p.ej. un editor o un transcriptor. indica il responsabile dell'intervento o interpretazione, per esempio un curatore o trascrittore - + + +

To reduce the ambiguity of a resp pointing directly to a person or organization, we @@ -66,9 +62,12 @@ $Id$ element which clarifies the exact role played by the agent. Pointing to multiple respStmts allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, - transcribing, encoding, editing, proofing etc.).

 -

resp が直接個人や組織を指した場合のあいまいさを減らすため、resp は行為者 (person or org) ではなく respStmt、author、editor などその行為者の正確な役割を明示するエレメントを指して用いることを推奨する。エンコード者は respStmt にTEI文書内の役割分担を明確に記述できる（作成・翻刻・エンコード・編集・校正など。

 - + transcribing, encoding, editing, proofing etc.).

+ + +

resp が直接個人や組織を指した場合のあいまいさを減らすため、resp は行為者 (person or org) ではなく respStmt、author、editor などその行為者の正確な役割を明示するエレメントを指して用いることを推奨する。エンコード者は respStmt にTEI文書内の役割分担を明確に記述できる（作成・翻刻・エンコード・編集・校正など。

+ + Blessed are the @@ -79,7 +78,7 @@ $Id$ - Punkes, Panders, baſe extortionizing + Punkes, Panders, baſe extortionizing slanues, @@ -91,7 +90,6 @@ $Id$ - @@ -99,4 +97,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/att.global.source.xml b/P5/Source/Specs/att.global.source.xml index 82b38e3da8..11bfe38579 100644 --- a/P5/Source/Specs/att.global.source.xml +++ b/P5/Source/Specs/att.global.source.xml @@ -1,11 +1,5 @@ - + provides attributes used by elements to point to an @@ -22,19 +16,11 @@ $Id$ - - + + When used on a schema description element (like ), the @source attribute - should have only 1 value. (This one has .) + should have only 1 value. (This one has .) @@ -62,7 +48,7 @@ $Id$ source should have only one value; when used on other elements multiple values are permitted.

- +

source 属性は外部ソースを指し示す。schemaSpec や moduleRef といったスキーマの構成要素を記述する要素で用いられた場合は、 その定義しようとしているオブジェクトの構成要素の宣言が得られるソースを特定する。 @@ -70,7 +56,7 @@ $Id$ 場所は何らかの URI、例えば絶対 URI や相対 URI、prefixDef に定められた方法で絶対 URI に展開できる私用形式の URI で与えることができる。 複数の場所が指定された場合、デフォルトでは要求されたソースがそれらのリソースの組み合わせによって得られるものと想定される。

- + @@ -116,4 +102,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/att.global.xml b/P5/Source/Specs/att.global.xml index 5206c756f7..670015a43a 100644 --- a/P5/Source/Specs/att.global.xml +++ b/P5/Source/Specs/att.global.xml @@ -1,11 +1,5 @@ - + provides attributes common to all elements in the TEI encoding scheme. @@ -27,7 +21,6 @@ $Id$ - identifier @@ -46,7 +39,9 @@ $Id$ al cual se asocia el atributo. assegna un identificatore unico all'elemento a cui è associato l'attributo - + + +

The xml:id attribute may be used to specify a canonical reference for an element; see section .

@@ -60,7 +55,7 @@ $Id$ para un elemento; ver la sección .

 -

xml:id属性は、その要素に対する基準的形式の参照を表すために用いてもよい。詳細は節を参照のこと。

+

xml:id属性は、その要素に対する基準的形式の参照を表すために用いてもよい。詳細は節を参照のこと。

 @@ -81,7 +76,9 @@ $Id$ que no es necesariamente único en el documento. assegna un numero (o altra etichetta) a un elemento che non è necessariamente unico all'interno del documento - + + +

The value of this attribute is always understood to be a single token, even if it contains space or other punctuation characters, and need not be composed of numbers only. It is typically used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system @@ -97,7 +94,9 @@ $Id$ capítulos, de las secciones, de los items de una lista, etc.; puede también ser utilizado en la especificación de un sistema de referencia estándar para el texto.

 -

この属性の値は、もし空白やその他の区切り符号があったとしても、つねにひとまとまりのトークンとして解釈され、また数字のみで構成される必要はない。この属性は典型的には章や節、リスト等の構成要素の付番に用いられる。テキストの標準的な参照体系の仕様に含めることができる。

 + +

この属性の値は、もし空白やその他の区切り符号があったとしても、つねにひとまとまりのトークンとして解釈され、また数字のみで構成される必要はない。この属性は典型的には章や節、リスト等の構成要素の付番に用いられる。テキストの標準的な参照体系の仕様に含めることができる。

+ language @@ -123,7 +122,9 @@ $Id$ utilizzando i codici tratti da RFC 3066 - + + +

… The consequences of @@ -162,7 +163,7 @@ $Id$ l'attributxml:lang de l'élément immédiatement supérieur est héritée ; c'est pour cette raison qu'une valeur devrait toujours être attribuée à l'élément du plus haut niveau hiérarchique (TEI).

-

La valeur doit être conforme au BCP 47. Si la +

La valeur doit être conforme au BCP 47. Si la valeur est un code d'usage privé (c'est-à-dire commence par x- ou contient -x-), il devrait correspondre à la valeur d'un attribut ident d'un élément language fourni dans l'en-tête TEI du document courant.

@@ -170,11 +171,10 @@ $Id$

Si no se especifica ningún valor para xml:lang, el valor de xml:lang para el elemento inmediatamente englobado, se hereda; por esta razón, un valor se debe especificar siempre en el elemento exterior (TEI).

-

xml:lang の値は、直接の親要素、そのまた親要素からというように、文書の上位階層から継承されてくる。できるだけ高い適切な階層に xml:lang を指定するのが一般には望ましいが、teiHeader には関連するリソース要素と異なるデフォルト値が必要となったり、一つのTEI文書が多くの言語のテキストを含みうることには注意されたい。登録された言語タグの正式なリストはIANAが管理しており、 から確認できる。言語タグの構造についての良い概説は を、手順を追った実用的なガイドは を参照されたい。利用する値は、BCP 47 に準拠しなければならない。もし値が私用コード（x- から始まったり -x- を含む）ならば、その ident 属性と一致する値を持つ language 要素をTEIヘッダ内に追加して内容を説明すべきである。この説明は私用コード以外にも任意で追加できるが、IETFInternet Engineering Task Force による定義と整合していなければならない。

 + +

xml:lang の値は、直接の親要素、そのまた親要素からというように、文書の上位階層から継承されてくる。できるだけ高い適切な階層に xml:lang を指定するのが一般には望ましいが、teiHeader には関連するリソース要素と異なるデフォルト値が必要となったり、一つのTEI文書が多くの言語のテキストを含みうることには注意されたい。登録された言語タグの正式なリストはIANAが管理しており、 から確認できる。言語タグの構造についての良い概説は を、手順を追った実用的なガイドは を参照されたい。利用する値は、BCP 47 に準拠しなければならない。もし値が私用コード（x- から始まったり -x- を含む）ならば、その ident 属性と一致する値を持つ language 要素をTEIヘッダ内に追加して内容を説明すべきである。この説明は私用コード以外にも任意で追加できるが、IETFInternet Engineering Task Force による定義と整合していなければならない。

+ - - - provides a base URI reference with which applications can resolve relative URI references into absolute URI references. @@ -192,32 +192,31 @@ $Id$ assegna un riferimento URI di base grazie al quale eventuali applicazioni possono analizzare riferimenti URI relativi come riferimenti URI assoluti - + + +
Selections from The Collected Letters of Robert Southey. Part 1: 1791-1797 - - Robert Southey to Grosvenor Charles Bedford, 3 April 1792. + Robert Southey to Grosvenor Charles Bedford, 3 April 1792. - - Robert Southey to Anna Seward, 18 September 1793. + Robert Southey to Anna Seward, 18 September 1793. - - Robert Southey to Robert Lovell, 5-6 April, 1794. + Robert Southey to Robert Lovell, 5-6 April, 1794.
- + provides attributes describing aspects of the hand in which a @@ -28,14 +22,18 @@ believed to be responsible for this hand. identifiant pour le scribe reconnu comme responsable de cette main. assegna un nome o altro identificatore standard al trascrittore che si ritiene corrisponda alla mano in questione asigna un nombre u otro identificador estándard para el transcriptor que se identifica con la mano en cuestión. - + + + points to a full description of the scribe concerned, typically supplied by a person element elsewhere in the description. 問題の筆写者についての詳細な記述へポイントする。典型的には記述のどこかでperson要素によって補われる。 - + + + characterizes the particular script or writing style used by @@ -54,14 +52,18 @@ this hand, for example secretary, copperplate< segretario, incisione su rame, Chancery, italiano, ecc. caracteriza un determinado estilo de escritura utilizado por la mano en cuestión, p.ej. secretario, grabado sobre cobre, cancelleresco, italiano, etc. - + + + points to a full description of the script or writing style used by this hand, typically supplied by a scriptNote element elsewhere in the description. 問題の筆体や書記スタイルについての詳細な記述へポイントする。典型的には記述のどこかでscriptNote要素によって補われる。 - + + + describes the tint or type of ink, e.g. brown, or other @@ -76,7 +78,9 @@ writing medium, e.g. pencil descrive la tinta o il tipo di inchiostro, per esempio marrone, o altri strumenti di scrittura, per esempio matita describe la tinta o el tipo de tinta, p.ej. marrón, u otros instrumentos de escritura, p.ej. lápiz. - + + + specifies how widely this hand is used in the manuscript. @@ -87,7 +91,9 @@ writing medium, e.g. pencil main dans le manuscrit. specifica in quale misura è utilizzata la mano in questione nel manoscritto especifica en qué medida es utilizada la mano en el manuscrito. - + + + only this hand is used throughout the manuscript diff --git a/P5/Source/Specs/att.identified.xml b/P5/Source/Specs/att.identified.xml index b8fc55b42d..04158b75e0 100644 --- a/P5/Source/Specs/att.identified.xml +++ b/P5/Source/Specs/att.identified.xml @@ -1,11 +1,5 @@ - + provides identifying attributes for elements which can be @@ -47,7 +41,9 @@ should correspond to an existing module, via a moduleSpec or élément. proporciona el identificador utilizado para indicar un elemento. specifica l'identificatore utilizzato per indicare l'elemento - + + + says whether this object should be predeclared in the @@ -59,7 +55,9 @@ should correspond to an existing module, via a moduleSpec or précise si cet objet nécessite une prédéfinition dans le module d'infrastructure tei. declara si la clase debe ser considerada global y por tanto definida en el módulo core dichiara se la classe debba essere considerata globale e quindi definita nel modulo core - + + + false @@ -71,7 +69,9 @@ should correspond to an existing module, via a moduleSpec or être défini cet objet. proporciona el nombre del módulo en que el objeto debe ser definido. indica il nome del modulo nel quale l'oggetto deve essere definito - + + + - \ No newline at end of file + diff --git a/P5/Source/Specs/att.internetMedia.xml b/P5/Source/Specs/att.internetMedia.xml index e5835976e6..e60e8aee14 100644 --- a/P5/Source/Specs/att.internetMedia.xml +++ b/P5/Source/Specs/att.internetMedia.xml @@ -1,11 +1,5 @@ - + provides attributes for specifying the type of a computer @@ -31,7 +25,9 @@ ressource informatique selon une taxinomie normalisée. specifica il tipo MIME appropriato El tipo de MIME MIME協定種類 - + + + @@ -69,4 +65,4 @@ ressource informatique selon une taxinomie normalisée. 当該属性クラスは、コンピューターリソースを示すためのもので、通常、インターネット上にあるリソースを標準的な用語で示す。現時点では、MIME（Multipurpose Internet Mail Extensions）タイプのみが標準的な用語として使用可能である。このMIMEタイプについては、IETF（Internet Engineering Task Force）のRFC 2046で規定されている。使用できるタイプ名のリストの管理は、IANA（Internet Assigned Numbers Authority）によって行われている。mimeType属性は上記のタイプ名リストにより定義された値を含んでいなくてはならない。

- \ No newline at end of file + diff --git a/P5/Source/Specs/att.interpLike.xml b/P5/Source/Specs/att.interpLike.xml index d15f6740d6..93799507c0 100644 --- a/P5/Source/Specs/att.interpLike.xml +++ b/P5/Source/Specs/att.interpLike.xml @@ -1,11 +1,5 @@ - + provides attributes for elements which represent a formal analysis or interpretation. @@ -32,7 +26,9 @@ $Id$ passage. indica que tipo de fenómeno está siendo anotado en el pasaje. indica quale sia il fenomeno osservato nella porzione di testo in questione - + + + identifies an image in the passage. @@ -80,7 +76,9 @@ texte. subtype sous-type provides a sub-categorization of the phenomenon is being noted in the passage, if needed - + + +

The subtype attribute may be used to provide any sub-classification for the element additional to that provided @@ -120,7 +118,9 @@ by the current element. l'interprétation représentées par l'élément courant. indica ejemplos de análisis o interpretaciones representadas por el elemento corriente indica esempi di analisi o interpretazione rappresentati dall'elemento corrente - + + +

The current element should be an analytic one. The element pointed at should be a textual one.

@@ -142,4 +142,4 @@ by the current element. - \ No newline at end of file + diff --git a/P5/Source/Specs/att.lexicographic.normalized.xml b/P5/Source/Specs/att.lexicographic.normalized.xml index 337300cddd..226205e030 100644 --- a/P5/Source/Specs/att.lexicographic.normalized.xml +++ b/P5/Source/Specs/att.lexicographic.normalized.xml @@ -1,10 +1,6 @@ - + + + provides attributes for usage within word-level elements in the analysis module and within lexicographic microstructure in the dictionaries module. @@ -15,39 +11,41 @@ $Id$ normalizado normalisé normalizzato - provides the normalized/standardized form of information present in the source text in a non-normalized form - 비표준형으로 원본 텍스트에서 제시된 정보의 표준형을 제시한다. - 提供一規格化形式的資訊，其來源文件為非規格化形式 - 当該テキストを、正規形を示す。 - donne une forme normalisée de + 비표준형으로 원본 텍스트에서 제시된 정보의 표준형을 제시한다. + 提供一規格化形式的資訊，其來源文件為非規格化形式 + 当該テキストを、正規形を示す。 + donne une forme normalisée de l'information fournie par le texte source sous une forme non normalisée. - proprorciona de manera normalizada información dada en el texto fuente de manera no normalizada - fornisce la forma normalizzata delle informazioni contenute nel testo di origine in forma non normalizzata. - - -

Normalization of part-of-speech information within a dictionary entry.

- - - n - - - - - - - n. - - - + proprorciona de manera normalizada información dada en el texto fuente de manera no normalizada + fornisce la forma normalizzata delle informazioni contenute nel testo di origine in forma non normalizzata. + + + + +

Normalization of part-of-speech information within a dictionary entry.

+ + + n + + + + + + + n. + + +

Normalization of a source form in a tokenized historical corpus.

for vertues - sake + sake + @@ -59,7 +57,6 @@ $Id$ -

Example of normalization from Aviso. Relation oder Zeitung. Wolfenbüttel, 1609. In: Deutsches Textarchiv.

@@ -72,19 +69,17 @@ $Id$ - - Theyll + Theyll - Frewde + Frewde - original 원본 @@ -97,8 +92,9 @@ $Id$ 元の文字列を示す。当該要素が元資料に無い場合には空になる。 da la serie original o la serie vacía cuando el elemento no aparece en el texto fuente fornisce la stringa originale o la srtinga vuota quando l'elemento non compare nel testo di origine. - - + + +

Example from a language documentation project of the Mixtepec-Mixtec language (ISO 639-3: 'mix'). This is a use case where speakers spell something incorrectly but we would @@ -128,7 +124,6 @@ $Id$ -

It needs to be stressed that the two attributes in this class are meant for strictly diff --git a/P5/Source/Specs/att.lexicographic.xml b/P5/Source/Specs/att.lexicographic.xml index 464bcfe8ff..1533888eed 100644 --- a/P5/Source/Specs/att.lexicographic.xml +++ b/P5/Source/Specs/att.lexicographic.xml @@ -1,11 +1,5 @@ - + provides a set of attributes for specifying standard and normalized values, grammatical functions, alternate or equivalent forms, and information about composite parts. @@ -30,9 +24,10 @@ $Id$ donne une forme développée de l'information présentée de manière plus concise dans le dictionnaire. proporciona de manera expandida la información presentada brevemente en el diccionario fornisce la forma estesa dellel informazioni presentate in modo più coinciso nel dizionario. - - - + + + + @@ -58,7 +53,9 @@ $Id$ donne la liste des valeurs distinctes d'une forme fusionnée. proporciona una lista de valores de abertura para una forma fusionada fornisce la lista dei valori suddivisi di una forma unita. - + + + value @@ -70,7 +67,9 @@ $Id$ indique une valeur qui manque à un quelconque fragment du texte source imprimé. proporciona un valor que carece de cualquier realización en el texto fuente impreso fornisce un valore privo di qualsiasi realizzazione nel testo di origine a mezzo stampa. - + + + location @@ -83,7 +82,9 @@ $Id$ fournit une référence à un élément anchor se trouvant ailleurs dans le document TEI, pour indiquer la localisation de ce composant. proporciona una referencia a un elemento anchor que aparece en algún punto del documento indicando la localización original de ese componente. fornisce un riferimento per un elemento anchor in una altra porzione del documento indicando la localizzazione origiraria del componente. - + + + merged into @@ -95,7 +96,9 @@ $Id$ donne une référence à un autre élément, où l'original apparaît comme une forme fusionnée. fa riferimento a un altro elemento, laddove quello originale si presenti come forma risultanteda una fusione - + + + optional @@ -110,11 +113,13 @@ l'original apparaît comme une forme fusionnée. indique si l'élément est facultatif ou pas. indica si el elemento es opcional o no. indica se l'elemento è opzionale o meno. - + + + false - \ No newline at end of file + diff --git a/P5/Source/Specs/att.linguistic.xml b/P5/Source/Specs/att.linguistic.xml index bd11bfbe4c..d0bd17e935 100644 --- a/P5/Source/Specs/att.linguistic.xml +++ b/P5/Source/Specs/att.linguistic.xml @@ -1,11 +1,5 @@ - + provides a set of attributes concerning linguistic features of tokens, for usage within token-level elements, specifically w and pc in the analysis module. @@ -21,7 +15,9 @@ $Id$ fournit le lemme du mot (entrée du dictionnaire) identifica el lema de una palabra (forma en que se encuentra como entrada en un diccionario). identifica il lemma (la voce di un dizionario) - + + + wives @@ -42,7 +38,9 @@ $Id$ provides a pointer to a definition of the lemma for the word, for example in an online lexicon. - + + + hitting @@ -60,7 +58,9 @@ $Id$ (part of speech) indicates the part of speech assigned to a token (i.e. information on whether it is a noun, adjective, or verb), usually according to some official reference vocabulary (e.g. for German: STTS, for English: CLAWS, for Polish: NKJP, etc.). - + + +

The German sentence Wir fahren in den Urlaub. tagged with the Stuttgart-Tuebingen-Tagset (STTS).

@@ -70,7 +70,8 @@ $Id$ in den Urlaub - . + . + @@ -102,8 +103,9 @@ $Id$ morphosyntactic information for a token, usually according to some official reference vocabulary (e.g. for German: STTS-large tagset; for a feature description system designed as (pragmatically) universal, see Universal Features). - - + + + @@ -119,7 +121,9 @@ $Id$ when present, provides information on whether the token in question is adjacent to another, and if so, on which side. - + + + the token is not adjacent to another @@ -171,7 +175,7 @@ $Id$ -

The definition of this attribute is adapted from ISO MAF +

The definition of this attribute is adapted from ISO MAF (Morpho-syntactic Annotation Framework), ISO 24611:2012.

 diff --git a/P5/Source/Specs/att.locatable.xml b/P5/Source/Specs/att.locatable.xml index df84373384..b550b1f60d 100644 --- a/P5/Source/Specs/att.locatable.xml +++ b/P5/Source/Specs/att.locatable.xml @@ -1,14 +1,7 @@ - + - + provides attributes for referencing locations by pointing to entries in a canonical list of places. @@ -16,7 +9,9 @@ $Id$ indique une ou plusieurs localisations en pointant vers un élément place ou autre description canonique. indica una o más localizaciónes señalando un elemento place u otra descripción canónica. indica una o più posizioni facendo riferimento a un elemento place o altra descrizione canonica. - + + + diff --git a/P5/Source/Specs/att.measurement.xml b/P5/Source/Specs/att.measurement.xml index ab96a55a59..e56a2dea7a 100644 --- a/P5/Source/Specs/att.measurement.xml +++ b/P5/Source/Specs/att.measurement.xml @@ -1,11 +1,5 @@ - + provides attributes to represent a regularized or normalized measurement. @@ -37,7 +31,9 @@ $Id$ s'agit en général du symbole normalisé pour les unités dont on a besoin. indica las unidades usadas para la medición, normalmente utilizando el símbolo estándard para la unidad de medición en cuestión. indica le unità impiegate per la misurazione, generalmente utilizzando il simbolo standard per l'unità di misura in questione - + + + @@ -46,7 +42,7 @@ $Id$ 公尺 mètre metro - metro + metro メートル SI base unit of length 길이의 SI 기본 단위 @@ -77,7 +73,7 @@ $Id$ 초 秒 秒 - seconde + seconde secondo segundo SI base unit of time @@ -100,7 +96,7 @@ $Id$ 헤르츠 赫茲 hérzio - ヘルツ + ヘルツ SI unit of frequency 주파수의 SI 단위 SI頻率單位 @@ -115,7 +111,7 @@ $Id$ 파스칼 Pascal PASCAL - パスカル + パスカル SI unit of pressure or stress 압력 또는 강도의 SI 단위 SI壓力單位 @@ -134,7 +130,7 @@ $Id$ 옴 歐姆 ohmio - オーム + オーム SI unit of electric resistance 전기 저항의 SI 단위 SI 電阻單位 @@ -166,7 +162,7 @@ $Id$ 公升 litro litro - リットル + リットル 1 dm³ 1dm³ リッター。体積を示す。 @@ -178,7 +174,7 @@ $Id$ 公噸 tonnellata tonelada - トン + トン 10³ kg 10³ 公斤 トン。重さを示す。 @@ -196,7 +192,7 @@ $Id$ 公頃 ettaro hectárea - ヘクタール + ヘクタール 1 hm² 1² hm ヘクタール。広さを示す。 @@ -209,7 +205,7 @@ $Id$ 埃格斯特朗 (單位) angstrom オングストローム - 10⁻¹⁰ m + 10⁻¹⁰ m 10⁻¹⁰ 公尺 オングストローム。長さの単位。 10⁻¹⁰ m @@ -295,7 +291,7 @@ $Id$ kibioctet 킬로바이바이트 キビバイト - 2¹⁰ or 1024 bytes + 2¹⁰ or 1024 bytes 2¹⁰ 또는 1024 바이트 2¹⁰或1024位元組 2¹⁰ o 1024 bytes @@ -394,7 +390,9 @@ $Id$ points to a unique identifier stored in the xml:id of a unitDef element that defines a unit of measure. - + + + quantity @@ -408,7 +406,9 @@ $Id$ spécifie le nombre des unités indiquées que comprend la mesure. especifica el número de las unidades que costituyen la medición indica il numero delle unità che costituiscono la misurazione - + + + commodity @@ -421,7 +421,9 @@ $Id$ indique ce qui est mesuré. indica la substancia que está siendo medida. identifica la sostanza misurata - + + +

In general, when the commodity is made of discrete entities, the plural form should be used, even when the @@ -459,7 +461,6 @@ a gallon, baby?

-

The unit should normally be named using the standard symbol for an SI unit (see further ; ). However, encoders may also specify measurements using informally defined units such diff --git a/P5/Source/Specs/att.media.xml b/P5/Source/Specs/att.media.xml index 5e5a093c2d..75bae1b2e3 100644 --- a/P5/Source/Specs/att.media.xml +++ b/P5/Source/Specs/att.media.xml @@ -1,16 +1,10 @@ - + provides attributes for specifying display and related properties of external media. - 外部メディアの表示と関連プロパティを指定するための諸属性を提供する。 + 外部メディアの表示と関連プロパティを指定するための諸属性を提供する。 @@ -18,18 +12,24 @@ $Id$ Where the media are displayed, indicates the display width メディアが表示されている場合、表示部分の幅を示す。 - + + + Where the media are displayed, indicates the display height メディアが表示されている場合、表示部分の高さを示す。 - + + + Where the media are displayed, indicates a scale factor to be applied when generating the desired display size メディアが表示されている場合、望ましい表示サイズを生成する際に適用されるスケール倍率を示す。 - + + + - \ No newline at end of file + diff --git a/P5/Source/Specs/att.metrical.xml b/P5/Source/Specs/att.metrical.xml index b36786bb2e..c5134c69ab 100644 --- a/P5/Source/Specs/att.metrical.xml +++ b/P5/Source/Specs/att.metrical.xml @@ -1,11 +1,5 @@ - + defines a set of attributes that certain elements may use to @@ -33,9 +27,11 @@ metrical structure of the element. contient un encodage spécifié par l'utilisateur pour la structure métrique conventionnelle de l'élément. contiene una codificación definida por el usuario de la estructura métrica convencional del elemento. contiene una codifica, definita dall'utente, della struttura metrica convenzionale dell'elemento - + + + -

The pattern may be specified by means of either a standard term for +

The pattern may be specified by means of either a standard term for the kind of metrical unit (e.g. hexameter) or an encoded representation for the metrical pattern (e.g. +--+-+-+-+-). In either case, the @@ -72,9 +68,11 @@ of the conventional metrical structure applicable to the element. contient un encodage, spécifié par l'utilisateur, de la réalisation effective de la structure métrique conventionnelle applicable à l'élément. contiene un codificación definida por el usuario para la realización efectiva de la estructura métrica convencional aplicable al elemento. contiene una codifica, definita dall'utente, dell'effettiva realizzazione della struttura metrica convenzionale applicabile all'elemento - + + + -

The pattern may be specified by means of either a standard term for +

The pattern may be specified by means of either a standard term for the kind of metrical unit (e.g. hexameter) or an encoded representation for the metrical pattern (e.g. +--+-+-+-+-). In either case, the @@ -112,14 +110,16 @@ to that specified or implied for the met attribute.

groupe de lignes versifiées. especifica el esquema de la rima de un grupo de versos. specifica lo schema rimico di un gruppo di versi - + + +

By default, the rhyme scheme is expressed as a string of alphabetic characters each corresponding with a rhyming line. Any non-rhyming lines should be represented by a hyphen or an X. Alternative notations may be defined as for met by use of the metDecl element in the TEI header.

-

When the default notation is used, it does not make sense to +

When the default notation is used, it does not make sense to specify this attribute on any unit smaller than a line. Nor does the default notation provide any way to record internal rhyme, or to specify non-conventional rhyming practice. These extensions would require @@ -131,7 +131,8 @@ user-defined alternative notations.

à une ligne rimée. Toute ligne non rimée doit être repésentée par un tiret ou un X. Des notations alternatives peuvent être définies comme pour l'attribut met en utilisant - l'élément metDecl dans l'en-tête TEI.

Lorsque + l'élément metDecl dans l'en-tête TEI.

+

Lorsque la notation par défaut est utilisée, cela n'a pas de sens de renseigner l'attribut rhyme pour une unité plus petite qu'une ligne de vers. La notation par défaut ne donne @@ -153,4 +154,4 @@ user-defined alternative notations.

- \ No newline at end of file + diff --git a/P5/Source/Specs/att.milestoneUnit.xml b/P5/Source/Specs/att.milestoneUnit.xml index 827ef2d624..7b91e5f585 100644 --- a/P5/Source/Specs/att.milestoneUnit.xml +++ b/P5/Source/Specs/att.milestoneUnit.xml @@ -1,11 +1,5 @@ - + @@ -24,7 +18,9 @@ $Id$ sección que cambia en este hito. fornisce un nome convenzionale per il tipo di sezione che cambia con l'elemento milestone. - + + + physical page breaks (synonymous with the pb element). @@ -163,7 +159,6 @@ $Id$ is encountered.

In addition to the values suggested, other terms may be appropriate (e.g. Stephanus for the Stephanus numbers in Plato).

-

The type attribute may be used to characterize the unit boundary in any respect other than simply identifying the type of unit, for example as word-breaking or not.

diff --git a/P5/Source/Specs/att.msClass.xml b/P5/Source/Specs/att.msClass.xml index 4406c1adfd..a0698bc97d 100644 --- a/P5/Source/Specs/att.msClass.xml +++ b/P5/Source/Specs/att.msClass.xml @@ -1,31 +1,27 @@ - + - provides attributes to indicate text type or classification. - - - identifies the text types or classifications applicable to this + provides attributes to indicate text type or classification. + + + identifies the text types or classifications applicable to this item by pointing to other elements or resources defining the classification concerned. - 이 항목에 적용할 수 있는 텍스트 유형 또는 분류를 식별한다. - 標明適合的文字類型或分類。 - 関連する分類を定義する他の要素またはリソースを指すことによって、この項目に適用可能なテキストタイプまたは分類を特定する。 - spécifie la ou les catégories ou classes + 이 항목에 적용할 수 있는 텍스트 유형 또는 분류를 식별한다. + 標明適合的文字類型或分類。 + 関連する分類を定義する他の要素またはリソースを指すことによって、この項目に適用可能なテキストタイプまたは分類を特定する。 + spécifie la ou les catégories ou classes auxquelles l'item appartient. - identifica la tipología textual u otras clasificaciones aplicables al objeto en cuestión. - identifica la tipologia testuale o altre classificazioni applicabili all'oggetto in questione - - - - - - - - \ No newline at end of file + identifica la tipología textual u otras clasificaciones aplicables al objeto en cuestión. + identifica la tipologia testuale o altre classificazioni applicabili all'oggetto in questione + + + + + + + + + + diff --git a/P5/Source/Specs/att.msExcerpt.xml b/P5/Source/Specs/att.msExcerpt.xml index 76e0c64442..87ab16a242 100644 --- a/P5/Source/Specs/att.msExcerpt.xml +++ b/P5/Source/Specs/att.msExcerpt.xml @@ -1,11 +1,5 @@ - + manuscript excerpt @@ -35,7 +29,9 @@ $Id$ indique si le passage décrit est fautif, i.e. incomplet en raison d'une lacune ou d'une détérioration. indica se il brano citato sia o meno incompleto a causa di perdite o danni indica si el pasaje que se describe es completo o no, p.ej. si ha sufrido pérdidas o daños. - + + + @@ -67,4 +63,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/att.namespaceable.xml b/P5/Source/Specs/att.namespaceable.xml index bd074e6118..db186e64a6 100644 --- a/P5/Source/Specs/att.namespaceable.xml +++ b/P5/Source/Specs/att.namespaceable.xml @@ -1,11 +1,5 @@ - + provides attributes indicating the target namespace for an object being created. @@ -26,7 +20,9 @@ $Id$ précise l'espace de noms auquel appartient cet élément. especifica el espacio de nombre al que pertenece tal elemento. indica lo spazio del nome al quale appartiene tale elemento - + + + http://www.tei-c.org/ns/1.0

When specified on an elementSpec, this attribute diff --git a/P5/Source/Specs/att.naming.xml b/P5/Source/Specs/att.naming.xml index 610b0cbebc..466d663d68 100644 --- a/P5/Source/Specs/att.naming.xml +++ b/P5/Source/Specs/att.naming.xml @@ -1,11 +1,5 @@ - + provides attributes common to elements which refer to named persons, places, organizations etc. @@ -23,7 +17,9 @@ $Id$ may be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place. この属性名によって参照されるエンティティに関する詳細な情報（例えば人物の職業や場所のステータスなど）を示すために用いられる。この値は空白文字で区切られる。 - + + + reference to the canonical name @@ -42,7 +38,9 @@ this name in the form of a set of whitespace-separated values, for example the o indique comment localiser la forme canonique (nym) des noms qui sont associés à l'objet nommé par l'élément qui le contient. indica un modo di localizzare la forma canonica (nym) dei nomi associati all'oggetto definito dall'elemento che lo contiene - + + +

The value must point directly to one or more XML elements by means of one or more URIs, separated by whitespace. If more @@ -70,4 +68,4 @@ this name in the form of a set of whitespace-separated values, for example the o - \ No newline at end of file + diff --git a/P5/Source/Specs/att.notated.xml b/P5/Source/Specs/att.notated.xml index e26c68d9d4..e54ca27cd0 100644 --- a/P5/Source/Specs/att.notated.xml +++ b/P5/Source/Specs/att.notated.xml @@ -1,11 +1,5 @@ - + @@ -23,7 +17,9 @@ $Id$ previamente y usada para el contenido de un elemento. fornisce il nome di un'annotazione definita precedentemente utilizzata come contenuto dell'elemento. - + + + diff --git a/P5/Source/Specs/att.partials.xml b/P5/Source/Specs/att.partials.xml index c5f1d17576..d6ca090fd2 100644 --- a/P5/Source/Specs/att.partials.xml +++ b/P5/Source/Specs/att.partials.xml @@ -1,11 +1,5 @@ - + provides attributes for describing the extent of lexical references for a dictionary term. @@ -19,56 +13,57 @@ $Id$ 発音または正書法が単語の全部または一部に適用されるかどうかを示す。 indica si se trata de la pronunciación de la palabra completa o de una parte. indica se la pronuncia riguarda l'intera parola o una sua parte. --> - - - - full form - forme pleine - forma completa - forma completa - 完全形 - - - prefix - préfixe - prefisso - prefijo - 接頭辞 - - - suffix - suffixe - suffisso - sufijo - 接尾辞 - - - infix - infixe - infisso - infijteio - 接中辞 - - - partial - partiel - parziale - parcial - 一部分 - - - -

+ + + + + + full form + forme pleine + forma completa + forma completa + 完全形 + + + prefix + préfixe + prefisso + prefijo + 接頭辞 + + + suffix + suffixe + suffisso + sufijo + 接尾辞 + + + infix + infixe + infisso + infijteio + 接中辞 + + + partial + partiel + parziale + parcial + 一部分 + + + +

This attribute is optional, and no default value is specified, so it can be omitted if this information is not necessary.

- - -

+ + +

この属性はオプションであり、デフォルト値は指定されていないため、この情報が不要な場合は省略することができる。

- + - diff --git a/P5/Source/Specs/att.patternReplacement.xml b/P5/Source/Specs/att.patternReplacement.xml index a085eace50..cc25994cb0 100644 --- a/P5/Source/Specs/att.patternReplacement.xml +++ b/P5/Source/Specs/att.patternReplacement.xml @@ -1,11 +1,5 @@ - + provides attributes for regular-expression matching and replacement. @@ -28,7 +22,9 @@ $Id$ valores de los atributos cRef pueden ser combinados. specifica un'esressione regolare alla qaule posso corrispondere i valori degli attributi cRef.--> - + + +

The syntax used should follow that defined by W3C XPath syntax. Note that parenthesized groups are used not only for establishing order of precedence and atoms for quantification, but also for creating subpatterns to be referenced by the @@ -67,7 +63,9 @@ $Id$ sustitución, proporciona un URI. specifica un replacement pattern che, una volta applicato un sub-pattern di sostituzione, fornisce un URI. - + + +

The strings $1, $2 etc. are references to the corresponding group in the regular expression specified by matchPattern (counting open parenthesis, left diff --git a/P5/Source/Specs/att.personal.xml b/P5/Source/Specs/att.personal.xml index 9d9924a140..73e4cee867 100644 --- a/P5/Source/Specs/att.personal.xml +++ b/P5/Source/Specs/att.personal.xml @@ -1,11 +1,5 @@ - + attributes for components of names usually, but not necessarily, personal names @@ -37,7 +31,9 @@ abbreviation or simply as an initial. indique si la composante du nom est donnée en intégralité, sous forme d'abréviation ou simplement d'initiale. indica si el componente del nombre aparece por completo, como una abreviatura o como una inicial. indica se la componente del nome compare per esteso, come abbreviazione o come iniziale - + + + yes @@ -95,7 +91,9 @@ one initial. précise dans quel ordre est placé la composante par rapport aux autres dans le nom d'une personne. especifica la posición del componente al interno del nombre propio de persona en relación con los otros componentes. specifica la posizione della componente all'interno del nome proprio di persona in relazione alle altre componenti - + + + diff --git a/P5/Source/Specs/att.placement.xml b/P5/Source/Specs/att.placement.xml index 78a8d466fe..bc2509e7e4 100644 --- a/P5/Source/Specs/att.placement.xml +++ b/P5/Source/Specs/att.placement.xml @@ -1,11 +1,5 @@ - + provides attributes for describing where on the source page or @@ -25,7 +19,9 @@ $Id$ specifies where this item is placed. specifie où cet item se trouve. このアイテムが置かれた場所を指定する。 - + + + at the top of the page @@ -79,11 +75,11 @@ $Id$ au-dessus de la ligne al di sopra della linea - - to the right, + + to the right, e.g. to the right of a vertical line of text, or to the right of a figure - 右側、つまり、縦書きテキストや図の右側。 - + 右側、つまり、縦書きテキストや図の右側。 + below the line 행 아래 @@ -93,11 +89,11 @@ $Id$ au-dessous de la ligne al di sotto della linea - - to the left, + + to the left, e.g. to the left of a vertical line of text, or to the left of a figure - 左側、つまり、縦書きテキストや図の左側。 - + 左側、つまり、縦書きテキストや図の左側。 + at the end of e.g. chapter or volume. 주석이 장 또는 책 뒤에 나타난다. @@ -110,7 +106,7 @@ $Id$ within the body of the text. dans le corps du texte - テキスト本文の中で。 + テキスト本文の中で。 in a predefined space, for example left by an earlier scribe. diff --git a/P5/Source/Specs/att.pointing.group.xml b/P5/Source/Specs/att.pointing.group.xml index 2427493314..66f932007c 100644 --- a/P5/Source/Specs/att.pointing.group.xml +++ b/P5/Source/Specs/att.pointing.group.xml @@ -1,11 +1,5 @@ - + provides a set of attributes common to all elements which @@ -31,7 +25,9 @@ $Id$ spécifie, facultativement, les identifiants des éléments englobant tous les éléments indiqués par le contenu de cet élément. establece facultativamente los identificadores de elementos al interno de los cuales se encuentran todos los elementos indicados de los contenidos del elemento en cuestión. stabilisce facoltativamente gli identificatori di elementi all'interno dei quali si trovano tutti gli elementi indicati dai contenuti dell'elemento in questione - + + +

If this attribute is supplied every element specified as a target must be contained within the element or elements @@ -82,7 +78,9 @@ $Id$ descrive la funzione di ognuno dei valori dell'attributo target dei marcatori corrispondenti link, join, o alt - + + +

The number of separate values must match the number of values in the target attribute in the enclosed @@ -113,4 +111,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/att.pointing.xml b/P5/Source/Specs/att.pointing.xml index d30eeafca6..1e21eba5ec 100644 --- a/P5/Source/Specs/att.pointing.xml +++ b/P5/Source/Specs/att.pointing.xml @@ -1,11 +1,5 @@ - + provides a set of attributes used by all elements which point @@ -21,7 +15,9 @@ $Id$ specifies the language of the content to be found at the destination referenced by target, using a language tag generated according to BCP 47. BCP 47に従って生成された言語タグを使用することで、targetの参照先にあるコンテンツの言語を特定する。 - + + + @@ -41,7 +37,8 @@ $Id$ Declaration of Human Rights: one of them is in Polish, the other in Swahili.

 -

The value must conform to BCP 47. If the value is a + +

The value must conform to BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a language element with a matching value for its ident attribute should be supplied in @@ -49,11 +46,12 @@ $Id$ also optionally be supplied for non-private-use codes, though these must remain consistent with their IETFInternet Engineering Task - Force definitions.

 - -

- 値はBCP 47に準拠している必要がある。 (x-で始まっていたり、-x-を含むような記述のように)値がプライベートに使用されるコードの場合、自身のident属性に対応する値をもったlanguage要素は、TEIのヘッダーにおいてその値を記述しなくてはならない。そうした（非公式なコードの）記述はあるいは公式なコードにオプションとして取り入れられることもあるが、公式なコードはIETFInternet Engineering Task Force （インターネット技術特別調査委員会）の定義に準拠したものでなくてはならない。

 - + Force definitions.

+ + +

+ 値はBCP 47に準拠している必要がある。 (x-で始まっていたり、-x-を含むような記述のように)値がプライベートに使用されるコードの場合、自身のident属性に対応する値をもったlanguage要素は、TEIのヘッダーにおいてその値を記述しなくてはならない。そうした（非公式なコードの）記述はあるいは公式なコードにオプションとして取り入れられることもあるが、公式なコードはIETFInternet Engineering Task Force （インターネット技術特別調査委員会）の定義に準拠したものでなくてはならない。

+ specifies the destination of the reference by supplying one or more URI References @@ -66,19 +64,27 @@ $Id$ proporcionando una o más referencias URI. specifica la destinazione di un riferimento, fornendo uno o più riferimenti URI - -

One or more syntactically valid URI references, separated by whitespace. Because + + + + +

One or more syntactically valid URI references, separated by whitespace. Because whitespace is used to separate URIs, no whitespace is permitted inside a single URI. If a whitespace character is required in a URI, it should be escaped with the normal mechanism, - e.g. TEI%20Consortium.

 -

Une ou plusieurs références URI syntaxiquement valables, séparée par + e.g. TEI%20Consortium.

+ + +

Une ou plusieurs références URI syntaxiquement valables, séparée par un espace. Puisqu'un espace est employé pour séparer des URIs, aucun espace n’est autorisé à l'intérieur d'un URI. Si un espace est requis dans un URI, il faut le représenter avec une séquence d'échappement, comme par exemple - TEI%20Consortium.

 -

+ TEI%20Consortium.

+ + +

空白で区切られた1つもしくはそれ以上の構文的に有効なURI参照。空白はURIを区切るために使用されるため、各URI中において空白を使用することはできない。URIに空白文字が必要な場合は、たとえば TEI％20Consortium と言ったような通常の方法でエスケープする必要がある。 -

+

+ evaluate @@ -91,7 +97,9 @@ $Id$ détermine le sens attendu, si la cible d'un pointeur est elle-même un pointeur. indica el significado previsto cuando la meta de un indicador es también un indicador. indica il significato previsto quando la destinazione di un puntatore è essa stessa un puntatore - + + + if the element pointed to is itself a pointer, then @@ -154,4 +162,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/att.predicate.xml b/P5/Source/Specs/att.predicate.xml index 9ee3e01f0c..170219ad4a 100644 --- a/P5/Source/Specs/att.predicate.xml +++ b/P5/Source/Specs/att.predicate.xml @@ -1,51 +1,43 @@ - + - provides attributes for filtering + provides attributes for filtering by an XPath predicate expression. - - - the condition under which the element + + + the condition under which the element bearing this attribute applies, given as an XPath predicate expression. - - - - -

The XPath predicate expression given as the value of the predicate + + + + +

The XPath predicate expression given as the value of the predicate attribute has to be provided without wrapping square brackets.

- - - - - - - If it is a child of a person element, treat as + + + + + + + If it is a child of a person element, treat as inline - - - - -

The following example declares that the name element can be mapped to, or is equivalent to, the external + + + + +

The following example declares that the name element can be mapped to, or is equivalent to, the external concepts of PERSON and PLACE depending on the XPath expression given in predicate

- - - - - - - - - - - - + + + + + + + + + + + + diff --git a/P5/Source/Specs/att.ranging.xml b/P5/Source/Specs/att.ranging.xml index 247bc3fb4d..cf7c93bc19 100644 --- a/P5/Source/Specs/att.ranging.xml +++ b/P5/Source/Specs/att.ranging.xml @@ -1,11 +1,5 @@ - + provides attributes for describing numerical ranges. @@ -16,14 +10,18 @@ donne une estimation de la valeur minimum pour la mesure. 概算推量のための最小推定値を与える。 - + + + gives a maximum estimated value for the approximate measurement. donne une estimation de la valeur maximum pour la mesure. 概算推量のための最大推定値を与える。 - + + + where the measurement summarizes more than one observation @@ -32,7 +30,9 @@ lorsque la mesure résume plus d'une observation, fournit la valeur minimum observée. 1回以上の観察あるいは範囲をまとめた推量において、観察された最小値を提供する。 - + + + where the measurement summarizes more than one observation @@ -41,13 +41,17 @@ lorsque la mesure résume plus d'une observation, fournit la valeur maximum observée. 1回以上の観察あるいは範囲をまとめた推量において、観察された最大値を提供する。 - + + + specifies the degree of statistical confidence (between zero and one) that a value falls within the range specified by min and max, or the proportion of observed values that fall within that range. minとmax、で指定された範囲内の値、あるいはその範囲内で観察された値の割合の統計的な信頼度を0から1の値で示す。 - + + + @@ -58,8 +62,7 @@ The MS. was lost in transmission by mail from Americares has been supporting the health sector in Eastern - Europe since 1986, and since 1992 has provided more than + Europe since 1986, and since 1992 has provided more than $120m in aid to Ukrainians. diff --git a/P5/Source/Specs/att.rdgPart.xml b/P5/Source/Specs/att.rdgPart.xml index d2248d3bad..b27cc5994d 100644 --- a/P5/Source/Specs/att.rdgPart.xml +++ b/P5/Source/Specs/att.rdgPart.xml @@ -1,11 +1,5 @@ - + provides attributes to mark the beginning or ending of a fragmentary @@ -32,7 +26,9 @@ to this reading beginning or ending at this point. contient une liste d'une ou plusieurs abréviations désignant les témoins qui commencent ou finissent à ce point. contiene una lista de una o más siglas que indican los testimonios que inician o acaban en ese punto. contiene una lista di una o più sigle indicanti i testimoni che cominciano o finiscono in questo punto - + + + @@ -52,4 +48,4 @@ and rdg, and also within any of their constituent elements.

- \ No newline at end of file + diff --git a/P5/Source/Specs/att.repeatable.xml b/P5/Source/Specs/att.repeatable.xml index 02c9990305..ec7fc9de4f 100644 --- a/P5/Source/Specs/att.repeatable.xml +++ b/P5/Source/Specs/att.repeatable.xml @@ -1,11 +1,5 @@ - + provides attributes for the elements which define @@ -42,8 +36,6 @@ $Id$ indicates the smallest number of times this component may occur. この部品が出現し得る最小回数を示す。 - - @@ -75,8 +67,8 @@ $Id$ always be greater than or equal to 1. An ODD processor should raise an error if either of these conditions is not met.

-

- minOccursの値は常にmaxOccursの値以下でなければならない。maxOccursのデフォルト値が1なので、maxOccursが指定されない時には、minOccursは1以下でなければならない。 + +

minOccursの値は常にmaxOccursの値以下でなければならない。maxOccursのデフォルト値が1なので、maxOccursが指定されない時には、minOccursは1以下でなければならない。 minOccursのデフォルト値も1なので、minOccursが指定されない時には、maxOccursは常に1以上でなければならない。これらの条件のいずれかが満たされなければ、ODDプロセッサはエラーとなるだろう。

 diff --git a/P5/Source/Specs/att.resourced.xml b/P5/Source/Specs/att.resourced.xml index 3a418b8924..016a37c160 100644 --- a/P5/Source/Specs/att.resourced.xml +++ b/P5/Source/Specs/att.resourced.xml @@ -1,11 +1,5 @@ - + provides attributes by which a resource (such as an externally @@ -21,7 +15,9 @@ $Id$ 統一資源位置指定子 specifies the URL from which the media concerned may be obtained. 関連するメディアを入手するURLを示す。 - + + + - \ No newline at end of file + diff --git a/P5/Source/Specs/att.scoping.xml b/P5/Source/Specs/att.scoping.xml index 0e842aab3f..852c4e80c4 100644 --- a/P5/Source/Specs/att.scoping.xml +++ b/P5/Source/Specs/att.scoping.xml @@ -1,11 +1,5 @@ - + provides attributes for selecting particular elements @@ -15,7 +9,9 @@ $Id$ points at one or more sets of zero or more elements each. ある文書の中の特定の要素を選択するための属性を提供する。 - + + + Elizabeth went to Essex @@ -27,7 +23,7 @@ $Id$ syntax defined in which identifies a set of nodes, selected within the context identified by the target attribute if this is supplied, or within the context of the parent element if it is not. - に定義された構文を用いて、ノードの集合を指し示す任意の XPath 式を記入する。 + に定義された構文を用いて、ノードの集合を指し示す任意の XPath 式を記入する。 選択範囲は target 属性が与えられた場合はそのコンテクスト、 なければ親要素のコンテクストとなる。 @@ -57,13 +53,13 @@ $Id$

Note that the value of the target attribute may include an XPointer expression including an XPath expression (see ).

-

確信度の表現は target 属性の値で指定されたノードセットに適用されるが、加えて match 属性の値によって修正されることがある。 + +

確信度の表現は target 属性の値で指定されたノードセットに適用されるが、加えて match 属性の値によって修正されることがある。 複数の識別子が与えられた場合、それらすべての要素（またはノードセット）を指すものと解される。 match 属性は要素のグループを指定するために用いることもできる。

target と match 両方がある場合、match の XPath 式は target で選択した要素のコンテクスト内で評価される。どちらの属性もない場合、表現は親要素に適用される。 target のみ与えられている場合、その選択する要素もしくはノードセットに表現が適用される。 match のみ与えられている場合、XPath 式はこの属性を含む要素の親要素のコンテクストで評価される。

-

なお、target 属性の値には XPath 式を含む XPointer 表現が入りうる（ を参照）。

 - - - \ No newline at end of file +

なお、target 属性の値には XPath 式を含む XPointer 表現が入りうる（ を参照）。

+ + diff --git a/P5/Source/Specs/att.segLike.xml b/P5/Source/Specs/att.segLike.xml index 959fcd1228..bc672e4619 100644 --- a/P5/Source/Specs/att.segLike.xml +++ b/P5/Source/Specs/att.segLike.xml @@ -1,11 +1,5 @@ - + provides attributes for elements used for arbitrary segmentation. @@ -31,16 +25,22 @@ $Id$ caractérise la fonction du segment. caracteriza la función de un segmento. caratterizza la funzione del segmento - -

Attribute values will often vary depending on the type of element to which they are attached. For example, a cl, may take values such as + + + + +

Attribute values will often vary depending on the type of element to which they are attached. For example, a cl, may take values such as coordinate, subject, adverbial etc. For a phr, such values as -subject, predicate etc. may be more appropriate. Such constraints will typically be implemented by a project-defined customization.

-

+subject, predicate etc. may be more appropriate. Such constraints will typically be implemented by a project-defined customization.

+ + +

属性値は付与された要素のタイプに応じてしばしば変化する。 たとえば、clは座標や主語、副詞のような値をとることができる。 phrの場合、主語や述語のような値はより適切かもしれない。 - そういった制約は、典型的には、プロジェクトで定義されたカスタマイズとして実装されるだろう。

 - @@ -48,4 +48,4 @@ subject, predicate etc. may be more appropriate. Such constraints will typically - \ No newline at end of file + diff --git a/P5/Source/Specs/att.sortable.xml b/P5/Source/Specs/att.sortable.xml index 5715c4bec9..68f61db59d 100644 --- a/P5/Source/Specs/att.sortable.xml +++ b/P5/Source/Specs/att.sortable.xml @@ -1,11 +1,5 @@ - + provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. @@ -14,7 +8,9 @@ supplies the sort key for this element in an index, list or group which contains it. インデックスやリスト、グループに含まれる要素のソートキーを提供する。 - + + + David's other principal backer, Josiah ha-Kohen Josiah ha-Kohen b. Azarya b. Azarya, son of one of the last gaons of Sura was David's own first @@ -63,10 +59,9 @@ それに対して、A1やA4、A5はa-とAAのあいだに数字順に置かれてしまうこともある。 ソートキーは、辞書項目の表記が辞書における順序を決定するのに不十分な際に必要となる。

- - \ No newline at end of file + diff --git a/P5/Source/Specs/att.spanning.xml b/P5/Source/Specs/att.spanning.xml index 303db259ed..a5b3e5e9ac 100644 --- a/P5/Source/Specs/att.spanning.xml +++ b/P5/Source/Specs/att.spanning.xml @@ -1,11 +1,5 @@ - + provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. @@ -26,7 +20,9 @@ $Id$ indique la fin d'un passage introduit par l'élément portant cet attribut. indica el final de un fragmento de texto iniciado con el elemento al cual es asignaado el atributo. indica la fine della porzione di testo che ha inizio con l'elemento a cui è assegnato l'attributo - + + + The @spanTo attribute must point to an element following the current element @@ -70,4 +66,4 @@ The element indicated by @spanTo () must follow - \ No newline at end of file + diff --git a/P5/Source/Specs/att.styleDef.xml b/P5/Source/Specs/att.styleDef.xml index 31f0d9aa66..0d7e6053b2 100644 --- a/P5/Source/Specs/att.styleDef.xml +++ b/P5/Source/Specs/att.styleDef.xml @@ -1,11 +1,5 @@ - + provides attributes to specify the name of a formal definition @@ -20,7 +14,9 @@ $Id$ identifie la langue employée pour décrire le rendu identifica la lingua utilizzata per descrivere la resa - + + + Cascading Stylesheet Language @@ -67,7 +63,9 @@ If no value for the @scheme attribute is provided, then the default assumption s supplies a version number for the style language provided in scheme. - + + + diff --git a/P5/Source/Specs/att.tableDecoration.xml b/P5/Source/Specs/att.tableDecoration.xml index ddc4e5845c..e6552569ef 100644 --- a/P5/Source/Specs/att.tableDecoration.xml +++ b/P5/Source/Specs/att.tableDecoration.xml @@ -1,11 +1,5 @@ - + provides attributes used to decorate rows or cells of a table. @@ -30,7 +24,9 @@ in each cell of this row. informations contenues dans cette cellule ou dans chaque cellule de cette ligne. especifica el tipo de información contenida en la celda en cuestión o en cada una de las celdas de la fila. specifica il tipo di informazione contenuta nela cella in questione o in ciascuna delle celle della riga presa in esame - + + + data @@ -91,7 +87,9 @@ el atributo role (papel) del elemento padre row (fila).

indique le nombre de lignes occupées par la cellule ou la ligne en question. indica el número de filas ocupado por una celda o por la fila en cuestión. indica il numero di righe occupate dalla cella o riga in questione - + + + 1

A value greater than one indicates that this @@ -127,7 +125,9 @@ to use nested tables.

indique le nombre de colonnes occupées par cette cellule ou cette ligne. indica el número de columnas que abraza una celda o fila. indica il numero di colonne occupate dalla cella o riga - + + + 1

A value greater than one indicates that this cell or row @@ -151,4 +151,4 @@ to use nested tables.

- \ No newline at end of file + diff --git a/P5/Source/Specs/att.textCritical.xml b/P5/Source/Specs/att.textCritical.xml index 79f1e25fd9..4609b41878 100644 --- a/P5/Source/Specs/att.textCritical.xml +++ b/P5/Source/Specs/att.textCritical.xml @@ -1,11 +1,5 @@ - + defines a set of attributes common to all elements representing variant readings in text critical work. @@ -37,7 +31,9 @@ $Id$ établit une classification de la leçon selon une typologie utile. clasifica la lectura según alguna tipología funcional. classifica la lettura secondo una tipologia funzionale - + + + substantive @@ -73,7 +69,9 @@ any appropriate typology of possible origins. établit une classification de la cause d'une variante de leçon, selon une typologie appropriée aux origines possibles de cette variation. clasifica la causa de una lectura alternativa según cualquier tipología adecuada de posibles orígenes. classifica le ragioni di una lettura alternativa secondo una qualsiasi tipologia adeguata di origini possibili - + + + @@ -102,7 +100,9 @@ sequence, when there is reason to presume a sequence to the variants. variantes de chaque lemme. proporciona un número que indica la posición de tal lectura dentro de una secuencia, cuando se de el caso de suponer una secuencia respecto a las variantes de un lema dado fornisce un numero che indica la posizione di tale lettura all'interno di una sequenza, qualora ci sia motivo di supporre una sequenza rispetto alle varianti per un dato lemma - + + +

Different variant sequences could be coded with distinct number trails: 1-2-3 for one sequence, 5-6-7 for another. More @@ -126,7 +126,9 @@ des séquences de variantes plus complexes (par exemple comportant de multiples points to other readings that are required when adopting the current reading or lemma. punta ad altre letture che vanno obbligatoriamente considerate insieme all'elemento corrente - + + + + provides attributes common to those elements which @@ -32,7 +26,9 @@ $Id$ indique dans un alignement temporel (un ordre chronologique) l'endroit où commence cet élément. indica el punto en el ámbito de un alineamiento temporal en el cual comienza el elemento indica il punto nell'ambito di un allineamento temporale in cui comincia l'elemento - + + +

If no value is supplied, the element is assumed to follow the immediately preceding element at the same hierarchic @@ -60,7 +56,9 @@ $Id$ indique l'endroit où se termine cet élément dans un alignement temporel. indica el punto en el ámbito de un alineamiento temporal en el cual comienza el elemento indica il punto nell'ambito di un allineamento temporale in cui termina l'elemento - + + +

If no value is supplied, the element is assumed to precede the immediately following element at the same hierarchic @@ -83,4 +81,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/att.transcriptional.xml b/P5/Source/Specs/att.transcriptional.xml index ef7fc0ab36..ad9435c074 100644 --- a/P5/Source/Specs/att.transcriptional.xml +++ b/P5/Source/Specs/att.transcriptional.xml @@ -1,11 +1,5 @@ - + provides attributes specific to elements encoding authorial or @@ -23,10 +17,9 @@ transcription de sources manuscrites ou assimilées. - - + provides attributes used to indicate the status of a translatable @@ -29,7 +23,9 @@ portion of an ODD document. source dont la version traduite a été tirée. indica nombre o número de versión del original del cual deriva la versione traducida indica nome o numero di versione dell'originale da cui deriva la versione tradotta - + + +

The versionDate attribute can be used to determine whether a translation might @@ -40,4 +36,4 @@ portion of an ODD document. - \ No newline at end of file + diff --git a/P5/Source/Specs/att.typed.xml b/P5/Source/Specs/att.typed.xml index b935b8ac26..36eaacaeb7 100644 --- a/P5/Source/Specs/att.typed.xml +++ b/P5/Source/Specs/att.typed.xml @@ -1,11 +1,5 @@ - + provides attributes that can be used to classify or subclassify elements in any way. @@ -37,7 +31,9 @@ $Id$ caractérise l'élément en utilisant n'importe quel système ou typologie de classification approprié. caracteriza el elemento utilizando una clasificación o tipología funcional. caratterizza l'elemento utilizzando una classificazione o tipologia funzionale - + + +

@@ -70,7 +66,9 @@ $Id$ c'est nécessaire. proporciona, si es necesario, una subcategorización del elemento. stabilisce, se necessario, una sottocategorizzazione dell'elemento - + + +

The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its @@ -121,4 +119,4 @@ sub-classification for the element additional to that provided by its - \ No newline at end of file + diff --git a/P5/Source/Specs/att.witnessed.xml b/P5/Source/Specs/att.witnessed.xml index 32d4fab08a..b5afa1b9c4 100644 --- a/P5/Source/Specs/att.witnessed.xml +++ b/P5/Source/Specs/att.witnessed.xml @@ -1,11 +1,5 @@ - + provides attributes used to identify the witnesses @@ -28,7 +22,9 @@ which attest to a given reading. les témoins attestant d'une leçon donnée. contiene una lista de uno o más indicadores que muestran los testimonios que presentan una determinada lectura. contiene una lista di uno o più puntatori indicanti i testimoni che attestano una determinata lettura - + + +

If the apparatus contains readings only for a single witness, this attribute may be consistently omitted.

@@ -64,4 +60,4 @@ supplied as the content of a child wit element.

- \ No newline at end of file + diff --git a/P5/Source/Specs/att.written.xml b/P5/Source/Specs/att.written.xml index 62885d9634..73841d19bd 100644 --- a/P5/Source/Specs/att.written.xml +++ b/P5/Source/Specs/att.written.xml @@ -1,11 +1,5 @@ - + @@ -15,16 +9,16 @@ $Id$ the textual content of an element was written in the source being transcribed.--> - - points to a handNote element describing the hand considered responsible for the + + points to a handNote element describing the hand considered responsible for the content of the element concerned. - - - - - - 간섭을 만든 당사자의 필적을 나타낸다. - 当該調整を行った主体の筆致を特定する。 + 간섭을 만든 당사자의 필적을 나타낸다. + 当該調整を行った主体の筆致を特定する。 - signale la main de celui qui est intervenue. - indica il responsabile dell'aggiunta o della cancellazione - indica el responsable de la adición o de la omisión. - - - - - + + - \ No newline at end of file + diff --git a/P5/Source/Specs/att.xml b/P5/Source/Specs/att.xml index 6843c304e1..ba82ae61d2 100644 --- a/P5/Source/Specs/att.xml +++ b/P5/Source/Specs/att.xml @@ -1,11 +1,5 @@ - + attribute @@ -49,7 +43,9 @@ $Id$ assegna un identificatore allo schema nel quale è definito tale nome liefert einen Identifikator für das Schema in dem der Name definiert ist. - + + + TEI @@ -132,7 +128,6 @@ $Id$ das Attribut ist Teil des xInclude-Schemas. 当該属性はxIncludeスキーマで定義されている。 - @@ -165,8 +160,10 @@ $Id$

Un préfixe d'espace de noms peut être utilisé pour spécifier le schéma, comme alternative à sa spécification par l'attribut scheme : le préfixe est alors prioritaire.

 -

scheme属性を使用する代わりに、名前空間接頭辞を使用することもできる。schemeと接頭辞の両方が使用されている場合は、接頭辞が優先される。 -

+ +

scheme属性を使用する代わりに、名前空間接頭辞を使用することもできる。schemeと接頭辞の両方が使用されている場合は、接頭辞が優先される。 +

+

Als Alternative zur Verwendung des scheme-Attributes kann ein Namensraum-Präfix verwendet werden. Wenn scheme und Präfix zugleich verwendet werden, hat das Präfix @@ -175,4 +172,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/attDef.xml b/P5/Source/Specs/attDef.xml index 6e90fdbd0f..c0b6a99839 100644 --- a/P5/Source/Specs/attDef.xml +++ b/P5/Source/Specs/attDef.xml @@ -1,11 +1,5 @@ - + attribute definition @@ -27,20 +21,20 @@ $Id$ - - - - - - - - - - - - - - + + + + + + + + + + + + + + @@ -54,7 +48,7 @@ $Id$ - Since the @ attribute is required, it will always be specified. Thus the default value (of "") will never be used. Either change the definition of the attribute so it is not required ("rec" or "opt"), or remove the defaultVal element. + Since the @ attribute is required, it will always be specified. Thus the default value (of "") will never be used. Either change the definition of the attribute so it is not required ("rec" or "opt"), or remove the defaultVal element. @@ -96,7 +90,9 @@ $Id$ elemento indica il carattere facoltativo di un attributo o elemento - + + + opt diff --git a/P5/Source/Specs/attList.xml b/P5/Source/Specs/attList.xml index b6b93b2875..bdb155c0fb 100644 --- a/P5/Source/Specs/attList.xml +++ b/P5/Source/Specs/attList.xml @@ -1,11 +1,5 @@ - + attribute list @@ -25,13 +19,11 @@ $Id$ - - - - - - - + + + + + @@ -51,7 +43,9 @@ $Id$ indica si solo uno (choice) o todos (group) los atributos de la lista están disponibles indica se gli attributi contenuti nella lista sono tutti disponibili (group) o se ne è disponibile solo uno (choice) - + + + group @@ -117,11 +111,15 @@ $Id$ identifies the active participants in a non-mutual relationship, or all the participants in a mutual one. - + + + supplies a list of participants amongst all of whom the relationship holds equally. - + + + @@ -130,4 +128,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/attRef.xml b/P5/Source/Specs/attRef.xml index 05d134b7d0..14980d0c55 100644 --- a/P5/Source/Specs/attRef.xml +++ b/P5/Source/Specs/attRef.xml @@ -1,11 +1,5 @@ - + attribute pointer @@ -25,15 +19,21 @@ $Id$ - + + + the name of the attribute class - + + + the name of the attribute - + + + diff --git a/P5/Source/Specs/author.xml b/P5/Source/Specs/author.xml index 5850d43e8c..fb0372a32f 100644 --- a/P5/Source/Specs/author.xml +++ b/P5/Source/Specs/author.xml @@ -1,10 +1,7 @@ - + + + + author autor/a auteur @@ -36,35 +33,35 @@ autor/a/es, ya sea una persona o una institución, de una obra; por ejemplo, en - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -137,10 +134,10 @@ places, in particular where multiple names are given.

réseau qui diffuse le programme.

 -

特にヘッダの内容をもとに目録作成が行われると考えられる場合、この要素の内容を広く知られた名前典拠ファイルに準拠することを推奨する。 +

特にヘッダの内容をもとに目録作成が行われると考えられる場合、この要素の内容を広く知られた名前典拠ファイルに準拠することを推奨する。 keyやref属性によって何らかの適切な典拠（たとえば図書館目録やオンライン情報のような）における著者（達）についての標準的な参照情報を示すこともできる。

-

放送番組の場合には、その番組の制作に責任を持つ放送局や放送ネットワークの名前を用いる。

-

著者が不明であったり不明確である場合、この要素は不詳や匿名のようなテキストであってもよい。 +

放送番組の場合には、その番組の制作に責任を持つ放送局や放送ネットワークの名前を用いる。

+

著者が不明であったり不明確である場合、この要素は不詳や匿名のようなテキストであってもよい。 特に、複数の名前が用いられている場合には、適切なTEIモジュールを用いて、人や組織、場所に関する名前をより詳細にタグ付けしてもよい。

 diff --git a/P5/Source/Specs/authority.xml b/P5/Source/Specs/authority.xml index 297d962128..2134898e6b 100644 --- a/P5/Source/Specs/authority.xml +++ b/P5/Source/Specs/authority.xml @@ -1,11 +1,5 @@ - + release authority @@ -23,7 +17,7 @@ $Id$ 출판사 또는 배포자 외에 전자 파일 사용 허가에 대한 권한을 갖는 개인 또는 기관의 이름을 제시한다. 說明除了出版者或發行者之外，負責提供電子檔案的個人或其他經銷商的名稱。 作品の供給に責任のある、出版者や発売者以外の個人または団体の名前を示す。 - gibt die Person oder Instanz (außer Verlag oder Distributor) an, die für den Zugang zu einer Ressource verantwortlich ist. + gibt die Person oder Instanz (außer Verlag oder Distributor) an, die für den Zugang zu einer Ressource verantwortlich ist. proporciona el nombre de la persona o agente responsable que ha hecho disponible un archivo electrónico, que no es ni el editor ni el distribudor. fornisce il nome di una persona o di un'organizzazione responsabile della messa a disposizione di un file elettronico, diversa dalll'editore o dal distributore. diff --git a/P5/Source/Specs/availability.xml b/P5/Source/Specs/availability.xml index 3bae1d644d..4893aeac9a 100644 --- a/P5/Source/Specs/availability.xml +++ b/P5/Source/Specs/availability.xml @@ -1,11 +1,5 @@ - + availability @@ -35,7 +29,7 @@ $Id$ - + @@ -52,7 +46,9 @@ $Id$ disponibilidad actual del texto. fornisce un codice che identifica l'attuale disponibilità del testo. - + + + free diff --git a/P5/Source/Specs/back.xml b/P5/Source/Specs/back.xml index 5176385ba4..4d5dd5a413 100644 --- a/P5/Source/Specs/back.xml +++ b/P5/Source/Specs/back.xml @@ -1,11 +1,5 @@ - + back matter diff --git a/P5/Source/Specs/bibl.xml b/P5/Source/Specs/bibl.xml index 4f44ebf955..3863bc5ef6 100644 --- a/P5/Source/Specs/bibl.xml +++ b/P5/Source/Specs/bibl.xml @@ -1,11 +1,5 @@ - + bibliographic citation @@ -15,7 +9,7 @@ cita bibliográfica. citazione bibliografica bibliografische Angabe - 典拠情報の明示 + 典拠情報の明示 contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. 하위 성분이 명시적으로 구분된 또는 그렇지 않은 덜 구조화된 서지 인용을 포함한다. @@ -41,19 +35,17 @@ - - - - - - - - - - - - - + + + + + + + + + + + diff --git a/P5/Source/Specs/biblFull.xml b/P5/Source/Specs/biblFull.xml index 462ec3aceb..c8d6d3d7fb 100644 --- a/P5/Source/Specs/biblFull.xml +++ b/P5/Source/Specs/biblFull.xml @@ -1,11 +1,5 @@ - + fully-structured bibliographic citation diff --git a/P5/Source/Specs/biblScope.xml b/P5/Source/Specs/biblScope.xml index 2b085e6491..08ac46382b 100644 --- a/P5/Source/Specs/biblScope.xml +++ b/P5/Source/Specs/biblScope.xml @@ -1,11 +1,5 @@ - + scope of bibliographic reference @@ -83,11 +77,11 @@ Kindelements) von imprint anzugeben, da es Informationen enthält, die nicht Teil des Impressums sind.

 - +

一つのページが引用される場合、from属性とto属性を同じ値で使用すべきである。 明確な終点が提供されていない場合、from属性はtoを使わずに使うことができる。 例えば、p. 3ffのような引用は、<biblScope from="3">p. 3ff</biblScope>となる。

-

出版事項の一部を構成しない情報を提供するため、この要素をimprintの子ではなく、兄弟として提供するほうが望ましい。

+

出版事項の一部を構成しない情報を提供するため、この要素をimprintの子ではなく、兄弟として提供するほうが望ましい。

 diff --git a/P5/Source/Specs/biblStruct.xml b/P5/Source/Specs/biblStruct.xml index b0c19ad88a..427134a8e1 100644 --- a/P5/Source/Specs/biblStruct.xml +++ b/P5/Source/Specs/biblStruct.xml @@ -1,11 +1,5 @@ - + structured bibliographic citation @@ -37,7 +31,7 @@ - + diff --git a/P5/Source/Specs/bicond.xml b/P5/Source/Specs/bicond.xml index 10fd209d21..79a142d4f8 100644 --- a/P5/Source/Specs/bicond.xml +++ b/P5/Source/Specs/bicond.xml @@ -1,11 +1,5 @@ - + bi-conditional feature-structure constraint diff --git a/P5/Source/Specs/binary.xml b/P5/Source/Specs/binary.xml index df6b3a0b8a..1fd5b09e48 100644 --- a/P5/Source/Specs/binary.xml +++ b/P5/Source/Specs/binary.xml @@ -1,11 +1,5 @@ - + binary value @@ -29,7 +23,9 @@ $Id$ - + + + supplies a binary value. @@ -39,14 +35,18 @@ $Id$ fournit une valeur binaire. proporciona un valor binario fornisce un valore binario. - -

This attribute has a datatype of teidata.truthValue, which + + + + +

This attribute has a datatype of teidata.truthValue, which may be represented by the values 1 or true, or 0 or false.

- -

この属性はteidata.truthValueのデータ型を持つ。 + + +

この属性はteidata.truthValueのデータ型を持つ。 その値は、1かtrue、あるいは0かfalseで表現される。

- + diff --git a/P5/Source/Specs/binaryObject.xml b/P5/Source/Specs/binaryObject.xml index f8de99bd6d..bd1ce02bc1 100644 --- a/P5/Source/Specs/binaryObject.xml +++ b/P5/Source/Specs/binaryObject.xml @@ -1,11 +1,5 @@ - + provides encoded binary data representing an inline graphic, @@ -44,7 +38,9 @@ binarios. Si no se espeficica, se supone que es Base64. Codifica utilizzata per codificare dati binari. Se non specificata si presume che sia Base64 - + + + @@ -61,4 +57,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/binding.xml b/P5/Source/Specs/binding.xml index 110efc583a..7e0f38fccb 100644 --- a/P5/Source/Specs/binding.xml +++ b/P5/Source/Specs/binding.xml @@ -1,10 +1,7 @@ - + + + + binding reliure contains a description of one binding, i.e. type of covering, boards, @@ -23,49 +20,45 @@ $Id$ - - - - - - - + + + + + - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + contemporary contemporaine specifies whether or not the binding is contemporary with the majority of its @@ -79,7 +72,9 @@ $Id$ mayoría del contenido del manuscrito. specifica se la legatura è coeva o meno rispetto alla maggior parte del suo contenuto - + + +

The value true indicates that the binding is contemporaneous with its contents; the value false that it is not. The value unknown should @@ -207,4 +202,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/bindingDesc.xml b/P5/Source/Specs/bindingDesc.xml index 2fc39632d6..0a914fadbf 100644 --- a/P5/Source/Specs/bindingDesc.xml +++ b/P5/Source/Specs/bindingDesc.xml @@ -1,11 +1,5 @@ - + binding description @@ -37,16 +31,12 @@ uno per ogni legatura del manoscritto - - - - - - - - - - + + + + + + @@ -108,4 +98,4 @@ endbands; the edges of the leaves and boards gilt.Boxed.

- \ No newline at end of file + diff --git a/P5/Source/Specs/birth.xml b/P5/Source/Specs/birth.xml index 561103390f..c49505c55a 100644 --- a/P5/Source/Specs/birth.xml +++ b/P5/Source/Specs/birth.xml @@ -1,10 +1,7 @@ - + + + + birth naissance contains information about a person's birth, such as its date and place. @@ -30,59 +27,57 @@ - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + - + - - caesarean section - 帝王切開 - - - vaginal delivery - 普通分娩 - - - ex nihilo - 無から - - - - + + caesarean section + 帝王切開 + + + vaginal delivery + 普通分娩 + + + ex nihilo + 無から + + + + @@ -122,4 +117,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/bloc.xml b/P5/Source/Specs/bloc.xml index 8e187f0769..9e722eea05 100644 --- a/P5/Source/Specs/bloc.xml +++ b/P5/Source/Specs/bloc.xml @@ -1,10 +1,7 @@ - + + + + bloc bloc contains the name of a geo-political unit consisting of two or more nation states or @@ -30,35 +27,35 @@ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -82,4 +79,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/body.xml b/P5/Source/Specs/body.xml index c04dd1c4ce..68e58055c9 100644 --- a/P5/Source/Specs/body.xml +++ b/P5/Source/Specs/body.xml @@ -1,11 +1,5 @@ - + text body @@ -34,23 +28,23 @@ $Id$ - + - + - + - + - + - + @@ -133,4 +127,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/broadcast.xml b/P5/Source/Specs/broadcast.xml index 2221d187e3..eabda9db7c 100644 --- a/P5/Source/Specs/broadcast.xml +++ b/P5/Source/Specs/broadcast.xml @@ -1,11 +1,5 @@ - + broadcast @@ -27,9 +21,7 @@ $Id$ - - - + @@ -76,4 +68,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/byline.xml b/P5/Source/Specs/byline.xml index 6f55cc74d2..b15e0b61cb 100644 --- a/P5/Source/Specs/byline.xml +++ b/P5/Source/Specs/byline.xml @@ -1,11 +1,5 @@ - + byline @@ -30,15 +24,13 @@ on its title page or at the head or end of the work. - - - - - - - - - + + + + + + + @@ -147,4 +139,4 @@ it may optionally be tagged using the docAuthor element.

- \ No newline at end of file + diff --git a/P5/Source/Specs/c.xml b/P5/Source/Specs/c.xml index cc9f79459b..3e9f101134 100644 --- a/P5/Source/Specs/c.xml +++ b/P5/Source/Specs/c.xml @@ -1,11 +1,5 @@ - + character @@ -77,4 +71,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/cRefPattern.xml b/P5/Source/Specs/cRefPattern.xml index f3bcffa580..9967175723 100644 --- a/P5/Source/Specs/cRefPattern.xml +++ b/P5/Source/Specs/cRefPattern.xml @@ -1,11 +1,5 @@ - + canonical reference pattern @@ -35,9 +29,7 @@ $Id$ - - - + @@ -71,4 +63,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/caesura.xml b/P5/Source/Specs/caesura.xml index aa5e553369..73fdfdbeb5 100644 --- a/P5/Source/Specs/caesura.xml +++ b/P5/Source/Specs/caesura.xml @@ -1,11 +1,5 @@ - + marks the point at which a metrical line may be divided. @@ -19,7 +13,9 @@ $Id$ - + + + Hwæt we Gar-Dena in gear-dagum @@ -45,4 +41,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/calendar.xml b/P5/Source/Specs/calendar.xml index 2fb79f36b3..c2f73aff26 100644 --- a/P5/Source/Specs/calendar.xml +++ b/P5/Source/Specs/calendar.xml @@ -1,11 +1,5 @@ - + calendar @@ -21,8 +15,8 @@ $Id$ - - + + @@ -63,4 +57,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/calendarDesc.xml b/P5/Source/Specs/calendarDesc.xml index c052006bc6..81f05300db 100644 --- a/P5/Source/Specs/calendarDesc.xml +++ b/P5/Source/Specs/calendarDesc.xml @@ -1,11 +1,5 @@ - + calendar description @@ -27,9 +21,7 @@ $Id$ - - - + @@ -166,11 +158,12 @@ $Id$ http://www.w3.org/TR/xpath-functions-11/#lang-cal-country

-

ひとつめの例での、暦の名とxml:idの略号は、 - http://www.w3.org/TR/xpath-functions-11/#lang-cal-countryにおけるW3Cガイドラインから来ている。

 - + +

ひとつめの例での、暦の名とxml:idの略号は、 + http://www.w3.org/TR/xpath-functions-11/#lang-cal-countryにおけるW3Cガイドラインから来ている。

+ - \ No newline at end of file + diff --git a/P5/Source/Specs/camera.xml b/P5/Source/Specs/camera.xml index 1f6c404934..1b7480e4a5 100644 --- a/P5/Source/Specs/camera.xml +++ b/P5/Source/Specs/camera.xml @@ -1,11 +1,5 @@ - + camera @@ -32,7 +26,9 @@ $Id$ New angle—shock cut Out the window the body of a dead man suddenly slams into frame - + + + Plan américain (très légère plongée) de la plate-forme @@ -50,4 +46,4 @@ Out the window the body of a dead man suddenly slams into frame - \ No newline at end of file + diff --git a/P5/Source/Specs/caption.xml b/P5/Source/Specs/caption.xml index b048bafabf..d8c137f4f7 100644 --- a/P5/Source/Specs/caption.xml +++ b/P5/Source/Specs/caption.xml @@ -1,11 +1,5 @@ - + caption @@ -29,7 +23,8 @@ a film script or screenplay. Zoom in to overlay showing some stock film of hansom cabs -galloping past London, 1895. +galloping past + London, 1895. The residence of Mr Oscar Wilde. Suitably classy music starts. Mix through to Wilde's drawing room. A crowd of suitably @@ -81,4 +76,4 @@ laughing affectedly and drinking champagne. - \ No newline at end of file + diff --git a/P5/Source/Specs/case.xml b/P5/Source/Specs/case.xml index 7fee52299c..b67d1c687a 100644 --- a/P5/Source/Specs/case.xml +++ b/P5/Source/Specs/case.xml @@ -1,11 +1,5 @@ - + case diff --git a/P5/Source/Specs/castGroup.xml b/P5/Source/Specs/castGroup.xml index 0f49b30933..48b511fa28 100644 --- a/P5/Source/Specs/castGroup.xml +++ b/P5/Source/Specs/castGroup.xml @@ -1,11 +1,5 @@ - + cast list grouping @@ -24,33 +18,26 @@ elements within a cast list. dans une distribution, catégorie qui rassemble un ou plusieurs personnages. raggruppa uno o più elementi individuali castItem in una lista dei personaggi. - - - - - - - + + + + - - - + - - - + @@ -124,4 +111,4 @@ Mathias is understood to apply to both roles equally.

- \ No newline at end of file + diff --git a/P5/Source/Specs/castItem.xml b/P5/Source/Specs/castItem.xml index 0c0c7c527e..d512af0b18 100644 --- a/P5/Source/Specs/castItem.xml +++ b/P5/Source/Specs/castItem.xml @@ -1,11 +1,5 @@ - + cast list item @@ -29,13 +23,13 @@ either a single role or a list of non-speaking roles. - - - - - - - + + + + + + + @@ -46,7 +40,9 @@ either a single role or a list of non-speaking roles. 当該項目の種類を示す。 caractérise le personnage. indica la voce della lista dei personaggi - + + + role @@ -112,4 +108,4 @@ either a single role or a list of non-speaking roles. - \ No newline at end of file + diff --git a/P5/Source/Specs/castList.xml b/P5/Source/Specs/castList.xml index 6bf8c3db2c..df85e3f60e 100644 --- a/P5/Source/Specs/castList.xml +++ b/P5/Source/Specs/castList.xml @@ -1,11 +1,5 @@ - + cast list @@ -395,4 +389,4 @@ Dr Bero, lately returned from the wars. - \ No newline at end of file + diff --git a/P5/Source/Specs/catDesc.xml b/P5/Source/Specs/catDesc.xml index 7f80b20ac1..620503d0d9 100644 --- a/P5/Source/Specs/catDesc.xml +++ b/P5/Source/Specs/catDesc.xml @@ -1,11 +1,5 @@ - + category description @@ -39,13 +33,11 @@ $Id$ - - - - - - - + + + + + @@ -115,4 +107,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/catRef.xml b/P5/Source/Specs/catRef.xml index dcfd95506b..a74deebb53 100644 --- a/P5/Source/Specs/catRef.xml +++ b/P5/Source/Specs/catRef.xml @@ -1,11 +1,5 @@ - + category reference @@ -32,7 +26,9 @@ $Id$ - + + + identifies the classification scheme within which the set of categories concerned is @@ -43,14 +39,16 @@ $Id$ 관련 범주 집합이 정의된 분류 스키마를 표시한다. 標明該分類架構，其中相關的類目群組已被定義 たとえばtaxonomy要素あるいはその他の資料によって、当該分類項目が定義されている分類スキームを同定する。 - gibt das Klassifikationsschema an, in dem die entsprechenden Kategorien definiert sind, + gibt das Klassifikationsschema an, in dem die entsprechenden Kategorien definiert sind, z. B. über ein taxonomy-Element oder eine andere Ressource. indica el esquema de clasificación al interno del cual se define una serie de categorias referidas. identifica lo schema di classificazione all'interno del quale sono definite le categorie interessate. - + + + @@ -119,9 +117,9 @@ $Id$

当該属性sdchemeは、複数の分類法が宣言されている場合にのみ、必要と なる。

-

Das scheme-Attribut muss nur dann verwendet werden, wenn mehr als eine Taxonomie deklariert ist.

+

Das scheme-Attribut muss nur dann verwendet werden, wenn mehr als eine Taxonomie deklariert ist.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/catchwords.xml b/P5/Source/Specs/catchwords.xml index e9cbc1b77f..100cab0121 100644 --- a/P5/Source/Specs/catchwords.xml +++ b/P5/Source/Specs/catchwords.xml @@ -1,11 +1,5 @@ - + catchwords @@ -39,7 +33,7 @@ typically by means of annotations at the foot of the page. --> The element should not be used outside of msDesc. - + @@ -50,4 +44,4 @@ the inner bounding line, reading from top to bottom. - \ No newline at end of file + diff --git a/P5/Source/Specs/category.xml b/P5/Source/Specs/category.xml index f3ce5ea56f..96c6e82db3 100644 --- a/P5/Source/Specs/category.xml +++ b/P5/Source/Specs/category.xml @@ -1,11 +1,5 @@ - + category diff --git a/P5/Source/Specs/cb.xml b/P5/Source/Specs/cb.xml index 9513db699e..160547f2f5 100644 --- a/P5/Source/Specs/cb.xml +++ b/P5/Source/Specs/cb.xml @@ -1,11 +1,5 @@ - + column beginning @@ -32,7 +26,9 @@ - + + +

Markup of an early English dictionary printed in two columns:

@@ -77,4 +73,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/cell.xml b/P5/Source/Specs/cell.xml index 2fa7642941..d40a051996 100644 --- a/P5/Source/Specs/cell.xml +++ b/P5/Source/Specs/cell.xml @@ -1,11 +1,5 @@ - + cell @@ -55,4 +49,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/certainty.xml b/P5/Source/Specs/certainty.xml index b8542ee9e1..3f44a12e2a 100644 --- a/P5/Source/Specs/certainty.xml +++ b/P5/Source/Specs/certainty.xml @@ -1,11 +1,5 @@ - + indicates the degree of certainty associated @@ -25,10 +19,10 @@ $Id$ - - - - + + + + @@ -50,7 +44,9 @@ $Id$ 確実性 signifies the degree of certainty associated with the object pointed to by the certainty element. このcertainty要素が指す対象に関する確実性の程度を示す。 - + + + indicates more exactly the aspect concerning which @@ -67,7 +63,9 @@ $Id$ ou de fin, valeur d'un attribut spécifique, etc. indica la posición precisa de la incertidumbre en el marcaje: aplicabilidad del elemento, posición precisa del comienzo y del final de la etiqueta, valor de un atributo específico, etc. indica la posizione dell'incertezza nella codifica: l'applicabilità dell'elemento, la precisa posizione del marcatore iniziale o finale, il valore di un singolo attributo, ecc. - + + + uncertainty concerns whether the name of the element @@ -131,7 +129,9 @@ in the text. alternativo especificado por assertedValue; si no viene dado ninguno, se aplica al marcaje en el texto. assegna un valore alternativo all'apetto della codifica in questione, un identificatore generico, una trascrizione, il valore di un attributo, o l'identificatore di un elemento anchor (per indicare una posizione di inizio o fine alternativa). Se viene fornito un attributo assertedValue, il livello di sicurezza specificato dall'attributo degree si applica alla codifica alternativa specificata dall'attributo assertedValue; se non viene fornito alcun attributo, si applica alla codifica del testo. - + + + @@ -145,7 +145,6 @@ rather than the person. -

This attribute makes it possible to indicate the degree of confidence in a specific alternative to some aspect @@ -178,7 +177,9 @@ element.

l'attribution d'un degré de confiance. indica las condiciones asumidas en la asignación de un grado de confianza indica le condizioni presunte nell'assegnare un grado di certezza - + + +

The envisioned typical value of this attribute would be the identifier of another certainty element or a list of @@ -260,7 +261,9 @@ of the markup named by the locus attribute. indique le degré de confiance attribué à l'aspect du balisage que désigne l'attribut locus. indica el grado de confianza asignado al aspecto del marcaje llamado por el atributo locus indica il grado di certezza assegnato ad un aspetto della codifica indicato dall'attributo locus. - + + + diff --git a/P5/Source/Specs/change.xml b/P5/Source/Specs/change.xml index 8038d8e5c9..e844656925 100644 --- a/P5/Source/Specs/change.xml +++ b/P5/Source/Specs/change.xml @@ -1,10 +1,7 @@ - + + + + change Änderung 変更 @@ -42,47 +39,47 @@ $Id$ - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + target Ziel 対象 points to one or more elements that belong to this change. verweist auf ein oder mehrere Elemente, die zu dieser Änderung gehören. この変更の対象となる一つ以上の要素を指す。 - + + + @@ -179,4 +176,4 @@ supplied to printer. - \ No newline at end of file + diff --git a/P5/Source/Specs/channel.xml b/P5/Source/Specs/channel.xml index 5a4a5a615e..1a848d4ca5 100644 --- a/P5/Source/Specs/channel.xml +++ b/P5/Source/Specs/channel.xml @@ -1,11 +1,5 @@ - + primary channel @@ -45,7 +39,9 @@ for a spoken one, radio, telephone, face-to-face, etc. précise le mode de ce canal relatif à l'oral et à l'écrit. especifica el modo del canal respecto al texto hablado y escrito. specifica il modo del canale rispetto a parlato e scritto. - + + + x @@ -129,4 +125,4 @@ for a spoken one, radio, telephone, face-to-face, etc. - \ No newline at end of file + diff --git a/P5/Source/Specs/char.xml b/P5/Source/Specs/char.xml index f4c5d107c5..9961641cd7 100644 --- a/P5/Source/Specs/char.xml +++ b/P5/Source/Specs/char.xml @@ -1,11 +1,5 @@ - + character @@ -28,15 +22,15 @@ otherwise available in the document character set-->. - - - - - - - - - + + + + + + + + + @@ -61,4 +55,4 @@ otherwise available in the document character set-->. - \ No newline at end of file + diff --git a/P5/Source/Specs/charDecl.xml b/P5/Source/Specs/charDecl.xml index 773cc98e34..4633d85ed5 100644 --- a/P5/Source/Specs/charDecl.xml +++ b/P5/Source/Specs/charDecl.xml @@ -1,11 +1,5 @@ - + character declarations @@ -31,11 +25,11 @@ $Id$ - - - - - + + + + + @@ -51,4 +45,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/choice.xml b/P5/Source/Specs/choice.xml index 481c3da878..7e8ac1d665 100644 --- a/P5/Source/Specs/choice.xml +++ b/P5/Source/Specs/choice.xml @@ -1,16 +1,10 @@ - + choice choix - Alternative + Alternative groups a number of alternative encodings for the same point in a text. 텍스트 동일 지점에서 대체 가능한 부호화를 모아 놓는다. @@ -26,12 +20,12 @@ - - - - - - + + + + + +

An American encoding of Gulliver's Travels which retains the British spelling but also provides a version @@ -113,15 +107,15 @@

-

+

Da die Kindelemente des choice-Elements alternative Kodierungsmöglichkeiten der selben Textstelle repräsentieren, ist es naheliegend, sie als sich gegenseitig ausschließend zu betrachten. Es sind jedoch Fälle vorstellbar, in der Kodierungsalternativen als Kodierungsparallelen verstanden werden müssen, um den Text vollständig zu repräsentieren.

-

+

Man beachte außerdem, dass choice-Elemente weitere choice-Elemente als Kindelemente enthalten können.

-

+

In Fällen, in denen nicht mehrere mögliche Kodierungsvarianten, sondern Varianten aus mehreren Zeugen eines Werkes kodiert werden sollen, sind das app-Element und dazu gehörige Elemente, die im Abschnitt erläutert werden, zu bevorzugen.

@@ -129,4 +123,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/cit.xml b/P5/Source/Specs/cit.xml index 452b3b4dee..fb36101217 100644 --- a/P5/Source/Specs/cit.xml +++ b/P5/Source/Specs/cit.xml @@ -1,11 +1,5 @@ - + cited quotation @@ -31,7 +25,7 @@ bibliográfica a la fuente. Un acitazione da un altro documento accompagnata da riferimenti bibliografici alla fonte. - enthält ein Zitat aus einem anderen Dokument, zusammen mit einer bibliografischen Referenz auf die Quelle. In einem Wörterbuch kann es ein Beispieltext mit mindestens einem Vorkommen der Wortform enthalten, + enthält ein Zitat aus einem anderen Dokument, zusammen mit einer bibliografischen Referenz auf die Quelle. In einem Wörterbuch kann es ein Beispieltext mit mindestens einem Vorkommen der Wortform enthalten, welches in dem beschriebenen Sinne verwendet wird, oder eine Übersetzung des Lemmas, oder ein Beispiel. @@ -40,19 +34,17 @@ - - - - - - - - - - - - - + + + + + + + + + + + @@ -153,4 +145,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/citeData.xml b/P5/Source/Specs/citeData.xml index 806659b50c..34b934aabe 100644 --- a/P5/Source/Specs/citeData.xml +++ b/P5/Source/Specs/citeData.xml @@ -1,11 +1,5 @@ - + citation data @@ -15,7 +9,7 @@ $Id$ - + @@ -24,7 +18,7 @@ $Id$ - + @@ -32,7 +26,7 @@ $Id$ - + diff --git a/P5/Source/Specs/citeStructure.xml b/P5/Source/Specs/citeStructure.xml index 9244d3cf24..fdc5c421f4 100644 --- a/P5/Source/Specs/citeStructure.xml +++ b/P5/Source/Specs/citeStructure.xml @@ -1,11 +1,5 @@ - + citation structure diff --git a/P5/Source/Specs/citedRange.xml b/P5/Source/Specs/citedRange.xml index deb0192e3d..94a45c5064 100644 --- a/P5/Source/Specs/citedRange.xml +++ b/P5/Source/Specs/citedRange.xml @@ -1,11 +1,5 @@ - + cited range @@ -38,7 +32,8 @@ an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as p. 3ff might be encoded <citedRange from="3">p. 3ff</citedRange>.

- + + - \ No newline at end of file + diff --git a/P5/Source/Specs/cl.xml b/P5/Source/Specs/cl.xml index 93f9fa9fe5..cdd2c034b7 100644 --- a/P5/Source/Specs/cl.xml +++ b/P5/Source/Specs/cl.xml @@ -1,11 +1,5 @@ - + clause @@ -33,9 +27,13 @@ $Id$ - Which frightened - both the heroes so, - They quite forgot their quarrel. + + Which frightened + both the heroes so, + + + They quite forgot their quarrel. + @@ -65,4 +63,4 @@ etc. as appropriate.

- \ No newline at end of file + diff --git a/P5/Source/Specs/classCode.xml b/P5/Source/Specs/classCode.xml index 8037f787b2..c9d66f6893 100644 --- a/P5/Source/Specs/classCode.xml +++ b/P5/Source/Specs/classCode.xml @@ -1,11 +1,5 @@ - + classification code @@ -20,7 +14,7 @@ $Id$ 표준 분류 체계에서 이 텍스트에 대하여 사용된 분류 부호를 포함한다. 包含文件在某標準分類系統中所屬的分類代碼。 当該テキストで使用されている、ある規格に従った分類コードを示す。 - enthält den für den Text verwendeten Klassifikationscode auf Basis eines normierten Klassifikationssystems. + enthält den für den Text verwendeten Klassifikationscode auf Basis eines normierten Klassifikationssystems. indica el código de clasificación empleado para este texto en algún sistema de clasificación estándard. contiene il codice di classificazione utilizzato per @@ -41,13 +35,15 @@ $Id$ 사용하고 있는 분류 체계 또는 분류법을 표시한다. 說明使用中的分類系統或分類法。 当該分類法を定義する。 - benennt das verwendete Klassifikationssystem, definiert z. B. durch Verweis auf ein + benennt das verwendete Klassifikationssystem, definiert z. B. durch Verweis auf ein taxonomy-Element oder eine andere Ressource identifica el sistema de clasificación o taxonomía en uso. idantifica il sistema di classificazione o la tassonomia utilizzati. - + + + @@ -64,4 +60,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/classDecl.xml b/P5/Source/Specs/classDecl.xml index ebb75fedae..70cc5392d9 100644 --- a/P5/Source/Specs/classDecl.xml +++ b/P5/Source/Specs/classDecl.xml @@ -1,18 +1,12 @@ - + classification declarations déclaration de classification 분류 선언 分類宣告 - Angabe zur Klassifikation + Angabe zur Klassifikation declaraciones de clasificación dichiarazioni sulla ckassificazione contains one or more taxonomies defining any classificatory @@ -22,7 +16,7 @@ codes used elsewhere in the text. 包含一個或多個分類法，用來定義在文件中他處所使用之任何分類碼。 当該テキスト中で使用されている分類コードを定義する、ひとつ以上の分類 法を示す。 - enthält eine oder mehrere Taxonomien, die im Text verwendete Klassifikationscodes definieren. + enthält eine oder mehrere Taxonomien, die im Text verwendete Klassifikationscodes definieren. contiene una o más taxonomías que definen cualquier código usado en algún punto del texto. contiene una o più tassonomie che definiscono un qualsiasi codice classificatorio usato in un'altra porzione del testo. @@ -30,9 +24,7 @@ codes used elsewhere in the text. - - - + @@ -72,4 +64,4 @@ codes used elsewhere in the text. - \ No newline at end of file + diff --git a/P5/Source/Specs/classRef.xml b/P5/Source/Specs/classRef.xml index f28b7afa08..8611575054 100644 --- a/P5/Source/Specs/classRef.xml +++ b/P5/Source/Specs/classRef.xml @@ -1,11 +1,5 @@ - + points to the specification for an attribute or model class which is to be included in a schema @@ -15,12 +9,16 @@ - + + + the identifier used for the required class within the source indicated. - + + + indicates how references @@ -50,8 +48,8 @@ - -

If the members of the class are a, + +

If the members of the class are a, b and c, then a reference to the class within a content model is understood as being a reference to a|b|c when expand is @@ -67,12 +65,16 @@ supplies a list of class members which are to be included in the schema being defined. - + + + supplies a list of class members which are to be excluded from the schema being defined. - - + + + + @@ -87,7 +89,7 @@ - +

Attribute and model classes are identified by the name supplied as value for the ident attribute on the classSpec element in which they are declared. All TEI class names are unique; attribute @@ -97,4 +99,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/classSpec.xml b/P5/Source/Specs/classSpec.xml index a9e64e6e77..f6897e159c 100644 --- a/P5/Source/Specs/classSpec.xml +++ b/P5/Source/Specs/classSpec.xml @@ -1,11 +1,5 @@ - + class specification @@ -35,16 +29,16 @@ that is a group of - - - - - - - - - - + + + + + + + + + + @@ -57,7 +51,9 @@ that is a group of une classe d'attributs indica si se trata de una clase de modelos o de atributos. indica se si tratta di una classe di modelli o di attributi - + + + content model @@ -104,7 +100,9 @@ that is a group of défaut, toutes les variations sont données. indica que alternancia y que tipos de secuencia se establecen para una clase de modelos; por defecto se indican todas las variaciones. indica quale alternanza e quali tipi di sequenza stabilire per una classe di modelli; di norma sono indicate tutte le variazioni - + + + members of the class are alternatives diff --git a/P5/Source/Specs/classes.xml b/P5/Source/Specs/classes.xml index 0b19b23249..0f96450618 100644 --- a/P5/Source/Specs/classes.xml +++ b/P5/Source/Specs/classes.xml @@ -1,11 +1,5 @@ - + @@ -24,9 +18,7 @@ class is a member or subclass. - - - + @@ -38,7 +30,9 @@ class is a member or subclass. indique l'effet de cette déclaration sur son module parent. indica l'effetto della dichiarazione sul modulo da cui trae origine - + + + replace @@ -107,4 +101,4 @@ déclaration de même nom dans la définition courante. - \ No newline at end of file + diff --git a/P5/Source/Specs/climate.xml b/P5/Source/Specs/climate.xml index a60a1b6573..86a3c26cce 100644 --- a/P5/Source/Specs/climate.xml +++ b/P5/Source/Specs/climate.xml @@ -1,10 +1,7 @@ - + + + + climate climat contains information about the physical climate of a place. @@ -25,66 +22,50 @@ - - - - - - + + - - - - - - - - - - + + - - - - - - - - - + + + + + - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -126,4 +107,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/closer.xml b/P5/Source/Specs/closer.xml index 8346d985d3..ff775579f5 100644 --- a/P5/Source/Specs/closer.xml +++ b/P5/Source/Specs/closer.xml @@ -1,11 +1,5 @@ - + closer @@ -32,17 +26,15 @@ aparecen en la última sección al final de una división, especialmente en una - - - - - - - - - - - + + + + + + + + + @@ -124,4 +116,4 @@ aparecen en la última sección al final de una división, especialmente en una - \ No newline at end of file + diff --git a/P5/Source/Specs/code.xml b/P5/Source/Specs/code.xml index 40e0259249..92c05ff2e7 100644 --- a/P5/Source/Specs/code.xml +++ b/P5/Source/Specs/code.xml @@ -1,11 +1,5 @@ - + contains literal code from some formal language such as a @@ -40,7 +34,9 @@ programming language. lequel le code est exprimé es el nombre que identifica el lenguaje formal en el que se expresa el código. è il nome che identifica il linguaggio formale nel quale viene espresso il codice - + + + @@ -56,4 +52,4 @@ programming language. - \ No newline at end of file + diff --git a/P5/Source/Specs/collation.xml b/P5/Source/Specs/collation.xml index 2e33414be2..a4a322dc91 100644 --- a/P5/Source/Specs/collation.xml +++ b/P5/Source/Specs/collation.xml @@ -1,11 +1,5 @@ - + collation @@ -41,15 +35,15 @@ conjoint with the pastedown. -

- 1-5.8 6.6 (catchword, f. 46, does not match following text) 7-8.8 9.10, 11.2 +

+ 1-5.8 6.6 (catchword, f. 46, does not match following text) 7-8.8 9.10, 11.2 (through f. 82) 12-14.8 15.8(-7) - Catchwords are written horizontally in center or towards the right lower + Catchwords are written horizontally in center or towards the right lower margin in various manners: in red ink for quires 1-6 (which are also signed in red ink with letters of the alphabet and arabic numerals); quires 7-9 in ink of text within yellow decorated frames; quire 10 in red decorated frame; quire 12 in ink of text; quire 13 with red decorative slashes; quire 14 added in cursive hand. -

+

@@ -68,10 +62,10 @@ conjoint with the pastedown. -

- 1-5.8 6.6 (catchword, f. 46, does not match following text) +

+ 1-5.8 6.6 (catchword, f. 46, does not match following text) 7-8.8 9.10, 11.2 (through f. 82) 12-14.8 15.8(-7) - Catchwords are written horizontally in center + Catchwords are written horizontally in center or towards the right lower margin in various manners: in red ink for quires 1-6 (which are also signed in red ink with letters of the alphabet and arabic numerals); @@ -79,11 +73,11 @@ conjoint with the pastedown. quire 10 in red decorated frame; quire 12 in ink of text; quire 13 with red decorative slashes; quire 14 added in cursive hand. -

+

- \ No newline at end of file + diff --git a/P5/Source/Specs/collection.xml b/P5/Source/Specs/collection.xml index d15255849a..67ceb716ab 100644 --- a/P5/Source/Specs/collection.xml +++ b/P5/Source/Specs/collection.xml @@ -1,11 +1,5 @@ - + collection diff --git a/P5/Source/Specs/colloc.xml b/P5/Source/Specs/colloc.xml index 0de6099e7d..661f7358d6 100644 --- a/P5/Source/Specs/colloc.xml +++ b/P5/Source/Specs/colloc.xml @@ -1,11 +1,5 @@ - + collocate @@ -71,4 +65,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/colophon.xml b/P5/Source/Specs/colophon.xml index 0dc561b7e9..4dfc6ed3fc 100644 --- a/P5/Source/Specs/colophon.xml +++ b/P5/Source/Specs/colophon.xml @@ -1,11 +1,5 @@ - + colophon @@ -84,4 +78,4 @@ libellus iste. - \ No newline at end of file + diff --git a/P5/Source/Specs/cond.xml b/P5/Source/Specs/cond.xml index 48d88ca063..89bde6d52e 100644 --- a/P5/Source/Specs/cond.xml +++ b/P5/Source/Specs/cond.xml @@ -1,11 +1,5 @@ - + conditional feature-structure constraint @@ -84,4 +78,4 @@ structure, or if the antecedent does not. - \ No newline at end of file + diff --git a/P5/Source/Specs/condition.xml b/P5/Source/Specs/condition.xml index daed2a0c98..140a0ae2bf 100644 --- a/P5/Source/Specs/condition.xml +++ b/P5/Source/Specs/condition.xml @@ -1,11 +1,5 @@ - + condition @@ -79,4 +73,4 @@ touching up in the section 36r-59r containing - \ No newline at end of file + diff --git a/P5/Source/Specs/constitution.xml b/P5/Source/Specs/constitution.xml index 25f8214d7e..4d5d1829be 100644 --- a/P5/Source/Specs/constitution.xml +++ b/P5/Source/Specs/constitution.xml @@ -1,11 +1,5 @@ - + constitution @@ -36,7 +30,9 @@ as fragmentary, complete, etc. précise comment le texte a été constitué. indica cómo el texto fue constituido specifica come era costituito il testo. - + + + single @@ -126,4 +122,4 @@ the org attribute on div and the - \ No newline at end of file + diff --git a/P5/Source/Specs/constraint.xml b/P5/Source/Specs/constraint.xml index 0183768f58..5bb79ee1db 100644 --- a/P5/Source/Specs/constraint.xml +++ b/P5/Source/Specs/constraint.xml @@ -1,11 +1,5 @@ - + constraint rules @@ -41,4 +35,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/constraintSpec.xml b/P5/Source/Specs/constraintSpec.xml index ca2aad8f6f..b4060bed03 100644 --- a/P5/Source/Specs/constraintSpec.xml +++ b/P5/Source/Specs/constraintSpec.xml @@ -1,11 +1,5 @@ - + constraint on schema @@ -92,11 +86,13 @@ $Id$ --> supplies the name of the language in which the constraints are defined - + + + - The @scheme attribute of <constraintSpec> is required when the @mode is . + The @scheme attribute of <constraintSpec> is required when the @mode is . @@ -125,7 +121,9 @@ $Id$ constraintSpec element in some sense; used to indicate when a constraintSpec warns about a deprecated construct. - + + + Indicates that diff --git a/P5/Source/Specs/content.xml b/P5/Source/Specs/content.xml index a0b75ca295..a11904f7d4 100644 --- a/P5/Source/Specs/content.xml +++ b/P5/Source/Specs/content.xml @@ -1,11 +1,5 @@ - + content model @@ -39,32 +33,29 @@ $Id$ future the content of content will be restricted to 1 and only 1 child element. - - - - - - - - - - - - - - - - - which could be wrapped in a <sequence> element. + + + + + + + + + + + + + + + + which could be wrapped in a <sequence> element. - - which could be wrapped in an <rng:div> element. + which could be wrapped in an <rng:div> element. - - but those children are neither all TEI elements nor - all RELAX NG elements, and thus this <content> is invalid and can not be easily rectified. + but those children are neither all TEI elements nor + all RELAX NG elements, and thus this <content> is invalid and can not be easily rectified. - + @@ -73,7 +64,9 @@ $Id$ not pattern names generated in the corresponding RELAX NG schema source are automatically prefixed to avoid potential nameclashes. - + + + true @@ -98,8 +91,11 @@ $Id$

This sample content element indicates that the element being specified has no content:

- - + + + + +

This content element defines a content model, expressed directly in the TEI ODD language, that allows either a @@ -108,11 +104,11 @@ $Id$ - - - - - + + + + + diff --git a/P5/Source/Specs/conversion.xml b/P5/Source/Specs/conversion.xml index 016a233242..daaa49a93f 100644 --- a/P5/Source/Specs/conversion.xml +++ b/P5/Source/Specs/conversion.xml @@ -1,10 +1,7 @@ - + + + + defines how to calculate one unit of measure in terms of another. @@ -12,42 +9,42 @@ $Id$ - + + + - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + indicates a source unit of measure that is to be converted into another unit indicated in toUnit. @@ -76,4 +73,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/corr.xml b/P5/Source/Specs/corr.xml index 9bde810624..d5bcefe298 100644 --- a/P5/Source/Specs/corr.xml +++ b/P5/Source/Specs/corr.xml @@ -1,11 +1,5 @@ - + correction @@ -13,7 +7,7 @@ 更正 corrección correzione - Korrektur + Korrektur contains the correct form of a passage apparently erroneous in the copy text. 복사된 텍스트에서 오류로 보이는 단락의 정정 형식을 포함한다. 包含文本中看似錯誤並加以更正過後的文字。 @@ -86,4 +80,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/correction.xml b/P5/Source/Specs/correction.xml index 21683e3e93..e6aba24fb5 100644 --- a/P5/Source/Specs/correction.xml +++ b/P5/Source/Specs/correction.xml @@ -1,11 +1,5 @@ - + correction principles @@ -33,9 +27,7 @@ $Id$ - - - + @@ -48,7 +40,9 @@ $Id$ dem Text vorgenommen wurden. indica el grado de corrección aplicado al texto indica il gradi di corrzione apportata al testo. - + + + the text has been thoroughly checked and proofread. @@ -104,7 +98,9 @@ $Id$ correcciones al interno del texto. indica il metodo adottato per indicare le correzioni all'interno di un testo. - + + + silent @@ -179,4 +175,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/correspAction.xml b/P5/Source/Specs/correspAction.xml index de1cfa7afc..11d61d5591 100644 --- a/P5/Source/Specs/correspAction.xml +++ b/P5/Source/Specs/correspAction.xml @@ -1,20 +1,14 @@ - + correspondence action - 書簡に関する所作 + 書簡に関する所作 contains a structured description of the place, the name of a person/organization and the date related to the sending/receiving of a message or any other action related to the correspondence. - メッセージの送信・受信をはじめとする書簡に関する所作についての場所、人名／組織名、日付の構造的記述を含む。 + メッセージの送信・受信をはじめとする書簡に関する所作についての場所、人名／組織名、日付の構造的記述を含む。 @@ -31,7 +25,7 @@ describes the nature of the action. - （書簡に関する）所作の性質を記述する。 + （書簡に関する）所作の性質を記述する。 @@ -39,29 +33,29 @@ information concerning the sending or dispatch of a message. - メッセージの送信や発送に関する情報。 + メッセージの送信や発送に関する情報。 information concerning the receipt of a message. - メッセージの受信に関する情報。 + メッセージの受信に関する情報。 information concerning the transmission of a message, i.e. between the dispatch and the next receipt, redirect or forwarding. - メッセージの転送に関する情報。発送者と次の受信者、転送等。 + メッセージの転送に関する情報。発送者と次の受信者、転送等。 - + information concerning the redirection of an unread message. - 未読なままに転送されるメッセージに関する情報。 + 未読なままに転送されるメッセージに関する情報。 information concerning the forwarding of a message. - メッセージの転送に関する情報。 + メッセージの転送に関する情報。 @@ -79,4 +73,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/correspContext.xml b/P5/Source/Specs/correspContext.xml index 3f79fbeccc..e25c950086 100644 --- a/P5/Source/Specs/correspContext.xml +++ b/P5/Source/Specs/correspContext.xml @@ -1,55 +1,49 @@ - + - correspondence context - Korrespondenzstelle + correspondence context + Korrespondenzstelle 書簡の文脈 - - provides references to + + provides references to preceding or following correspondence related to this piece of correspondence. - 当該書簡に関連する前後の書簡への参照。 - - - - - - - - - - - - - - - - - - - + 当該書簡に関連する前後の書簡への参照。 + + + + + + + + + + + + + + + + + + + Previous letter of Carl Maria von Weber to Caroline Brandt: December 30, 1816 - - + + Next letter of Carl Maria von Weber to Caroline Brandt: January 5, 1817 - - - - - - - \ No newline at end of file + + + + + + + diff --git a/P5/Source/Specs/correspDesc.xml b/P5/Source/Specs/correspDesc.xml index eab25147a1..69874ea8c6 100644 --- a/P5/Source/Specs/correspDesc.xml +++ b/P5/Source/Specs/correspDesc.xml @@ -1,11 +1,5 @@ - + correspondence description @@ -25,12 +19,8 @@ - - - - - - + + @@ -63,4 +53,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/country.xml b/P5/Source/Specs/country.xml index 673cc04cc7..593dac0b78 100644 --- a/P5/Source/Specs/country.xml +++ b/P5/Source/Specs/country.xml @@ -1,10 +1,7 @@ - + + + + country pays contains the name of a geo-political unit, such as a nation, country, colony, or @@ -35,35 +32,35 @@ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -93,4 +90,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/creation.xml b/P5/Source/Specs/creation.xml index d996fd6126..f98f97749a 100644 --- a/P5/Source/Specs/creation.xml +++ b/P5/Source/Specs/creation.xml @@ -1,10 +1,7 @@ - + + + + creation création Entstehung @@ -14,7 +11,7 @@ $Id$ 텍스트 생성에 관한 정보를 포함한다. 包含關於文件建置的資訊。 テキストの作成に関する情報を示す。 - beinhaltet Informationen zur Entstehung eines Textes. + beinhaltet Informationen zur Entstehung eines Textes. contiene información sobre la creación del texto. contiene informazioni riguardanti la creazione di un testo. @@ -24,45 +21,43 @@ $Id$ - - - - - - - + + + + + - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -134,10 +129,10 @@ $Id$ 示す要素publicationStmtと混同しないように。

-

+

Das creation-Element kann dafür verwendet werden, Einzelheiten über die Entstehung eines Textes, z. B. Entstehungszeit und Entstehungsort, zu dokumentieren, wenn diese von Interesse sind.

-

Es kann auch eine mehr oder weniger strukturierte Entstehungsgeschichte mit den einzelnen Bearbeitungs- und Revisionstufen +

Es kann auch eine mehr oder weniger strukturierte Entstehungsgeschichte mit den einzelnen Bearbeitungs- und Revisionstufen enthalten; diese sollten mithilfe des listChange-Elements ausgezeichnet werden. Das creation-Element darf aber nicht mit dem publicationStmt-Element, das Zeit und Ort der Veröffentlichung verzeichnet, verwechselt werden.

@@ -146,4 +141,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/custEvent.xml b/P5/Source/Specs/custEvent.xml index 52b3ab5565..a59c2070da 100644 --- a/P5/Source/Specs/custEvent.xml +++ b/P5/Source/Specs/custEvent.xml @@ -1,10 +1,7 @@ - + + + + custodial event 보관 사건 @@ -29,35 +26,35 @@ $Id$ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -82,4 +79,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/custodialHist.xml b/P5/Source/Specs/custodialHist.xml index 230b2ecbae..66ae87fac8 100644 --- a/P5/Source/Specs/custodialHist.xml +++ b/P5/Source/Specs/custodialHist.xml @@ -1,11 +1,5 @@ - + custodial history @@ -29,12 +23,8 @@ as running prose or as a series of dated custodial events. - - - - - - + + @@ -76,4 +66,4 @@ Dispatched to Iceland - \ No newline at end of file + diff --git a/P5/Source/Specs/damage.xml b/P5/Source/Specs/damage.xml index 570c0f827e..ff96978a4b 100644 --- a/P5/Source/Specs/damage.xml +++ b/P5/Source/Specs/damage.xml @@ -1,10 +1,7 @@ - + + + + damage 当該文献におけるテキストの損傷部分を示す。 dommage @@ -57,7 +54,8 @@ appropriate for which circumstance.

Les éléments damage, gap, del, unclear etsupplied peuvent être utilisés en étroite association. Voir la section pour savoir en quelle circonstance chacun de ces éléments est approprié.

-

+ +

文献中のテキストが読み取れないほどの損傷である場合、要素damageは、 要素unclearをとるのが一般的である。 当該損傷部分が連続的ではない場合(例えば、文字列に被さるしみなど)、 @@ -65,13 +63,13 @@ appropriate for which circumstance.

とめることができる。また、要素joinを使い、要素 damageや要素unclearをまとめることで、同じような 損傷 がある部分を示すこともできる。 -

-

+

+

要素damage、gap、del、unclear、suppliedは、このような使用をされる。これらのどの要素が相 応しいかについての詳細はを参照のこと。 -

- +

+ - \ No newline at end of file + diff --git a/P5/Source/Specs/damageSpan.xml b/P5/Source/Specs/damageSpan.xml index 8eece011b5..84b946cbc4 100644 --- a/P5/Source/Specs/damageSpan.xml +++ b/P5/Source/Specs/damageSpan.xml @@ -1,11 +1,5 @@ - + damaged span of text @@ -29,7 +23,9 @@ endommagée d'une manière quelconque mais toujours lisible. - + + + The @spanTo attribute of is required. @@ -110,4 +106,4 @@ the start of the undamaged part of the text. ...

- \ No newline at end of file + diff --git a/P5/Source/Specs/dataFacet.xml b/P5/Source/Specs/dataFacet.xml index e6625f0a15..8640389d57 100644 --- a/P5/Source/Specs/dataFacet.xml +++ b/P5/Source/Specs/dataFacet.xml @@ -1,11 +1,5 @@ - + Restricts the value of the strings used to represent values of a datatype, @@ -14,30 +8,36 @@ - + + + - - the name of the facet. - - - - - - - - - - - - - - - - - - the facet value. - - + + the name of the facet. + + + + + + + + + + + + + + + + + + + + the facet value. + + + + @@ -52,13 +52,13 @@ - datatype used for attributes taking an integer value between 0 and 99 - + datatype used for attributes taking an integer value between 0 and 99 + - + diff --git a/P5/Source/Specs/dataRef.xml b/P5/Source/Specs/dataRef.xml index 0ec03f9ac7..82790078f6 100644 --- a/P5/Source/Specs/dataRef.xml +++ b/P5/Source/Specs/dataRef.xml @@ -1,11 +1,5 @@ - + identifies the datatype of an attribute value, either by referencing an item in an externally defined datatype library, or by @@ -39,23 +33,31 @@ the identifier used for this datatype specification - + + + the name of a datatype in the list provided by XML Schema Part 2: Datatypes Second Edition - + + + a pointer to a datatype defined in some datatype library - + + + supplies a string representing a regular expression providing additional constraints on the strings used to represent values of this datatype - - + + + + @@ -73,16 +75,18 @@ - - - - - datatype used for attributes taking an integer value between 0 and 99 - - - - - + + + + + + datatype used for attributes taking an integer value between 0 and 99 + + + + + +

Only one of the attributes key, name, and ref may be used on any given instance of dataRef.

Neither a restriction attribute nor a dataFacet child element may be used unless the dataRef refers to a datatype from the specification XML Schema Part 2: Datatypes Second Edition with a name attribute.

diff --git a/P5/Source/Specs/dataSpec.xml b/P5/Source/Specs/dataSpec.xml index 45038fd7c8..7a3c0a9d7a 100644 --- a/P5/Source/Specs/dataSpec.xml +++ b/P5/Source/Specs/dataSpec.xml @@ -1,11 +1,5 @@ - + datatype specification @@ -20,10 +14,10 @@ $Id$ - + - - + + diff --git a/P5/Source/Specs/datatype.xml b/P5/Source/Specs/datatype.xml index 08231604d8..5c76d969df 100644 --- a/P5/Source/Specs/datatype.xml +++ b/P5/Source/Specs/datatype.xml @@ -1,11 +1,5 @@ - + datatype @@ -130,4 +124,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/date.xml b/P5/Source/Specs/date.xml index 6df99c070a..2211459b50 100644 --- a/P5/Source/Specs/date.xml +++ b/P5/Source/Specs/date.xml @@ -1,11 +1,5 @@ - + date @@ -31,7 +25,7 @@ - + diff --git a/P5/Source/Specs/dateline.xml b/P5/Source/Specs/dateline.xml index 4c6fe76e63..e20248f804 100644 --- a/P5/Source/Specs/dateline.xml +++ b/P5/Source/Specs/dateline.xml @@ -1,11 +1,5 @@ - + dateline @@ -38,15 +32,13 @@ $Id$ docDate to the content model, so it now has to be explicit instead of macro.phraseSeq. --> - - - - - - - - - + + + + + + + @@ -114,4 +106,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/death.xml b/P5/Source/Specs/death.xml index e61e7384cb..9aaf7b0bb0 100644 --- a/P5/Source/Specs/death.xml +++ b/P5/Source/Specs/death.xml @@ -1,10 +1,7 @@ - + + + + death décès contains information about a person's death, such as its date and place. @@ -27,56 +24,54 @@ - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + - + - - - - - - - - - + + + + + + + + + -

This attribute is not intended to express the cause of death.

+

This attribute is not intended to express the cause of death.

 @@ -108,4 +103,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/decoDesc.xml b/P5/Source/Specs/decoDesc.xml index e2a52e9c07..f88459d41b 100644 --- a/P5/Source/Specs/decoDesc.xml +++ b/P5/Source/Specs/decoDesc.xml @@ -1,11 +1,5 @@ - + decoration description @@ -31,16 +25,10 @@ $Id$ - - - + - - - - - - + + @@ -72,4 +60,4 @@ with 1-line initials, alternately blue or red.

- \ No newline at end of file + diff --git a/P5/Source/Specs/decoNote.xml b/P5/Source/Specs/decoNote.xml index 6c95ba57f4..b7258b8322 100644 --- a/P5/Source/Specs/decoNote.xml +++ b/P5/Source/Specs/decoNote.xml @@ -1,11 +1,5 @@ - + note on decoration @@ -87,4 +81,4 @@ alternately blue or red.

- \ No newline at end of file + diff --git a/P5/Source/Specs/def.xml b/P5/Source/Specs/def.xml index f7151abe78..de93922425 100644 --- a/P5/Source/Specs/def.xml +++ b/P5/Source/Specs/def.xml @@ -1,11 +1,5 @@ - + definition @@ -88,4 +82,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/default.xml b/P5/Source/Specs/default.xml index 1e149c388d..53c6959b33 100644 --- a/P5/Source/Specs/default.xml +++ b/P5/Source/Specs/default.xml @@ -1,11 +1,5 @@ - + default feature value @@ -27,7 +21,9 @@ $Id$ - + + + @@ -45,4 +41,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/defaultVal.xml b/P5/Source/Specs/defaultVal.xml index aafe69f4b5..5904b8426f 100644 --- a/P5/Source/Specs/defaultVal.xml +++ b/P5/Source/Specs/defaultVal.xml @@ -1,11 +1,5 @@ - + default value @@ -59,4 +53,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/del.xml b/P5/Source/Specs/del.xml index 1f04fabb6a..d5e3236bb5 100644 --- a/P5/Source/Specs/del.xml +++ b/P5/Source/Specs/del.xml @@ -1,11 +1,5 @@ - + deletion @@ -166,4 +160,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/delSpan.xml b/P5/Source/Specs/delSpan.xml index 9f1a06edb9..9f0ca0cb84 100644 --- a/P5/Source/Specs/delSpan.xml +++ b/P5/Source/Specs/delSpan.xml @@ -1,11 +1,5 @@ - + deleted span of text @@ -33,7 +27,9 @@ author, scribe, annotator, or corrector. - + + + The @spanTo attribute of is required. @@ -131,4 +127,4 @@ the resumption of the text. ...

- \ No newline at end of file + diff --git a/P5/Source/Specs/depth.xml b/P5/Source/Specs/depth.xml index e4a8171c38..94daeb9478 100644 --- a/P5/Source/Specs/depth.xml +++ b/P5/Source/Specs/depth.xml @@ -1,11 +1,5 @@ - + depth @@ -40,4 +34,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/derivation.xml b/P5/Source/Specs/derivation.xml index a237382430..50143e0653 100644 --- a/P5/Source/Specs/derivation.xml +++ b/P5/Source/Specs/derivation.xml @@ -1,11 +1,5 @@ - + derivation @@ -35,7 +29,9 @@ $Id$ catégorise la dérivation du texte. caracteriza la derivación del texto classifica la provenienza del testo. - + + + text is original @@ -117,8 +113,7 @@ est l'un des nombreux textes dérivés d'un ancêtre commun. - - de Béranger, Pierre-Jean. 1839. "Rosette". In H. Fournier, ed. Œuvres complètes de Béranger. Vol 2 (p. 29-30). + de Béranger, Pierre-Jean. 1839. "Rosette". In H. Fournier, ed. Œuvres complètes de Béranger. Vol 2 (p. 29-30). @@ -148,4 +143,4 @@ may be included in the source description.

- \ No newline at end of file + diff --git a/P5/Source/Specs/desc.xml b/P5/Source/Specs/desc.xml index e5bdf55bf3..868aee5166 100644 --- a/P5/Source/Specs/desc.xml +++ b/P5/Source/Specs/desc.xml @@ -1,11 +1,5 @@ - + description @@ -75,13 +69,13 @@ - + Several standards bodies, including NIST in the USA, strongly recommend against ending the representation of a number with a decimal point. So instead of 3. use either 3 or 3.0. - + @@ -100,16 +94,16 @@

Example of a desc element in a non-documentation element.

- - - Kerguelen Islands - - - antarctic tundra - - - - + + + Kerguelen Islands + + + antarctic tundra + + + + @@ -145,4 +139,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/dictScrap.xml b/P5/Source/Specs/dictScrap.xml index c4174b6283..40e8516795 100644 --- a/P5/Source/Specs/dictScrap.xml +++ b/P5/Source/Specs/dictScrap.xml @@ -1,11 +1,5 @@ - + dictionary scrap @@ -28,17 +22,15 @@ $Id$ - - - - - - - - - - - + + + + + + + + + @@ -103,4 +95,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/dim.xml b/P5/Source/Specs/dim.xml index e4238bc1af..9dc2dae40c 100644 --- a/P5/Source/Specs/dim.xml +++ b/P5/Source/Specs/dim.xml @@ -1,11 +1,5 @@ - + contains any single measurement forming part of a dimensional @@ -32,4 +26,4 @@ wherever appropriate.

- \ No newline at end of file + diff --git a/P5/Source/Specs/dimensions.xml b/P5/Source/Specs/dimensions.xml index da74e64b90..c6ba5d8a35 100644 --- a/P5/Source/Specs/dimensions.xml +++ b/P5/Source/Specs/dimensions.xml @@ -1,11 +1,5 @@ - + dimensions @@ -51,7 +45,9 @@ $Id$ indique quel aspect de l'objet est mesuré. indica que aspecto del objeto se mide. indica quale aspetto dell'oggetto viene misurato - + + + dimensions relate to one or more leaves (e.g. a single leaf, a diff --git a/P5/Source/Specs/distinct.xml b/P5/Source/Specs/distinct.xml index 92d02f8f3c..aae90e9029 100644 --- a/P5/Source/Specs/distinct.xml +++ b/P5/Source/Specs/distinct.xml @@ -1,11 +1,5 @@ - + identifies any word or phrase which is regarded as linguistically distinct, for example as @@ -45,7 +39,9 @@ asigna una palabra, locución o sintagma. indica la lingua secondaria o il registro al quale la parola o il sintagma è ricondotto - + + + specifies how the phrase is distinct diachronically @@ -57,7 +53,9 @@ diacrónicamente indica come il sintagma sia distinto diacronicamente - + + + specifies how the phrase is distinct diatopically @@ -70,7 +68,9 @@ diatópicamente indica come il sintagma sia distinto in modo diatopico - + + + specifies how the phrase is distinct diastratically @@ -83,7 +83,9 @@ diastáticamente. indica come il sintagma sia distinto in modo diastratico - + + + @@ -106,4 +108,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/distributor.xml b/P5/Source/Specs/distributor.xml index 9b134e6914..76a7c78df7 100644 --- a/P5/Source/Specs/distributor.xml +++ b/P5/Source/Specs/distributor.xml @@ -1,11 +1,5 @@ - + distributor @@ -17,7 +11,7 @@ distribution of a text. 텍스트 배포 권한을 갖는 개인 또는 기관의 이름을 제시한다. 提供負責發行文件的個人或其他經銷商的名稱。 テキストの頒布に責任を持つ人物または団体の名前を示す。 - gibt die Person oder Instanz an, die für die Distribution des Textes verantwortlich ist. + gibt die Person oder Instanz an, die für die Distribution des Textes verantwortlich ist. proporciona el nombre de la persona o agente responsable de la distribución de un texto. fornisce il nome di una persona o di un'organizzazione responsabile della distribuzione di un testo. @@ -51,4 +45,4 @@ distribution of a text. - \ No newline at end of file + diff --git a/P5/Source/Specs/district.xml b/P5/Source/Specs/district.xml index cc2b2aa76d..425802285a 100644 --- a/P5/Source/Specs/district.xml +++ b/P5/Source/Specs/district.xml @@ -1,10 +1,7 @@ - + + + + district district contains the name of any kind of subdivision of a settlement, such as a parish, ward, or other administrative or geographic unit. @@ -29,35 +26,35 @@ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -111,4 +108,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/div.xml b/P5/Source/Specs/div.xml index 7422d13557..577f50536f 100644 --- a/P5/Source/Specs/div.xml +++ b/P5/Source/Specs/div.xml @@ -1,11 +1,5 @@ - + text division @@ -164,4 +158,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/div1.xml b/P5/Source/Specs/div1.xml index f5db865235..a5a2cc3b9e 100644 --- a/P5/Source/Specs/div1.xml +++ b/P5/Source/Specs/div1.xml @@ -1,11 +1,5 @@ - + level-1 text division @@ -138,4 +132,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/div2.xml b/P5/Source/Specs/div2.xml index e9b1bef023..0436ba4a04 100644 --- a/P5/Source/Specs/div2.xml +++ b/P5/Source/Specs/div2.xml @@ -1,11 +1,5 @@ - + level-2 text division @@ -181,4 +175,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/div3.xml b/P5/Source/Specs/div3.xml index 3d1dbf0fbc..868c55716d 100644 --- a/P5/Source/Specs/div3.xml +++ b/P5/Source/Specs/div3.xml @@ -1,11 +1,5 @@ - + level-3 text division @@ -143,4 +137,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/div4.xml b/P5/Source/Specs/div4.xml index a36839d6b7..902bab446b 100644 --- a/P5/Source/Specs/div4.xml +++ b/P5/Source/Specs/div4.xml @@ -1,11 +1,5 @@ - + level-4 text division diff --git a/P5/Source/Specs/div5.xml b/P5/Source/Specs/div5.xml index 578b7b5840..f3128394de 100644 --- a/P5/Source/Specs/div5.xml +++ b/P5/Source/Specs/div5.xml @@ -1,11 +1,5 @@ - + level-5 text division diff --git a/P5/Source/Specs/div6.xml b/P5/Source/Specs/div6.xml index c64d65ff3a..3a66bebfc4 100644 --- a/P5/Source/Specs/div6.xml +++ b/P5/Source/Specs/div6.xml @@ -1,11 +1,5 @@ - + level-6 text division diff --git a/P5/Source/Specs/div7.xml b/P5/Source/Specs/div7.xml index b680a248b5..f9b2381e34 100644 --- a/P5/Source/Specs/div7.xml +++ b/P5/Source/Specs/div7.xml @@ -1,11 +1,5 @@ - + level-7 text division @@ -27,96 +21,96 @@ $Id$ Vorspann (front), Kerntext oder Nachspann (back) eines Textes, die größer als ein Absatz ist. contiene la subdivisión más pequeña, pero más grande que un párrafo, del paratexto inicial, del cuerpo del texto o del paratexto final. - contiene la sezione più ristretta, ma più ampia di un + contiene la sezione più ristretta, ma più ampia di un paragrafo, del peritesto iniziale, del corpo del testo, o del peritesto finale - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + - - - - - Recipes - Chapter VI. - - Fruit and vegetable soups -

...

- - Stocks for all kinds of soups - - Asparagus soup - - I. - - Ingredients - - ... - - - - Mode -

Put the beef, cut into pieces and rolled in flour, into a + + + + + + Recipes + Chapter VI. + + Fruit and vegetable soups +

...

+ + Stocks for all kinds of soups + + Asparagus soup + + I. + + Ingredients + + ... + + + + Mode +

Put the beef, cut into pieces and rolled in flour, into a stewpan...

- - - - - II. - - Ingredients - - ... - - - - Mode -

Boil the peas, and rub them through a sieve; add the gravy...

- - - - - - - - - -

any sequence of low-level structural elements, e.g., paragraphs (p), + + + + + II. + + Ingredients + + ... + + + + Mode +

Boil the peas, and rub them through a sieve; add the gravy...

+ + + + + + + + + +

any sequence of low-level structural elements, e.g., paragraphs (p), lists (list), or examples (eg or egXML).

- - -

Cet élément contient une séquence d'éléments structurels de bas niveau, par + + +

Cet élément contient une séquence d'éléments structurels de bas niveau, par exemple des paragraphes (p), des listes (list), ou des exemples (eg ou egXML).

- - -

一連の低レベル構造単位要素。例えば、段落(p)、リスト + + +

一連の低レベル構造単位要素。例えば、段落(p)、リスト (list)、用例(egまたはegXML)など。

- - - - - \ No newline at end of file + + + + + diff --git a/P5/Source/Specs/divGen.xml b/P5/Source/Specs/divGen.xml index f563e704c6..76a0101559 100644 --- a/P5/Source/Specs/divGen.xml +++ b/P5/Source/Specs/divGen.xml @@ -1,11 +1,5 @@ - + automatically generated text division @@ -31,7 +25,7 @@ - + @@ -45,7 +39,9 @@ table des matières, etc.) especifica que tipo de divisón de texto generada aparece (p.ej. índice, tabla de contenidos, etc.) specifica quale tipo di partizione testuale generata (ad esempio indice, sommario, ecc.) apparirà - + + + an index is to be generated and inserted at this point. diff --git a/P5/Source/Specs/docAuthor.xml b/P5/Source/Specs/docAuthor.xml index a7572502c3..0c5e6c8fb8 100644 --- a/P5/Source/Specs/docAuthor.xml +++ b/P5/Source/Specs/docAuthor.xml @@ -1,11 +1,5 @@ - + document author @@ -92,4 +86,4 @@ and then a Captain of several Ships - \ No newline at end of file + diff --git a/P5/Source/Specs/docDate.xml b/P5/Source/Specs/docDate.xml index 4d1ac7b53f..bc43bf7da6 100644 --- a/P5/Source/Specs/docDate.xml +++ b/P5/Source/Specs/docDate.xml @@ -1,11 +1,5 @@ - + document date diff --git a/P5/Source/Specs/docEdition.xml b/P5/Source/Specs/docEdition.xml index c9fdbfed02..4aabfee97c 100644 --- a/P5/Source/Specs/docEdition.xml +++ b/P5/Source/Specs/docEdition.xml @@ -1,11 +1,5 @@ - + document edition @@ -71,4 +65,4 @@ more frequent element.

- \ No newline at end of file + diff --git a/P5/Source/Specs/docImprint.xml b/P5/Source/Specs/docImprint.xml index 4bdb5a9da0..5e96df31ef 100644 --- a/P5/Source/Specs/docImprint.xml +++ b/P5/Source/Specs/docImprint.xml @@ -1,11 +1,5 @@ - + document imprint @@ -34,17 +28,15 @@ publisher name), as given - - - - - - - - - - - + + + + + + + + + @@ -133,4 +125,4 @@ reserved for the element likely to be used more often.

- \ No newline at end of file + diff --git a/P5/Source/Specs/docTitle.xml b/P5/Source/Specs/docTitle.xml index 58420939ce..a21b3a2ceb 100644 --- a/P5/Source/Specs/docTitle.xml +++ b/P5/Source/Specs/docTitle.xml @@ -1,11 +1,5 @@ - + document title @@ -34,14 +28,10 @@ constituents, as given on a title page. - - - + - - - + @@ -72,4 +62,4 @@ constituents, as given on a title page. - \ No newline at end of file + diff --git a/P5/Source/Specs/domain.xml b/P5/Source/Specs/domain.xml index 8e76214bbd..9549d87969 100644 --- a/P5/Source/Specs/domain.xml +++ b/P5/Source/Specs/domain.xml @@ -1,11 +1,5 @@ - + domain of use @@ -43,7 +37,9 @@ education, religion, etc. catégorise le domaine d'usage clasifica el campo de uso. classifica l'ambito di uso. - + + + art and entertainment @@ -159,4 +155,4 @@ purposes.

- \ No newline at end of file + diff --git a/P5/Source/Specs/eLeaf.xml b/P5/Source/Specs/eLeaf.xml index c2c5fbaf04..362f6d94b3 100644 --- a/P5/Source/Specs/eLeaf.xml +++ b/P5/Source/Specs/eLeaf.xml @@ -1,11 +1,5 @@ - + leaf or terminal node of an embedding tree @@ -29,12 +23,8 @@ be encoded with the eTree element. - - - - - - + + @@ -48,8 +38,11 @@ structure or other analytic element. 素である。 fournit l'identifiant de l'objet représenté par la feuille de l'arbre englobant ; cet objet peut être une paire nom-valeur ou tout autre élément analytique. assegna alla foglia integrata un valore, che può essere una struttura di tratti o altro elemento di analisi - - + + + + + @@ -82,4 +75,4 @@ embedding trees; they are distinguished by their arrangement.

- \ No newline at end of file + diff --git a/P5/Source/Specs/eTree.xml b/P5/Source/Specs/eTree.xml index 1fdf34fe96..32adf5e3f4 100644 --- a/P5/Source/Specs/eTree.xml +++ b/P5/Source/Specs/eTree.xml @@ -1,11 +1,5 @@ - + embedding tree @@ -49,7 +43,9 @@ structure or other analytic element. fournit l'identifiant de l'objet représenté par l'arbre englobant ; cet objet peut être une paire nom-valeur ou tout autre élément analytique. adscribe al árbol integrado un valor, que puede ser una estructura de rasgos u otro elemento de análisis. assegna all'albero integrato un valore, che può essere una struttura di tratti o altro elemento di analisi - + + + @@ -123,4 +119,4 @@ structure or other analytic element. - \ No newline at end of file + diff --git a/P5/Source/Specs/edition.xml b/P5/Source/Specs/edition.xml index 7e8cbed118..9b8dd26b18 100644 --- a/P5/Source/Specs/edition.xml +++ b/P5/Source/Specs/edition.xml @@ -1,11 +1,5 @@ - + edition @@ -20,7 +14,7 @@ $Id$ 텍스트의 한 판의 특성을 기술한다. 描述文件某一版本的特質。 テキストの版の詳細を示す。 - beschreibt die Details einer Ausgabe eines Textes. + beschreibt die Details einer Ausgabe eines Textes. describe las particularidades de la edición de un texto. descrive le peculiarità di una edizione del testo. @@ -53,4 +47,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/editionStmt.xml b/P5/Source/Specs/editionStmt.xml index 4620c6c305..a5f701a719 100644 --- a/P5/Source/Specs/editionStmt.xml +++ b/P5/Source/Specs/editionStmt.xml @@ -1,11 +1,5 @@ - + edition statement @@ -20,7 +14,7 @@ $Id$ 텍스트의 한 판에 관련된 정보를 모아 놓는다. 匯集文件某一版本的相關資訊。 版に関する情報をまとめる。 - umfasst Angaben, die sich auf eine spezifische Ausgabe eines Textes beziehen. + umfasst Angaben, die sich auf eine spezifische Ausgabe eines Textes beziehen. agrupa la información relativa a la edición de un texto. raggruppa le informazioni riguardo una edizione di un testo. @@ -28,14 +22,10 @@ $Id$ - - - + - - - + @@ -100,4 +90,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/editor.xml b/P5/Source/Specs/editor.xml index d566c65068..e44da3f761 100644 --- a/P5/Source/Specs/editor.xml +++ b/P5/Source/Specs/editor.xml @@ -1,10 +1,7 @@ - + + + + contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, @@ -36,38 +33,37 @@ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - Ron Van den Branden @@ -111,4 +107,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/editorialDecl.xml b/P5/Source/Specs/editorialDecl.xml index 50f39b8eb9..615a87f9c0 100644 --- a/P5/Source/Specs/editorialDecl.xml +++ b/P5/Source/Specs/editorialDecl.xml @@ -1,18 +1,12 @@ - + editorial practice declaration déclaration des pratiques éditoriales 편집 실행 선언 編輯實行宣告 - Angabe der Editionsprinzipien + Angabe der Editionsprinzipien declaración de la edición dichiarazione sulle pratiche editoriali provides details of editorial principles and practices applied @@ -21,7 +15,7 @@ during the encoding of a text. 텍스트 부호화에서 적용된 편집 원리 및 기준의 상세 항목을 제시한다. 提供文件編碼時使用的編輯原則與實行方法的細節。 テキストを符号化する際に適用される編集方針や編集方法の詳細を示す。 - beschreibt die Details der Editionsprinzipien und Verfahren, die bei der Kodierung des Textes angewandt wurden. + beschreibt die Details der Editionsprinzipien und Verfahren, die bei der Kodierung des Textes angewandt wurden. proporciona detalles de principios editoriales y prácticas aplicadas en la codificación de un texto. fornisce dettagli su principi e pratiche editoriali seguite nella codifica di un testo. @@ -30,12 +24,10 @@ during the encoding of a text. - - - - - - + + + + @@ -83,4 +75,4 @@ during the encoding of a text. - \ No newline at end of file + diff --git a/P5/Source/Specs/education.xml b/P5/Source/Specs/education.xml index 5867523916..7c73b9ffd1 100644 --- a/P5/Source/Specs/education.xml +++ b/P5/Source/Specs/education.xml @@ -1,10 +1,7 @@ - + + + + education éducation contains a description of the educational experience of a person. @@ -26,50 +23,48 @@ - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + - + - - - - - - + + + + + + @@ -79,7 +74,7 @@ - + Attended Cherwell School @@ -107,4 +102,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/eg.xml b/P5/Source/Specs/eg.xml index 18f8406df5..64698b533a 100644 --- a/P5/Source/Specs/eg.xml +++ b/P5/Source/Specs/eg.xml @@ -1,11 +1,5 @@ - + example @@ -76,4 +70,4 @@ references must be used to represent the markup delimiters. If the - \ No newline at end of file + diff --git a/P5/Source/Specs/egXML.xml b/P5/Source/Specs/egXML.xml index 4839ff6a0a..7db4a4186f 100644 --- a/P5/Source/Specs/egXML.xml +++ b/P5/Source/Specs/egXML.xml @@ -1,11 +1,5 @@ - + example of XML @@ -42,7 +36,9 @@ $Id$ indicates the intended validity of the example with respect to a schema. - + + + true @@ -66,51 +62,45 @@ and contains deliberate errors. - -
- A slide about egXML - - egXML can be used to give XML examples in the TEI + +
+ A slide about egXML + + egXML can be used to give XML examples in the TEI Examples namespace - Attributes values for valid: - - true: intended to be fully -valid - feasible: valid if missing nodes -provided - false: not intended to be valid - + Attributes values for valid: + true: intended to be fully +validfeasible: valid if missing nodes +providedfalse: not intended to be valid - The rend attribute can be + The rend attribute can be used for recording how parts of the example were rendered. - -
- - - + +
+ + - - - - - - - - - - - - - + + + + + + + + + + + - - + - <egXML xmlns="http://www.tei-c.org/ns/Examples" valid="false"> @@ -118,7 +108,6 @@ provided </egXML> -

In the source of the TEI Guidelines, this element declares itself and its content as belonging to the namespace http://www.tei-c.org/ns/Examples. This @@ -148,4 +137,4 @@ provided - \ No newline at end of file + diff --git a/P5/Source/Specs/elementRef.xml b/P5/Source/Specs/elementRef.xml index 5dcc969eff..71658b36d9 100644 --- a/P5/Source/Specs/elementRef.xml +++ b/P5/Source/Specs/elementRef.xml @@ -1,11 +1,5 @@ - + points to the specification for some element which is to be included in a schema @@ -15,12 +9,16 @@ - + + + the identifier used for the required element within the source indicated. - + + + @@ -46,4 +44,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/elementSpec.xml b/P5/Source/Specs/elementSpec.xml index 5602119338..2aa54f15a7 100644 --- a/P5/Source/Specs/elementSpec.xml +++ b/P5/Source/Specs/elementSpec.xml @@ -1,11 +1,5 @@ - + element specification @@ -72,7 +66,9 @@ $Id$ specifies a default prefix which will be prepended to all patterns relating to the element, unless otherwise stated. - + + + diff --git a/P5/Source/Specs/ellipsis.xml b/P5/Source/Specs/ellipsis.xml index 41fd5f921d..95797e121b 100644 --- a/P5/Source/Specs/ellipsis.xml +++ b/P5/Source/Specs/ellipsis.xml @@ -1,11 +1,5 @@ - + deliberately marked omission @@ -45,8 +39,8 @@ And what does it reck, should you e’en break your neck, If ’tis steam that brings on the disaster? - * * * * - The printer omits four lines here, + * * * * + The printer omits four lines here, skipping the second half of the second octave, before the refrain. Oh dear! think of a scheme, odd though it seem— diff --git a/P5/Source/Specs/email.xml b/P5/Source/Specs/email.xml index d178f73fb2..1acecb707b 100644 --- a/P5/Source/Specs/email.xml +++ b/P5/Source/Specs/email.xml @@ -1,11 +1,5 @@ - + electronic mail address @@ -60,4 +54,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/emph.xml b/P5/Source/Specs/emph.xml index 8eda527511..319f9a0b76 100644 --- a/P5/Source/Specs/emph.xml +++ b/P5/Source/Specs/emph.xml @@ -1,11 +1,5 @@ - + emphasized @@ -72,4 +66,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/empty.xml b/P5/Source/Specs/empty.xml index 466c44b5eb..6408e9cce0 100644 --- a/P5/Source/Specs/empty.xml +++ b/P5/Source/Specs/empty.xml @@ -1,11 +1,5 @@ - + indicates the presence of an empty node within a @@ -14,7 +8,9 @@ $Id$ - + + + @@ -28,4 +24,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/encodingDesc.xml b/P5/Source/Specs/encodingDesc.xml index 59e4007d1e..b35e14d424 100644 --- a/P5/Source/Specs/encodingDesc.xml +++ b/P5/Source/Specs/encodingDesc.xml @@ -1,11 +1,5 @@ - + encoding description @@ -21,7 +15,7 @@ source or sources from which it was derived. 전자 텍스트와 그것의 원전 텍스트 혹은 텍스트들 사이의 관련성을 기록한다. 記錄電子文件和其ㄧ個或多個文件來源之間的關係。 電子テキストとその元資料との関係を示す。 - dokumentiert das Verhältnis zwischen dem elektronischen Text und seiner Quelle oder den Quellen, von denen er sich ableitet. + dokumentiert das Verhältnis zwischen dem elektronischen Text und seiner Quelle oder den Quellen, von denen er sich ableitet. documenta la relación entre un texto electrónico y la fuente o fuentes de las que este deriva. documenta la relazione fra un documento elettronico e la o le fonti da cui è derivato. @@ -29,14 +23,10 @@ source or sources from which it was derived. - - - - - - - - + + + + @@ -67,4 +57,4 @@ formatting or layout information preserved.

- \ No newline at end of file + diff --git a/P5/Source/Specs/entry.xml b/P5/Source/Specs/entry.xml index 6f664581a1..9df7af60ac 100644 --- a/P5/Source/Specs/entry.xml +++ b/P5/Source/Specs/entry.xml @@ -1,11 +1,5 @@ - + entry @@ -123,4 +117,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/entryFree.xml b/P5/Source/Specs/entryFree.xml index e4350e10dd..d4557291ef 100644 --- a/P5/Source/Specs/entryFree.xml +++ b/P5/Source/Specs/entryFree.xml @@ -1,11 +1,5 @@ - + unstructured entry @@ -32,17 +26,15 @@ $Id$ - - - - - - - - - - - + + + + + + + + + @@ -96,4 +88,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/epigraph.xml b/P5/Source/Specs/epigraph.xml index 17e71d7bb8..5fe34666fc 100644 --- a/P5/Source/Specs/epigraph.xml +++ b/P5/Source/Specs/epigraph.xml @@ -1,11 +1,5 @@ - + epigraph @@ -30,12 +24,10 @@ $Id$ - - - - - - + + + + @@ -68,4 +60,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/epilogue.xml b/P5/Source/Specs/epilogue.xml index d3b54436a4..ca29b554ad 100644 --- a/P5/Source/Specs/epilogue.xml +++ b/P5/Source/Specs/epilogue.xml @@ -1,11 +1,5 @@ - + epilogue @@ -30,27 +24,17 @@ $Id$ - - - - - - + + + + - - - - - - + + - - - - - - + + @@ -135,4 +119,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/equipment.xml b/P5/Source/Specs/equipment.xml index 297e6af725..38f56d90d8 100644 --- a/P5/Source/Specs/equipment.xml +++ b/P5/Source/Specs/equipment.xml @@ -1,11 +1,5 @@ - + equipment @@ -29,9 +23,7 @@ an audio or video recording used as the source for a spoken text. - - - + @@ -85,4 +77,4 @@ an audio or video recording used as the source for a spoken text. - \ No newline at end of file + diff --git a/P5/Source/Specs/equiv.xml b/P5/Source/Specs/equiv.xml index dfebda007c..ac0b9dd81e 100644 --- a/P5/Source/Specs/equiv.xml +++ b/P5/Source/Specs/equiv.xml @@ -1,11 +1,5 @@ - + equivalent @@ -31,7 +25,9 @@ $Id$ - + + + a single word which follows the rules defining a @@ -45,7 +41,9 @@ $Id$ representación. specifica un concetto sottostante di cui il genitore è una rappesentazione - + + + uniform resource identifier @@ -64,7 +62,9 @@ $Id$ una representación mediante algún identificador externo indica il concetto sottostante di cui il genitore è una rappesentazione attraverso un identificatore esterno - + + + references an external script which contains a method to transform instances of this @@ -78,7 +78,9 @@ $Id$ para transformar ejemplos de este elemento a TEI canónico. indica uno script esterno contenente un metodo per trasformare le occorrenze dell'elemento in TEI canonico - + + + diff --git a/P5/Source/Specs/etym.xml b/P5/Source/Specs/etym.xml index b466558839..6070ccebf2 100644 --- a/P5/Source/Specs/etym.xml +++ b/P5/Source/Specs/etym.xml @@ -1,11 +1,5 @@ - + etymology @@ -31,21 +25,19 @@ $Id$ - - - - - - - - - - - - - - - + + + + + + + + + + + + +
publish ...
ME.publisshen, @@ -57,7 +49,9 @@ $Id$
weekend ...
- source: English weekend + source: + English + weekend @@ -132,4 +126,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/event.xml b/P5/Source/Specs/event.xml index be3b90ba68..3c879dfd93 100644 --- a/P5/Source/Specs/event.xml +++ b/P5/Source/Specs/event.xml @@ -1,11 +1,5 @@ - + event @@ -114,7 +108,9 @@ https://d-nb.info/gnd/133946118 - Prague + + Prague + Thirty Years’ War @@ -125,7 +121,9 @@ https://d-nb.info/gnd/4202901-6 Rocroi - 49.926111 4.522222 + + 49.926111 4.522222 + @@ -171,8 +169,7 @@ - + Nr. 1 Ministerrat, Wien, 1. April 1848 @@ -205,13 +202,43 @@ - Kolowrat - Ficquelmont - Taaffe - Pillersdorf - Sommaruga - KolowratBdE. 2. 4. - Franz KarlBdE. 2. 4. + + + Kolowrat + + + + + Ficquelmont + + + + + Taaffe + + + + + Pillersdorf + + + + + Sommaruga + + + + + Kolowrat + + BdE. 2. 4. + + + + Franz Karl + + BdE. 2. 4. + diff --git a/P5/Source/Specs/eventName.xml b/P5/Source/Specs/eventName.xml index ec724ecbc4..9320c97f91 100644 --- a/P5/Source/Specs/eventName.xml +++ b/P5/Source/Specs/eventName.xml @@ -1,11 +1,5 @@ - + name of an event @@ -39,7 +33,9 @@ $Id$ Gdańsk - 54.350556, 18.652778 + + 54.350556, 18.652778 + @@ -74,10 +70,8 @@ $Id$ TEI 2019: What is text, really? TEI and beyond TEI 2019 - The abstract leading to the eventName element is available at https://gams.uni-graz.at/o:tei2019.141. - Other related documents are available through https://gams.uni-graz.at/tei2019, as well as in the + The abstract leading to the eventName element is available at https://gams.uni-graz.at/o:tei2019.141. + Other related documents are available through https://gams.uni-graz.at/tei2019, as well as in the TEI 2019 Zenodo community. @@ -126,8 +120,7 @@ $Id$ - + diff --git a/P5/Source/Specs/ex.xml b/P5/Source/Specs/ex.xml index 7770328af1..4a58eebde2 100644 --- a/P5/Source/Specs/ex.xml +++ b/P5/Source/Specs/ex.xml @@ -1,11 +1,5 @@ - + editorial expansion @@ -47,4 +41,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/exemplum.xml b/P5/Source/Specs/exemplum.xml index e731bac941..2d326db8b6 100644 --- a/P5/Source/Specs/exemplum.xml +++ b/P5/Source/Specs/exemplum.xml @@ -1,11 +1,5 @@ - + exemplum @@ -28,16 +22,12 @@ $Id$ - - - + - - - + @@ -84,4 +74,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/expan.xml b/P5/Source/Specs/expan.xml index a577c7f5ba..6deb88ab32 100644 --- a/P5/Source/Specs/expan.xml +++ b/P5/Source/Specs/expan.xml @@ -1,11 +1,5 @@ - + expansion @@ -14,7 +8,7 @@ expansion expansión espansione - Abkürzungsauflösung + Abkürzungsauflösung contains the expansion of an abbreviation. 약어의 확장(비약어) 표기 包含一個縮寫詞的還原形式。 @@ -22,7 +16,7 @@ contient l'expansion d'une abréviation. contiene la expansión de una abreviatura. contiene l'esapnsione di un'abbreviazione. - enthält die aufgelöste Form einer Abkürzung. + enthält die aufgelöste Form einer Abkürzung. @@ -34,18 +28,12 @@ The address is Southmoor - - Road - Rd - + RoadRd Il habite - - Avenue - Av. - de la Paix + AvenueAv.de la Paix @@ -61,15 +49,14 @@ Imp Imperator - + -

The content of this element should be the expanded +

The content of this element should be the expanded abbreviation, usually (but not always) a complete word or phrase. The ex element provided by the transcr module may be used to mark up sequences of letters supplied within such an expansion.

-

If abbreviations are expanded silently, this practice should be documented in the editorialDecl, either with a normalization element or a p.

@@ -84,7 +71,7 @@ を使い、省略形の元の形を文字列として示すことができる。

-

Der Inhalt dieses Elements sollte die aufgelöste Abkürzung sein, üblicherweise ein vollständiges Wort oder eine Phrase. +

Der Inhalt dieses Elements sollte die aufgelöste Abkürzung sein, üblicherweise ein vollständiges Wort oder eine Phrase. Das ex-Element aus dem Modul transcr kann verwendet werden, um einzelne Buchstaben innerhalb der Auflösung auszuzeichnen.

Werden Abkürzungen stillschweigend aufgelöst, @@ -94,4 +81,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/explicit.xml b/P5/Source/Specs/explicit.xml index 0ab2b0c78f..7b010e6ea4 100644 --- a/P5/Source/Specs/explicit.xml +++ b/P5/Source/Specs/explicit.xml @@ -1,11 +1,5 @@ - + explicit @@ -60,4 +54,4 @@ proporti - \ No newline at end of file + diff --git a/P5/Source/Specs/extent.xml b/P5/Source/Specs/extent.xml index 5e6e23863b..cf2177ad94 100644 --- a/P5/Source/Specs/extent.xml +++ b/P5/Source/Specs/extent.xml @@ -1,11 +1,5 @@ - + extent diff --git a/P5/Source/Specs/f.xml b/P5/Source/Specs/f.xml index dfa68ba832..2c88e4d99c 100644 --- a/P5/Source/Specs/f.xml +++ b/P5/Source/Specs/f.xml @@ -1,11 +1,5 @@ - + feature @@ -32,7 +26,7 @@ $Id$ - + @@ -44,7 +38,9 @@ $Id$ donne un nom pour le trait proporciona un nombre para un rasgo. fornisce il nome del tratto. - + + + feature value @@ -61,7 +57,9 @@ $Id$ utilisé pour représenter la valeur d'un trait. indica cualquier elemento que puede ser usado para representar el valor de un rasgo. indica un qualsiasi elemento che può essere usato come valore di un tratto. - + + +

If this attribute is supplied as well as content, the value referenced is to be unified with that contained.

 @@ -117,4 +115,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/fDecl.xml b/P5/Source/Specs/fDecl.xml index 43fda19c43..f3c73d6f42 100644 --- a/P5/Source/Specs/fDecl.xml +++ b/P5/Source/Specs/fDecl.xml @@ -1,11 +1,5 @@ - + feature declaration @@ -29,13 +23,9 @@ range of allowed values, and optionally its default value. - - - + - - - + @@ -51,7 +41,9 @@ range of allowed values, and optionally its default value. l'attribut name des éléments f du texte. indica el nombre del rasgo que está siendo declarado; combina el atributo name de elementos f en el texto. indica il nome del tratto che si sta dichiarando; corrisponde all'attributo name dell'elemento f nel testo. - + + + indicates whether or not the value of this feature may @@ -63,7 +55,9 @@ range of allowed values, and optionally its default value. exister indica si el valor del rasgo debe estar presente o no. indica se il valore del tratto possa o meno essere presente - + + + true

If a feature is marked as optional, it is possible @@ -144,4 +138,4 @@ range of allowed values, and optionally its default value. - \ No newline at end of file + diff --git a/P5/Source/Specs/fDescr.xml b/P5/Source/Specs/fDescr.xml index 4f63618dc6..237ec2fda2 100644 --- a/P5/Source/Specs/fDescr.xml +++ b/P5/Source/Specs/fDescr.xml @@ -1,11 +1,5 @@ - + feature description (in FSD) @@ -63,4 +57,4 @@ inter-level elements.

- \ No newline at end of file + diff --git a/P5/Source/Specs/fLib.xml b/P5/Source/Specs/fLib.xml index 002bc93b9e..ff0a97d41c 100644 --- a/P5/Source/Specs/fLib.xml +++ b/P5/Source/Specs/fLib.xml @@ -1,11 +1,5 @@ - + feature library @@ -27,9 +21,7 @@ $Id$ - - - + @@ -86,4 +78,4 @@ name to categorize the library's contents.

- \ No newline at end of file + diff --git a/P5/Source/Specs/facsimile.xml b/P5/Source/Specs/facsimile.xml index 9553f47c11..1426244edb 100644 --- a/P5/Source/Specs/facsimile.xml +++ b/P5/Source/Specs/facsimile.xml @@ -1,13 +1,7 @@ - + - + contains a representation of some written source in the form of a set of images rather than as transcribed or encoded text. 전사 또는 부호화된 텍스트 형태보다는 이미지 집합의 형태로 기록 원본의 표상을 포함한다. diff --git a/P5/Source/Specs/factuality.xml b/P5/Source/Specs/factuality.xml index 4f423e3b39..872f5f46c6 100644 --- a/P5/Source/Specs/factuality.xml +++ b/P5/Source/Specs/factuality.xml @@ -1,11 +1,5 @@ - + factuality @@ -37,7 +31,9 @@ or a non-fictional world. détermine le caractère factuel ou non du texte. clasifica la objetividad de un texto classifica la fattualità del testo. - + + + the text is to be regarded as entirely imaginative @@ -155,4 +151,4 @@ that works characterized as fact are in any sense true.

- \ No newline at end of file + diff --git a/P5/Source/Specs/faith.xml b/P5/Source/Specs/faith.xml index 681a7b4d3a..c0ed6c27e7 100644 --- a/P5/Source/Specs/faith.xml +++ b/P5/Source/Specs/faith.xml @@ -1,10 +1,7 @@ - + + + + faith religion specifies the faith, religion, or belief set of a person. @@ -26,49 +23,47 @@ - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + - + - - - - - + + + + + @@ -95,4 +90,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/figDesc.xml b/P5/Source/Specs/figDesc.xml index 9b254f4eae..7ff85d85eb 100644 --- a/P5/Source/Specs/figDesc.xml +++ b/P5/Source/Specs/figDesc.xml @@ -1,11 +1,5 @@ - + description of figure @@ -86,4 +80,4 @@ purposes.

- \ No newline at end of file + diff --git a/P5/Source/Specs/figure.xml b/P5/Source/Specs/figure.xml index 611d941705..4e338e0520 100644 --- a/P5/Source/Specs/figure.xml +++ b/P5/Source/Specs/figure.xml @@ -1,11 +1,5 @@ - + figure @@ -32,16 +26,14 @@ $Id$ - - - - - - - - - - + + + + + + + + @@ -75,4 +67,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/fileDesc.xml b/P5/Source/Specs/fileDesc.xml index 3ebf7bfb01..f9d4925e5d 100644 --- a/P5/Source/Specs/fileDesc.xml +++ b/P5/Source/Specs/fileDesc.xml @@ -1,11 +1,5 @@ - + file description @@ -21,7 +15,7 @@ $Id$ 전자 파일에 관한 완전한 서지 정보의 기술을 포함한다. 包含對電子檔案的完整書目敘述。 電子ファイルに関する完全な書誌情報を示す。 - enthält die vollständige bibliografische Beschreibung einer elektronischen Datei. + enthält die vollständige bibliografische Beschreibung einer elektronischen Datei. contiene una descripción bibliográfica completa del archivo electrónico. contiene una descrizione bibliografica completa di un file elettronico. @@ -32,23 +26,13 @@ $Id$ - - - - - - + + - - - - - - + + - - - + @@ -112,7 +96,7 @@ $Id$ れいない書誌情報に関する詳細な事項を含む。また、当該電子ファイルの 元になった、元資料に関する完全な書誌情報も示す。

-

Die wesentliche Informationsquelle für die Erstellung eines Katalogeintrags oder eines bibliografischen +

Die wesentliche Informationsquelle für die Erstellung eines Katalogeintrags oder eines bibliografischen Zitats einer elektronischen Datei. Das Element liefert einen Titel und Angaben zu Verantwortlichkeiten zusammen mit Details zu Publikation und Distribution der Datei, sowie eine mögliche Zugehörigkeit zu einer Reihe. Außerdem kann es detaillierte bibliografische Anmerkungen für Sachverhalte, die an keiner anderen Stelle im TEI-Header @@ -123,4 +107,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/filiation.xml b/P5/Source/Specs/filiation.xml index a0bfe39e75..e7fb87eff9 100644 --- a/P5/Source/Specs/filiation.xml +++ b/P5/Source/Specs/filiation.xml @@ -1,11 +1,5 @@ - + filiation @@ -113,4 +107,4 @@ link to some other manuscript description which has the identifier DN17 - \ No newline at end of file + diff --git a/P5/Source/Specs/finalRubric.xml b/P5/Source/Specs/finalRubric.xml index 92e7129406..cd03fbe433 100644 --- a/P5/Source/Specs/finalRubric.xml +++ b/P5/Source/Specs/finalRubric.xml @@ -1,11 +1,5 @@ - + final rubric diff --git a/P5/Source/Specs/floatingText.xml b/P5/Source/Specs/floatingText.xml index 762aacc90d..1b4388ed8e 100644 --- a/P5/Source/Specs/floatingText.xml +++ b/P5/Source/Specs/floatingText.xml @@ -1,11 +1,5 @@ - + floating text @@ -32,27 +26,19 @@ $Id$ - - - + - - - + - - - + - - - + @@ -143,4 +129,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/floruit.xml b/P5/Source/Specs/floruit.xml index a9da6728e2..fb360a3f1d 100644 --- a/P5/Source/Specs/floruit.xml +++ b/P5/Source/Specs/floruit.xml @@ -1,10 +1,7 @@ - + + + + floruit période d'activité contains information about a person's period of activity. @@ -26,35 +23,35 @@ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -73,4 +70,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/foliation.xml b/P5/Source/Specs/foliation.xml index 1bc40b6a7e..ed31de2ed6 100644 --- a/P5/Source/Specs/foliation.xml +++ b/P5/Source/Specs/foliation.xml @@ -1,11 +1,5 @@ - + foliation @@ -46,4 +40,4 @@ of the outer margin. - \ No newline at end of file + diff --git a/P5/Source/Specs/foreign.xml b/P5/Source/Specs/foreign.xml index b8c03c75c9..cf312d7c82 100644 --- a/P5/Source/Specs/foreign.xml +++ b/P5/Source/Specs/foreign.xml @@ -1,11 +1,5 @@ - + foreign @@ -109,4 +103,4 @@ Ce ne seroyt que bon que nous rendissiez noz cloches... - \ No newline at end of file + diff --git a/P5/Source/Specs/forename.xml b/P5/Source/Specs/forename.xml index 2f3890d79e..ae226048bb 100644 --- a/P5/Source/Specs/forename.xml +++ b/P5/Source/Specs/forename.xml @@ -1,11 +1,5 @@ - + forename @@ -56,4 +50,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/forest.xml b/P5/Source/Specs/forest.xml index 0e606446f7..6bf0f3910a 100644 --- a/P5/Source/Specs/forest.xml +++ b/P5/Source/Specs/forest.xml @@ -1,11 +1,5 @@ - + forest @@ -93,4 +87,4 @@ trees (triangles).

- \ No newline at end of file + diff --git a/P5/Source/Specs/form.xml b/P5/Source/Specs/form.xml index 53adf9b547..a6623a90e0 100644 --- a/P5/Source/Specs/form.xml +++ b/P5/Source/Specs/form.xml @@ -1,11 +1,5 @@ - + form information group @@ -33,16 +27,14 @@ $Id$ - - - - - - - - - - + + + + + + + + @@ -53,7 +45,9 @@ $Id$ qualifie la forme comme simple, composée, etc. clasifica la forma como simple, compuesta, etc. classifica la forma in simplice, composta, ecc. - + + + single free lexical item @@ -156,4 +150,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/formula.xml b/P5/Source/Specs/formula.xml index 480b5b60cd..9e32f94ee3 100644 --- a/P5/Source/Specs/formula.xml +++ b/P5/Source/Specs/formula.xml @@ -1,11 +1,5 @@ - + formula @@ -26,14 +20,12 @@ $Id$ - - - - - + + + + + - - $E=mc^2$ @@ -67,4 +59,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/front.xml b/P5/Source/Specs/front.xml index 99dd015b78..39fc867814 100644 --- a/P5/Source/Specs/front.xml +++ b/P5/Source/Specs/front.xml @@ -1,11 +1,5 @@ - + front matter @@ -198,7 +192,7 @@ $Id$ - +
@@ -260,4 +254,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/fs.xml b/P5/Source/Specs/fs.xml index c400ef40ca..2febc3bf54 100644 --- a/P5/Source/Specs/fs.xml +++ b/P5/Source/Specs/fs.xml @@ -1,11 +1,5 @@ - + feature structure @@ -32,9 +26,7 @@ structural unit. - - - + @@ -45,7 +37,9 @@ structural unit. spécifie le type de la structure de traits. especifica el tipo de estructura de rasgo. specifica il tipo di struttura dei tratti - + + + features @@ -62,7 +56,9 @@ structural unit. indica las especificaciones de valor de rasgo que constituyen esta estructura de rasgo. indica le specifiche del valore dei tratti che formano questa struttura. - + + +

May be used either instead of having features as content, or in addition. In the latter case, the features referenced and contained @@ -107,4 +103,4 @@ rasgo. - \ No newline at end of file + diff --git a/P5/Source/Specs/fsConstraints.xml b/P5/Source/Specs/fsConstraints.xml index 7d59163590..6c0265d840 100644 --- a/P5/Source/Specs/fsConstraints.xml +++ b/P5/Source/Specs/fsConstraints.xml @@ -1,11 +1,5 @@ - + feature-structure constraints @@ -27,12 +21,10 @@ structures. - - - - - - + + + + @@ -66,4 +58,4 @@ structures. - \ No newline at end of file + diff --git a/P5/Source/Specs/fsDecl.xml b/P5/Source/Specs/fsDecl.xml index 3122c8d764..8b9162325a 100644 --- a/P5/Source/Specs/fsDecl.xml +++ b/P5/Source/Specs/fsDecl.xml @@ -1,11 +1,5 @@ - + feature structure declaration @@ -28,15 +22,9 @@ $Id$ - - - - - - - - - + + + @@ -49,7 +37,9 @@ $Id$ déclaré. proporciona un nombre para el tipo de estructura de rasgo que está siendo declarada. fornisce il nome per il tipo di struttura di tratti che si sta dichiarando. - + + + gives the name of one or more typed feature structures @@ -87,7 +77,9 @@ $Id$ se questo tipo include una specifica di tratti con lo stesso nome specificato da questo attributo, o se più di una specifica dello stesso nome è ereditata, allora l'insieme dei possibili valori è definito attraverso l'unificazione. In modo analogo, l'insieme dei vincoli applicabile deriva dalla combinazione di quelli specificati in modo esplicito all'interno dell'elemento con quelli sottintesi dall'attributo baseTypes Se nessun baseTypes è specificato, nessuna specificazione o vincolo di tratti è ereditata. - + + +

Inheritance is defined here as a monotonous relation.

The process of combining constraints @@ -141,4 +133,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/fsDescr.xml b/P5/Source/Specs/fsDescr.xml index 0b5ae895a7..8e038f6ac6 100644 --- a/P5/Source/Specs/fsDescr.xml +++ b/P5/Source/Specs/fsDescr.xml @@ -1,11 +1,5 @@ - + feature system description (in FSD) @@ -74,4 +68,4 @@ inter-level elements.

- \ No newline at end of file + diff --git a/P5/Source/Specs/fsdDecl.xml b/P5/Source/Specs/fsdDecl.xml index 6d4f0faf3f..603165f014 100644 --- a/P5/Source/Specs/fsdDecl.xml +++ b/P5/Source/Specs/fsdDecl.xml @@ -1,11 +1,5 @@ - + feature system declaration @@ -76,4 +70,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/fsdLink.xml b/P5/Source/Specs/fsdLink.xml index dd41ca6b1b..81a3b5d9e0 100644 --- a/P5/Source/Specs/fsdLink.xml +++ b/P5/Source/Specs/fsdLink.xml @@ -1,11 +1,5 @@ - + feature structure declaration link @@ -26,7 +20,9 @@ sa déclaration de structure de traits. - + + + identifies the type of feature structure to be documented; @@ -39,7 +35,9 @@ feature structure. identifica il tipo di dichiarazione del sistema di tratti attraverso il FSD, sarà il valore dell'attributo type di almeno una struttura di tratti. identifica el tipo de estructura de rasgos documentada por el FSD; éste será el valor del atributo type al menos en una estructura de rasgos. identifie le type de structure de traits à documenter ; ce sera la valeur de l’attribut type d’au moins une structure de traits. - + + + supplies a pointer to a feature structure declaration @@ -52,7 +50,9 @@ feature structure. déclaration de structure de traits (fsDecl) dans le document courant ou ailleurs. fornisce un puntatore che indica l'elemento relativo alla dichiarazione di una struttura di tratti (fsDecl) all'interno del documento corrente o altrove - + + + @@ -68,4 +68,4 @@ ailleurs. - \ No newline at end of file + diff --git a/P5/Source/Specs/funder.xml b/P5/Source/Specs/funder.xml index bbeb4e49a1..056ebd64fa 100644 --- a/P5/Source/Specs/funder.xml +++ b/P5/Source/Specs/funder.xml @@ -1,10 +1,7 @@ - + + + + funding body financeur 재정 지원 조직체 @@ -19,7 +16,7 @@ $Id$ 프로젝트 또는 텍스트의 재정 지원 책임을 지는 개인, 기관, 조직의 이름을 명시한다. 標明負責資助一項計畫或文件製作的個人、機構或組織名稱。 テキストやプロジェクトの資金提供に責任を持つ個人、団体、組織の名前を 示す。 - gibt den Namen einer Einzelperson, Institution oder Organisation an, die für die + gibt den Namen einer Einzelperson, Institution oder Organisation an, die für die Finanzierung eines Projekts oder Textes verantwortlich ist. proporciona el nombre del individuo, la institución o la organización responsable de la financiación de un proyecto o de un texto. @@ -36,35 +33,35 @@ $Id$ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -105,11 +102,11 @@ $Id$

当該要素の資金提供者とは、プロジェクトへの資金を支援するものである。 知的支援や責任を持つ人物示す要素sponsorsは異なる。

-

+

Die Geldgeber finanzieren das Projekt. Sie sind zu unterscheiden von den Förderern (siehe sponsor-Element), die das Projekt intellektuell und mit fachlicher Autorität unterstützen.

- \ No newline at end of file + diff --git a/P5/Source/Specs/fvLib.xml b/P5/Source/Specs/fvLib.xml index 71667c1ca2..3a72fea8b4 100644 --- a/P5/Source/Specs/fvLib.xml +++ b/P5/Source/Specs/fvLib.xml @@ -1,11 +1,5 @@ - + feature-value library @@ -29,11 +23,7 @@ $Id$ - - - - - + @@ -83,4 +73,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/fw.xml b/P5/Source/Specs/fw.xml index 5b617dce51..99b545e61a 100644 --- a/P5/Source/Specs/fw.xml +++ b/P5/Source/Specs/fw.xml @@ -1,11 +1,5 @@ - + forme work @@ -41,7 +35,9 @@ $Id$ caractérise l'information encodée conformément à une typologie appropriée. clasifica las convenciones usadas según una tipología funcional. classifica le convenzioni usate secondo una tipologia funzionale - + + + a running title at the top of the page @@ -162,4 +158,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/g.xml b/P5/Source/Specs/g.xml index c3f89ff89f..31304a7ee4 100644 --- a/P5/Source/Specs/g.xml +++ b/P5/Source/Specs/g.xml @@ -1,11 +1,5 @@ - + character or glyph @@ -39,7 +33,9 @@ $Id$ visé indica la descripción del carácter o pictograma dado. punta a una descrizione del carattere o glifo. - + + + @@ -92,4 +88,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/gap.xml b/P5/Source/Specs/gap.xml index 0596868f14..b2b20f83cd 100644 --- a/P5/Source/Specs/gap.xml +++ b/P5/Source/Specs/gap.xml @@ -1,11 +1,5 @@ - + @@ -41,10 +35,10 @@ - - - - + + + + @@ -63,55 +57,55 @@ indica il motivo dell'omisione gibt den Grund für die Auslassung an - + - - cancelled - abgebrochen - cancellato - cancelado - biffé - - - deleted - getilgt - - - editorial - for features omitted from + + cancelled + abgebrochen + cancellato + cancelado + biffé + + + deleted + getilgt + + + editorial + for features omitted from transcription due to editorial policy - für Bestandteile, + für Bestandteile, die aus editorischen Gründen nicht übertragen wurden - - - illegible - unleserlich - illegibile - ilegible - illisible - - - inaudible - nicht hörbar - incomprensibile - inaudible - inaudible - - - irrelevant - irrelevant - irrilevante - irrelevante - non pertinent - - - sampling - Auswahl - campionatura - ejemplificación - échantillonnage - + + + illegible + unleserlich + illegibile + ilegible + illisible + + + inaudible + nicht hörbar + incomprensibile + inaudible + inaudible + + + irrelevant + irrelevant + irrilevante + irrelevante + non pertinent + + + sampling + Auswahl + campionatura + ejemplificación + échantillonnage + @@ -130,7 +124,9 @@ danneggiamento, indica la causa del danno qualora possa essere identificata. bestimmt im Falle von Text, der wegen Beschädigung weggelassen wird, die Ursache für den Schaden, sofern er ermittelt werden kann. - + + + rubbing @@ -248,7 +244,7 @@

Die Elemente gap, unclear und del aus dem Core-Modul sind eng verwandt mit den Elementen damage und supplied, die mit dem transcr zur Verfügung - gestellt werden. Die Unterschiede im Gebrauch dieser Elemente werden in näher beschrieben.

+ gestellt werden. Die Unterschiede im Gebrauch dieser Elemente werden in näher beschrieben.

Das gap-Element weist nur darauf hin, dass die Bearbeiter*innen sich entschieden haben, eine Textpassage auszulassen oder sie nicht transkribieren konnten. Ergänzende Informationen, wie die Interpretation, dass der Text absichtlich unlesbar gemacht wurde, @@ -257,4 +253,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/gb.xml b/P5/Source/Specs/gb.xml index 28b2b2e15e..f1262b167d 100644 --- a/P5/Source/Specs/gb.xml +++ b/P5/Source/Specs/gb.xml @@ -1,11 +1,5 @@ - + gathering beginning @@ -18,7 +12,9 @@ - + + + @@ -39,4 +35,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/gen.xml b/P5/Source/Specs/gen.xml index 51fd950c97..c72497f5d7 100644 --- a/P5/Source/Specs/gen.xml +++ b/P5/Source/Specs/gen.xml @@ -1,11 +1,5 @@ - + @@ -94,4 +88,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/genName.xml b/P5/Source/Specs/genName.xml index a36482ec9b..7c0eb89330 100644 --- a/P5/Source/Specs/genName.xml +++ b/P5/Source/Specs/genName.xml @@ -1,11 +1,5 @@ - + generational name component @@ -85,4 +79,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/gender.xml b/P5/Source/Specs/gender.xml index b7776cdc2f..ab94776c0f 100644 --- a/P5/Source/Specs/gender.xml +++ b/P5/Source/Specs/gender.xml @@ -1,10 +1,7 @@ - + + + + gender specifies the gender identity of a person, persona, or character. especifica la identidad de género de una persona. @@ -21,42 +18,42 @@ $Id$ - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + supplies a coded value for gender identity - + + +

Values for this attribute may be locally defined by a project, or they may refer to an external standard.

 @@ -89,4 +86,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/geo.xml b/P5/Source/Specs/geo.xml index 020770a883..51c15da10b 100644 --- a/P5/Source/Specs/geo.xml +++ b/P5/Source/Specs/geo.xml @@ -1,11 +1,5 @@ - + geographical coordinates @@ -72,4 +66,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/geoDecl.xml b/P5/Source/Specs/geoDecl.xml index 44c2d7271d..e4e0a53be9 100644 --- a/P5/Source/Specs/geoDecl.xml +++ b/P5/Source/Specs/geoDecl.xml @@ -1,11 +1,5 @@ - + geographic coordinates declaration @@ -44,7 +38,9 @@ $Id$ employées. indica un nome in codice comunemente impiegato per il dato utilizzato - + + + WGS84 diff --git a/P5/Source/Specs/geogFeat.xml b/P5/Source/Specs/geogFeat.xml index a5017b24c6..44c125d8a0 100644 --- a/P5/Source/Specs/geogFeat.xml +++ b/P5/Source/Specs/geogFeat.xml @@ -1,10 +1,7 @@ - + + + + geographical feature name 지리적 특성명 nom de caractéristique géographique @@ -28,41 +25,41 @@ - + - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -84,4 +81,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/geogName.xml b/P5/Source/Specs/geogName.xml index ad00164f35..51f7324db0 100644 --- a/P5/Source/Specs/geogName.xml +++ b/P5/Source/Specs/geogName.xml @@ -1,10 +1,7 @@ - + + + + geographical name 지리명 地理名稱 @@ -31,35 +28,35 @@ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -86,4 +83,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/gi.xml b/P5/Source/Specs/gi.xml index 6c5e1c6cc6..d1b53bf2eb 100644 --- a/P5/Source/Specs/gi.xml +++ b/P5/Source/Specs/gi.xml @@ -1,11 +1,5 @@ - + element name @@ -44,7 +38,9 @@ $Id$ fornisce il nome dello schema in cui è definito tale nome enthält den Namen des Schemas, in dem der Name definiert ist. - + + + TEI @@ -136,4 +132,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/gloss.xml b/P5/Source/Specs/gloss.xml index 3f3ed9ff04..1fcbbc52b7 100644 --- a/P5/Source/Specs/gloss.xml +++ b/P5/Source/Specs/gloss.xml @@ -1,11 +1,5 @@ - + gloss diff --git a/P5/Source/Specs/glyph.xml b/P5/Source/Specs/glyph.xml index 42d557e141..833a622766 100644 --- a/P5/Source/Specs/glyph.xml +++ b/P5/Source/Specs/glyph.xml @@ -1,11 +1,5 @@ - + character glyph @@ -61,4 +55,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/gram.xml b/P5/Source/Specs/gram.xml index 509c218607..189fd69cef 100644 --- a/P5/Source/Specs/gram.xml +++ b/P5/Source/Specs/gram.xml @@ -1,11 +1,5 @@ - + grammatical information @@ -38,23 +32,18 @@ $Id$ classifies grammatical information provided by gram according to some convenient and shared typology, ideally one defined in an external - reference taxonomy, such as the CLARIN Concept + reference taxonomy, such as the CLARIN Concept Registry. 다양한 유형에 따라 문법 정보를 분류한다. - 전문용어 정보의 경우 가급적 ISO WD 12 620에서 명시한 데이터 요소 유형의 사전을 따른다. - 用合適的分類方法將不同的文法資訊加以分類－若是專門術語，可參照 ISO 12620 所指定資料元素類別。 - 当該文法情報の分類を示す。用語を示す場合、ISO 12620に従うこ とが望ましい。 + 用合適的分類方法將不同的文法資訊加以分類－若是專門術語，可參照 ISO 12620 所指定資料元素類別。 + 当該文法情報の分類を示す。用語を示す場合、ISO 12620に従うこ とが望ましい。 classe l'information grammaticale fournie selon une typologie particulière : dans le cas d'informations terminologiques, de préférence au - moyen du dictionnaire des types d'éléments de données spécifiés dans la norme ISO 12620. + moyen du dictionnaire des types d'éléments de données spécifiés dans la norme ISO 12620. clasifica la información gramatical dada de acuerdo a una tipología funcional — en el caso de información terminológica, preferiblemente - el diccionario de tipos de elemento de datos se especifica en ISO 12620. + el diccionario de tipos de elemento de datos se especifica en ISO 12620. classifica le informazioni grammaticali secondo un'appropriata tipologia - nel caso di informazioni terminologiche, preferibilmente il dizionario di degli elementi specificati in ISO @@ -171,8 +160,7 @@ $Id$

Une liste de valeurs beaucoup plus complète pour l'attribut type peut être produite à partir du dictionnaire des types d'éléments de données en préparation sous la - référence ISO TC 37/SC 3/WD 12 620, Computational Aids in Terminology. Voir l'ISO 12620 pour plus de détails.

+ référence ISO TC 37/SC 3/WD 12 620, Computational Aids in Terminology. Voir l'ISO 12620 pour plus de détails.

属性typeに付与される値の全リストは、 ISO TC 37/SC 3が策定したWD 12620 Computational Aids in @@ -220,9 +208,9 @@ $Id$ - - - - + diff --git a/P5/Source/Specs/gramGrp.xml b/P5/Source/Specs/gramGrp.xml index 6cd4b2cfce..0428271746 100644 --- a/P5/Source/Specs/gramGrp.xml +++ b/P5/Source/Specs/gramGrp.xml @@ -1,11 +1,5 @@ - + grammatical information group @@ -38,16 +32,14 @@ $Id$ - - - - - - - - - - + + + + + + + + @@ -91,4 +83,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/graph.xml b/P5/Source/Specs/graph.xml index a7be2a2f0c..2027a729bc 100644 --- a/P5/Source/Specs/graph.xml +++ b/P5/Source/Specs/graph.xml @@ -1,11 +1,5 @@ - + graph @@ -28,7 +22,7 @@ connect the nodes. - + @@ -64,7 +58,9 @@ connect the nodes. décrit le type de graphe. describe el tipo de gráfico descrive il tipo di grafo - + + + undirected graph @@ -143,7 +139,9 @@ instead of the adj attribute.

établit l'ordre du graphe, c'est-à-dire le nombre de ses nœuds. define el orden del gráfico, es decir, el número de sus nodos. definisce l'ordine del grafo, cioè il numero dei suoi nodi - + + + states the size of the graph, i.e., the number of its arcs. @@ -153,7 +151,9 @@ instead of the adj attribute.

établit la taille du graphe, c'est-à-dire le nombre de ses arcs. define la dimensión del gráfico, es decir, el número de sus arcos. definisce la dimensione del grafo, cioè il numero dei suoi archi - + + + @@ -249,4 +249,4 @@ or more nodes and zero or more arcs in any order.

- \ No newline at end of file + diff --git a/P5/Source/Specs/graphic.xml b/P5/Source/Specs/graphic.xml index 60478ce72a..717d35fe2a 100644 --- a/P5/Source/Specs/graphic.xml +++ b/P5/Source/Specs/graphic.xml @@ -1,11 +1,5 @@ - + graphic @@ -33,7 +27,7 @@ - + @@ -109,7 +103,8 @@

The mimeType attribute should be used to supply the MIME media type of the image - specified by the url attribute.

Within the body of a text, a graphic element indicates the + specified by the url attribute.

+

Within the body of a text, a graphic element indicates the presence of a graphic component in the source itself. Within the context of a facsimile or sourceDoc element, however, a graphic element provides an additional digital representation of some part of the source being encoded.

@@ -132,6 +127,5 @@ - - \ No newline at end of file + diff --git a/P5/Source/Specs/group.xml b/P5/Source/Specs/group.xml index 39460b164d..7d388fdbe1 100644 --- a/P5/Source/Specs/group.xml +++ b/P5/Source/Specs/group.xml @@ -1,11 +1,5 @@ - + group @@ -38,28 +32,22 @@ $Id$ - - - - - - + + + + - - - - - - - + + + + + - - - + @@ -128,4 +116,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/handDesc.xml b/P5/Source/Specs/handDesc.xml index 43ba1a31d1..27fae0bc4f 100644 --- a/P5/Source/Specs/handDesc.xml +++ b/P5/Source/Specs/handDesc.xml @@ -1,11 +1,5 @@ - + description of hands @@ -28,16 +22,10 @@ $Id$ - - - + - - - - - - + + @@ -53,7 +41,9 @@ $Id$ pu être identifiées dans le manuscrit especifica el número de manos distintas identificadas al interno de un manuscrito. specifica il numero delle diverse mani identificate all'interno del manoscritto - + + + @@ -117,4 +107,4 @@ on f. 24, but the evidence for this is insubstantial.

- \ No newline at end of file + diff --git a/P5/Source/Specs/handNote.xml b/P5/Source/Specs/handNote.xml index 9dcac2b1ef..747592d788 100644 --- a/P5/Source/Specs/handNote.xml +++ b/P5/Source/Specs/handNote.xml @@ -1,11 +1,5 @@ - + note on hand @@ -58,4 +52,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/handNotes.xml b/P5/Source/Specs/handNotes.xml index 3e1472bdf2..d601695c17 100644 --- a/P5/Source/Specs/handNotes.xml +++ b/P5/Source/Specs/handNotes.xml @@ -1,11 +1,5 @@ - + contains one or more handNote elements documenting the @@ -22,9 +16,7 @@ different hands identified within the source texts. - - - + @@ -37,4 +29,4 @@ different hands identified within the source texts. - \ No newline at end of file + diff --git a/P5/Source/Specs/handShift.xml b/P5/Source/Specs/handShift.xml index 3823607363..bfa6fda736 100644 --- a/P5/Source/Specs/handShift.xml +++ b/P5/Source/Specs/handShift.xml @@ -1,11 +1,5 @@ - + handwriting shift @@ -24,7 +18,9 @@ hand, or the beginning of a scribal stint. - + + + indicates a @@ -36,7 +32,9 @@ hand, or the beginning of a scribal stint. donne l'identifiant de la nouvelle main. identifica una nueva mano. indica la nuova mano - + + +

This attribute serves the same function as the hand attribute provided for those elements which are members of the @@ -77,4 +75,4 @@ autre), soit pour indiquer un changement dans la main, comme un changement d'éc - \ No newline at end of file + diff --git a/P5/Source/Specs/head.xml b/P5/Source/Specs/head.xml index c998baf736..16e313eecf 100644 --- a/P5/Source/Specs/head.xml +++ b/P5/Source/Specs/head.xml @@ -1,11 +1,5 @@ - + heading @@ -37,17 +31,15 @@ - - - - - - - - - - - + + + + + + + + +

The most common use for the head element is to mark the headings of sections. In @@ -98,9 +90,7 @@

Secunda conclusio -

- Potencia: habitus: et actus: recipiunt speciem ab obiectis. - Probatur sic. Omne importans necessariam habitudinem ad proprium +

Potencia: habitus: et actus: recipiunt speciem ab obiectis.Probatur sic. Omne importans necessariam habitudinem ad proprium [...]

@@ -197,4 +187,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/headItem.xml b/P5/Source/Specs/headItem.xml index e71a4e3faa..5d2ed6caec 100644 --- a/P5/Source/Specs/headItem.xml +++ b/P5/Source/Specs/headItem.xml @@ -1,11 +1,5 @@ - + heading for list items @@ -60,4 +54,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/headLabel.xml b/P5/Source/Specs/headLabel.xml index 8f64d38f9c..b2dc500673 100644 --- a/P5/Source/Specs/headLabel.xml +++ b/P5/Source/Specs/headLabel.xml @@ -1,11 +1,5 @@ - + heading for list labels @@ -51,4 +45,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/height.xml b/P5/Source/Specs/height.xml index 9157f1b300..ea445ec936 100644 --- a/P5/Source/Specs/height.xml +++ b/P5/Source/Specs/height.xml @@ -1,11 +1,5 @@ - + height @@ -40,4 +34,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/heraldry.xml b/P5/Source/Specs/heraldry.xml index 0a0bc60726..d8f5eb7edc 100644 --- a/P5/Source/Specs/heraldry.xml +++ b/P5/Source/Specs/heraldry.xml @@ -1,11 +1,5 @@ - + heraldry @@ -49,4 +43,4 @@ crest, and the legend Cole Deum.

- \ No newline at end of file + diff --git a/P5/Source/Specs/hi.xml b/P5/Source/Specs/hi.xml index fb7e610b77..0be3035354 100644 --- a/P5/Source/Specs/hi.xml +++ b/P5/Source/Specs/hi.xml @@ -1,11 +1,5 @@ - + highlighted @@ -25,8 +19,7 @@ graphiquement distincte du texte environnant, sans en donner la raison. marca una palabra o frase gráficamente diferente del resto del texto que la circunda, por causas sobre las que no se hace ninguna declaracion. codifica una parola o sintagma in quanto graficamente distinta dal testo circostante, senza che vengano specificate le ragioni dell'evidenziazione. - markiert ein Wort oder eine Textpassage, das/die sich grafisch vom umgebenden Text abhebt, ohne dass ein inhaltlicher Grund dafür angegeben wird. - + markiert ein Wort oder eine Textpassage, das/die sich grafisch vom umgebenden Text abhebt, ohne dass ein inhaltlicher Grund dafür angegeben wird. @@ -54,4 +47,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/history.xml b/P5/Source/Specs/history.xml index 201e15ab9a..1e71417e69 100644 --- a/P5/Source/Specs/history.xml +++ b/P5/Source/Specs/history.xml @@ -1,11 +1,5 @@ - + history @@ -25,22 +19,12 @@ describing the full history of a manuscript, manuscript part, or other object. - - - + - - - - - - - - - - - - + + + + @@ -104,4 +88,4 @@ Thomas Gale and his son Roger.

- \ No newline at end of file + diff --git a/P5/Source/Specs/hom.xml b/P5/Source/Specs/hom.xml index cf36c621d0..8d220d0782 100644 --- a/P5/Source/Specs/hom.xml +++ b/P5/Source/Specs/hom.xml @@ -1,11 +1,5 @@ - + homograph @@ -28,14 +22,12 @@ $Id$ - - - - - - - - + + + + + + @@ -110,4 +102,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/hyph.xml b/P5/Source/Specs/hyph.xml index 1bb7a1271d..a3651a4ac6 100644 --- a/P5/Source/Specs/hyph.xml +++ b/P5/Source/Specs/hyph.xml @@ -1,11 +1,5 @@ - + hyphenation @@ -71,4 +65,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/hyphenation.xml b/P5/Source/Specs/hyphenation.xml index d8f60b32ed..86db795f3a 100644 --- a/P5/Source/Specs/hyphenation.xml +++ b/P5/Source/Specs/hyphenation.xml @@ -1,11 +1,5 @@ - + hyphenation @@ -29,9 +23,7 @@ $Id$ - - - + @@ -52,7 +44,9 @@ $Id$ conservado en un texto. indica se il trattino a fine riga sia stato mantenuto o meno. - + + + some @@ -138,4 +132,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/iNode.xml b/P5/Source/Specs/iNode.xml index 5ce7826716..8b62d24dba 100644 --- a/P5/Source/Specs/iNode.xml +++ b/P5/Source/Specs/iNode.xml @@ -1,11 +1,5 @@ - + intermediate (or internal) node @@ -25,9 +19,7 @@ $Id$ - - - + @@ -39,7 +31,9 @@ structure or other analytic element. fournit l'identifiant de l'objet représenté par le nœud intermédiaire ; cet objet peut être une paire nom-valeur ou tout autre élément analytique. proporciona el valor de un nodo intermedio, que puede ser una estructura de rasgos u otro elemento de análisis. assegna a un nodo intermedio un valore, che può essere una struttura di tratti o altro elemento di analisi - + + + provides a list of identifiers of the elements which are the children of @@ -51,7 +45,9 @@ the intermediate node. éléments qui sont les enfants du nœud intermédiaire. proporciona una lista de identificadores de elementos que son hijos de un nodo intermedio. fornisce una lista di identificatori degli elementi figli del nodo intermedio - + + + provides the identifier of the element which is the parent of this node. @@ -62,7 +58,9 @@ the intermediate node. de ce nœud. proporciona el identificador del elemento padre de un nodo dado. assegna un identificatore all'elemento genitore del nodo - + + + ordered @@ -77,7 +75,9 @@ the intermediate node. indique si le nœud interne est ou non ordonné. indica si el nodo interno está ordenado o no. indica se il nodo interno è ordinato o meno - + + +

The value true indicates that the children of the intermediate node are ordered, whereas false @@ -111,7 +111,9 @@ an element which this node follows. fournit l'identifiant de l'élément que ce nœud suit. proporciona un identificador al elemento que precede al nodo. assegna un identificatore all'elemento che precede il nodo - + + +

If the tree is unordered or partially ordered, this attribute has the property of fixing the relative order of the intermediate node @@ -139,7 +141,9 @@ children. donne le degré sortant d'un nœud intermédiaire, c'est-à-dire le nombre de ses enfants. indica el grado de salida del nodo intermedio, es decir, el número de sus hijos. indica il grado in uscita di un nodo intermedio, cioè il numero dei suoi figli - + + +

The in degree of an intermediate node is always 1.

 @@ -170,4 +174,4 @@ children. - \ No newline at end of file + diff --git a/P5/Source/Specs/iType.xml b/P5/Source/Specs/iType.xml index 56a7f59f04..d0cc58fb33 100644 --- a/P5/Source/Specs/iType.xml +++ b/P5/Source/Specs/iType.xml @@ -1,11 +1,5 @@ - + inflectional class @@ -56,7 +50,9 @@ $Id$ specificare la tipologia di flessione, qualora sia necessario distinguere tra le indicazioni abbreviate solite (ad esempio inv)e altri tipi di indicatori, quali codici speciali per fare riferimento al tipo di coniugazione, ecc. - + + + abbreviated indicator @@ -125,4 +121,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/ident.xml b/P5/Source/Specs/ident.xml index c8142e1eb4..c79a4757be 100644 --- a/P5/Source/Specs/ident.xml +++ b/P5/Source/Specs/ident.xml @@ -1,11 +1,5 @@ - + identifier @@ -58,4 +52,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/idno.xml b/P5/Source/Specs/idno.xml index 6e78cc3fba..223d5101e7 100644 --- a/P5/Source/Specs/idno.xml +++ b/P5/Source/Specs/idno.xml @@ -1,10 +1,7 @@ - + + + + identifier identifiant 식별 숫자 @@ -41,49 +38,45 @@ $Id$ - - - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + categorizes the identifier, for example as an ISBN, Social Security number, etc. classe un numéro dans une catégorie, par exemple @@ -181,8 +174,7 @@ $Id$ ISBN, ISSN, DOI, and URI.

-

- idno sollte für Identifikatoren genutzt werden, die ein Objekt oder Konzept in einem +

idno sollte für Identifikatoren genutzt werden, die ein Objekt oder Konzept in einem formalen Katalogsystem wie z. B. einer Datenbank oder einem RDF store oder in einem verteilten System wie dem World Wide Web eindeutig identifizieren. Als Werte für type von idno bieten sich z. B. die ISBN, die ISSN, ein DOI @@ -194,4 +186,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/if.xml b/P5/Source/Specs/if.xml index c5bf214b26..c9368731f3 100644 --- a/P5/Source/Specs/if.xml +++ b/P5/Source/Specs/if.xml @@ -1,11 +1,5 @@ - + defines a conditional default value for a feature; the condition @@ -32,9 +26,7 @@ default value is sought. - - - + @@ -74,4 +66,4 @@ the two are separated by a then element.

- \ No newline at end of file + diff --git a/P5/Source/Specs/iff.xml b/P5/Source/Specs/iff.xml index bd4df70435..eb167a844d 100644 --- a/P5/Source/Specs/iff.xml +++ b/P5/Source/Specs/iff.xml @@ -1,11 +1,5 @@ - + if and only if @@ -26,7 +20,9 @@ element. - + + + @@ -60,4 +56,4 @@ human readability of the feature-system declaration.

- \ No newline at end of file + diff --git a/P5/Source/Specs/imprimatur.xml b/P5/Source/Specs/imprimatur.xml index a4ba223e22..795122bdd7 100644 --- a/P5/Source/Specs/imprimatur.xml +++ b/P5/Source/Specs/imprimatur.xml @@ -1,11 +1,5 @@ - + imprimatur @@ -48,4 +42,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/imprint.xml b/P5/Source/Specs/imprint.xml index aa538c8c53..10a6af4c10 100644 --- a/P5/Source/Specs/imprint.xml +++ b/P5/Source/Specs/imprint.xml @@ -1,11 +1,5 @@ - + @@ -23,29 +17,19 @@ - - - - - - + + + + - - - - - - - - + + + + - - - - - - + + @@ -79,4 +63,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/incident.xml b/P5/Source/Specs/incident.xml index b42f195967..683e982c0c 100644 --- a/P5/Source/Specs/incident.xml +++ b/P5/Source/Specs/incident.xml @@ -1,11 +1,5 @@ - + incident @@ -31,9 +25,7 @@ communication. - - - + @@ -59,4 +51,4 @@ communication. - \ No newline at end of file + diff --git a/P5/Source/Specs/incipit.xml b/P5/Source/Specs/incipit.xml index 7cf7ee5d59..ec727f0a86 100644 --- a/P5/Source/Specs/incipit.xml +++ b/P5/Source/Specs/incipit.xml @@ -1,11 +1,5 @@ - + contains the incipit of a manuscript or similar object item, that is the opening words of the text proper, exclusive of any rubric which might precede it, of sufficient length to identify the work uniquely; such incipits were, in former times, frequently used a means of reference to a work, in place of a title. @@ -62,4 +56,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/index.xml b/P5/Source/Specs/index.xml index db994f01f5..6c7c93637a 100644 --- a/P5/Source/Specs/index.xml +++ b/P5/Source/Specs/index.xml @@ -1,11 +1,5 @@ - + index entry @@ -27,14 +21,10 @@ - - - - - - - - + + + + @@ -49,7 +39,9 @@ (de entre varios) pertence la entrada de íncide. fornisce un nome per specificare a quale indice (o indici) la voce di indice appartiene. - + + +

This attribute makes it possible to create multiple indexes for a text.

 @@ -76,4 +68,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/institution.xml b/P5/Source/Specs/institution.xml index 03d07c38ab..01681ffb9e 100644 --- a/P5/Source/Specs/institution.xml +++ b/P5/Source/Specs/institution.xml @@ -1,11 +1,5 @@ - + institution diff --git a/P5/Source/Specs/interaction.xml b/P5/Source/Specs/interaction.xml index 840dbd9b3b..03cc326cef 100644 --- a/P5/Source/Specs/interaction.xml +++ b/P5/Source/Specs/interaction.xml @@ -1,11 +1,5 @@ - + interaction @@ -42,7 +36,9 @@ form of response or interjection, commentary, etc. participants actifs et passifs au sein du texte describe el grado de interacción entre los participantes activos y pasivos en un texto. specifica il grado di interazione tra partecipanti attivi e passivi all'interno del testo. - + + + no interaction of any kind, e.g. a monologue @@ -100,7 +96,9 @@ inapplicable dans ce cas. émetteurs) qui produisent des parties du texte especifica el número de participantes activos (o emisores) que producen partes del texto. specifica il numero di partecipanti attivi (o addressor) che producono parti del testo. - + + + a single addressor @@ -157,7 +155,9 @@ impossible à spécifier. ou représenté specifica il numero dei partecipanti o destinatari passivi ai quali il testo è diretto o alla presenza dei quali viene prodotto o recitato especifica el nombre de participantes pasivos (o receptores) a quienes se dirige el texto, o en cuya presencia se creó o representó el texto. - + + + text is addressed to the originator e.g. a diary @@ -244,4 +244,4 @@ indéfini et illimité de personnes, comme un livre publié par exemple. - \ No newline at end of file + diff --git a/P5/Source/Specs/interp.xml b/P5/Source/Specs/interp.xml index 2578c86534..432126b477 100644 --- a/P5/Source/Specs/interp.xml +++ b/P5/Source/Specs/interp.xml @@ -1,11 +1,5 @@ - + interpretation @@ -72,4 +66,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/interpGrp.xml b/P5/Source/Specs/interpGrp.xml index e747bb8a68..385a24941f 100644 --- a/P5/Source/Specs/interpGrp.xml +++ b/P5/Source/Specs/interpGrp.xml @@ -1,11 +1,5 @@ - + interpretation group @@ -93,4 +87,4 @@ interpretive framework --> - \ No newline at end of file + diff --git a/P5/Source/Specs/interpretation.xml b/P5/Source/Specs/interpretation.xml index d9923ea2e1..f7ce1cc77c 100644 --- a/P5/Source/Specs/interpretation.xml +++ b/P5/Source/Specs/interpretation.xml @@ -1,11 +1,5 @@ - + interpretation @@ -29,9 +23,7 @@ $Id$ - - - + @@ -59,4 +51,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/item.xml b/P5/Source/Specs/item.xml index a06d37d241..cf14fe0a1d 100644 --- a/P5/Source/Specs/item.xml +++ b/P5/Source/Specs/item.xml @@ -1,11 +1,5 @@ - + item @@ -102,9 +96,8 @@ der zu definierende Term im label-Element und nicht im n-Attribut angegeben werden.

- - \ No newline at end of file + diff --git a/P5/Source/Specs/join.xml b/P5/Source/Specs/join.xml index 3bb10bfcb7..535475dd1a 100644 --- a/P5/Source/Specs/join.xml +++ b/P5/Source/Specs/join.xml @@ -1,5 +1,5 @@ - + join @@ -18,12 +18,10 @@ - - - - - - + + + + @@ -41,7 +39,9 @@ You must supply at least two values for @target on spécifie le nom de l'élément que cette agrégation est censée former. indica el nombre del elemento representado por el conjunto de identificadores en cuestión. indica il nome dell'elemento rappresentato dall'insieme di identificatori in questione - + + + indicates whether the targets to be joined include the entire element indicated (the entire subtree including its root), or just the children of the target (the branches of the subtree). @@ -51,7 +51,9 @@ You must supply at least two values for @target on indique si les cibles à réunir incluent l'intégralité de l'élément indiqué (le sous-arbre entier y compris sa racine) ou seulement les enfants de la cible (les branches du sous-arbre). especifica si las metas a enlazar incluyen el elemento entero indicado (el árbol entero con la raíz inclusive) o sólo los elementos que tienen como padre la misma meta (las ramas del árbol). specifica se le destinazioni da collegare includono l'intero elemento indicato (l'intero albero compresa la radice) oppure solo gli elementi che hanno come genitore la stessa destinazione (i rami dell'albero) - + + + root @@ -199,4 +201,4 @@ You must supply at least two values for @target on - \ No newline at end of file + diff --git a/P5/Source/Specs/joinGrp.xml b/P5/Source/Specs/joinGrp.xml index 56d0084095..c544a16185 100644 --- a/P5/Source/Specs/joinGrp.xml +++ b/P5/Source/Specs/joinGrp.xml @@ -1,5 +1,5 @@ - + join group @@ -42,7 +42,9 @@ décrit le résultat produit par le rassemblement dans cette collection des éléments join. describe el resultado de los enlaces agrupados en tal conjunto. descrive il risultato dei collegamenti raggruppati in tale insieme - + + + @@ -73,4 +75,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/keywords.xml b/P5/Source/Specs/keywords.xml index f3d9f61080..f0eeda73bc 100644 --- a/P5/Source/Specs/keywords.xml +++ b/P5/Source/Specs/keywords.xml @@ -1,11 +1,5 @@ - + keywords @@ -17,7 +11,7 @@ $Id$ 텍스트의 주제 또는 특성을 식별하는 주제어 또는 구의 목록을 포함한다. 包含標明文件主題或性質的關鍵詞或字詞列表。 テキストの話題や性格を特定するキーワードや句のリストを示す。 - enthält eine Zusammenstellung von Schlagwörtern oder Phrasen zur Art oder Thematik des Textes. + enthält eine Zusammenstellung von Schlagwörtern oder Phrasen zur Art oder Thematik des Textes. contiene una lista de palabras clave o sintagmas que identifican la temática o la naturaleza del texto. contiene una lista delle parole chiave o frasi che @@ -27,7 +21,7 @@ $Id$ - + @@ -41,13 +35,15 @@ $Id$ 관련 키워드 집합이 정의된 통제 어휘를 식별하며, 이 정의는 통제 어휘 내에서 수행된다. 標明相關關鍵詞所使用到的詞彙範圍。 当該キーワードリストが定義されている統制語彙を示す。 - gibt das kontrollierte Vokabular an, in dem die benutzten Schlagwörter + gibt das kontrollierte Vokabular an, in dem die benutzten Schlagwörter definiert sind. Dabei kann das scheme-Attribut auf ein taxonomy-Element oder eine andere Ressource verweisen. identifican el vocabulario con el que se define el conjunto de palabras clave referidas. identifica il vocabolario controllato all'interno del quale sono definite le parole chiave. - + + + @@ -98,14 +94,14 @@ permitted for backwards compatibility, but is deprecated.

should be supplied for the scheme attribute.

-

Jedes einzelne Schlagwort (zusammengesetzte Themen-Schlagwörter eingeschlossen) +

Jedes einzelne Schlagwort (zusammengesetzte Themen-Schlagwörter eingeschlossen) sollte als term-Element direkt im keywords-Element notiert werden. Aus Gründen der Rückwärtskompatibilität ist es zwar auch erlaubt, ein term-Element in einem item-Element zu notieren, das wiederum Kindelement eines list-Elementes ist. Allerdings ist dieses Vorgehen veraltet und wird daher nicht empfohlen.

-

Wenn keine kontrollierte Liste für die verwendeten Schlagwörter existiert, sollte das scheme-Attribute nicht gesetzt werden.

+

Wenn keine kontrollierte Liste für die verwendeten Schlagwörter existiert, sollte das scheme-Attribute nicht gesetzt werden.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/kinesic.xml b/P5/Source/Specs/kinesic.xml index 15db325a14..e06186d4a2 100644 --- a/P5/Source/Specs/kinesic.xml +++ b/P5/Source/Specs/kinesic.xml @@ -1,11 +1,5 @@ - + kinesic @@ -28,9 +22,7 @@ $Id$ - - - + @@ -43,7 +35,9 @@ $Id$ répété. indica si el fenómeno es eventual o si se repite. indica l'eventuale ripetizione del fenomeno - + + + false

The value true indicates that the kinesic is @@ -85,4 +79,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/l.xml b/P5/Source/Specs/l.xml index 906375ab08..676e70756d 100644 --- a/P5/Source/Specs/l.xml +++ b/P5/Source/Specs/l.xml @@ -1,11 +1,5 @@ - + verse line @@ -67,4 +61,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/label.xml b/P5/Source/Specs/label.xml index 355552ca4c..9777ecc422 100644 --- a/P5/Source/Specs/label.xml +++ b/P5/Source/Specs/label.xml @@ -1,11 +1,5 @@ - + label @@ -345,4 +339,4 @@ entre les Romains. - \ No newline at end of file + diff --git a/P5/Source/Specs/lacunaEnd.xml b/P5/Source/Specs/lacunaEnd.xml index eb0c6f250c..b51c9e77e2 100644 --- a/P5/Source/Specs/lacunaEnd.xml +++ b/P5/Source/Specs/lacunaEnd.xml @@ -1,11 +1,5 @@ - + lacuna end @@ -24,7 +18,9 @@ witness. - + + + auctorite @@ -43,4 +39,4 @@ witness. - \ No newline at end of file + diff --git a/P5/Source/Specs/lacunaStart.xml b/P5/Source/Specs/lacunaStart.xml index ab2524033c..0613e46c4d 100644 --- a/P5/Source/Specs/lacunaStart.xml +++ b/P5/Source/Specs/lacunaStart.xml @@ -1,11 +1,5 @@ - + lacuna start @@ -24,7 +18,9 @@ complete textual witness. - + + + @@ -38,4 +34,4 @@ complete textual witness. - \ No newline at end of file + diff --git a/P5/Source/Specs/lang.xml b/P5/Source/Specs/lang.xml index a5825ef522..7ca94bc8b2 100644 --- a/P5/Source/Specs/lang.xml +++ b/P5/Source/Specs/lang.xml @@ -1,11 +1,5 @@ - + language name diff --git a/P5/Source/Specs/langKnowledge.xml b/P5/Source/Specs/langKnowledge.xml index b3ca2bc8ec..1c97ad051c 100644 --- a/P5/Source/Specs/langKnowledge.xml +++ b/P5/Source/Specs/langKnowledge.xml @@ -1,10 +1,7 @@ - + + + + language knowledge 언어 지식 conocimiento del lenguaje @@ -30,57 +27,55 @@ - - - - - - - + + + + + + + - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + - + - - - - + + + + @@ -91,7 +86,9 @@ fournit un ou plusieurs codes de langue valides pour les langues spécifiées. asigna uno o más marcadores válidos a las lenguas indicadas. assegna uno o più marcatori validi alle lingue indicate - + + +

This attribute should be supplied only if the element contains no langKnown children. Its values are language tags as defined in RFC 4646 or its @@ -156,4 +153,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/langKnown.xml b/P5/Source/Specs/langKnown.xml index a2bfb78124..c1f853e93d 100644 --- a/P5/Source/Specs/langKnown.xml +++ b/P5/Source/Specs/langKnown.xml @@ -1,10 +1,7 @@ - + + + + language known 언어 능력 語言能力 @@ -27,40 +24,38 @@ - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + supplies a valid language tag for the language concerned. 관련 언어에 대한 유효한 언어 태그를 제공한다. 用有效的語言標籤來表示所指語言。 @@ -68,7 +63,9 @@ fournit un code de langue valide pour la langue concernée. asigna un marcador válido a las lengua referida. assegna un marcatore valido alla lingua in questione - + + +

The value for this attribute should be a language tag as defined in BCP 47.

 @@ -87,7 +84,9 @@ un code indiquant le niveau de connaissance qu'une personne a de cette langue. código indicativo del nivel de competencia de una persona en una lengua. codice che indica il livello di competenza della persona in una determinata lingua - + + + @@ -100,7 +99,7 @@ - + Mixtepec-Mixtec English Spanish @@ -123,4 +122,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/langUsage.xml b/P5/Source/Specs/langUsage.xml index 93481ceb62..b82e9bf64c 100644 --- a/P5/Source/Specs/langUsage.xml +++ b/P5/Source/Specs/langUsage.xml @@ -1,11 +1,5 @@ - + language usage @@ -20,7 +14,7 @@ $Id$ 텍스트 내에 나타나는 언어, 특수 언어, 레지스터, 방언 등을 기술한다. 描述文件中使用的語言、次要語言、語域、方言等。 テキスト中にある言語、特殊言語、社会的方言、方言などを示す。 - beschreibt Sprachen, Subsprachen, Register, Dialekte usw., die innerhalb eines Textes vorkommen. + beschreibt Sprachen, Subsprachen, Register, Dialekte usw., die innerhalb eines Textes vorkommen. describe las lenguas, jergas, registros, dialectos, etc. presentes en el texto. descrive le lingue, i linguaggi secondari, i registri, i dialetti ecc. rappresentati all'interno di un testo. @@ -29,14 +23,10 @@ $Id$ - - - - - - - - + + + + diff --git a/P5/Source/Specs/language.xml b/P5/Source/Specs/language.xml index bda6f92ad7..9c27ff3975 100644 --- a/P5/Source/Specs/language.xml +++ b/P5/Source/Specs/language.xml @@ -1,11 +1,5 @@ - + language @@ -17,7 +11,7 @@ $Id$ 텍스트 내에서 사용되는 언어 또는 특수 언어의 특징을 기술한다. 個別敘述文本中使用的語言或次要語言。 テキスト中にあるひとつの言語または特殊言語を示す。 - beschreibt eine einzelne Sprache oder eine Subsprache, die innerhalb eines Textes verwendet wird. + beschreibt eine einzelne Sprache oder eine Subsprache, die innerhalb eines Textes verwendet wird. caracteriza una lengua o jerga empleada en un texto. indica una lingua o un linguaggio secondario utilizzato all'interno di un testo. @@ -34,8 +28,8 @@ $Id$ identificador identificateur identificatore - Identifikator - + Identifikator + Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which may be referenced by the global xml:lang attribute. @@ -50,7 +44,7 @@ $Id$ ，用來識別此元素所紀錄的語言，並由全域屬性xml:lang所參照。 当該要素で記録される言語を特定するために、 BCP 47 で定義されている言語コードを示す。また、 BCP 47 は、グローバル属性xml:langでも使用される。 - gibt einen Sprachcode, aufgebaut nach BCP 47 an, + gibt einen Sprachcode, aufgebaut nach BCP 47 an, der zur Identifikation der im Element dokumentierten Sprache benutzt wird und auf den das globale xml:lang-Attribut verweist. proporciona un código de lengua construido según se define en BCP 47 (o en su sucesor) @@ -60,7 +54,9 @@ $Id$ definito in BCP 47 (o nei sui successori), utilizzato per identificare la lingua documentata da questo elemento e che è indicato dall'attributo globale xml:lang. - + + + specifies the approximate percentage of the text which uses this language. @@ -69,12 +65,14 @@ $Id$ 이 언어를 사용하는 텍스트의 대략적 백분율(분량)을 명시한다. 標明該文本使用此語言的大約比例 (以冊計) 。 当該言語がテキスト中で使用されているおよその割合を示す。 - gibt den ungefähren prozentualen Anteil des Textes an, der in dieser Sprache verfasst wurde. + gibt den ungefähren prozentualen Anteil des Textes an, der in dieser Sprache verfasst wurde. especifica el porcentaje (de volumen) aproximado de texto que usa esa lengua. specifica la percentuale approsimativa (per volume) di testo che usa questa lingua. - + + + @@ -120,9 +118,9 @@ $Id$

特殊言語の場合には、非公式の散文による記述にすべきである。

-

Insbesondere für Subsprachen sollte eine Beschreibung als Inhalt des Elements angegeben werden.

+

Insbesondere für Subsprachen sollte eine Beschreibung als Inhalt des Elements angegeben werden.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/layout.xml b/P5/Source/Specs/layout.xml index 3fa64200ad..d10aeaf971 100644 --- a/P5/Source/Specs/layout.xml +++ b/P5/Source/Specs/layout.xml @@ -1,11 +1,5 @@ - + layout @@ -39,17 +33,23 @@ $Id$ page indica el número de columnas por página. specifica il numero di colonne per pagina - -

If a single number is given, all pages referenced have this number of columns. If two numbers are given, the number of columns per page varies between the values supplied. Where columns is omitted the number is assumed to be 1.

-

Columns may be independent of page orientation or reading direction, and a single textual stream may have one or more columns.

- + + + + +

If a single number is given, all pages referenced have this number of columns. If two numbers are given, the number of columns per page varies between the values supplied. Where columns is omitted the number is assumed to be 1.

+

Columns may be independent of page orientation or reading direction, and a single textual stream may have one or more columns.

+ - textual streams - indicates the number of streams per page, each of which contains an independent textual stream - -

If a single number is given, all pages referenced have this number of textual streams. If two numbers are given, the number of textual streams per page varies between the values supplied. Where streams is omitted the number is assumed to be 1 and unless specified elsewhere the script orientation of the source is identical to that used in the TEI document.

- + textual streams + indicates the number of streams per page, each of which contains an independent textual stream + + + + +

If a single number is given, all pages referenced have this number of textual streams. If two numbers are given, the number of textual streams per page varies between the values supplied. Where streams is omitted the number is assumed to be 1 and unless specified elsewhere the script orientation of the source is identical to that used in the TEI document.

+ ruled lines @@ -62,11 +62,15 @@ $Id$ par colonne especifica el número de líneas delineadas por columna. specifica il numero di righe per colonna - -

If a single + + + + +

If a single number is given, all columns have this number of ruled lines. If two numbers are given, the number of ruled lines per column varies between - the values supplied.

 + the values supplied.

+ written lines @@ -79,11 +83,15 @@ $Id$ spécifie le nombre de lignes écrites par colonne especifica el número de líneas escritas por columna. specifica il numero di righe scritte per colonna - -

If a single + + + + +

If a single number is given, all columns have this number of written lines. If two numbers are given, the number of written lines per column varies between - the values supplied.

 + the values supplied.

+ @@ -150,18 +158,18 @@ between the columns; each column with between 40 and 50 lines of writing.

 - - -
+ + +
一二三 一二三 一二三 -
- - +
+ + - \ No newline at end of file + diff --git a/P5/Source/Specs/layoutDesc.xml b/P5/Source/Specs/layoutDesc.xml index 28c7b7468e..3ef88b156b 100644 --- a/P5/Source/Specs/layoutDesc.xml +++ b/P5/Source/Specs/layoutDesc.xml @@ -1,11 +1,5 @@ - + layout description @@ -27,16 +21,10 @@ $Id$ - - - + - - - - - - + + @@ -82,7 +70,7 @@ $Id$

小孔的三欄可見.

- + @@ -103,4 +91,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/lb.xml b/P5/Source/Specs/lb.xml index 1d48306e51..495dfb4a42 100644 --- a/P5/Source/Specs/lb.xml +++ b/P5/Source/Specs/lb.xml @@ -1,11 +1,5 @@ - + line beginning @@ -35,7 +29,9 @@ - + + +

This example shows typographical line breaks within metrical lines, where they occur at different places in different editions:

@@ -128,7 +124,7 @@ soi-xante & dixhuytiesme livre. an der eine neue Zeile beginnt. Das n-Attribut enhält gegebenenfalls die Nummer der Zeile oder einen ähnlichen Wert, der sich auf den Text bezieht, der bis zum nächsten lb folgt, typischerweise die Nummer einer Zeile - auf einer Seite oder andere einschlägige Einheiten.

+ auf einer Seite oder andere einschlägige Einheiten.

Das Element dient dazu, typographische oder paläographische Phänomene an der Stelle zu beschreiben, an der sie auf dem Schriftträger sichtbar sind; es sollte nicht für Struktureinheiten wie z. B. Verszeilen in Lyrik verwendet @@ -143,4 +139,4 @@ soi-xante & dixhuytiesme livre. - \ No newline at end of file + diff --git a/P5/Source/Specs/lbl.xml b/P5/Source/Specs/lbl.xml index f63f590c44..017e5fbb7c 100644 --- a/P5/Source/Specs/lbl.xml +++ b/P5/Source/Specs/lbl.xml @@ -1,11 +1,5 @@ - + label @@ -35,7 +29,7 @@ $Id$ - + @@ -53,7 +47,9 @@ $Id$ funcional classifica le etichette secondo una tipologia funzionale - + + + @@ -111,4 +107,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/leaf.xml b/P5/Source/Specs/leaf.xml index f151cbe30d..be68621689 100644 --- a/P5/Source/Specs/leaf.xml +++ b/P5/Source/Specs/leaf.xml @@ -1,11 +1,5 @@ - + leaf @@ -22,9 +16,7 @@ $Id$ - - - + @@ -36,7 +28,9 @@ structure or other analytic element. fournit l'identifiant de l'objet représenté par la feuille ; cet objet peut être une paire nom-valeur ou tout autre élément analytique. proporciona un identificador de una estructura de rasgos u otro elemento de análisis. assegna alla foglia un valore, che può essere una struttura di tratti o altro elemento di analisi - + + + provides the identifier of parent of a leaf. @@ -46,7 +40,9 @@ structure or other analytic element. fournit l'identifiant du parent de la feuille. proporciona el identificador que es padre de una hoja. assegna un identificatore al genitore della foglia - + + + provides an identifier of an element which this leaf follows. @@ -56,7 +52,9 @@ structure or other analytic element. fournit l'identifiant d'un élément que cette feuille suit. proporciona un identificador al elemento que precede a la hoja. assegna un identificatore all'elemento che precede la foglia - + + +

If the tree is unordered or partially ordered, this attribute has the property of fixing the relative order of the leaf and @@ -102,4 +100,4 @@ the element which is the value of the attribute.

- \ No newline at end of file + diff --git a/P5/Source/Specs/lem.xml b/P5/Source/Specs/lem.xml index fda8a5a690..9c75a33d8d 100644 --- a/P5/Source/Specs/lem.xml +++ b/P5/Source/Specs/lem.xml @@ -1,10 +1,7 @@ - + + + + lemma 레마 主題 @@ -23,7 +20,7 @@ $Id$ - + @@ -97,4 +94,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/lg.xml b/P5/Source/Specs/lg.xml index dabe40e72d..93b0a62723 100644 --- a/P5/Source/Specs/lg.xml +++ b/P5/Source/Specs/lg.xml @@ -1,11 +1,5 @@ - + line group @@ -40,7 +34,7 @@ - + @@ -56,7 +50,7 @@ - + @@ -152,4 +146,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/licence.xml b/P5/Source/Specs/licence.xml index 23392114ca..40451a4bca 100644 --- a/P5/Source/Specs/licence.xml +++ b/P5/Source/Specs/licence.xml @@ -1,16 +1,13 @@ - + + + + contains information about a licence or other legal agreement applicable to the text. contient des informations légales applicables au texte, notamment le contrat de licence définissant les droits d'utilisation. - beinhaltet für den Text gültige Lizenzinformationen oder andere rechtswirksame Vereinbarungen. + beinhaltet für den Text gültige Lizenzinformationen oder andere rechtswirksame Vereinbarungen. @@ -22,35 +19,35 @@ définissant les droits d'utilisation. - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -97,7 +94,7 @@ définissant les droits d'utilisation. applicability of the licence.

-

+

Das licence-Element soll für jede Lizenzvereinbarung, die sich auf den Text bezieht, angegeben werden. Das target-Attribut kann verwendet werden, um auf eine vollständige Version der Lizenz zu referenzieren. Die Attribute when, notBefore, notAfter, from oder to können in Kombination verwendet werden, um den Gültigkeitszeitraum der Lizenz anzugeben. @@ -106,4 +103,4 @@ définissant les droits d'utilisation. - \ No newline at end of file + diff --git a/P5/Source/Specs/line.xml b/P5/Source/Specs/line.xml index 9e4f673189..14a5300d70 100644 --- a/P5/Source/Specs/line.xml +++ b/P5/Source/Specs/line.xml @@ -1,11 +1,5 @@ - + contains the transcription of a topographic line in the source @@ -18,14 +12,12 @@ - - - - - - - - + + + + + + @@ -67,4 +59,4 @@ using structural elements such as p (for which use - \ No newline at end of file + diff --git a/P5/Source/Specs/link.xml b/P5/Source/Specs/link.xml index 520264faf1..7898733207 100644 --- a/P5/Source/Specs/link.xml +++ b/P5/Source/Specs/link.xml @@ -1,5 +1,5 @@ - + link @@ -17,7 +17,9 @@ - + + + You must supply at least two values for @target or on @@ -51,4 +53,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/linkGrp.xml b/P5/Source/Specs/linkGrp.xml index d03a4d33bb..75cf961a8f 100644 --- a/P5/Source/Specs/linkGrp.xml +++ b/P5/Source/Specs/linkGrp.xml @@ -1,5 +1,5 @@ - + link group @@ -113,4 +113,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/list.xml b/P5/Source/Specs/list.xml index 9991668cab..c3fc29aa1c 100644 --- a/P5/Source/Specs/list.xml +++ b/P5/Source/Specs/list.xml @@ -1,11 +1,5 @@ - + list @@ -20,7 +14,7 @@ organizados en una lista. contiene una qualsiasi sequenza di voci organizzate in una lista. - enthält eine Reihe von Listenpunkten, die als Liste organisiert sind. + enthält eine Reihe von Listenpunkten, die als Liste organisiert sind. @@ -42,72 +36,54 @@ - - - - - - - - + + + + + - - - + - - - - - - + + - - - + - - - + - - - - - - - - - - + + + + - The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element + The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element - - type Typ describes the nature of the items in the list. beschreibt die Art der Listenpunkte. - + + + gloss @@ -125,14 +101,14 @@ concept qui est donné par un élément label précédant l'item de la liste. ogni voce dell'elenco è la glossa di un termine o concetto dato da un elemento legenda che precede la voce stessa - jeder Listenpunkt erläutert einen Begriff oder ein Konzept, das von einem voranstehenden label-Element genannt wird. + jeder Listenpunkt erläutert einen Begriff oder ein Konzept, das von einem voranstehenden label-Element genannt wird. index Index each list item is an entry in an index such as the alphabetical topical index at the back of a print volume. - jeder Listenpunkt ist ein Registereintrag z. B. in einem alphabetisch geordneten + jeder Listenpunkt ist ein Registereintrag z. B. in einem alphabetisch geordneten Sachregister am Ende einer Druckausgabe. @@ -140,7 +116,7 @@ Arbeitsschritt each list item is a step in a sequence of instructions, as in a recipe. - jeder Listenpunkt ist ein Arbeitsschritt in einer Folge von Anweisungen, + jeder Listenpunkt ist ein Arbeitsschritt in einer Folge von Anweisungen, wie z. B. in einem Rezept. @@ -148,7 +124,7 @@ Litanei each list item is one of a sequence of petitions, supplications or invocations, typically in a religious ritual. - jeder Listenpunkt ist Teil einer Reihenfolge von Gebeten, Bitten oder Anrufungen die + jeder Listenpunkt ist Teil einer Reihenfolge von Gebeten, Bitten oder Anrufungen die üblicherweise in einem religiösen Ritual verwendet werden. @@ -156,7 +132,7 @@ logischer Schluss each list item is part of an argument consisting of two or more propositions and a final conclusion derived from them. - jeder Listenpunkt ist Teil eines Arguments, das aus zwei oder mehr Prämissen + jeder Listenpunkt ist Teil eines Arguments, das aus zwei oder mehr Prämissen und einem daraus gezogenen Schluss besteht. @@ -182,14 +158,14 @@ これは意味上のエラーになる。

-

In älteren Versionen dieser Richtlinien wurde empfohlen, mit dem Attribut type am list-Element +

In älteren Versionen dieser Richtlinien wurde empfohlen, mit dem Attribut type am list-Element die Darstellung oder das Erscheinungsbild einer Liste zu kodieren (also ob sie z. B. nummeriert oder mit Symbolen versehen ist). Die aktuelle Empfehlung ist, dafür die Attribute rend oder style zu verwenden, während mit type der Inhalt der Liste charakterisiert werden sollte.

-

Die formale Syntax der Elementdeklaration +

Die formale Syntax der Elementdeklaration erlaubt es, Listen vom list type="gloss" ohne das Element label zu verwenden; das ist jedoch ein semantischer Fehler.

- + @@ -394,7 +370,6 @@ Struktur der zweistufigen Nummerierung der Klauseln wider. Die Klauseln könnten auch als eine einstufige Liste mit unregelmäßiger Nummerierung behandelt werden.

 -

These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they @@ -427,10 +402,10 @@ 先行することがある。

-

Die Liste kann mit einer Überschrift head beginnen. Sie kann auch aus Paaren von Labels und Beschreibungen bestehen, +

Die Liste kann mit einer Überschrift head beginnen. Sie kann auch aus Paaren von Labels und Beschreibungen bestehen, sodass dann für jeden Teil spezielle Überschriften (headLabel, headItem) verwendet werden können.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/listAnnotation.xml b/P5/Source/Specs/listAnnotation.xml index eed95be842..fc3fe52687 100644 --- a/P5/Source/Specs/listAnnotation.xml +++ b/P5/Source/Specs/listAnnotation.xml @@ -1,14 +1,7 @@ - + - + contains a list of annotations, typically encoded as annotation, annotationBlock, or note, possibly organized with nested listAnnotation elements. @@ -111,7 +104,8 @@ $Id$ Harry Pratt Judson the verb is singular, because the two rivers make one boundary; as we should say, - ‘is divided by the line of the Seine and Marne.’ + ‘is divided by the line of the Seine and Marne.’ + diff --git a/P5/Source/Specs/listApp.xml b/P5/Source/Specs/listApp.xml index 928010c452..7ab6a6396f 100644 --- a/P5/Source/Specs/listApp.xml +++ b/P5/Source/Specs/listApp.xml @@ -1,11 +1,5 @@ - + @@ -26,15 +20,12 @@ - - - - - - - - - + + + + + + @@ -100,4 +91,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/listBibl.xml b/P5/Source/Specs/listBibl.xml index 48213c3628..c293f7ae56 100644 --- a/P5/Source/Specs/listBibl.xml +++ b/P5/Source/Specs/listBibl.xml @@ -1,11 +1,5 @@ - + citation list @@ -122,4 +116,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/listChange.xml b/P5/Source/Specs/listChange.xml index 941d7c5cd1..7400d0729b 100644 --- a/P5/Source/Specs/listChange.xml +++ b/P5/Source/Specs/listChange.xml @@ -1,11 +1,5 @@ - + groups a number of change descriptions associated @@ -16,9 +10,9 @@ with either the creation of a source text or the revision of an encoded text. - + - + @@ -29,7 +23,9 @@ with either the creation of a source text or the revision of an encoded text. indicates whether the ordering of its child change elements is to be considered significant or not - + + + true @@ -70,4 +66,4 @@ during the evolution of the encoded representation of that text.

- \ No newline at end of file + diff --git a/P5/Source/Specs/listEvent.xml b/P5/Source/Specs/listEvent.xml index ced312e626..28fc3ba030 100644 --- a/P5/Source/Specs/listEvent.xml +++ b/P5/Source/Specs/listEvent.xml @@ -1,11 +1,5 @@ - + list of events @@ -32,14 +26,14 @@ - - - - - - - - + + + + + + + + diff --git a/P5/Source/Specs/listForest.xml b/P5/Source/Specs/listForest.xml index ef16b48998..b7b63dd3c8 100644 --- a/P5/Source/Specs/listForest.xml +++ b/P5/Source/Specs/listForest.xml @@ -1,11 +1,5 @@ - + provides for lists of forests. @@ -31,7 +25,9 @@ $Id$ précise le type du groupe de forêts. identifica el tipo de grupo de bosque identifica il tipo di gruppo di foresta - + + + @@ -71,4 +67,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/listNym.xml b/P5/Source/Specs/listNym.xml index 5de66e6487..f8c4cb9288 100644 --- a/P5/Source/Specs/listNym.xml +++ b/P5/Source/Specs/listNym.xml @@ -1,11 +1,5 @@ - + list of canonical names @@ -27,26 +21,26 @@ - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + @@ -109,4 +103,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/listObject.xml b/P5/Source/Specs/listObject.xml index cdf5442ed3..514afb7a3b 100644 --- a/P5/Source/Specs/listObject.xml +++ b/P5/Source/Specs/listObject.xml @@ -1,11 +1,5 @@ - + list of objects @@ -82,10 +76,7 @@

Das type-Attribut kann verwendet werden, um unterschiedliche Typen von Objekten zu unterscheiden.

 - - - diff --git a/P5/Source/Specs/listOrg.xml b/P5/Source/Specs/listOrg.xml index 0d3fc2105b..5e5631e220 100644 --- a/P5/Source/Specs/listOrg.xml +++ b/P5/Source/Specs/listOrg.xml @@ -1,11 +1,5 @@ - + list of organizations @@ -92,4 +86,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/listPerson.xml b/P5/Source/Specs/listPerson.xml index 31963bd909..427760dd3b 100644 --- a/P5/Source/Specs/listPerson.xml +++ b/P5/Source/Specs/listPerson.xml @@ -1,11 +1,5 @@ - + list of persons @@ -31,7 +25,7 @@ los participantes de una interacción verbal o las personas referidas en una fuente histórica. contiene una lista di descrizioni, ciascuna delle quali fornisce informazioni relative a una persona specifica o a un gruppo di persone, per esempio i - partecipanti a un'interazione verbale o le persone identificate da una fonte storica + partecipanti a un'interazione verbale o le persone identificate da una fonte storica @@ -101,4 +95,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/listPlace.xml b/P5/Source/Specs/listPlace.xml index 30b7fb9df2..918cc354d1 100644 --- a/P5/Source/Specs/listPlace.xml +++ b/P5/Source/Specs/listPlace.xml @@ -1,11 +1,5 @@ - + list of places @@ -68,4 +62,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/listPrefixDef.xml b/P5/Source/Specs/listPrefixDef.xml index 07d4ca6c7f..6a7cbe54b8 100644 --- a/P5/Source/Specs/listPrefixDef.xml +++ b/P5/Source/Specs/listPrefixDef.xml @@ -1,11 +1,5 @@ - + list of prefix definitions @@ -17,12 +11,12 @@ - - - - + + + + - +

In this example, two private URI scheme prefixes are defined and patterns are provided for dereferencing them. Each prefix is also supplied with a human-readable explanation in a @@ -51,4 +45,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/listRef.xml b/P5/Source/Specs/listRef.xml index 21f8d13d4b..ef5a5f714e 100644 --- a/P5/Source/Specs/listRef.xml +++ b/P5/Source/Specs/listRef.xml @@ -1,11 +1,5 @@ - + list of references @@ -34,7 +28,7 @@ $Id$ - + In the context of tagset documentation, the listRef element must not self-nest. @@ -64,13 +58,10 @@ $Id$

When listRef is used in the context of tagdocs, further restrictons apply: - - It may only contain ptr or ref - elements. - Each ptr or ref child should bear a + It may only contain ptr or ref + elements.Each ptr or ref child should bear a target attribute, the value of which should be a - single URI pointer. - + single URI pointer.

- \ No newline at end of file + diff --git a/P5/Source/Specs/listRelation.xml b/P5/Source/Specs/listRelation.xml index b8b4d6563d..a26a29045b 100644 --- a/P5/Source/Specs/listRelation.xml +++ b/P5/Source/Specs/listRelation.xml @@ -1,11 +1,5 @@ - + provides information about relationships identified amongst people, places, and @@ -52,14 +46,14 @@ $Id$ - - - - - - - - + + + + + + + +

The persons with identifiers pp1 and pp2 are the parents of pp3 and pp4; they are also married to each other; pp1 is the employer of pp3, pp5, pp6, and pp7.

@@ -141,4 +135,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/listTranspose.xml b/P5/Source/Specs/listTranspose.xml index 841cd3a091..c69b99d618 100644 --- a/P5/Source/Specs/listTranspose.xml +++ b/P5/Source/Specs/listTranspose.xml @@ -1,11 +1,5 @@ - + supplies a list of transpositions, each of which is indicated at some point in @@ -39,4 +33,4 @@ source.

- \ No newline at end of file + diff --git a/P5/Source/Specs/listWit.xml b/P5/Source/Specs/listWit.xml index bfe9547086..537fbe796d 100644 --- a/P5/Source/Specs/listWit.xml +++ b/P5/Source/Specs/listWit.xml @@ -1,11 +1,5 @@ - + witness list @@ -32,17 +26,15 @@ témoignages cités dans un apparat critique, pouvant être groupées de façon - - - - - - - - - @@ -117,4 +109,4 @@ therefore only appear within a single listWit element.

- \ No newline at end of file + diff --git a/P5/Source/Specs/localProp.xml b/P5/Source/Specs/localProp.xml index dd12a5f824..1a0eed4460 100644 --- a/P5/Source/Specs/localProp.xml +++ b/P5/Source/Specs/localProp.xml @@ -1,38 +1,38 @@ - + + - - locally defined property - provides a locally defined character (or glyph) property. - - - - - - - - - - - - - - 人 - - - - -

No definitive list of local names is proposed. However, the name entity is recommended as a means of naming the property identifying the recommended + + locally defined property + provides a locally defined character (or glyph) property. + + + + + + + + + + + + + + 人 + + + + +

No definitive list of local names is proposed. However, the name entity is recommended as a means of naming the property identifying the recommended character entity name for this character or glyph.

- - -

Il n'est pas proposé de liste fermée de noms locaux de propriétés. Cependant, la dénomination entity (entité) est recommandée pour la propriété donnant le + + +

Il n'est pas proposé de liste fermée de noms locaux de propriétés. Cependant, la dénomination entity (entité) est recommandée pour la propriété donnant le nom de l'entité caractère conseillée pour le caractère ou le glyphe en cours de description.

- - -

ローカル名のリストで勧告されているものはない。但し、文字やグリフを 表す文字エンティティを特定する際には、名前エンティティ を使い素性に名付けることは推奨されている。

- - - - + + +

ローカル名のリストで勧告されているものはない。但し、文字やグリフを 表す文字エンティティを特定する際には、名前エンティティ を使い素性に名付けることは推奨されている。

+ + + + diff --git a/P5/Source/Specs/locale.xml b/P5/Source/Specs/locale.xml index b9ec4e9f4e..c8c737319b 100644 --- a/P5/Source/Specs/locale.xml +++ b/P5/Source/Specs/locale.xml @@ -1,11 +1,5 @@ - + @@ -44,4 +38,4 @@ place concerned, for example: a room, a restaurant, a park bench, etc. - \ No newline at end of file + diff --git a/P5/Source/Specs/location.xml b/P5/Source/Specs/location.xml index 2a2cd16bd2..1565922f5c 100644 --- a/P5/Source/Specs/location.xml +++ b/P5/Source/Specs/location.xml @@ -1,10 +1,7 @@ - + + + + location localisation defines the location of a place as a set of geographical coordinates, in terms of other named geo-political entities, or as an @@ -25,50 +22,48 @@ - - - - - - - - - - - - + + + + + + + + + + - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -110,4 +105,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/locus.xml b/P5/Source/Specs/locus.xml index 5dabd4ee0b..c0c35db20b 100644 --- a/P5/Source/Specs/locus.xml +++ b/P5/Source/Specs/locus.xml @@ -1,11 +1,5 @@ - + locus @@ -31,12 +25,12 @@ $Id$ - - - - - - + + + + + + @@ -54,7 +48,9 @@ $Id$ especificada. identifica la foliazione in base alla posizione specificata - + + + from @@ -71,7 +67,9 @@ $Id$ forma estándard. specifica l'inizio della posizione in forma normalizzata - + + + to @@ -88,7 +86,9 @@ $Id$ forma estándard. specifica il termine della posizione in forma normalizzata - + + + diff --git a/P5/Source/Specs/locusGrp.xml b/P5/Source/Specs/locusGrp.xml index 366114db64..55c8c3b894 100644 --- a/P5/Source/Specs/locusGrp.xml +++ b/P5/Source/Specs/locusGrp.xml @@ -1,11 +1,5 @@ - + locus group @@ -28,7 +22,9 @@ $Id$ locations contained by the group are specified by pointing to some foliation element defining it, or to some other equivalent resource. désigne le système de foliotation selon lequel les emplacements contenus dans le groupe sont définis. - + + + diff --git a/P5/Source/Specs/m.xml b/P5/Source/Specs/m.xml index 4539961b5c..22e8c051b4 100644 --- a/P5/Source/Specs/m.xml +++ b/P5/Source/Specs/m.xml @@ -1,11 +1,5 @@ - + morpheme @@ -29,17 +23,15 @@ $Id$ - - - - - - - - - - - + + + + + + + + + @@ -50,7 +42,9 @@ $Id$ identifie la forme de base du morphème identifica la forma base del morfema identifica la forma base del morfema - + + + @@ -97,4 +91,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/macro.abContent.xml b/P5/Source/Specs/macro.abContent.xml index 896739362e..1455f385b1 100644 --- a/P5/Source/Specs/macro.abContent.xml +++ b/P5/Source/Specs/macro.abContent.xml @@ -1,16 +1,10 @@ - + anonymous block content defines the content of anonymous block elements. - + diff --git a/P5/Source/Specs/macro.limitedContent.xml b/P5/Source/Specs/macro.limitedContent.xml index 9b21aa5493..d3b719d4ea 100644 --- a/P5/Source/Specs/macro.limitedContent.xml +++ b/P5/Source/Specs/macro.limitedContent.xml @@ -1,11 +1,5 @@ - + paragraph content @@ -21,15 +15,13 @@ $Id$ pas utilisés pour la transcription des contenus existants. define el contenido de elementos de prosa que no se usan para la transcripción de materiales existentes. - - - - - - - + + + + + - \ No newline at end of file + diff --git a/P5/Source/Specs/macro.paraContent.xml b/P5/Source/Specs/macro.paraContent.xml index 21112a4822..ad86a4bfd8 100644 --- a/P5/Source/Specs/macro.paraContent.xml +++ b/P5/Source/Specs/macro.paraContent.xml @@ -1,11 +1,5 @@ - + paragraph content @@ -22,7 +16,7 @@ $Id$ semblables. define el contenido de párrafos y elementos similares. definisce il contenuto di paragrafi ed elementi simili - + @@ -31,4 +25,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/macro.phraseSeq.limited.xml b/P5/Source/Specs/macro.phraseSeq.limited.xml index b2fae86a03..c1ad91eb8c 100644 --- a/P5/Source/Specs/macro.phraseSeq.limited.xml +++ b/P5/Source/Specs/macro.phraseSeq.limited.xml @@ -1,11 +1,5 @@ - + limited phrase sequence @@ -24,15 +18,13 @@ used for transcribing extant documents. documents existants. define una secuencia de caracteres y elementos de tipo sintagmático que no se usan normalmente para transcribir. - - - - - - - + + + + + - \ No newline at end of file + diff --git a/P5/Source/Specs/macro.phraseSeq.xml b/P5/Source/Specs/macro.phraseSeq.xml index aeff2e469e..2c624c58ba 100644 --- a/P5/Source/Specs/macro.phraseSeq.xml +++ b/P5/Source/Specs/macro.phraseSeq.xml @@ -1,11 +1,5 @@ - + phrase sequence @@ -24,17 +18,15 @@ $Id$ definisce una sequenza di caratteri ed elementi di tipo sintagmatico - - - - - - - - - + + + + + + + - \ No newline at end of file + diff --git a/P5/Source/Specs/macro.specialPara.xml b/P5/Source/Specs/macro.specialPara.xml index a531a633e4..6ff84a5546 100644 --- a/P5/Source/Specs/macro.specialPara.xml +++ b/P5/Source/Specs/macro.specialPara.xml @@ -1,11 +1,5 @@ - + 'special' paragraph content @@ -33,18 +27,16 @@ $Id$ o voci di lista che contiene una serie di elementi a livello di componenti aventi la stessa struttura di un paragrafo con una serie di elementi a livello sintagmatico e interlivello - - - - - - - - - - + + + + + + + + - \ No newline at end of file + diff --git a/P5/Source/Specs/macro.xtext.xml b/P5/Source/Specs/macro.xtext.xml index 3c1a9d0bb8..87192ef46f 100644 --- a/P5/Source/Specs/macro.xtext.xml +++ b/P5/Source/Specs/macro.xtext.xml @@ -1,11 +1,5 @@ - + extended text @@ -23,11 +17,9 @@ $Id$ define una secuencia de caracteres y elementos gaiji. definisce una sequenza di caratteri ed elementi gaiji - - - - - - + + + + - \ No newline at end of file + diff --git a/P5/Source/Specs/macroRef.xml b/P5/Source/Specs/macroRef.xml index ba756f8d91..5f3e8221be 100644 --- a/P5/Source/Specs/macroRef.xml +++ b/P5/Source/Specs/macroRef.xml @@ -1,11 +1,5 @@ - + points to the specification for some pattern which is to be included in a schema @@ -14,12 +8,16 @@ - + + + the identifier used for the required pattern within the source indicated. - + + + @@ -40,4 +38,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/macroSpec.xml b/P5/Source/Specs/macroSpec.xml index bda9b5aca2..7749fd1fe4 100644 --- a/P5/Source/Specs/macroSpec.xml +++ b/P5/Source/Specs/macroSpec.xml @@ -1,11 +1,5 @@ - + macro specification @@ -47,10 +41,10 @@ $Id$ - - - - + + + + diff --git a/P5/Source/Specs/mapping.xml b/P5/Source/Specs/mapping.xml index 6cc9808dc1..bf135b2197 100644 --- a/P5/Source/Specs/mapping.xml +++ b/P5/Source/Specs/mapping.xml @@ -1,11 +1,5 @@ - + character mapping diff --git a/P5/Source/Specs/material.xml b/P5/Source/Specs/material.xml index 403b4f0cf2..52a08f0e99 100644 --- a/P5/Source/Specs/material.xml +++ b/P5/Source/Specs/material.xml @@ -1,11 +1,5 @@ - + material @@ -69,7 +63,9 @@ $Id$ identifies one or more elements to which the metamark applies. - + + + diff --git a/P5/Source/Specs/measure.xml b/P5/Source/Specs/measure.xml index 31c78873c9..67d41147f9 100644 --- a/P5/Source/Specs/measure.xml +++ b/P5/Source/Specs/measure.xml @@ -1,11 +1,5 @@ - + measure diff --git a/P5/Source/Specs/measureGrp.xml b/P5/Source/Specs/measureGrp.xml index 0d6c2a77ad..87d9ed6ac2 100644 --- a/P5/Source/Specs/measureGrp.xml +++ b/P5/Source/Specs/measureGrp.xml @@ -1,11 +1,5 @@ - + measure group @@ -32,13 +26,11 @@ - - - - - - - + + + + + + indicates the location of any form of external media such as @@ -21,9 +15,7 @@ - - - + @@ -73,4 +65,4 @@ the resource specified by the url attribute.

- \ No newline at end of file + diff --git a/P5/Source/Specs/meeting.xml b/P5/Source/Specs/meeting.xml index dcde91d528..3104a8793e 100644 --- a/P5/Source/Specs/meeting.xml +++ b/P5/Source/Specs/meeting.xml @@ -1,10 +1,7 @@ - + + + + contains the formalized descriptive title for a meeting or conference, for use in a bibliographic description for an item derived from such a meeting, or as a heading or preamble to publications emanating from it. @@ -32,35 +29,35 @@ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -121,4 +118,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/memberOf.xml b/P5/Source/Specs/memberOf.xml index 0ec6ae5d05..b574a82d1d 100644 --- a/P5/Source/Specs/memberOf.xml +++ b/P5/Source/Specs/memberOf.xml @@ -1,11 +1,5 @@ - + specifies class membership of the documented element or class. @@ -37,7 +31,9 @@ $Id$ el elemento o clase indicados son un miembro o una subclase. indica l'identificatore di una classe di cui l'elemento o classe indicati sono un membro o una sottoclasse - + + + specifies the effect of this declaration on its parent module. @@ -49,7 +45,9 @@ $Id$ parent. specifica l'effetto della dichiarazione sul modulo genitore - + + + add @@ -78,11 +76,15 @@ $Id$ supplies the maximum number of times the element can occur in elements which use this model class in their content model - + + + supplies the minumum number of times the element must occur in elements which use this model class in their content model - + + + @@ -134,4 +136,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/mentioned.xml b/P5/Source/Specs/mentioned.xml index 1ac30b1f74..7dbf966e6b 100644 --- a/P5/Source/Specs/mentioned.xml +++ b/P5/Source/Specs/mentioned.xml @@ -1,11 +1,5 @@ - + @@ -48,4 +42,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/metDecl.xml b/P5/Source/Specs/metDecl.xml index 16cb3e411e..fe81432720 100644 --- a/P5/Source/Specs/metDecl.xml +++ b/P5/Source/Specs/metDecl.xml @@ -1,11 +1,5 @@ - + metrical notation declaration @@ -48,15 +42,11 @@ $Id$ - - - - - - - - - + + + + + @@ -78,7 +68,9 @@ $Id$ ello. indica se l'annotazione fornisce la forma metrica estratta, la sua realizzazione prosodica,lo schema delle rime o un loro combinazione - + + + met real @@ -127,15 +119,14 @@ $Id$ una estructura métrica convencional codificada en el atributo real. - - + - - declaration applies to the rhyme scheme recorded on the rhyme attribute + declaration applies to the rhyme scheme recorded on the rhyme attribute 선언은 rhyme 속성에 기록된 운 스키마에 적용한다. la declaración se aplica al esquema de rima registrado en el atributo rima @@ -183,14 +174,19 @@ $Id$ valor válido para esta notación. specifica un'espressione regolare che definisce qualsiasi valore legale per l'annotazione - -

The value must be a valid regular expression per the World Wide Web Consortium's + + + + +

The value must be a valid regular expression per the World Wide Web Consortium's XML Schema Part 2: Datatypes Second Edition, Appendix F. -

 -

La valeur doit être une expression régulière valide pour le Consortium - du World Wide Web XML Schema Part 2: Datatypes Second Edition, Appendix F.

 - +

+ + +

La valeur doit être une expression régulière valide pour le Consortium + du World Wide Web XML Schema Part 2: Datatypes Second Edition, Appendix F.

+ diff --git a/P5/Source/Specs/metSym.xml b/P5/Source/Specs/metSym.xml index a2a0abc6a4..9ad1b824b4 100644 --- a/P5/Source/Specs/metSym.xml +++ b/P5/Source/Specs/metSym.xml @@ -1,11 +1,5 @@ - + metrical notation symbol @@ -53,7 +47,9 @@ $Id$ documentando. specifica il carattere o la sequenza di caratteri documentata. - + + + specifies whether the symbol is defined in terms of other symbols (terminal @@ -77,7 +73,9 @@ $Id$ indica se il simbolo è definito con altri simboli (terminal definito dal valore false) o con una descrizione (terminal definito dal valore true). - + + + true

The value true indicates that the element contains a prose definition of its @@ -120,4 +118,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/metamark.xml b/P5/Source/Specs/metamark.xml index 4844932e02..429d7c839b 100644 --- a/P5/Source/Specs/metamark.xml +++ b/P5/Source/Specs/metamark.xml @@ -1,11 +1,5 @@ - + contains or describes any kind of graphic or written signal @@ -26,11 +20,15 @@ describes the function (for example status, insertion, deletion, transposition) of the metamark. - + + + identifies one or more elements to which the metamark applies. - + + + @@ -44,25 +42,25 @@ - - - I am that halfgrown angry boy, fallen asleep - The tears of foolish passion yet undried - upon my cheeks. - - I pass through the travels and fortunes of + + + I am that halfgrown angry boy, fallen asleep + The tears of foolish passion yet undried + upon my cheeks. + + I pass through the travels and fortunes of thirty - years and become old, - Each in its due order comes and goes, - And thus a message for me comes. - The - - Entered - Yes - + years and become old, + Each in its due order comes and goes, + And thus a message for me comes. + The + + Entered - Yes + - + - \ No newline at end of file + diff --git a/P5/Source/Specs/milestone.xml b/P5/Source/Specs/milestone.xml index d24366a5cf..f917b29566 100644 --- a/P5/Source/Specs/milestone.xml +++ b/P5/Source/Specs/milestone.xml @@ -1,11 +1,5 @@ - + milestone @@ -41,7 +35,9 @@ $Id$ - + + + @@ -96,4 +92,4 @@ milestones for line numbers. --> - \ No newline at end of file + diff --git a/P5/Source/Specs/mod.xml b/P5/Source/Specs/mod.xml index 315f67df7a..b049bfb52a 100644 --- a/P5/Source/Specs/mod.xml +++ b/P5/Source/Specs/mod.xml @@ -1,11 +1,5 @@ - + represents any kind of modification identified within a single document. @@ -33,4 +27,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.addrPart.xml b/P5/Source/Specs/model.addrPart.xml index 6757003ae1..d2fd3f9ec7 100644 --- a/P5/Source/Specs/model.addrPart.xml +++ b/P5/Source/Specs/model.addrPart.xml @@ -1,11 +1,5 @@ - + groups elements such as names or postal codes which may appear as part of a @@ -23,4 +17,4 @@ other form of--> address. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.addressLike.xml b/P5/Source/Specs/model.addressLike.xml index f0910c30b5..4d702f9446 100644 --- a/P5/Source/Specs/model.addressLike.xml +++ b/P5/Source/Specs/model.addressLike.xml @@ -1,11 +1,5 @@ - + groups elements used to represent a postal or email address. @@ -25,4 +19,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.annotationLike.xml b/P5/Source/Specs/model.annotationLike.xml index d3f62378ab..dcff8ff408 100644 --- a/P5/Source/Specs/model.annotationLike.xml +++ b/P5/Source/Specs/model.annotationLike.xml @@ -1,11 +1,5 @@ - + groups elements used to represent annotations. diff --git a/P5/Source/Specs/model.annotationPart.body.xml b/P5/Source/Specs/model.annotationPart.body.xml index e3d6448857..4013aa4e54 100644 --- a/P5/Source/Specs/model.annotationPart.body.xml +++ b/P5/Source/Specs/model.annotationPart.body.xml @@ -1,11 +1,5 @@ - + groups elements which may be used as an annotation body. diff --git a/P5/Source/Specs/model.applicationLike.xml b/P5/Source/Specs/model.applicationLike.xml index a00d21edca..12f76341db 100644 --- a/P5/Source/Specs/model.applicationLike.xml +++ b/P5/Source/Specs/model.applicationLike.xml @@ -1,11 +1,5 @@ - + groups elements used to record application-specific information about a document in its @@ -18,4 +12,4 @@ $Id$ l'en-tête TEI d'un document des informations d'applications spécifiques. raggruppa elementi utilizzati per registrare informazioni specifiche di un'applicazione e relative a un documento nell'intestazione corrispondente - \ No newline at end of file + diff --git a/P5/Source/Specs/model.attributable.xml b/P5/Source/Specs/model.attributable.xml index 646494fcc2..82dfc479eb 100644 --- a/P5/Source/Specs/model.attributable.xml +++ b/P5/Source/Specs/model.attributable.xml @@ -1,13 +1,10 @@ - + + + + groups elements that contain a word or phrase that can be attributed to a source. gruppiert Elemente, die ein Wort oder eine Phrase enthalten, welche einer Quelle zugeschrieben werden können. - + groups elements such as licences and paragraphs of text which may appear as part of an @@ -14,4 +8,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.biblLike.xml b/P5/Source/Specs/model.biblLike.xml index 19e72966ac..e0be7dc4c2 100644 --- a/P5/Source/Specs/model.biblLike.xml +++ b/P5/Source/Specs/model.biblLike.xml @@ -1,11 +1,5 @@ - + groups elements containing a bibliographic description. @@ -26,4 +20,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.biblPart.xml b/P5/Source/Specs/model.biblPart.xml index 6c20cde833..36bdd2e09e 100644 --- a/P5/Source/Specs/model.biblPart.xml +++ b/P5/Source/Specs/model.biblPart.xml @@ -1,11 +1,5 @@ - + groups elements which represent components of a bibliographic description. @@ -21,4 +15,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.castItemPart.xml b/P5/Source/Specs/model.castItemPart.xml index 747a62fa9c..012c6f0010 100644 --- a/P5/Source/Specs/model.castItemPart.xml +++ b/P5/Source/Specs/model.castItemPart.xml @@ -1,11 +1,5 @@ - + groups component elements of an entry in a cast list, such as dramatic role or actor's name. @@ -19,4 +13,4 @@ $Id$ elementi utilizzati all'interno di una voce in una lista di personaggi, per esempio ruolo o nome dell'attore - \ No newline at end of file + diff --git a/P5/Source/Specs/model.catDescPart.xml b/P5/Source/Specs/model.catDescPart.xml index 17dd6e556d..6a4747f95a 100644 --- a/P5/Source/Specs/model.catDescPart.xml +++ b/P5/Source/Specs/model.catDescPart.xml @@ -1,11 +1,5 @@ - + groups component elements of the TEI header Category Description. @@ -18,4 +12,4 @@ $Id$ catDesc y que aparecen en numerosas ocasiones. raggruppa gli elementi utilizzati all'interno di catDesc e che appaiono più volte - \ No newline at end of file + diff --git a/P5/Source/Specs/model.certLike.xml b/P5/Source/Specs/model.certLike.xml index 560582e476..f8d09571e8 100644 --- a/P5/Source/Specs/model.certLike.xml +++ b/P5/Source/Specs/model.certLike.xml @@ -1,11 +1,5 @@ - + groups elements which are used to indicate uncertainty or diff --git a/P5/Source/Specs/model.choicePart.xml b/P5/Source/Specs/model.choicePart.xml index b2eaf285af..d3a5bee73a 100644 --- a/P5/Source/Specs/model.choicePart.xml +++ b/P5/Source/Specs/model.choicePart.xml @@ -1,11 +1,5 @@ - + groups elements (other than choice itself) which can be used within a @@ -26,4 +20,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.common.xml b/P5/Source/Specs/model.common.xml index 36bb880a66..34e19bdd0f 100644 --- a/P5/Source/Specs/model.common.xml +++ b/P5/Source/Specs/model.common.xml @@ -1,11 +1,5 @@ - + groups common chunk- and inter-level elements. @@ -37,4 +31,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.contentPart.xml b/P5/Source/Specs/model.contentPart.xml index 220a6b424b..0d932b7bd8 100644 --- a/P5/Source/Specs/model.contentPart.xml +++ b/P5/Source/Specs/model.contentPart.xml @@ -1,16 +1,10 @@ - + groups elements which may appear as part of the content element. - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.correspActionPart.xml b/P5/Source/Specs/model.correspActionPart.xml index 23493cafab..0e7af6b5a3 100644 --- a/P5/Source/Specs/model.correspActionPart.xml +++ b/P5/Source/Specs/model.correspActionPart.xml @@ -1,13 +1,7 @@ - + - groups elements which define the + groups elements which define the parts (usually names, dates and places) of one action related to the correspondence. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.correspContextPart.xml b/P5/Source/Specs/model.correspContextPart.xml index 07359944e9..9ba2160ba9 100644 --- a/P5/Source/Specs/model.correspContextPart.xml +++ b/P5/Source/Specs/model.correspContextPart.xml @@ -1,13 +1,7 @@ - + - groups elements which may + groups elements which may appear as part of the correspContext element - \ No newline at end of file + diff --git a/P5/Source/Specs/model.correspDescPart.xml b/P5/Source/Specs/model.correspDescPart.xml index f8027993bf..c0376ca538 100644 --- a/P5/Source/Specs/model.correspDescPart.xml +++ b/P5/Source/Specs/model.correspDescPart.xml @@ -1,13 +1,7 @@ - + - groups together metadata + groups together metadata elements for describing correspondence - \ No newline at end of file + diff --git a/P5/Source/Specs/model.dateLike.xml b/P5/Source/Specs/model.dateLike.xml index 8d8bab23c2..d18c1cc34c 100644 --- a/P5/Source/Specs/model.dateLike.xml +++ b/P5/Source/Specs/model.dateLike.xml @@ -1,11 +1,5 @@ - + groups elements containing temporal expressions. @@ -26,4 +20,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.descLike.xml b/P5/Source/Specs/model.descLike.xml index dca08fbb4a..1a4ee0741f 100644 --- a/P5/Source/Specs/model.descLike.xml +++ b/P5/Source/Specs/model.descLike.xml @@ -1,13 +1,7 @@ - + groups elements which contain a description of their function. regroupe des éléments qui contiennent une description de la fonction d'un élément. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.describedResource.xml b/P5/Source/Specs/model.describedResource.xml index dbb15bdd1f..afa69b0775 100644 --- a/P5/Source/Specs/model.describedResource.xml +++ b/P5/Source/Specs/model.describedResource.xml @@ -1,11 +1,5 @@ - + groups elements which diff --git a/P5/Source/Specs/model.dimLike.xml b/P5/Source/Specs/model.dimLike.xml index 046a0672fb..e96282174a 100644 --- a/P5/Source/Specs/model.dimLike.xml +++ b/P5/Source/Specs/model.dimLike.xml @@ -1,13 +1,7 @@ - + groups elements which describe a measurement forming part of the physical dimensions of some object. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.div1Like.xml b/P5/Source/Specs/model.div1Like.xml index 6a3a2f125e..585f8b988c 100644 --- a/P5/Source/Specs/model.div1Like.xml +++ b/P5/Source/Specs/model.div1Like.xml @@ -1,11 +1,5 @@ - + groups top-level structural divisions. @@ -16,4 +10,4 @@ $Id$ haut. raggruppa partizioni testuali di primo livello agrupa divisiones estructurales de nivel superior. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.div2Like.xml b/P5/Source/Specs/model.div2Like.xml index eb543417ad..97da24858c 100644 --- a/P5/Source/Specs/model.div2Like.xml +++ b/P5/Source/Specs/model.div2Like.xml @@ -1,11 +1,5 @@ - + groups second-level structural divisions. @@ -15,4 +9,4 @@ $Id$ regroupe des divisions structurelles de deuxième niveau. raggruppa partizioni testuali di secondo livello agrupa divisiones estructurales de segundo nivel. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.div3Like.xml b/P5/Source/Specs/model.div3Like.xml index d4d29eb3ee..6195d40172 100644 --- a/P5/Source/Specs/model.div3Like.xml +++ b/P5/Source/Specs/model.div3Like.xml @@ -1,11 +1,5 @@ - + groups third-level structural divisions. @@ -15,4 +9,4 @@ $Id$ regroupe des divisions structurelles de troisième niveau. raggruppa partizioni testuali di terzo livello agrupa divisiones estructurales de tercer nivel - \ No newline at end of file + diff --git a/P5/Source/Specs/model.div4Like.xml b/P5/Source/Specs/model.div4Like.xml index a1d4e399c8..a0e7d85c01 100644 --- a/P5/Source/Specs/model.div4Like.xml +++ b/P5/Source/Specs/model.div4Like.xml @@ -1,11 +1,5 @@ - + groups fourth-level structural divisions. @@ -15,4 +9,4 @@ $Id$ regroupe des divisions structurelles de quatrième niveau. raggruppa partizioni testuali di quarto livello agrupa divisiones estructurales de cuarto nivel - \ No newline at end of file + diff --git a/P5/Source/Specs/model.div5Like.xml b/P5/Source/Specs/model.div5Like.xml index 7095fcd034..e245be663c 100644 --- a/P5/Source/Specs/model.div5Like.xml +++ b/P5/Source/Specs/model.div5Like.xml @@ -1,11 +1,5 @@ - + groups fifth-level structural divisions. @@ -15,4 +9,4 @@ $Id$ regroupe des divisions structurelles de cinquième niveau. raggruppa partizioni testuali di quinto livello agrupa divisiones estructurales de quinto nivel - \ No newline at end of file + diff --git a/P5/Source/Specs/model.div6Like.xml b/P5/Source/Specs/model.div6Like.xml index e15a8f7d91..8123f22f53 100644 --- a/P5/Source/Specs/model.div6Like.xml +++ b/P5/Source/Specs/model.div6Like.xml @@ -1,11 +1,5 @@ - + groups sixth-level structural divisions. @@ -15,4 +9,4 @@ $Id$ regroupe des divisions structurelles de sixième niveau. raggruppa partizioni testuali di sesto livello agrupa divisiones estructurales de sexto nivel - \ No newline at end of file + diff --git a/P5/Source/Specs/model.div7Like.xml b/P5/Source/Specs/model.div7Like.xml index 6d019eab9d..dccf9f4ba5 100644 --- a/P5/Source/Specs/model.div7Like.xml +++ b/P5/Source/Specs/model.div7Like.xml @@ -1,11 +1,5 @@ - + groups seventh-level structural divisions. @@ -15,4 +9,4 @@ $Id$ regroupe des divisions structurelles de septième niveau. raggruppa partizioni testuali di settimo livello agrupa divisiones estructurales de séptimo nivel - \ No newline at end of file + diff --git a/P5/Source/Specs/model.divBottom.xml b/P5/Source/Specs/model.divBottom.xml index ca8ce87e11..de5a700006 100644 --- a/P5/Source/Specs/model.divBottom.xml +++ b/P5/Source/Specs/model.divBottom.xml @@ -1,11 +1,5 @@ - + groups elements appearing at the end of a text @@ -25,4 +19,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.divBottomPart.xml b/P5/Source/Specs/model.divBottomPart.xml index 4d34848811..e71be2ac7b 100644 --- a/P5/Source/Specs/model.divBottomPart.xml +++ b/P5/Source/Specs/model.divBottomPart.xml @@ -1,11 +1,5 @@ - + groups elements which can occur only at the end of a text @@ -22,4 +16,4 @@ fin d'une division de texte. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.divGenLike.xml b/P5/Source/Specs/model.divGenLike.xml index efdb29702c..0d754d4b63 100644 --- a/P5/Source/Specs/model.divGenLike.xml +++ b/P5/Source/Specs/model.divGenLike.xml @@ -1,11 +1,5 @@ - + groups elements used to represent a structural division which is generated rather than @@ -19,4 +13,4 @@ $Id$ partizione testuale generata piuttosto che esplicitamente presente nella fonte agrupa elementos usados para representar divisiones estructurales que se generan explícitamente porque estan presentes en la fuente. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.divLike.xml b/P5/Source/Specs/model.divLike.xml index effe212310..9e6c77b14d 100644 --- a/P5/Source/Specs/model.divLike.xml +++ b/P5/Source/Specs/model.divLike.xml @@ -1,11 +1,5 @@ - + groups elements used to represent un-numbered generic structural divisions. @@ -18,4 +12,4 @@ $Id$ partizioni testuali generiche non numerate agrupa los elementos usados para representar divisiones estructurales recursivamente. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.divPart.spoken.xml b/P5/Source/Specs/model.divPart.spoken.xml index 40919d95fd..078964de97 100644 --- a/P5/Source/Specs/model.divPart.spoken.xml +++ b/P5/Source/Specs/model.divPart.spoken.xml @@ -1,11 +1,5 @@ - + groups elements structurally analogous to paragraphs within spoken texts. @@ -19,21 +13,21 @@ $Id$ comprende gli elementi a livello di componente specifici dei testi parlati - + -

Spoken texts may be structured in many ways; elements in this class are typically larger +

Spoken texts may be structured in many ways; elements in this class are typically larger units such as turns or utterances.

-

Les textes contenant de la parole transcrite peuvent être structurés de plusieurs façons; les +

Les textes contenant de la parole transcrite peuvent être structurés de plusieurs façons; les éléments de cette classe sont habituellement des unités plus grandes, comme des tournures ou des énoncés.

-

発話テキストは、様々に構造化される。当該クラスの要素は、一般に発話 の順番といった大きめの単位とされる。

+

発話テキストは、様々に構造化される。当該クラスの要素は、一般に発話 の順番といった大きめの単位とされる。

- + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.divPart.xml b/P5/Source/Specs/model.divPart.xml index 4bdc6c87b4..9154c7809b 100644 --- a/P5/Source/Specs/model.divPart.xml +++ b/P5/Source/Specs/model.divPart.xml @@ -1,11 +1,5 @@ - + groups paragraph-level elements appearing directly within divisions. @@ -38,4 +32,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.divTop.xml b/P5/Source/Specs/model.divTop.xml index 0403bd0558..fe22ccc74a 100644 --- a/P5/Source/Specs/model.divTop.xml +++ b/P5/Source/Specs/model.divTop.xml @@ -1,11 +1,5 @@ - + groups elements appearing at the beginning of a @@ -21,6 +15,6 @@ $Id$ division de texte. raggruppa elementi che si presentano all'inizio di una partizione testuale - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.divTopPart.xml b/P5/Source/Specs/model.divTopPart.xml index 9ace91dd2a..3b040bd8c9 100644 --- a/P5/Source/Specs/model.divTopPart.xml +++ b/P5/Source/Specs/model.divTopPart.xml @@ -1,11 +1,5 @@ - + groups elements which can occur only at the beginning of a text division. @@ -18,9 +12,9 @@ $Id$ raggruppa elementi che possono presentarsi solo all'inizio di una partizione testuale - + - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.divWrapper.xml b/P5/Source/Specs/model.divWrapper.xml index 5ea3a94050..8e6fad5682 100644 --- a/P5/Source/Specs/model.divWrapper.xml +++ b/P5/Source/Specs/model.divWrapper.xml @@ -1,11 +1,5 @@ - + groups elements which can appear at either top or bottom of a @@ -18,10 +12,10 @@ $Id$ agrupa elementos que pueden aparecer al principio o al final de cualquier elemento de clase de división. raggruppa gli elementi che appaiono all'inizio di una partizione testuale - - + + - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.editorialDeclPart.xml b/P5/Source/Specs/model.editorialDeclPart.xml index 1fa7d8cbfe..fd2cf66dcf 100644 --- a/P5/Source/Specs/model.editorialDeclPart.xml +++ b/P5/Source/Specs/model.editorialDeclPart.xml @@ -1,18 +1,11 @@ - + groups elements which may be used inside editorialDecl and appear multiple times. regroupe des éléments qui peuvent être employés dans l'élément editorialDecl et souvent à de nombreuses reprises. - - editorialDecl 내부에 사용되어 여러 번 출현될 수 있는 요소들을 모아 + editorialDecl 내부에 사용되어 여러 번 출현될 수 있는 요소들을 모아 놓는다. 匯集可在editorialDecl中使用並且可多次出現的元素 要素editorialDecl中で使われ、複数回出現可能な要素をまとめる。 @@ -22,4 +15,4 @@ $Id$ editorialDecl (declaración editorial) y que aparecen en diversas ocasiones. raggruppa gli elementi utilizzati all'interno di editorialDecl e che appaiono più volte. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.egLike.xml b/P5/Source/Specs/model.egLike.xml index 71e612dc95..ddfdbf1c7d 100644 --- a/P5/Source/Specs/model.egLike.xml +++ b/P5/Source/Specs/model.egLike.xml @@ -1,11 +1,5 @@ - + groups elements containing examples or illustrations. @@ -17,10 +11,10 @@ $Id$ raggruppa elementi che contengono esempi o illustrazioni agrupa elementos que contienen ejemplos. - - + + - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.emphLike.xml b/P5/Source/Specs/model.emphLike.xml index d63c0f715a..6f7479e529 100644 --- a/P5/Source/Specs/model.emphLike.xml +++ b/P5/Source/Specs/model.emphLike.xml @@ -1,11 +1,5 @@ - + groups phrase-level elements which are typographically @@ -18,10 +12,10 @@ $Id$ raggruppa elementi a livello di sintagma tipograficamente distinti e ai quali è attribuibile una funzione specifica agrupa elementos sintagmáticos semánticos. - - + + - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.encodingDescPart.xml b/P5/Source/Specs/model.encodingDescPart.xml index 35a4917274..bf68e14341 100644 --- a/P5/Source/Specs/model.encodingDescPart.xml +++ b/P5/Source/Specs/model.encodingDescPart.xml @@ -1,19 +1,12 @@ - + groups elements which may be used inside encodingDesc and appear multiple times. regroupe des éléments qui peuvent apparaître plusieurs fois dans l'élément encodingDesc. - - encodingDesc 내부에 사용되어 여러 번 출현될 수 있는 요소들을 모아 놓는다. + encodingDesc 내부에 사용되어 여러 번 출현될 수 있는 요소들을 모아 놓는다. 匯集可在encodingDesc中使用並且可多次出現的元素 要素encodingDesc内で使われ、複数回出現可能な要素をまとめる。 umfasst Elemente, die innerhalb des encodingDesc-Elements verwendet @@ -22,4 +15,4 @@ $Id$ encodingDesc (Descripción de la codificación) y que aparecen en diversas ocasiones. raggruppa gli elementi utilizzati all'interno di encodingDesc e che appaiono più volte. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.entryLike.xml b/P5/Source/Specs/model.entryLike.xml index 9a34dc85a1..8bff954534 100644 --- a/P5/Source/Specs/model.entryLike.xml +++ b/P5/Source/Specs/model.entryLike.xml @@ -1,11 +1,5 @@ - + groups elements structurally analogous to paragraphs within dictionaries. @@ -26,4 +20,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.entryPart.top.xml b/P5/Source/Specs/model.entryPart.top.xml index 2d9463cec2..ba7faa7951 100644 --- a/P5/Source/Specs/model.entryPart.top.xml +++ b/P5/Source/Specs/model.entryPart.top.xml @@ -1,11 +1,5 @@ - + groups high level elements within a structured dictionary entry @@ -40,4 +34,4 @@ subdivision, for example a particular sense, homonym, etc. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.entryPart.xml b/P5/Source/Specs/model.entryPart.xml index 3e21a2fcdd..d34d985787 100644 --- a/P5/Source/Specs/model.entryPart.xml +++ b/P5/Source/Specs/model.entryPart.xml @@ -1,11 +1,5 @@ - + groups non-morphological elements appearing within a dictionary entry. @@ -17,6 +11,6 @@ niveau dans une entrée de dictionnaire. raggruppa tutti gli elementi specificatamente definiti per i dizionari. agrupa todos los elementos definidos específicamente para diccionarios. - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.eventLike.xml b/P5/Source/Specs/model.eventLike.xml index 18c62b330a..9db272db0e 100644 --- a/P5/Source/Specs/model.eventLike.xml +++ b/P5/Source/Specs/model.eventLike.xml @@ -1,11 +1,5 @@ - + groups elements which describe events. @@ -13,4 +7,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.featureVal.complex.xml b/P5/Source/Specs/model.featureVal.complex.xml index 05ee1f274f..e3ce74a171 100644 --- a/P5/Source/Specs/model.featureVal.complex.xml +++ b/P5/Source/Specs/model.featureVal.complex.xml @@ -1,11 +1,5 @@ - + groups elements which express complex feature values in feature @@ -18,6 +12,6 @@ traits complexes dans des structures de traits raggruppa elementi che esprimono valori di tratti complessi in strutture di tratti agrupa elementos que exprimen valores de rasgos complejos en estructuras de rasgos. - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.featureVal.single.xml b/P5/Source/Specs/model.featureVal.single.xml index 05e5a2df70..139a90fedf 100644 --- a/P5/Source/Specs/model.featureVal.single.xml +++ b/P5/Source/Specs/model.featureVal.single.xml @@ -1,11 +1,5 @@ - + group elements used to represent atomic feature values in feature structures. @@ -17,6 +11,6 @@ valeurs de traits atomiques dans des structures de traits raggruppa elementi utilizzati per descrivere valori di tratti atomici in strutture di tratti agrupa elementos utilizados para describir valores de rasgos aislados en estructuras de rasgos. - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.featureVal.xml b/P5/Source/Specs/model.featureVal.xml index c36cc9f01e..8e8a61e30c 100644 --- a/P5/Source/Specs/model.featureVal.xml +++ b/P5/Source/Specs/model.featureVal.xml @@ -1,11 +1,5 @@ - + groups elements which represent feature values in feature structures. @@ -18,4 +12,4 @@ $Id$ rasgos en estructuras de rasgos raggruppa tutti gli elementi che rappresentano valori di tratti in strutture di tratti - \ No newline at end of file + diff --git a/P5/Source/Specs/model.formPart.xml b/P5/Source/Specs/model.formPart.xml index eb3cda22af..0eb55a8802 100644 --- a/P5/Source/Specs/model.formPart.xml +++ b/P5/Source/Specs/model.formPart.xml @@ -1,11 +1,5 @@ - + groups elements allowed within a form element in a dictionary. @@ -20,8 +14,7 @@ $Id$ all'inerno di un elemento form - - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.frontPart.drama.xml b/P5/Source/Specs/model.frontPart.drama.xml index fa17334878..1194dfe63e 100644 --- a/P5/Source/Specs/model.frontPart.drama.xml +++ b/P5/Source/Specs/model.frontPart.drama.xml @@ -1,11 +1,5 @@ - + groups elements which appear at the level of divisions within front or back matter of @@ -21,9 +15,9 @@ $Id$ testuali all'interno del peritesto iniziale o del peritesto finale solo in testi di tipo teatrale - + - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.frontPart.xml b/P5/Source/Specs/model.frontPart.xml index dd0c66cae9..fd29fcf300 100644 --- a/P5/Source/Specs/model.frontPart.xml +++ b/P5/Source/Specs/model.frontPart.xml @@ -1,11 +1,5 @@ - + groups elements which appear at the level of divisions within front or back matter. @@ -20,6 +14,6 @@ $Id$ raggruppa gli elementi che appaiono a livello di partizioni testuali all'interno del peritesto iniziale o finale - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.fsdDeclPart.xml b/P5/Source/Specs/model.fsdDeclPart.xml index a4d3e9224d..95f867f508 100644 --- a/P5/Source/Specs/model.fsdDeclPart.xml +++ b/P5/Source/Specs/model.fsdDeclPart.xml @@ -1,9 +1,5 @@ - + groups elements which can occur as direct children of fsdDecl. diff --git a/P5/Source/Specs/model.gLike.xml b/P5/Source/Specs/model.gLike.xml index 4f5b02e7a5..b0a97b378d 100644 --- a/P5/Source/Specs/model.gLike.xml +++ b/P5/Source/Specs/model.gLike.xml @@ -1,11 +1,5 @@ - + groups elements used to represent individual non-Unicode characters or glyphs. diff --git a/P5/Source/Specs/model.global.edit.xml b/P5/Source/Specs/model.global.edit.xml index d2e8630a26..81ee4f8a72 100644 --- a/P5/Source/Specs/model.global.edit.xml +++ b/P5/Source/Specs/model.global.edit.xml @@ -1,11 +1,5 @@ - + groups globally available elements which perform a specifically editorial function. @@ -21,9 +15,9 @@ $Id$ specifiche, per esempio l'indicazione dell'inizio di una porzione di testo aggiunto, rimosso o mancante nell'originale - + - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.global.meta.xml b/P5/Source/Specs/model.global.meta.xml index a6fcad2972..59a063ad4b 100644 --- a/P5/Source/Specs/model.global.meta.xml +++ b/P5/Source/Specs/model.global.meta.xml @@ -1,11 +1,5 @@ - + groups globally available elements which describe the status of other elements. @@ -57,4 +51,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.global.spoken.xml b/P5/Source/Specs/model.global.spoken.xml index 5cc7a505a3..8e8b82e20f 100644 --- a/P5/Source/Specs/model.global.spoken.xml +++ b/P5/Source/Specs/model.global.spoken.xml @@ -1,11 +1,5 @@ - + groups elements @@ -38,4 +32,4 @@ généralement dans des textes oraux - \ No newline at end of file + diff --git a/P5/Source/Specs/model.global.xml b/P5/Source/Specs/model.global.xml index d172ad3b9d..092cbf47d2 100644 --- a/P5/Source/Specs/model.global.xml +++ b/P5/Source/Specs/model.global.xml @@ -1,11 +1,5 @@ - + groups elements which may appear at any point within a TEI text. @@ -21,6 +15,6 @@ $Id$ - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.gramPart.xml b/P5/Source/Specs/model.gramPart.xml index 889af593de..17add2ce10 100644 --- a/P5/Source/Specs/model.gramPart.xml +++ b/P5/Source/Specs/model.gramPart.xml @@ -1,11 +1,5 @@ - + groups elements allowed within a gramGrp element in a dictionary. @@ -19,9 +13,9 @@ $Id$ in un dizionario, raggruppa quegli elementi ammessi all'interno di un elemento gramGrp. - + - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.graphicLike.xml b/P5/Source/Specs/model.graphicLike.xml index 8273497390..96ed3689eb 100644 --- a/P5/Source/Specs/model.graphicLike.xml +++ b/P5/Source/Specs/model.graphicLike.xml @@ -1,11 +1,5 @@ - + groups elements containing images, formulae, and @@ -18,9 +12,9 @@ $Id$ agrupa elementos que contienen imágenes, fórmulas u objetos similares. raggruppa elementi che contengono immagini, formule, esempi, e oggetti simili - + - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.headLike.xml b/P5/Source/Specs/model.headLike.xml index b9afd6f9ed..7d674f1f4f 100644 --- a/P5/Source/Specs/model.headLike.xml +++ b/P5/Source/Specs/model.headLike.xml @@ -1,11 +1,5 @@ - + groups elements used to provide a title or heading at the start of a text @@ -17,6 +11,6 @@ $Id$ un intitulé au début d'une division de texte raggruppa elementi utilizzati per fornire un titolo all'inizio di una partizione testuale - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.hiLike.xml b/P5/Source/Specs/model.hiLike.xml index 67c6ee0cc5..bc91e28774 100644 --- a/P5/Source/Specs/model.hiLike.xml +++ b/P5/Source/Specs/model.hiLike.xml @@ -1,11 +1,5 @@ - + groups phrase-level elements which are typographically distinct but to which no specific @@ -20,11 +14,11 @@ $Id$ raggruppa elementi a livello sintagmatico relativi a evidenziatura - - - + + + - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.highlighted.xml b/P5/Source/Specs/model.highlighted.xml index 4b78cc5422..ddaee0989c 100644 --- a/P5/Source/Specs/model.highlighted.xml +++ b/P5/Source/Specs/model.highlighted.xml @@ -1,11 +1,5 @@ - + groups phrase-level elements which are typographically distinct. @@ -19,9 +13,9 @@ $Id$ agrupa elementos de nivel sintagmático relativos al énfasis. - + - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.identEquiv.xml b/P5/Source/Specs/model.identEquiv.xml index ba4dcff36d..8b84fe821f 100644 --- a/P5/Source/Specs/model.identEquiv.xml +++ b/P5/Source/Specs/model.identEquiv.xml @@ -1,11 +1,5 @@ - + groups elements which provide an equivalent value to the identity of their parent element, either as a formal construct or in natural language. diff --git a/P5/Source/Specs/model.identSynonyms.xml b/P5/Source/Specs/model.identSynonyms.xml index c3b8d13d06..4a2de1b59d 100644 --- a/P5/Source/Specs/model.identSynonyms.xml +++ b/P5/Source/Specs/model.identSynonyms.xml @@ -1,11 +1,5 @@ - + groups elements which provide an explanation, equivalency, or alternative name for a markup construct. diff --git a/P5/Source/Specs/model.imprintPart.xml b/P5/Source/Specs/model.imprintPart.xml index ad0df3eae6..eb3dad5612 100644 --- a/P5/Source/Specs/model.imprintPart.xml +++ b/P5/Source/Specs/model.imprintPart.xml @@ -1,11 +1,5 @@ - + groups the bibliographic elements which occur inside imprints. @@ -19,9 +13,9 @@ $Id$ raggruppa gli elementi bibliografici che appaiono all'interno delle sigle editoriali - + - + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.inter.xml b/P5/Source/Specs/model.inter.xml index 18aaa6b9a6..41e1e2f3e1 100644 --- a/P5/Source/Specs/model.inter.xml +++ b/P5/Source/Specs/model.inter.xml @@ -1,11 +1,5 @@ - + groups elements which can appear either within or between paragraph-like elements. diff --git a/P5/Source/Specs/model.lLike.xml b/P5/Source/Specs/model.lLike.xml index eedc50e6c8..c401f6e030 100644 --- a/P5/Source/Specs/model.lLike.xml +++ b/P5/Source/Specs/model.lLike.xml @@ -1,11 +1,5 @@ - + groups elements representing metrical components such as verse lines. @@ -20,4 +14,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.lPart.xml b/P5/Source/Specs/model.lPart.xml index 74209d799e..1531d0f019 100644 --- a/P5/Source/Specs/model.lPart.xml +++ b/P5/Source/Specs/model.lPart.xml @@ -1,11 +1,5 @@ - + groups phrase-level elements which may appear within verse only. @@ -24,4 +18,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.labelLike.xml b/P5/Source/Specs/model.labelLike.xml index 8405c94f18..d91c8cefa1 100644 --- a/P5/Source/Specs/model.labelLike.xml +++ b/P5/Source/Specs/model.labelLike.xml @@ -1,11 +1,5 @@ - + groups elements used to gloss or explain other parts of a document. @@ -18,4 +12,4 @@ expliquer d'autres parties d'un document. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.lexicalRefinement.xml b/P5/Source/Specs/model.lexicalRefinement.xml index 73f14455e8..e1e263569a 100644 --- a/P5/Source/Specs/model.lexicalRefinement.xml +++ b/P5/Source/Specs/model.lexicalRefinement.xml @@ -1,11 +1,5 @@ - + @@ -14,4 +8,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.limitedPhrase.xml b/P5/Source/Specs/model.limitedPhrase.xml index c959b1eac7..3e99ebe7bc 100644 --- a/P5/Source/Specs/model.limitedPhrase.xml +++ b/P5/Source/Specs/model.limitedPhrase.xml @@ -1,11 +1,5 @@ - + groups phrase-level elements excluding those elements primarily intended for transcription @@ -22,4 +16,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.linePart.xml b/P5/Source/Specs/model.linePart.xml index 7e0e2027c3..bc1a8fee55 100644 --- a/P5/Source/Specs/model.linePart.xml +++ b/P5/Source/Specs/model.linePart.xml @@ -1,15 +1,9 @@ - + groups transcriptional elements which appear within lines or zones of a source-oriented transcription within a sourceDoc element. regroupe des éléments qui peuvent figurer dans les zones d'une transcription orientée source dans un élément sourceDoc. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.listLike.xml b/P5/Source/Specs/model.listLike.xml index ce84746b4d..f25e9772af 100644 --- a/P5/Source/Specs/model.listLike.xml +++ b/P5/Source/Specs/model.listLike.xml @@ -1,11 +1,5 @@ - + groups list-like elements. @@ -23,4 +17,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.measureLike.xml b/P5/Source/Specs/model.measureLike.xml index fdfcdd07a4..40ce945c61 100644 --- a/P5/Source/Specs/model.measureLike.xml +++ b/P5/Source/Specs/model.measureLike.xml @@ -1,11 +1,5 @@ - + groups elements which denote a number, a quantity, a measurement, or similar piece of text @@ -25,4 +19,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.milestoneLike.xml b/P5/Source/Specs/model.milestoneLike.xml index ed1fc5d87e..b59b6d2f02 100644 --- a/P5/Source/Specs/model.milestoneLike.xml +++ b/P5/Source/Specs/model.milestoneLike.xml @@ -1,11 +1,5 @@ - + groups milestone-style @@ -25,4 +19,4 @@ elements used to represent reference systems. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.morphLike.xml b/P5/Source/Specs/model.morphLike.xml index 1d7b0a2377..e8622a3d95 100644 --- a/P5/Source/Specs/model.morphLike.xml +++ b/P5/Source/Specs/model.morphLike.xml @@ -1,11 +1,5 @@ - + groups elements which provide morphological information within a dictionary entry. @@ -24,4 +18,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.msItemPart.xml b/P5/Source/Specs/model.msItemPart.xml index 21afd6bf93..5bc28fb20c 100644 --- a/P5/Source/Specs/model.msItemPart.xml +++ b/P5/Source/Specs/model.msItemPart.xml @@ -1,11 +1,5 @@ - + groups elements which can appear within a manuscript item description. @@ -18,4 +12,4 @@ $Id$ descripción de un manuscrito. classe di elementi che appaiono all'interno della descrizione di un manoscritto - \ No newline at end of file + diff --git a/P5/Source/Specs/model.msQuoteLike.xml b/P5/Source/Specs/model.msQuoteLike.xml index b3405d23b4..50319c895b 100644 --- a/P5/Source/Specs/model.msQuoteLike.xml +++ b/P5/Source/Specs/model.msQuoteLike.xml @@ -1,11 +1,5 @@ - + groups elements which represent passages such as titles quoted from a manuscript as a part @@ -15,4 +9,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.nameLike.agent.xml b/P5/Source/Specs/model.nameLike.agent.xml index 0a24434fc2..843fd2af8d 100644 --- a/P5/Source/Specs/model.nameLike.agent.xml +++ b/P5/Source/Specs/model.nameLike.agent.xml @@ -1,11 +1,5 @@ - + groups elements which contain names of individuals @@ -40,4 +34,4 @@ or corporate bodies. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.nameLike.xml b/P5/Source/Specs/model.nameLike.xml index 3682f1fc5c..036039d9f7 100644 --- a/P5/Source/Specs/model.nameLike.xml +++ b/P5/Source/Specs/model.nameLike.xml @@ -1,11 +1,5 @@ - + groups elements which name or refer to a person, place, or organization. @@ -38,4 +32,4 @@ $Id$

日付欄、住所情報、責任表示等に現れる、名前を示す要素の親集合。

- \ No newline at end of file + diff --git a/P5/Source/Specs/model.noteLike.xml b/P5/Source/Specs/model.noteLike.xml index 3b04a4a961..499149cef9 100644 --- a/P5/Source/Specs/model.noteLike.xml +++ b/P5/Source/Specs/model.noteLike.xml @@ -1,11 +1,5 @@ - + groups globally-available note-like elements. @@ -24,4 +18,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.objectLike.xml b/P5/Source/Specs/model.objectLike.xml index 170ba0f896..5fd74a24da 100644 --- a/P5/Source/Specs/model.objectLike.xml +++ b/P5/Source/Specs/model.objectLike.xml @@ -1,10 +1,6 @@ - + + + groups elements which describe objects. diff --git a/P5/Source/Specs/model.oddDecl.xml b/P5/Source/Specs/model.oddDecl.xml index fcde75c52a..dc5d64ff23 100644 --- a/P5/Source/Specs/model.oddDecl.xml +++ b/P5/Source/Specs/model.oddDecl.xml @@ -1,11 +1,5 @@ - + groups elements which generate declarations in some markup language in ODD documents. @@ -22,4 +16,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.oddRef.xml b/P5/Source/Specs/model.oddRef.xml index c495deef4b..7809472c80 100644 --- a/P5/Source/Specs/model.oddRef.xml +++ b/P5/Source/Specs/model.oddRef.xml @@ -1,11 +1,5 @@ - + groups elements which reference declarations in some markup language in ODD documents. @@ -18,4 +12,4 @@ $Id$ un lenguaje dado de codificación en documentos aislados. raggruppa elementi che fanno riferimento a dichiarazioni in un dato linguaggio di codifica in documenti isolati - \ No newline at end of file + diff --git a/P5/Source/Specs/model.offsetLike.xml b/P5/Source/Specs/model.offsetLike.xml index e669c6e819..f689f92480 100644 --- a/P5/Source/Specs/model.offsetLike.xml +++ b/P5/Source/Specs/model.offsetLike.xml @@ -1,11 +1,5 @@ - + groups elements which can appear only as part of a place name. @@ -22,4 +16,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.orgPart.xml b/P5/Source/Specs/model.orgPart.xml index 04bce9960c..008f892ff5 100644 --- a/P5/Source/Specs/model.orgPart.xml +++ b/P5/Source/Specs/model.orgPart.xml @@ -1,13 +1,7 @@ - + groups elements which form part of the description of an organization. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.orgStateLike.xml b/P5/Source/Specs/model.orgStateLike.xml index 2c83dd4173..abc042303f 100644 --- a/P5/Source/Specs/model.orgStateLike.xml +++ b/P5/Source/Specs/model.orgStateLike.xml @@ -1,11 +1,5 @@ - + groups elements describing changeable characteristics of an organization which have a @@ -17,4 +11,4 @@ $Id$ regroupe des éléments qui décrivent des caractéristiques variables et définies dans le temps d'une organisation. raggruppa elementi che descrivono caratteristiche mutevoli di un'organizzazione che hanno una durata definita - \ No newline at end of file + diff --git a/P5/Source/Specs/model.pLike.front.xml b/P5/Source/Specs/model.pLike.front.xml index 39dd6f603b..8a314643ea 100644 --- a/P5/Source/Specs/model.pLike.front.xml +++ b/P5/Source/Specs/model.pLike.front.xml @@ -1,11 +1,5 @@ - + groups paragraph-like elements which can occur as direct constituents of front matter. @@ -21,4 +15,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.pLike.xml b/P5/Source/Specs/model.pLike.xml index 75995b415c..150d6609ee 100644 --- a/P5/Source/Specs/model.pLike.xml +++ b/P5/Source/Specs/model.pLike.xml @@ -1,11 +1,5 @@ - + groups paragraph-like elements. @@ -21,4 +15,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.pPart.data.xml b/P5/Source/Specs/model.pPart.data.xml index c85b685050..44b3487677 100644 --- a/P5/Source/Specs/model.pPart.data.xml +++ b/P5/Source/Specs/model.pPart.data.xml @@ -1,11 +1,5 @@ - + groups phrase-level elements containing names, dates, numbers, measures, and similar data. @@ -25,4 +19,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.pPart.edit.xml b/P5/Source/Specs/model.pPart.edit.xml index 0242090461..2374c8ab08 100644 --- a/P5/Source/Specs/model.pPart.edit.xml +++ b/P5/Source/Specs/model.pPart.edit.xml @@ -1,11 +1,5 @@ - + groups phrase-level elements for simple editorial correction and transcription. @@ -24,4 +18,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.pPart.editorial.xml b/P5/Source/Specs/model.pPart.editorial.xml index a1d119dbe4..1d17469a74 100644 --- a/P5/Source/Specs/model.pPart.editorial.xml +++ b/P5/Source/Specs/model.pPart.editorial.xml @@ -1,11 +1,5 @@ - + groups phrase-level elements for simple editorial interventions that may be useful both @@ -26,4 +20,4 @@ in transcribing and in authoring. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.pPart.msdesc.xml b/P5/Source/Specs/model.pPart.msdesc.xml index 608aaa0f94..753cbe98cd 100644 --- a/P5/Source/Specs/model.pPart.msdesc.xml +++ b/P5/Source/Specs/model.pPart.msdesc.xml @@ -1,11 +1,5 @@ - + groups phrase-level elements used in manuscript description. @@ -25,4 +19,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.pPart.transcriptional.xml b/P5/Source/Specs/model.pPart.transcriptional.xml index 2ae2eb9b2a..d8f08a4710 100644 --- a/P5/Source/Specs/model.pPart.transcriptional.xml +++ b/P5/Source/Specs/model.pPart.transcriptional.xml @@ -1,11 +1,5 @@ - + groups phrase-level elements used for editorial transcription of pre-existing source @@ -20,10 +14,11 @@ $Id$ agrupa solo elementos sintagmáticos utilizados para simples correcciones y transcripciones editoriales que no parecen ser útiles para la autoría. - + + - \ No newline at end of file + diff --git a/P5/Source/Specs/model.paraPart.xml b/P5/Source/Specs/model.paraPart.xml index 7ea160c1d1..dc92bdc5af 100644 --- a/P5/Source/Specs/model.paraPart.xml +++ b/P5/Source/Specs/model.paraPart.xml @@ -1,11 +1,5 @@ - + groups elements that may appear in paragraphs and similar elements diff --git a/P5/Source/Specs/model.persNamePart.xml b/P5/Source/Specs/model.persNamePart.xml index 58cea70614..bd252726e0 100644 --- a/P5/Source/Specs/model.persNamePart.xml +++ b/P5/Source/Specs/model.persNamePart.xml @@ -1,11 +1,5 @@ - + groups elements which form part of a personal name. @@ -24,4 +18,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.persStateLike.xml b/P5/Source/Specs/model.persStateLike.xml index 97814c8636..bafedaac57 100644 --- a/P5/Source/Specs/model.persStateLike.xml +++ b/P5/Source/Specs/model.persStateLike.xml @@ -1,11 +1,5 @@ - + groups elements describing changeable characteristics of a person which have a definite @@ -42,4 +36,4 @@ $Id$

当該個人の特性は、自らの行動などによる結果である。

- \ No newline at end of file + diff --git a/P5/Source/Specs/model.personLike.xml b/P5/Source/Specs/model.personLike.xml index e063f11388..81c2a2cb76 100644 --- a/P5/Source/Specs/model.personLike.xml +++ b/P5/Source/Specs/model.personLike.xml @@ -1,11 +1,5 @@ - + groups elements which provide information about people and their relationships. @@ -23,4 +17,4 @@ $Id$ populated unless the namesdates module is included in a schema.

--> - \ No newline at end of file + diff --git a/P5/Source/Specs/model.personPart.xml b/P5/Source/Specs/model.personPart.xml index baad6b7d18..88a45692fd 100644 --- a/P5/Source/Specs/model.personPart.xml +++ b/P5/Source/Specs/model.personPart.xml @@ -1,11 +1,5 @@ - + groups elements which form part of the description of a person. @@ -23,4 +17,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.phrase.xml b/P5/Source/Specs/model.phrase.xml index baf3ba6770..6d27b45d01 100644 --- a/P5/Source/Specs/model.phrase.xml +++ b/P5/Source/Specs/model.phrase.xml @@ -1,11 +1,5 @@ - + groups elements which can occur at the level of individual words or phrases. @@ -38,4 +32,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.phrase.xml.xml b/P5/Source/Specs/model.phrase.xml.xml index f290a08970..7cb62d4f4a 100644 --- a/P5/Source/Specs/model.phrase.xml.xml +++ b/P5/Source/Specs/model.phrase.xml.xml @@ -1,11 +1,5 @@ - + groups phrase-level elements used to encode XML constructs such as element names, attribute @@ -27,4 +21,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.physDescPart.xml b/P5/Source/Specs/model.physDescPart.xml index e180f81ee1..af75ef9769 100644 --- a/P5/Source/Specs/model.physDescPart.xml +++ b/P5/Source/Specs/model.physDescPart.xml @@ -1,11 +1,5 @@ - + @@ -21,4 +15,4 @@ $Id$ elementi descrittivi specifici che costituiscono la descrizione fisica di un manoscritto o di una fonte scritta simile - \ No newline at end of file + diff --git a/P5/Source/Specs/model.placeLike.xml b/P5/Source/Specs/model.placeLike.xml index 02f7ecfa49..666bb9af50 100644 --- a/P5/Source/Specs/model.placeLike.xml +++ b/P5/Source/Specs/model.placeLike.xml @@ -1,11 +1,5 @@ - + groups elements used to provide information about places and their relationships. @@ -16,4 +10,4 @@ $Id$ regroupe des éléments qui donne des informations sur des lieux et leurs relations. raggruppa elementi utilizzati per fornire informazioni relative a luoghi e relazioni corrispondenti - \ No newline at end of file + diff --git a/P5/Source/Specs/model.placeNamePart.xml b/P5/Source/Specs/model.placeNamePart.xml index 1bc882fd3a..4408bf845b 100644 --- a/P5/Source/Specs/model.placeNamePart.xml +++ b/P5/Source/Specs/model.placeNamePart.xml @@ -1,11 +1,5 @@ - + groups elements which form part of a place name. @@ -24,4 +18,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.placeStateLike.xml b/P5/Source/Specs/model.placeStateLike.xml index 364180593e..466ca4844c 100644 --- a/P5/Source/Specs/model.placeStateLike.xml +++ b/P5/Source/Specs/model.placeStateLike.xml @@ -1,11 +1,5 @@ - + groups elements which describe changing states of a place. @@ -19,4 +13,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.profileDescPart.xml b/P5/Source/Specs/model.profileDescPart.xml index cba998ec0f..a1e5af630c 100644 --- a/P5/Source/Specs/model.profileDescPart.xml +++ b/P5/Source/Specs/model.profileDescPart.xml @@ -1,11 +1,5 @@ - + groups elements which may be used inside profileDesc @@ -18,4 +12,4 @@ and appear multiple times. können. agrupa los elementos que pueden ser usados al interno de profileDesc y que aparecen en diversas ocasiones. raggruppa gli elementi utilizzati all'interno di profileDesc e che appaiono più volte. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.ptrLike.form.xml b/P5/Source/Specs/model.ptrLike.form.xml index 86a9143dc7..713b97d60a 100644 --- a/P5/Source/Specs/model.ptrLike.form.xml +++ b/P5/Source/Specs/model.ptrLike.form.xml @@ -1,11 +1,5 @@ - + groups elements used for purposes of location of particular orthographic or pronunciation @@ -25,4 +19,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.ptrLike.xml b/P5/Source/Specs/model.ptrLike.xml index e956afd057..571067c27a 100644 --- a/P5/Source/Specs/model.ptrLike.xml +++ b/P5/Source/Specs/model.ptrLike.xml @@ -1,11 +1,5 @@ - + groups elements used for purposes of location and reference. @@ -26,4 +20,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.publicationStmtPart.agency.xml b/P5/Source/Specs/model.publicationStmtPart.agency.xml index ba75c8a844..b9391b0a94 100644 --- a/P5/Source/Specs/model.publicationStmtPart.agency.xml +++ b/P5/Source/Specs/model.publicationStmtPart.agency.xml @@ -1,11 +1,5 @@ - + groups the child @@ -30,4 +24,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.publicationStmtPart.detail.xml b/P5/Source/Specs/model.publicationStmtPart.detail.xml index 42565d0c80..e84e669598 100644 --- a/P5/Source/Specs/model.publicationStmtPart.detail.xml +++ b/P5/Source/Specs/model.publicationStmtPart.detail.xml @@ -1,11 +1,5 @@ - + groups the agency-specific child elements of the publicationStmt element of the TEI header. @@ -26,4 +20,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.quoteLike.xml b/P5/Source/Specs/model.quoteLike.xml index ad3e6eef43..0301f419c6 100644 --- a/P5/Source/Specs/model.quoteLike.xml +++ b/P5/Source/Specs/model.quoteLike.xml @@ -1,11 +1,5 @@ - + groups elements used to directly contain quotations. @@ -21,4 +15,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.rdgLike.xml b/P5/Source/Specs/model.rdgLike.xml index 560e6c2908..3c8848cd3e 100644 --- a/P5/Source/Specs/model.rdgLike.xml +++ b/P5/Source/Specs/model.rdgLike.xml @@ -1,11 +1,5 @@ - + groups elements which contain a single reading, other than the lemma, within a textual @@ -38,4 +32,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.rdgPart.xml b/P5/Source/Specs/model.rdgPart.xml index aa74a30e71..707824d9ab 100644 --- a/P5/Source/Specs/model.rdgPart.xml +++ b/P5/Source/Specs/model.rdgPart.xml @@ -1,11 +1,5 @@ - + groups elements which mark the beginning or ending of a fragmentary manuscript or other @@ -33,4 +27,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.recordingPart.xml b/P5/Source/Specs/model.recordingPart.xml index 7a38e29433..c3d6193975 100644 --- a/P5/Source/Specs/model.recordingPart.xml +++ b/P5/Source/Specs/model.recordingPart.xml @@ -1,11 +1,5 @@ - + groups elements used to describe details of an audio or video recording. @@ -21,4 +15,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.resource.xml b/P5/Source/Specs/model.resource.xml index 7fcfcf4030..50606a89a0 100644 --- a/P5/Source/Specs/model.resource.xml +++ b/P5/Source/Specs/model.resource.xml @@ -1,11 +1,5 @@ - + groups separate elements diff --git a/P5/Source/Specs/model.respLike.xml b/P5/Source/Specs/model.respLike.xml index 9f265d8104..eb438d30a7 100644 --- a/P5/Source/Specs/model.respLike.xml +++ b/P5/Source/Specs/model.respLike.xml @@ -1,11 +1,5 @@ - + groups elements which are used to indicate intellectual or other significant responsibility, @@ -24,4 +18,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.segLike.xml b/P5/Source/Specs/model.segLike.xml index 6509ebac88..6a94b249a4 100644 --- a/P5/Source/Specs/model.segLike.xml +++ b/P5/Source/Specs/model.segLike.xml @@ -1,11 +1,5 @@ - + groups elements used for arbitrary segmentation. @@ -44,4 +38,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.settingPart.xml b/P5/Source/Specs/model.settingPart.xml index b937ea3e65..82c0d00675 100644 --- a/P5/Source/Specs/model.settingPart.xml +++ b/P5/Source/Specs/model.settingPart.xml @@ -1,11 +1,5 @@ - + groups elements used to describe the setting of a linguistic interaction. @@ -19,4 +13,4 @@ $Id$ elementi utilizzati per descrivere lo scenario di un'interazione linguistica - \ No newline at end of file + diff --git a/P5/Source/Specs/model.sourceDescPart.xml b/P5/Source/Specs/model.sourceDescPart.xml index 97bde75630..f9f91920df 100644 --- a/P5/Source/Specs/model.sourceDescPart.xml +++ b/P5/Source/Specs/model.sourceDescPart.xml @@ -1,11 +1,5 @@ - + groups elements which may be used inside sourceDesc and appear multiple times. @@ -19,4 +13,4 @@ $Id$ sourceDesc (descripción de la fuente) y que aparecen en diversas ocasiones. raggruppa gli elementi utilizzati all'interno di sourceDesc e che appaiono più volte. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.specDescLike.xml b/P5/Source/Specs/model.specDescLike.xml index 8113e35251..fd910a42c5 100644 --- a/P5/Source/Specs/model.specDescLike.xml +++ b/P5/Source/Specs/model.specDescLike.xml @@ -1,11 +1,5 @@ - + groups elements for referring to specification elements. @@ -22,4 +16,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.stageLike.xml b/P5/Source/Specs/model.stageLike.xml index 9d3e15a64f..7d20bd5a97 100644 --- a/P5/Source/Specs/model.stageLike.xml +++ b/P5/Source/Specs/model.stageLike.xml @@ -1,11 +1,5 @@ - + groups elements containing stage directions or similar things defined by the module for @@ -41,4 +35,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.standOffPart.xml b/P5/Source/Specs/model.standOffPart.xml index a13d76c2b5..a018a9339c 100644 --- a/P5/Source/Specs/model.standOffPart.xml +++ b/P5/Source/Specs/model.standOffPart.xml @@ -1,11 +1,5 @@ - + groups elements which may be used as children of standOff. diff --git a/P5/Source/Specs/model.teiHeaderPart.xml b/P5/Source/Specs/model.teiHeaderPart.xml index 0d3d13eb0f..5fbbd99992 100644 --- a/P5/Source/Specs/model.teiHeaderPart.xml +++ b/P5/Source/Specs/model.teiHeaderPart.xml @@ -1,11 +1,5 @@ - + groups high level elements which may appear more than once in a TEI header. @@ -20,4 +14,4 @@ $Id$ teiHeader y aparecen en diversas ocasiones. raggruppa gli elementi utilizzati all'interno di teiHeader e che appaiono più volte. - \ No newline at end of file + diff --git a/P5/Source/Specs/model.textDescPart.xml b/P5/Source/Specs/model.textDescPart.xml index aa17586653..e94f34a657 100644 --- a/P5/Source/Specs/model.textDescPart.xml +++ b/P5/Source/Specs/model.textDescPart.xml @@ -1,11 +1,5 @@ - + @@ -21,4 +15,4 @@ $Id$ elementi utilizzati per categorizzare un testo, per esempio in termini di relativi parametri situazionali - \ No newline at end of file + diff --git a/P5/Source/Specs/model.titlepagePart.xml b/P5/Source/Specs/model.titlepagePart.xml index 47ed12300d..d382cce51e 100644 --- a/P5/Source/Specs/model.titlepagePart.xml +++ b/P5/Source/Specs/model.titlepagePart.xml @@ -1,11 +1,5 @@ - + groups elements which can occur as direct constituents of a title page, such as @@ -28,4 +22,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/model.xml b/P5/Source/Specs/model.xml index 636ebc63f1..e51c072c58 100644 --- a/P5/Source/Specs/model.xml +++ b/P5/Source/Specs/model.xml @@ -1,11 +1,5 @@ - + describes the processing intended for a specified diff --git a/P5/Source/Specs/modelGrp.xml b/P5/Source/Specs/modelGrp.xml index 15f897bb36..d240657212 100644 --- a/P5/Source/Specs/modelGrp.xml +++ b/P5/Source/Specs/modelGrp.xml @@ -1,11 +1,5 @@ - + model group diff --git a/P5/Source/Specs/modelSequence.xml b/P5/Source/Specs/modelSequence.xml index cbd5e51ba6..15ecab4d62 100644 --- a/P5/Source/Specs/modelSequence.xml +++ b/P5/Source/Specs/modelSequence.xml @@ -1,11 +1,5 @@ - + any sequence of model or modelSequence elements which diff --git a/P5/Source/Specs/moduleRef.xml b/P5/Source/Specs/moduleRef.xml index 2c1e52ba10..4389912270 100644 --- a/P5/Source/Specs/moduleRef.xml +++ b/P5/Source/Specs/moduleRef.xml @@ -1,11 +1,5 @@ - + module reference @@ -26,9 +20,7 @@ $Id$ - - - + @@ -43,7 +35,9 @@ Child elements of are only allowed when an external module is being load specifies a default prefix which will be prepended to all patterns from the imported module - + + + @@ -72,12 +66,16 @@ Child elements of are only allowed when an external module is being load supplies a list of the elements which are to be copied from the specified module into the schema being defined. - + + + supplies a list of the elements which are not to be copied from the specified module into the schema being defined. - + + + @@ -86,7 +84,9 @@ specified module into the schema being defined. el nombre de un módulo de TEI le nom d'un module TEI. nome di un modulo TEI - + + + uniform resource locator @@ -98,7 +98,9 @@ specified module into the schema being defined. fait référence à un module non TEI de code RELAX NG par une localisation externe. indica la collocazione esterna di un modulo non TEI che utilizza il codice RELAX NG - + + + @@ -121,7 +123,6 @@ RELAX NG par une localisation externe.

This includes all elements available from the linking module except for the link and linkGrp elements.

 - @@ -146,7 +147,8 @@ processor should signal an error.

online source from which the specification of that module may be read. A URI may alternatively be supplied in the case of a non-TEI module, and this is expected to be written as a RELAX NG schema. -

If the url attribute is used, the content element may also be supplied as +

+

If the url attribute is used, the content element may also be supplied as a child of this element. Its content (which is assumed to be a fragment of RELAX NG code) will be copied along with the content of the resource indicated by the url attribute into the target RELAX NG schema.

@@ -173,4 +175,4 @@ processor should signal an error.

- \ No newline at end of file + diff --git a/P5/Source/Specs/moduleSpec.xml b/P5/Source/Specs/moduleSpec.xml index 9d46eaa7f4..76866bae5a 100644 --- a/P5/Source/Specs/moduleSpec.xml +++ b/P5/Source/Specs/moduleSpec.xml @@ -1,11 +1,5 @@ - + module specification @@ -31,15 +25,15 @@ module, i.e. a named and externally visible group of declarations. - - - - - - - - - + + + + + + + + + diff --git a/P5/Source/Specs/monogr.xml b/P5/Source/Specs/monogr.xml index c7ddd4f8bc..866ddc584c 100644 --- a/P5/Source/Specs/monogr.xml +++ b/P5/Source/Specs/monogr.xml @@ -1,11 +1,5 @@ - + monographic level @@ -34,88 +28,68 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - + - - - - + + + + + + + + + + + - - - + + + + + + - + + + + + + + @@ -179,4 +153,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/mood.xml b/P5/Source/Specs/mood.xml index 304b0145a4..590fe8ceb8 100644 --- a/P5/Source/Specs/mood.xml +++ b/P5/Source/Specs/mood.xml @@ -1,11 +1,5 @@ - + mood @@ -95,4 +89,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/move.xml b/P5/Source/Specs/move.xml index ae6f03d189..3ea356846b 100644 --- a/P5/Source/Specs/move.xml +++ b/P5/Source/Specs/move.xml @@ -1,11 +1,5 @@ - + movement @@ -29,7 +23,9 @@ $Id$ - + + + characterizes the movement, for example as an entrance or exit. @@ -42,7 +38,9 @@ $Id$ une sortie. indica il tipo di movimento, ad esempio come entrata o uscita. - + + + character is entering the stage. @@ -81,7 +79,9 @@ $Id$ 舞台上の動きの方向を示す。 indique la direction d'un mouvement sur scène. specifica la direzione di un movimento in scena. - + + + left @@ -161,7 +161,9 @@ $Id$ desquelles s'est effectué le déplacement décrit. indica la rappresentazione o le rappresentazioni in cui il movimento è stato eseguito così come specificato. - + + + @@ -213,4 +215,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/msContents.xml b/P5/Source/Specs/msContents.xml index 8dca42b0cf..a5f229e2e3 100644 --- a/P5/Source/Specs/msContents.xml +++ b/P5/Source/Specs/msContents.xml @@ -1,11 +1,5 @@ - + manuscript contents @@ -32,25 +26,15 @@ $Id$ - - - + - - - - - - - - - - - - - - - + + + + + + + @@ -245,4 +229,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/msDesc.xml b/P5/Source/Specs/msDesc.xml index f15468cf8c..fa743599d7 100644 --- a/P5/Source/Specs/msDesc.xml +++ b/P5/Source/Specs/msDesc.xml @@ -1,13 +1,7 @@ - + - + manuscript description 원고 기술 @@ -70,9 +64,7 @@ $Id$ $gi][2]" because then an error would be generated for each of the multiple occurences of $gi. --> - + Only one is allowed as a child of . diff --git a/P5/Source/Specs/msFrag.xml b/P5/Source/Specs/msFrag.xml index 683ad8e813..a9560023d4 100644 --- a/P5/Source/Specs/msFrag.xml +++ b/P5/Source/Specs/msFrag.xml @@ -1,28 +1,22 @@ - + - manuscript fragment - - - Fragment einer Handschrift - fragmento del manuscrito - fragment d'un manuscrit - frammento di un manoscritto - contains information about a fragment described in relation to a prior context, typically as a description of a virtual reconstruction of a manuscript or other object whose fragments were catalogued separately - + + Fragment einer Handschrift + fragmento del manuscrito + fragment d'un manuscrit + frammento di un manoscritto + contains information about a fragment described in relation to a prior context, typically as a description of a virtual reconstruction of a manuscript or other object whose fragments were catalogued separately + - contient des informations sur un fragment d'un manuscrit dispersé, aujourd'hui conservé séparément ou incorporé dans un autre manuscrit. - enthält Informationen zu einem Handschriftenfragment einer fragmentierten Handschrift, das heute als Einzeldokument oder eingebunden in eine Handschrift aufbewahrt wird. - - + contient des informations sur un fragment d'un manuscrit dispersé, aujourd'hui conservé séparément ou incorporé dans un autre manuscrit. + enthält Informationen zu einem Handschriftenfragment einer fragmentierten Handschrift, das heute als Einzeldokument oder eingebunden in eine Handschrift aufbewahrt wird. + + diff --git a/P5/Source/Specs/msIdentifier.xml b/P5/Source/Specs/msIdentifier.xml index 6fa7e4a4d2..9da01b8464 100644 --- a/P5/Source/Specs/msIdentifier.xml +++ b/P5/Source/Specs/msIdentifier.xml @@ -1,11 +1,5 @@ - + manuscript identifier @@ -29,7 +23,7 @@ the manuscript or similar object being described. - + diff --git a/P5/Source/Specs/msItem.xml b/P5/Source/Specs/msItem.xml index 6b18d25a95..4238a1da15 100644 --- a/P5/Source/Specs/msItem.xml +++ b/P5/Source/Specs/msItem.xml @@ -1,11 +1,5 @@ - + manuscript item @@ -31,23 +25,17 @@ $Id$ - - - - - - + + + + - - - - - - - - - - + + + + + + @@ -110,4 +98,4 @@ reiþar - \ No newline at end of file + diff --git a/P5/Source/Specs/msItemStruct.xml b/P5/Source/Specs/msItemStruct.xml index 33c554110c..f3c2c52dc3 100644 --- a/P5/Source/Specs/msItemStruct.xml +++ b/P5/Source/Specs/msItemStruct.xml @@ -1,11 +1,5 @@ - + structured manuscript item @@ -32,63 +26,31 @@ $Id$ - - - - - - + + + + - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + - - - - - - + + @@ -142,4 +104,4 @@ DEO GRACIAS AGO. FINITO LABORE ISTO. - \ No newline at end of file + diff --git a/P5/Source/Specs/msName.xml b/P5/Source/Specs/msName.xml index bc60809960..a9cd2878f9 100644 --- a/P5/Source/Specs/msName.xml +++ b/P5/Source/Specs/msName.xml @@ -1,11 +1,5 @@ - + alternative name @@ -56,4 +50,4 @@ nominum, o soprannome - \ No newline at end of file + diff --git a/P5/Source/Specs/msPart.xml b/P5/Source/Specs/msPart.xml index 9399926215..d6c3ce071c 100644 --- a/P5/Source/Specs/msPart.xml +++ b/P5/Source/Specs/msPart.xml @@ -1,18 +1,13 @@ - + manuscript part Handschriftenteil (kodikologische Einheit) 원고 부분 - parte del manuscrito + parte del manuscrito + unité codicologique d'un manuscrit parte di un manoscritto contains information about an originally @@ -96,12 +91,14 @@ $Id$ - ms. 10066-77 ff. 140r-156v + + ms. 10066-77 ff. 140r-156v + Physiologus Latin - + diff --git a/P5/Source/Specs/musicNotation.xml b/P5/Source/Specs/musicNotation.xml index 7a23aa5aed..69fb71a81a 100644 --- a/P5/Source/Specs/musicNotation.xml +++ b/P5/Source/Specs/musicNotation.xml @@ -1,11 +1,5 @@ - + music notation @@ -69,4 +63,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/name.xml b/P5/Source/Specs/name.xml index 13deaf9f82..75ad0df2d5 100644 --- a/P5/Source/Specs/name.xml +++ b/P5/Source/Specs/name.xml @@ -1,10 +1,7 @@ - + + + + name, proper noun 이름, 고유명사 名稱，特定名稱 @@ -19,7 +16,7 @@ contient un nom propre ou un syntagme nominal. contiene un nombre propio o un sintagma nominal contiene un nome proprio o un sintagma nominale. - enthält einen Eigennamen in Form eines Nomens oder einer Nominalphrase. + enthält einen Eigennamen in Form eines Nomens oder einer Nominalphrase. @@ -34,35 +31,35 @@ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -84,10 +81,10 @@ lorsque le module TEI concernant les noms et dates est inclus.

-

TEI名前モジュールが使われる場合には、人々、場所、組織を示す固有名 詞は、それぞれ要素persName、placeName、orgNameを使い示されるかもしれない。

+

TEI名前モジュールが使われる場合には、人々、場所、組織を示す固有名 詞は、それぞれ要素persName、placeName、orgNameを使い示されるかもしれない。

-

+

Eigennamen, die auf Personen, Orte und Organisationen verweisen, können stattdessen auch mit den Elementen persName, placeName oder orgName ausgezeichnet werden, vorausgesetzt, das TEI-Modul namesdates ist inkludiert. @@ -96,4 +93,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/nameLink.xml b/P5/Source/Specs/nameLink.xml index 56dc6a1276..94981e68b5 100644 --- a/P5/Source/Specs/nameLink.xml +++ b/P5/Source/Specs/nameLink.xml @@ -1,11 +1,5 @@ - + name link @@ -76,4 +70,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/namespace.xml b/P5/Source/Specs/namespace.xml index b829366ced..8a05deb278 100644 --- a/P5/Source/Specs/namespace.xml +++ b/P5/Source/Specs/namespace.xml @@ -1,11 +1,5 @@ - + namespace @@ -40,7 +34,9 @@ $Id$ Namensraums an. el nombre formal completo del namespace concerniente. l'intero nome formale del namespace in questione. - + + + diff --git a/P5/Source/Specs/nationality.xml b/P5/Source/Specs/nationality.xml index d588aed471..0116edc9c1 100644 --- a/P5/Source/Specs/nationality.xml +++ b/P5/Source/Specs/nationality.xml @@ -1,10 +1,7 @@ - + + + + nationality nationalité contains an informal description of a person's present or past nationality or citizenship. @@ -29,47 +26,45 @@ $Id$ - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + - + - - - + + + @@ -91,4 +86,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/node.xml b/P5/Source/Specs/node.xml index 43861db564..ec59dd3a99 100644 --- a/P5/Source/Specs/node.xml +++ b/P5/Source/Specs/node.xml @@ -1,11 +1,5 @@ - + node @@ -37,7 +31,9 @@ other analytic element. fournit l'identifiant de l'objet représenté par le nœud ; cet objet peut être une paire nom-valeur ou tout autre élément analytique. proporciona el valor de un nodo, que puede ser una estructura de rasgos u otro elemento de análisis. assegna al nodo un valore, che può essere una struttura di tratti o altro elemento di analisi - + + + provides a type for a node. @@ -47,7 +43,9 @@ other analytic element. indique le type du nœud. define un tipo de nodo. definisce un tipo di nodo - + + + initial node in a transition network @@ -99,7 +97,9 @@ transition. donne les identifiants des nœuds qui précèdent immédiatement le nœud décrit. proporciona los identificadores a los nodos adyacentes al nodo corriente. assegna degli identificatori ai nodi adiacenti al nodo corrente - + + + @@ -130,7 +130,9 @@ node. donne les identifiants des nœuds qui suivent immédiatement le nœud décrit. proporciona los identificadores a los nodos adyacentes al nodo corriente. assegna degli identificatori ai nodi non adiacenti al nodo corrente - + + + @@ -161,7 +163,9 @@ adjacent from the current node. 無向グラフにおける、現行ノードに隣接するノードの識別子を示す。 proporciona los identificadores a los nodos adyacentes al nodo corriente. assegna degli identificatori ai nodi adiacenti e non adiacenti al nodo corrente - + + + @@ -202,7 +206,9 @@ are adjacent from the given node. donne le degré entrant du nœud, c'est-à-dire le nombre de nœuds qui précèdent immédiatement le nœud décrit. indica el grado de entrada del nodo, es decir, el número de los nodos no adyacentes al nodo dado. indica il grado in entrata del nodo, cioè il numero dei nodi non adiacenti al nodo stesso - + + + @@ -229,7 +235,9 @@ are adjacent to the given node. c'est-à-dire le nombre de nœuds qui suivent immédiatement le nœud décrit. indica el grado de salida del nodo, es decir, el número de los nodos no adyacentes al nodo dado. indica il grado in uscita del nodo, cioè il numero dei nodi adiacenti al nodo stesso - + + + @@ -255,7 +263,9 @@ the node is incident. donne le degré du nœud, c'est-à-dire le nombre d'arcs avec lesquels le nœud est lié. define el grado del nodo, es decir, el número de los arcos incidentes al nodo definisce il grado del nodo, cioè il numero degli archi incidenti al nodo - + + + @@ -326,4 +336,4 @@ qu'avec des arcs.

- \ No newline at end of file + diff --git a/P5/Source/Specs/normalization.xml b/P5/Source/Specs/normalization.xml index 42727bba0b..37fe919875 100644 --- a/P5/Source/Specs/normalization.xml +++ b/P5/Source/Specs/normalization.xml @@ -1,11 +1,5 @@ - + normalization @@ -47,7 +41,6 @@ $Id$ --> - indicates the method adopted to indicate normalizations within the text. indique la méthode adoptée pour signaler les @@ -61,7 +54,9 @@ $Id$ normalizaciones al interno del texto. indica il metodo adottato per indicare le normalizzazioni all'interno di un testo. - + + + silent diff --git a/P5/Source/Specs/notatedMusic.xml b/P5/Source/Specs/notatedMusic.xml index 0a2be5e113..ec97eb46dd 100644 --- a/P5/Source/Specs/notatedMusic.xml +++ b/P5/Source/Specs/notatedMusic.xml @@ -1,11 +1,5 @@ - + encodes the presence of music notation in a text @@ -16,13 +10,13 @@ - - - - - - - + + + + + + + @@ -51,4 +45,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/note.xml b/P5/Source/Specs/note.xml index 93a06cd96f..0023004d38 100644 --- a/P5/Source/Specs/note.xml +++ b/P5/Source/Specs/note.xml @@ -1,11 +1,5 @@ - + note @@ -37,7 +31,7 @@

In the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly":

-And yet it is not only + And yet it is not only in the great line of Italian renaissance art, but even in the painterly Malerisch. This word has, in the German, two distinct meanings, one objective, a quality residing in the object, @@ -49,20 +43,16 @@ Dutch genre painters of the seventeenth century that drapery has this psychological significance. - - translation from German to English - Hottinger, Marie Donald Mackie - + translation from German to EnglishHottinger, Marie Donald Mackie

For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header.

 -

Im folgenden Beispiel hat der Übersetzer eine Fußnote mit einer Erklärung des als "painterly" übersetzten Begriffs "Malerisch" bereitgestellt:

- And yet it is not only + And yet it is not only in the great line of Italian renaissance art, but even in the painterly Malerisch. This word has, in the German, two distinct meanings, one objective, a quality residing in the object, @@ -75,15 +65,11 @@ psychological significance. - - translation from German to English - Hottinger, Marie Donald Mackie - + translation from German to EnglishHottinger, Marie Donald Mackie

Damit dieses Beispiel valide ist, muss der Code MDMH-1 an anderer Stelle definiert werden, beispielsweise durch die Angabe der Verantwortlichkeit im respStmt-Element des zugehörigen TEI-Headers.

- @@ -136,7 +122,7 @@ psychological significance. mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to Judah's children; cf. above, nn. 111 and 54. is well known from Geniza documents published by Jacob - Mann. + Mann.

Cependant, si les notes sont ordonnées et numérotées et qu’on veuille reconstruire automatiquement leur numérotation par un traitement informatique, il est inutile d’enregistrer le @@ -148,4 +134,4 @@ psychological significance. - \ No newline at end of file + diff --git a/P5/Source/Specs/noteGrp.xml b/P5/Source/Specs/noteGrp.xml index a8d179bc64..3d3582f37e 100644 --- a/P5/Source/Specs/noteGrp.xml +++ b/P5/Source/Specs/noteGrp.xml @@ -1,10 +1,7 @@ - + + + + note group contains a group of notes @@ -21,11 +18,11 @@ - - - - - + + + + + @@ -35,20 +32,17 @@

(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses necnon episcopum in duplicibus Quatuortemporibus - - Quatuor Tempora, so called dry fast days (Wednesday, Friday, and Saturday) + Quatuor Tempora, so called dry fast days (Wednesday, Friday, and Saturday) falling on each of the quarters of the year. In the first quarter they were called Cinerum (following Ash Wednesday), second Spiritus (following Pentecost), third Crucis (after the Exaltation of the Holy Cross, September 14th), and Luciae in the fourth (after the feast of St. Lucia, December 13th). - - Quatuor Tempora, tzw. Suche dni postne (środa, piątek i sobota) + Quatuor Tempora, tzw. Suche dni postne (środa, piątek i sobota) przypadające cztery razy w roku. W pierwszym kwartale zwały się Cinerum (po Popielcu), w drugim Spiritus (po Zielonych Świętach), w trzecim Crucis (po święcie Podwyższenia Krzyża 14 września), w czwartym Luciae (po dniu św. Łucji 13 grudnia). - - + totaliter expediui.

diff --git a/P5/Source/Specs/notesStmt.xml b/P5/Source/Specs/notesStmt.xml index 33e32507d4..ab1c3914a6 100644 --- a/P5/Source/Specs/notesStmt.xml +++ b/P5/Source/Specs/notesStmt.xml @@ -1,18 +1,12 @@ - + notes statement mention de notes 주석 진술 附註陳述 - Zusätzliche Anmerkungen + Zusätzliche Anmerkungen declaración de notas dichiarazione sulle note collects together any notes providing information about a text additional to that recorded @@ -24,7 +18,7 @@ $Id$ 놓는다. 收集其他部分的書目描述中所未記載的任何文件相關附註。 当該書誌情報の他の場所に記録されているテキストに関する注釈をまとめる。 - fasst Anmerkungen zu einem Text zusammen, zusätzlich zu jenen Informationen, die in anderen Teilen der bibliografischen Beschreibung bereits festgehalten sind. + fasst Anmerkungen zu einem Text zusammen, zusätzlich zu jenen Informationen, die in anderen Teilen der bibliografischen Beschreibung bereits festgehalten sind. agrupa algunas notas que proporcionan información sobre un texto adicional referido en otras partes de la descripción bibliográfica. raggruppa tutte le note sul testo in aggiunta a quelle @@ -33,12 +27,10 @@ $Id$ - - - - - - + + + + @@ -79,10 +71,10 @@ $Id$

種類が異なる情報は、同じ注釈としてまとめるべきではない。

-

Informationen unterschiedlicher Art sollten nicht in einer gemeinsamen Anmerkung gruppiert werden.

+

Informationen unterschiedlicher Art sollten nicht in einer gemeinsamen Anmerkung gruppiert werden.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/num.xml b/P5/Source/Specs/num.xml index 20483d389a..f5d31a744d 100644 --- a/P5/Source/Specs/num.xml +++ b/P5/Source/Specs/num.xml @@ -1,11 +1,5 @@ - + number @@ -42,7 +36,9 @@ indica el tipo de valor numérico. indica il tipo di valore numerico bestimmt die Art des numerischen Wertes. - + + + absolute number, e.g. 21, 21.5 @@ -62,7 +58,7 @@ 序数。例えば、21番など。 nombre ordinal, par exemple 21ème numero ordinale, ad esempio 21° - Ordinalzahl, z. B. 21., fünfter + Ordinalzahl, z. B. 21., fünfter fraction, e.g. one half or three-quarters @@ -97,7 +93,7 @@

上記とは別の分類が必要であれば、それを使うことができる。

-

Je nach gewünschter Typologie können andere Werte für dieses Attribut verwendet werden.

+

Je nach gewünschter Typologie können andere Werte für dieses Attribut verwendet werden.

 @@ -111,7 +107,9 @@ estándard. indica il valore del numero in formato standard beinhaltet den Zahlenwert in standardisierter Form. - + + + a numeric value. une valeur numérique. ein numerischer Wert @@ -126,7 +124,7 @@

標準的な形式は、TEIデータ型teidata.numericで定義されている。

-

Die benutzte standardisierte Form wird im TEI-Datentyp teidata.numeric definiert.

+

Die benutzte standardisierte Form wird im TEI-Datentyp teidata.numeric definiert.

 @@ -164,7 +162,7 @@ my twenty-first birthday

当該要素numは、簡単なソフトウェアで使われることが想定され ている。

-

+

Detaillierte Analysen von Mengen und Maßeinheiten in historischen Dokumenten können auch den 'feature structure' Mechanismus verwenden, wie in Kapitel beschrieben. Das num-Element ist für einfache Anwendungen vorgesehen. diff --git a/P5/Source/Specs/number.xml b/P5/Source/Specs/number.xml index 1d6536c640..f0bbc9b66e 100644 --- a/P5/Source/Specs/number.xml +++ b/P5/Source/Specs/number.xml @@ -1,11 +1,5 @@ - + number diff --git a/P5/Source/Specs/numeric.xml b/P5/Source/Specs/numeric.xml index 46c26c179c..cc22510217 100644 --- a/P5/Source/Specs/numeric.xml +++ b/P5/Source/Specs/numeric.xml @@ -1,11 +1,5 @@ - + numeric value @@ -28,7 +22,9 @@ $Id$ - + + + supplies a lower bound for the numeric value represented, @@ -41,7 +37,9 @@ $Id$ numérique représentée et aussi (simax n'est pas donné) sa limite supérieure. proporciona el límite inferior para el valor numérico representado, y también (si no se proporciona max) su límite superior. fornisce un limite inferiore al valore numerico rappresentato e anche (qualora l'attributo max (maz) non sia presente) il limite superiore. - + + + supplies an upper bound for the numeric value represented. @@ -52,7 +50,9 @@ $Id$ numérique représentée. proporciona el límite superior para el valor numérico representado. fornisce un superiore inferiore al valore numerico rappresentato. - + + + specifies whether the value represented should be @@ -64,7 +64,9 @@ $Id$ tronquée pour donner un nombre entier. especifica si el valor representado debe ser truncado para dar un valor entero. indica se il valore rappresentato debba essere troncato per ottenere un numero intero. - + + + @@ -124,4 +126,4 @@ in the absence of a value for the value attribute.

- \ No newline at end of file + diff --git a/P5/Source/Specs/nym.xml b/P5/Source/Specs/nym.xml index 13dc85b6a9..eac0b3d88a 100644 --- a/P5/Source/Specs/nym.xml +++ b/P5/Source/Specs/nym.xml @@ -1,11 +1,5 @@ - + canonical name @@ -27,21 +21,10 @@ $Id$ - - - - - - - - - - - - - - - + + + + @@ -53,7 +36,9 @@ $Id$ pointe vers des éléments constituants canoniques. indica nym costitutivi señala un componente nyms. - + + + @@ -89,4 +74,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/oRef.xml b/P5/Source/Specs/oRef.xml index 5e2572fc3d..d0f8d14a67 100644 --- a/P5/Source/Specs/oRef.xml +++ b/P5/Source/Specs/oRef.xml @@ -1,11 +1,5 @@ - + orthographic-form reference @@ -37,7 +31,7 @@ $Id$ - + @@ -51,7 +45,9 @@ $Id$ el lema en la referencia. indica il tipo di modifica tipografica del lemma in un riferimento. - + + + capital @@ -129,4 +125,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/object.xml b/P5/Source/Specs/object.xml index ef1b06766a..cec0474ce3 100644 --- a/P5/Source/Specs/object.xml +++ b/P5/Source/Specs/object.xml @@ -1,10 +1,6 @@ - + + + contains a description of a single identifiable physical object. enthält die Beschreibung eines einzelnen identifizierbaren physischen Objekts. @@ -46,7 +42,7 @@ $Id$ - + @@ -80,17 +76,12 @@ $Id$ the Ashmolean Museum in Oxford. - -

The Minster Lovell Jewel is probably the most similar to the Alfred Jewel and was found in Minster - Lovell in Oxfordshire and is kept at the Ashmolean Museum. + Lovell in Oxfordshire and is kept at the Ashmolean Museum.

- - @@ -131,8 +122,7 @@ $Id$ -

The mask of Tutankhamun was created in Egypt around 1323 BC. It is a death mask of the 18th-dynasty ancient Egyptian Pharaoh Tutankhamun +

The mask of Tutankhamun was created in Egypt around 1323 BC. It is a death mask of the 18th-dynasty ancient Egyptian Pharaoh Tutankhamun who reigned 1332–1323 BC.

@@ -165,32 +155,26 @@ $Id$ - - -

- + +

The object element is a recent addition to the TEI P5 Guidelines as of version 3.5.0 and as such may be more prone to further revision in the next few releases as its use develops. This may be particularly evident where its contents have been borrowed from msDesc and have yet to be generalized from their use in the context of manuscript descriptions.

- -

The object element may be used for describing any object, text-bearing or not, though where the textuality of the object is the +

The object element may be used for describing any object, text-bearing or not, though where the textuality of the object is the primary concern or a collection is mostly composed of manuscripts, encoders may prefer the msDesc element (a more specific form of object) which may be used not only to describe manuscripts but any form of text-bearing objects such as early printed books.

- - - - -

+ + +

Das object-Element ist eine Neuerung zu den TEI P5 Guidelines ab Version 3.5.0 und kann daher in den nächsten Releases noch weiter überarbeitet werden. Dies kann besonders dann vorkommen, wenn der Inhalt von msDesc übernommen wurde und durch seine spezifische Verwendung im Rahmen von Manuskriptbeschreibungen noch verallgemeinert werden muss.

- - + - + diff --git a/P5/Source/Specs/objectDesc.xml b/P5/Source/Specs/objectDesc.xml index 12814fd5bb..c4f02dda69 100644 --- a/P5/Source/Specs/objectDesc.xml +++ b/P5/Source/Specs/objectDesc.xml @@ -1,11 +1,5 @@ - + object description @@ -24,16 +18,10 @@ $Id$ - - - + - - - - - - + + @@ -53,11 +41,15 @@ $Id$ de feuillet, découpe, etc. un nombre breve específico de un proyecto que identifica la forma física del documento, por ejemplo códex, rollo, fragmento, folio parcial, recorte, etc. un nome breve specifico di un progetto che identifica la forma fisica del documento, per esempio codice, rotolo, frammento, foglio parziale, ritaglio, ecc. - -

Definitions for the + + + + +

Definitions for the terms used may typically be provided by a valList element in the project schema -specification.

 +specification.

+ @@ -104,4 +96,4 @@ specification.

- \ No newline at end of file + diff --git a/P5/Source/Specs/objectIdentifier.xml b/P5/Source/Specs/objectIdentifier.xml index 73ad199656..d428c8a33b 100644 --- a/P5/Source/Specs/objectIdentifier.xml +++ b/P5/Source/Specs/objectIdentifier.xml @@ -1,10 +1,6 @@ - + + + object identifier Objektidentifikator @@ -26,7 +22,7 @@ $Id$ - + @@ -52,7 +48,7 @@ $Id$ Calesvol Kaledvoulc'h Caliburnus - Wales + Wales

Excalibur is the name for the legendary sword of King Arthur, in Welsh it is called Caledfwlch, in Cornish it is called Calesvol, in Breton it is called Kaledvoulc'h, and in Latin it is called Caliburnus. @@ -60,9 +56,8 @@ $Id$ "Take me up" and "Cast me away" (or similar).

 - + - diff --git a/P5/Source/Specs/objectName.xml b/P5/Source/Specs/objectName.xml index 4afb2ee24d..acfffc0f3c 100644 --- a/P5/Source/Specs/objectName.xml +++ b/P5/Source/Specs/objectName.xml @@ -1,10 +1,7 @@ - + + + + name of an object Name eines Objekts contains a proper noun or noun phrase used to refer to an object. @@ -22,38 +19,37 @@ $Id$ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + -

@@ -66,5 +62,4 @@ $Id$ - - \ No newline at end of file + diff --git a/P5/Source/Specs/objectType.xml b/P5/Source/Specs/objectType.xml index 87b6bdc7b4..ed4166b6ab 100644 --- a/P5/Source/Specs/objectType.xml +++ b/P5/Source/Specs/objectType.xml @@ -1,11 +1,5 @@ - + object type @@ -60,4 +54,4 @@ externally.

- \ No newline at end of file + diff --git a/P5/Source/Specs/occupation.xml b/P5/Source/Specs/occupation.xml index 09501d3f59..a0152c9b83 100644 --- a/P5/Source/Specs/occupation.xml +++ b/P5/Source/Specs/occupation.xml @@ -1,10 +1,7 @@ - + + + + occupation activité contains an informal description of a person's trade, profession or occupation. @@ -27,40 +24,38 @@ $Id$ - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + @@ -85,7 +80,9 @@ $Id$ elemento taxonomy colocado en el encabezado. identifica il sistema di classificazione o la tassonomia utilizzate tramite l'identificatore di un elemento taxonomy collocato nell'intestazione - + + + identifies an occupation code defined within the classification system or taxonomy defined by the scheme @@ -100,7 +97,9 @@ $Id$ corrisponde a un codice relativo all'occupazione definito nel sistema di classificazione o tassonomia stabiliti dall'attributo scheme - + + + @@ -153,4 +152,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/offset.xml b/P5/Source/Specs/offset.xml index a4940b9d5f..19be2001cb 100644 --- a/P5/Source/Specs/offset.xml +++ b/P5/Source/Specs/offset.xml @@ -1,10 +1,7 @@ - + + + + offset distance relative marks that part of a relative temporal or spatial expression which indicates the direction of the offset between the two place names, dates, or @@ -25,42 +22,42 @@ $Id$ - + - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -77,4 +74,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/opener.xml b/P5/Source/Specs/opener.xml index 7b663ad345..abceb63ba4 100644 --- a/P5/Source/Specs/opener.xml +++ b/P5/Source/Specs/opener.xml @@ -1,11 +1,5 @@ - + opener @@ -34,21 +28,19 @@ $Id$ - - - - - - - - - - - - - - - + + + + + + + + + + + + + @@ -108,4 +100,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/org.xml b/P5/Source/Specs/org.xml index e5423df3b8..9d275d9a99 100644 --- a/P5/Source/Specs/org.xml +++ b/P5/Source/Specs/org.xml @@ -1,11 +1,5 @@ - + organization @@ -102,4 +96,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/orgName.xml b/P5/Source/Specs/orgName.xml index d5dcca0617..66a883ce9e 100644 --- a/P5/Source/Specs/orgName.xml +++ b/P5/Source/Specs/orgName.xml @@ -1,10 +1,7 @@ - + + + + organization name 조직명 組織名稱 @@ -31,35 +28,35 @@ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -77,4 +74,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/orig.xml b/P5/Source/Specs/orig.xml index d9caf97eb8..2470babfcc 100644 --- a/P5/Source/Specs/orig.xml +++ b/P5/Source/Specs/orig.xml @@ -1,11 +1,5 @@ - + original form @@ -26,7 +20,7 @@ original. contiene una lettura codificata come conforme all'originale piuttosto che ad una versione normalizzata o corretta - enthält jene Schreibweise, die der Vorlage folgt und nicht normalisiert oder korrigiert ist. + enthält jene Schreibweise, die der Vorlage folgt und nicht normalisiert oder korrigiert ist. @@ -105,4 +99,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/origDate.xml b/P5/Source/Specs/origDate.xml index d6ca446f25..3dae716e63 100644 --- a/P5/Source/Specs/origDate.xml +++ b/P5/Source/Specs/origDate.xml @@ -1,11 +1,5 @@ - + origin date diff --git a/P5/Source/Specs/origPlace.xml b/P5/Source/Specs/origPlace.xml index 286a02d69b..caa1927edd 100644 --- a/P5/Source/Specs/origPlace.xml +++ b/P5/Source/Specs/origPlace.xml @@ -1,10 +1,7 @@ - + + + + origin place 생산 장소 @@ -34,35 +31,35 @@ place of origin for a manuscript, manuscript part, or other object. - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + diff --git a/P5/Source/Specs/origin.xml b/P5/Source/Specs/origin.xml index 80ef7fcd00..b9460af10c 100644 --- a/P5/Source/Specs/origin.xml +++ b/P5/Source/Specs/origin.xml @@ -1,10 +1,7 @@ - + + + + origin origine contains any descriptive or other information @@ -26,35 +23,35 @@ concerning the origin of a manuscript, manuscript part, or other object. - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -79,4 +76,4 @@ old Flemish original, between 1802 and 1845, according to - \ No newline at end of file + diff --git a/P5/Source/Specs/orth.xml b/P5/Source/Specs/orth.xml index 48b90b3984..b5e45db4a8 100644 --- a/P5/Source/Specs/orth.xml +++ b/P5/Source/Specs/orth.xml @@ -1,11 +1,5 @@ - + orthographic form @@ -43,7 +37,9 @@ $Id$ donne le type d’orthographe indica el tipo de ortografía. fornisce il tipo di trascrizione ortografica. - + + + @@ -82,4 +78,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/outputRendition.xml b/P5/Source/Specs/outputRendition.xml index 4d13201301..da509b57a5 100644 --- a/P5/Source/Specs/outputRendition.xml +++ b/P5/Source/Specs/outputRendition.xml @@ -1,11 +1,5 @@ - + @@ -25,7 +19,7 @@ pseudo-elements, that is, styling rules applicable to specific sub-portions of an element. - + @@ -68,7 +62,6 @@ be combined with any provided by an outputRendition element.

It is strongly recommended that the W3C Cascading Stylesheet language (CSS2 or later) be used to express the required formatting information.

- - \ No newline at end of file + diff --git a/P5/Source/Specs/p.xml b/P5/Source/Specs/p.xml index 1bf9c34e77..bde8362b58 100644 --- a/P5/Source/Specs/p.xml +++ b/P5/Source/Specs/p.xml @@ -1,11 +1,5 @@ - + paragraph @@ -79,4 +73,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/pRef.xml b/P5/Source/Specs/pRef.xml index b66f7ad71c..6d3253db6c 100644 --- a/P5/Source/Specs/pRef.xml +++ b/P5/Source/Specs/pRef.xml @@ -1,11 +1,5 @@ - + pronunciation reference @@ -24,37 +18,37 @@ $Id$ in un esempio in un dizionario, indica un riferimento alla pronuncia del lemma - - - - - + + + + + - - - - - + + + + + - - -
- umfahren - umf'ahren - 'umfahren -
- - Paul musste die Pfütze , wenn er nicht nass werden wollte. - - - Paul wollte das Schild nicht absichtlich und beschädigen. - - - - + + +
+ umfahren + umf'ahren + 'umfahren +
+ + Paul musste die Pfütze , wenn er nicht nass werden wollte. + + + Paul wollte das Schild nicht absichtlich und beschädigen. + + + + - + - \ No newline at end of file + diff --git a/P5/Source/Specs/param.xml b/P5/Source/Specs/param.xml index 9a45e044f4..a33a83ddad 100644 --- a/P5/Source/Specs/param.xml +++ b/P5/Source/Specs/param.xml @@ -1,11 +1,5 @@ - + provides a parameter for a model behaviour by @@ -13,7 +7,9 @@ $Id: $ - + + + a name for the parameter being supplied @@ -140,4 +136,4 @@ $Id: $ - \ No newline at end of file + diff --git a/P5/Source/Specs/paramList.xml b/P5/Source/Specs/paramList.xml index 9d457462a7..5bc90497ec 100644 --- a/P5/Source/Specs/paramList.xml +++ b/P5/Source/Specs/paramList.xml @@ -1,45 +1,38 @@ - + - + list of parameter specifications - + + - - create a specialized display of alternating elements for displaying the preferred version and an alternative, both at once or by some method of toggling between the two. - - - - preferred content - - - alternate content - - - + + create a specialized display of alternating elements for displaying the preferred version and an alternative, both at once or by some method of toggling between the two. + + + preferred content + + + alternate content + + + -

The paramList element provides a a mechanism to document parameter specifications using child paramSpec elements.

 - - \ No newline at end of file + --> + diff --git a/P5/Source/Specs/paramSpec.xml b/P5/Source/Specs/paramSpec.xml index 14aabaa225..c144cdc245 100644 --- a/P5/Source/Specs/paramSpec.xml +++ b/P5/Source/Specs/paramSpec.xml @@ -1,11 +1,5 @@ - + supplies specification for one parameter of a model diff --git a/P5/Source/Specs/particDesc.xml b/P5/Source/Specs/particDesc.xml index a64f75e8be..e52341f5c5 100644 --- a/P5/Source/Specs/particDesc.xml +++ b/P5/Source/Specs/particDesc.xml @@ -1,109 +1,151 @@ - + - participation description - 참여 기술 - 參與描述 - description des participants - descripción de participación - descrizione dei partecipanti - describes the identifiable speakers, voices, or + participation description + 참여 기술 + 參與描述 + description des participants + descripción de participación + descrizione dei partecipanti + describes the identifiable speakers, voices, or other participants in any kind of text or other persons named or otherwise referred to in a text, edition, or metadata. - 언어적 상호작용에서 식별가능한 화자, 음성, 또는 기타 참여자를 기술한다. - 描述在一個語言互動中可辨識的說話者、聲音或其他參與者。 - 言語交流における、特定可能な発話者、声、その他の参加者を示す。 - décrit les locuteurs, voix ou autres participants + 언어적 상호작용에서 식별가능한 화자, 음성, 또는 기타 참여자를 기술한다. + 描述在一個語言互動中可辨識的說話者、聲音或其他參與者。 + 言語交流における、特定可能な発話者、声、その他の参加者を示す。 + décrit les locuteurs, voix ou autres participants identifiables d'une interaction linguistique. - describe los hablantes identificables, voces u + describe los hablantes identificables, voces u otros participantes de una interacción lingüística. - descrive parlanti, voci o altri parlanti + descrive parlanti, voci o altri parlanti identificabili in una interazione linguistica. - - - - - - - - - - - - - - - - - - - - -

Female informant, well-educated, born in + + + + + + + + + + + + + + + + + + + + +

Female informant, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. - Socio-Economic status B2.

 - Hancock Antony Aloysius - St John -
+ Socio-Economic status B2.

+ + + + Hancock + Antony + Aloysius + St John + + +
Railway Cuttings East Cheam
- comedian - -

This example shows both a very simple person description, and a very detailed one, using + + comedian + + + + + + + +

This example shows both a very simple person description, and a very detailed one, using some of the more specialized elements from the module for Names and Dates.

- - -

informateur, sexe féminin, bonne éducation, née + + + + + + +

informateur, sexe féminin, bonne éducation, née à Shropshire UK, 12 Jan 1950, commerçante parle français couramment., Statut - socio-économique (SSE) : commerçant.

 - Delaunay Liliane - Andrée Alberte -
+ socio-économique (SSE) : commerçant.

+ + + + Delaunay + Liliane + Andrée + Alberte + + +
rue de Falaise la Guérinière, Caen
- serveuse - -

Cet exemple montre une description très + + serveuse + + + + + + + +

Cet exemple montre une description très simple d'une personne et une description très détaillée, utilisant quelques éléments plus spécialisés du module pour les noms et les dates.

- - - - -

女性，穿了一件黑紗金絲相間的緊身旗袍，一個大道士髻梳得烏光水滑的高聳在頭頂上；耳墜、項鍊、手串、髮針、金碧輝煌的掛滿了一身。

 金 兆麗 - 金大班 -
+ + + + + + +

女性，穿了一件黑紗金絲相間的緊身旗袍，一個大道士髻梳得烏光水滑的高聳在頭頂上；耳墜、項鍊、手串、髮針、金碧輝煌的掛滿了一身。

+ + + + 金 + 兆麗 + 金大班 + + +
西門町 台北
- 舞女 - - - -

May contain a prose description organized as paragraphs, or a structured + + 舞女 + + + + + + + + + +

May contain a prose description organized as paragraphs, or a structured list of persons and person groups, with an optional formal specification of any relationships amongst them.

- - -

Peut contenir un texte organisé en paragraphes ou une liste structurée de + + +

Peut contenir un texte organisé en paragraphes ou une liste structurée de personnes, ou encore de groupes de personne, avec facultativement des spécifications formelles des rapports qui les unissent.

- - -

段落としてある散文の解説または、関連性の形式定義を選択的に持つ、人 物やグループの構造化リストが示されるかもしれない。

- - - - - - \ No newline at end of file + + diff --git a/P5/Source/Specs/path.xml b/P5/Source/Specs/path.xml index 8f9ec73136..b27d84ef51 100644 --- a/P5/Source/Specs/path.xml +++ b/P5/Source/Specs/path.xml @@ -1,11 +1,5 @@ - + path @@ -23,10 +17,9 @@ element. - - Since a path> represents a line with distinct start and + Since a path> represents a line with distinct start and end points, the last coordinate should not be the same as the first coordinate. @@ -44,7 +37,6 @@ element. - identifies a line @@ -54,11 +46,11 @@ element. gives the x,y coordinates of a point on the line. beschreibt eine Linie innerhalb eines Begrenzungsrahmens, der durch das Elternelement definiert ist, über eine Reihe von zwei oder mehr Zahlenpaaren, die jeweils die X- und Y-Koordinaten eines Punktes dieser Linie angeben. - + + + - - @@ -68,16 +60,14 @@ element. -

Although the simplest form of a path is a straight line between two points, a line with more than two points may bend at any point. The order of coordinates in points is significant, because the line follows the coordinate sequence.

-

To specify a closed polygon, use +

To specify a closed polygon, use the zone element rather than the path element.

- - + diff --git a/P5/Source/Specs/pause.xml b/P5/Source/Specs/pause.xml index 231b29aa00..3fe730aeb7 100644 --- a/P5/Source/Specs/pause.xml +++ b/P5/Source/Specs/pause.xml @@ -1,11 +1,5 @@ - + pause @@ -25,7 +19,9 @@ $Id$ - + + + @@ -39,4 +35,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/pb.xml b/P5/Source/Specs/pb.xml index 0128120334..6bed0e2ba0 100644 --- a/P5/Source/Specs/pb.xml +++ b/P5/Source/Specs/pb.xml @@ -1,11 +1,5 @@ - + page beginning @@ -34,7 +28,9 @@ - + + +

Page numbers may vary in different editions of a text.

@@ -132,4 +128,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/pc.xml b/P5/Source/Specs/pc.xml index 2d5c970f89..3fa25ce461 100644 --- a/P5/Source/Specs/pc.xml +++ b/P5/Source/Specs/pc.xml @@ -1,11 +1,5 @@ - + punctuation character @@ -24,14 +18,12 @@ $Id$ - - - - - - - - + + + + + + @@ -39,7 +31,9 @@ $Id$ conventionally separates words or phrases gibt an, in welchem Maß das betreffende Interpunktionszeichen Wörter oder Phrasen gewöhnlich voneinander trennt. - + + + the punctuation mark is a word separator @@ -58,13 +52,17 @@ $Id$ provides a name for the kind of unit delimited by this punctuation mark. gibt die Art der Einheit an, die durch das Interpunktionszeichen begrenzt wird. - + + + indicates whether this punctuation mark precedes or follows the unit it delimits. gibt an, ob das Interpunktionszeichen der Einheit, die es begrenzt, vorangeht oder folgt. - + + + @@ -96,10 +94,11 @@ $Id$ - \ No newline at end of file +--> diff --git a/P5/Source/Specs/per.xml b/P5/Source/Specs/per.xml index 0016c2a374..abf9ffb922 100644 --- a/P5/Source/Specs/per.xml +++ b/P5/Source/Specs/per.xml @@ -1,11 +1,5 @@ - + @@ -101,4 +95,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/performance.xml b/P5/Source/Specs/performance.xml index 0e392fb01a..655b1a4b9d 100644 --- a/P5/Source/Specs/performance.xml +++ b/P5/Source/Specs/performance.xml @@ -1,11 +1,5 @@ - + performance @@ -31,27 +25,17 @@ $Id$ - - - - - - + + + + - - - - - - + + - - - - - - + + @@ -126,4 +110,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/persName.xml b/P5/Source/Specs/persName.xml index e670a2d5a9..ed2cb8be80 100644 --- a/P5/Source/Specs/persName.xml +++ b/P5/Source/Specs/persName.xml @@ -1,10 +1,7 @@ - + + + + personal name 개인 이름 個人名稱 @@ -41,38 +38,37 @@ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - EdwardGeorgeBulwer-Lytton, Baron Lytton of @@ -82,21 +78,27 @@ - Poncet Olivier professeur d'archivistique et diplomatique moderne + + Poncet + Olivier + professeur d'archivistique et diplomatique moderne + - Joseph Le Pétomane Pujol - + + Joseph + Le Pétomane + Pujol + + - Catherine II, la Grande, impératrice de Russie + CatherineII, la Grande, impératrice de Russie - - 夏爾皮耶波特萊爾，法國象徵派詩人 @@ -106,4 +108,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/persPronouns.xml b/P5/Source/Specs/persPronouns.xml index 6f4b4f59f5..6b845fba00 100644 --- a/P5/Source/Specs/persPronouns.xml +++ b/P5/Source/Specs/persPronouns.xml @@ -1,10 +1,7 @@ - + + + + personal pronouns indicates the personal pronouns used, or assumed to be used, by the individual being described. @@ -19,40 +16,38 @@ $Id$ - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + evidence indicates support @@ -62,25 +57,25 @@ $Id$ - conjecture - The given value + conjecture + The given value was selected based on assumptions by someone besides the person to whom this pronoun applies. As a result, the value may be erroneous. - self identification + self identification The given value has been explicitly stated or confirmed by the person to whom this pronoun applies. - - trusted third party - The given value + + trusted third party + The given value has been supplied by another individual trusted by the encoder to know the preferences of the person to whom this pronoun applies. - + @@ -88,28 +83,28 @@ $Id$ supplies a regularized value for personal pronouns. - + - - e - e/eirs - - - he - he/him/his - - - she - she/her/hers - - - they - they/them/theirs - + + e + e/eirs + + + he + he/him/his + + + she + she/her/hers + + + they + they/them/theirs + -

+

The sample values list shown here is intended to be reflective of English usage. There is nothing restricting users from defining lists reflective of other languages, @@ -121,43 +116,43 @@ $Id$ - - SUE - the T. rex - - The Field Museum. Chicago, Illinois, United States. - - they/them - - - Specimen FMNH PR 2081. Legendary Fossil. Apex + + SUE + the T. rex + + The Field Museum. Chicago, Illinois, United States. + + they/them + + + Specimen FMNH PR 2081. Legendary Fossil. Apex Predator. National Treasure. Murderbird. - SUEtheTrex, Twitter biography. + SUEtheTrex, Twitter biography. . Accessed March 25th, 2020. - - + + - Lal Zimman - (he/him/his) - (FAQ) - [lɑɫ ˈzimn̩] - zimman at ucsb dot edu - Assistant Professor of Linguistics - Affiliated Faculty in Feminist Studies -

- South Hall 3518 - University of California, Santa Barbara -
+ Lal Zimman + (he/him/his) + (FAQ) + [lɑɫ ˈzimn̩] + zimman at ucsb dot edu + Assistant Professor of Linguistics + Affiliated Faculty in Feminist Studies +
+ South Hall 3518 + University of California, Santa Barbara +
- \ No newline at end of file + diff --git a/P5/Source/Specs/person.xml b/P5/Source/Specs/person.xml index 233e6cfd3d..2cbeda1162 100644 --- a/P5/Source/Specs/person.xml +++ b/P5/Source/Specs/person.xml @@ -1,11 +1,5 @@ - + person @@ -29,16 +23,12 @@ - - - - - - - - - - + + + + + + @@ -50,15 +40,18 @@ précise un rôle principal ou une classification principale pour cette personne. establece el rol o la clasificación primaria de una persona. stabilisce il ruolo o la classificazione primaria di una persona - - + + + +

Values for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, author, relative, or servant, each of which should be associated with a definition. Such local definitions will typically be provided by a valList element in the project schema -specification.

 +specification.

+ specifies the sex of the person. @@ -68,14 +61,18 @@ specification.

précise le sexe de la personne. especifica el sexo de una persona. indica il sesso di una persona - + + +

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

 specifies the gender of the person. - + + +

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

 @@ -88,15 +85,18 @@ specification.

précise une tranche d'âge pour la personne. especifica un intervalo de edad para una persona. indica la fascia di età di una persona - - + + + +

Values for this attribute may be locally defined by a project, using arbitrary keywords such as infant, child, teen, adult, or senior, each of which should be associated with a definition. Such local definitions will typically be provided by a valList element in the project schema -specification.

 +specification.

+ @@ -191,4 +191,4 @@ specification.

- \ No newline at end of file + diff --git a/P5/Source/Specs/personGrp.xml b/P5/Source/Specs/personGrp.xml index defdf630e8..fb4bce5e50 100644 --- a/P5/Source/Specs/personGrp.xml +++ b/P5/Source/Specs/personGrp.xml @@ -1,11 +1,5 @@ - + personal group @@ -28,15 +22,11 @@ - - - - - - - - - + + + + + @@ -48,16 +38,18 @@ précise le rôle joué par ce groupe de personnes dans l'interaction. especifica el role de ese grupo de participantes en la interacción. specifica il ruolo del gruppo di partecipanti all'interazione - - - + + + +

Values for this attribute may be locally defined by a project, using arbitrary keywords such as movement, employers, relatives, or servants, each of which should be associated with a definition. Such local definitions will typically be provided by a valList element in the project schema -specification.

 +specification.

+ specifies the sex of the participant group. @@ -67,14 +59,18 @@ specification.

précise le sexe du groupe participant. especifica el sexo del grupo de participantes. indica il sesso del gruppo di partecipanti - + + +

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

 specifies the gender of the participant group. - + + +

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

 @@ -87,15 +83,18 @@ specification.

précise la tranche d'âge des participants. especifica el intervalo de edad del grupo de partecipantes. indica la fascia di età del gruppo di partecipanti - - + + + +

Values for this attribute may be locally defined by a project, using arbitrary keywords such as infant, child, teen, adult, or senior, each of which should be associated with a definition. Such local definitions will typically be provided by a valList element in the project schema -specification.

 +specification.

+ describes @@ -107,7 +106,9 @@ specification.

précise la taille exacte ou approximative du groupe. especifica la dimensión o dimensiones aproximadas del grupo. indica le dimensioni (anche approssimative) del gruppo - + + + @@ -138,4 +139,4 @@ specification.

- \ No newline at end of file + diff --git a/P5/Source/Specs/persona.xml b/P5/Source/Specs/persona.xml index f4ac55b3cd..43248eda86 100644 --- a/P5/Source/Specs/persona.xml +++ b/P5/Source/Specs/persona.xml @@ -1,28 +1,22 @@ - + provides information about one of the personalities identified for a given individual, where an individual has multiple personalities. - + - - - - - - + + + + + + @@ -34,15 +28,18 @@ précise un rôle principal ou une classification principale pour cette personne. establece el rol o la clasificación primaria de una persona. stabilisce il ruolo o la classificazione primaria di una persona - - + + + +

Values for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, author, relative, or servant, each of which should be associated with a definition. Such local definitions will typically be provided by a valList element in the project schema -specification.

 +specification.

+ specifies the sex of the persona. @@ -52,14 +49,18 @@ specification.

précise le sexe de la personne. especifica el sexo de una persona. indica il sesso di una persona - + + +

Values for this attribute may be locally defined by a project, or may refer to an external standard.

 specifies the gender of the persona. - + + +

Values for this attribute may be locally defined by a project, or they may refer to an external standard.

 @@ -72,15 +73,18 @@ specification.

précise une tranche d'âge pour la personne. especifica un intervalo de edad para una persona. indica la fascia di età di una persona - - + + + +

Values for this attribute may be locally defined by a project, using arbitrary keywords such as infant, child, teen, adult, or senior, each of which should be associated with a definition. Such local definitions will typically be provided by a valList element in the project schema -specification.

 +specification.

+ @@ -95,14 +99,13 @@ specification.

 - -

Note that a persona is not the same as a role. A role +

Note that a persona is not the same as a role. A role may be assumed by different people on different occasions, whereas a persona is unique to a particular person, even though it may resemble others. Similarly, when an actor takes on or enacts the role of a historical person, they do not - thereby acquire a new persona.

- + thereby acquire a new persona.

+ - - \ No newline at end of file + + diff --git a/P5/Source/Specs/phr.xml b/P5/Source/Specs/phr.xml index 235afbe19e..f8a6c81e98 100644 --- a/P5/Source/Specs/phr.xml +++ b/P5/Source/Specs/phr.xml @@ -1,11 +1,5 @@ - + phrase @@ -67,4 +61,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/physDesc.xml b/P5/Source/Specs/physDesc.xml index d47e1c1a4a..7d07219d7e 100644 --- a/P5/Source/Specs/physDesc.xml +++ b/P5/Source/Specs/physDesc.xml @@ -1,11 +1,5 @@ - + physical description @@ -31,13 +25,9 @@ specialized elements from the model.physDescPart cla - - - - - - - + + + @@ -66,4 +56,4 @@ specialized elements from the model.physDescPart cla - \ No newline at end of file + diff --git a/P5/Source/Specs/place.xml b/P5/Source/Specs/place.xml index 26f8798cd5..a7cb0fe220 100644 --- a/P5/Source/Specs/place.xml +++ b/P5/Source/Specs/place.xml @@ -1,11 +1,5 @@ - + place @@ -25,40 +19,28 @@ $Id$ - - - + - - - - - - - - - - - - - - - - - - - - - - - - - + - - + + + + - + + + + + + + + + + + + + @@ -78,4 +60,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/placeName.xml b/P5/Source/Specs/placeName.xml index 48ee8c47a9..59351ea7a6 100644 --- a/P5/Source/Specs/placeName.xml +++ b/P5/Source/Specs/placeName.xml @@ -1,10 +1,7 @@ - + + + + place name nom de lieu contains an absolute or relative place name. @@ -28,35 +25,35 @@ $Id$ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -137,4 +134,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/population.xml b/P5/Source/Specs/population.xml index 410b82b6bf..d98cd00363 100644 --- a/P5/Source/Specs/population.xml +++ b/P5/Source/Specs/population.xml @@ -1,10 +1,7 @@ - + + + + population population contains information about the population of a place. @@ -42,38 +39,38 @@ $Id$ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - + @@ -100,4 +97,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/pos.xml b/P5/Source/Specs/pos.xml index 8a381f7982..3086c8d839 100644 --- a/P5/Source/Specs/pos.xml +++ b/P5/Source/Specs/pos.xml @@ -1,11 +1,5 @@ - + part of speech @@ -30,7 +24,6 @@ headword such as noun, verb, or adjective. - @@ -75,4 +68,4 @@ headword such as noun, verb, or adjective. - \ No newline at end of file + diff --git a/P5/Source/Specs/postBox.xml b/P5/Source/Specs/postBox.xml index 827ca90758..803c442c52 100644 --- a/P5/Source/Specs/postBox.xml +++ b/P5/Source/Specs/postBox.xml @@ -1,11 +1,5 @@ - + postal box or post office box @@ -71,4 +65,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/postCode.xml b/P5/Source/Specs/postCode.xml index 1e2e5016c3..a6c6ab7f8a 100644 --- a/P5/Source/Specs/postCode.xml +++ b/P5/Source/Specs/postCode.xml @@ -1,11 +1,5 @@ - + postal code @@ -77,4 +71,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/postscript.xml b/P5/Source/Specs/postscript.xml index b350289758..afc866c6aa 100644 --- a/P5/Source/Specs/postscript.xml +++ b/P5/Source/Specs/postscript.xml @@ -1,11 +1,5 @@ - + contains a postscript, e.g. to a letter. @@ -23,28 +17,18 @@ lettre. - - - - - - - + + + + + + + - - - - - - - + - - - - - - + + @@ -122,4 +106,4 @@ lettre. - \ No newline at end of file + diff --git a/P5/Source/Specs/precision.xml b/P5/Source/Specs/precision.xml index 8fecf29376..b37234c23c 100644 --- a/P5/Source/Specs/precision.xml +++ b/P5/Source/Specs/precision.xml @@ -1,10 +1,7 @@ - + + + + indicates the numerical accuracy or precision associated with some aspect of the text markup. @@ -16,56 +13,56 @@ - - - - - - + + + + - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + characterizes the precision of the element or attribute pointed to by the precision element. - + + + supplies a standard deviation associated with the value in question - + + + @@ -96,4 +93,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/prefixDef.xml b/P5/Source/Specs/prefixDef.xml index 53ae3aa73c..667bcf8fa8 100644 --- a/P5/Source/Specs/prefixDef.xml +++ b/P5/Source/Specs/prefixDef.xml @@ -1,11 +1,5 @@ - + prefix definition @@ -16,20 +10,20 @@ $Id$ - + supplies a name which functions as the prefix for an abbreviated pointing scheme such as a private URI scheme. The prefix constitutes the text preceding the first colon. - - - - -

The value is limited to teidata.prefix so that it may be + + + + +

The value is limited to teidata.prefix so that it may be mapped directly to a URI prefix.

- + @@ -53,4 +47,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/preparedness.xml b/P5/Source/Specs/preparedness.xml index b28d79149f..8ce47c83c1 100644 --- a/P5/Source/Specs/preparedness.xml +++ b/P5/Source/Specs/preparedness.xml @@ -1,11 +1,5 @@ - + preparedness @@ -36,7 +30,9 @@ prepared or spontaneous. un mot clé caractérisant le type de préparation una palabra clave que caracteriza el tipo de preparación. una parola chiava che caratterizza il grado di spontaneità - + + + spontaneous or unprepared @@ -97,4 +93,4 @@ présentation. - \ No newline at end of file + diff --git a/P5/Source/Specs/principal.xml b/P5/Source/Specs/principal.xml index edd5a71ba7..f1a19c2525 100644 --- a/P5/Source/Specs/principal.xml +++ b/P5/Source/Specs/principal.xml @@ -1,10 +1,7 @@ - + + + + principal researcher chercheur principal 책임 연구자 @@ -18,7 +15,7 @@ creation of an electronic text. 전자 텍스트 생성에 대한 책임을 지는 책임 연구자의 이름을 제시한다. 提供負責電子文件製作的主導研究者的姓名。 電子テキストの生成に責任のある中心的な研究者の名前を示す。 - gibt den Namen des Projektleiters an, der für die Erstellung eines + gibt den Namen des Projektleiters an, der für die Erstellung eines elektronischen Textes verantwortlich ist. proporciona el nombre del investigador principal de la creación de un texto electrónico. fornisce il nome del ricercatore principale responsabile della creazione di un documento elettronico. @@ -33,35 +30,35 @@ creation of an electronic text. - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -82,4 +79,4 @@ creation of an electronic text. - \ No newline at end of file + diff --git a/P5/Source/Specs/profileDesc.xml b/P5/Source/Specs/profileDesc.xml index af13139cee..da8750213b 100644 --- a/P5/Source/Specs/profileDesc.xml +++ b/P5/Source/Specs/profileDesc.xml @@ -1,11 +1,5 @@ - + text-profile description @@ -25,7 +19,7 @@ $Id$ 측면을 상세히 기술한다. 提供文件非書目性方面的細節描述，特別是所使用的語言及次要語言、在何種情況下製作、參與人員及其環境背景。 書誌情報的ではない詳細な解説を示す。例えば、言語や特殊言語、生成され たときの状況、参加者など。 - enthält eine detaillierte Beschreibung der nicht-bibliografischen Merkmale des Textes, besonders der verwendeten Sprachen und Subsprachen, + enthält eine detaillierte Beschreibung der nicht-bibliografischen Merkmale des Textes, besonders der verwendeten Sprachen und Subsprachen, der Entstehungsbedingungen eines Textes sowie der Beteiligten und deren Umfeld. proporciona una descripción detallada de los aspectos no bibliográficos de un texto, especialmente las lenguas y jergas usadas, la situación en que se @@ -38,11 +32,7 @@ $Id$ - - - - - + @@ -128,7 +118,7 @@ meaningful to supply multiple occurrences for any of the child elements of profileDesc unless these are documenting multiple texts.

-

Obwohl durch das Inhaltsmodell erlaubt, erscheint es in den seltensten Fällen sinnvoll, mehrere Vorkommen der erlaubten Kindelemente der profileDesc zu notieren – außer diese beziehen sich auf unterschiedliche Texte. +

Obwohl durch das Inhaltsmodell erlaubt, erscheint es in den seltensten Fällen sinnvoll, mehrere Vorkommen der erlaubten Kindelemente der profileDesc zu notieren – außer diese beziehen sich auf unterschiedliche Texte.

diff --git a/P5/Source/Specs/projectDesc.xml b/P5/Source/Specs/projectDesc.xml index d40aecf0c9..af9013012f 100644 --- a/P5/Source/Specs/projectDesc.xml +++ b/P5/Source/Specs/projectDesc.xml @@ -1,11 +1,5 @@ - + project description @@ -25,7 +19,7 @@ $Id$ 기술한다, . 詳述將電子檔案編碼的目標或目的，以及其他關於檔案匯集或收集程序的任何資訊。 制作過程に関する情報も含めて、電子ファイルが作られた目的の詳細を示す。 - beschreibt detailliert Ziel bzw. Zweck, für den eine Datei kodiert wurde, zusammen mit weiteren relevanten Informationen, + beschreibt detailliert Ziel bzw. Zweck, für den eine Datei kodiert wurde, zusammen mit weiteren relevanten Informationen, die das Verfahren betreffen, nach dem die Daten zusammengestellt oder gesammelt wurden. describe con detalle el objetivo o propósito para el que un archivo electrónico ha sido codificado, junto a cualquier otra información relevante sobre el @@ -39,9 +33,7 @@ $Id$ - - - + diff --git a/P5/Source/Specs/prologue.xml b/P5/Source/Specs/prologue.xml index ef682277ab..68daa7daf9 100644 --- a/P5/Source/Specs/prologue.xml +++ b/P5/Source/Specs/prologue.xml @@ -1,11 +1,5 @@ - + prologue @@ -30,27 +24,17 @@ $Id$ - - - - - - + + + + - - - - - - + + - - - - - - + + @@ -109,4 +93,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/pron.xml b/P5/Source/Specs/pron.xml index b37752e0f8..bfdd381ca1 100644 --- a/P5/Source/Specs/pron.xml +++ b/P5/Source/Specs/pron.xml @@ -1,11 +1,5 @@ - + pronunciation @@ -33,7 +27,6 @@ $Id$ - @@ -71,7 +64,6 @@ $Id$ - @@ -85,12 +77,13 @@ $Id$ -

The values used to + +

The values used to specify the notation may be taken from any appropriate project-defined list of values. Typical values might be IPA, -Murray, for example.

 - +Murray, for example.

+ - \ No newline at end of file + diff --git a/P5/Source/Specs/provenance.xml b/P5/Source/Specs/provenance.xml index 90e6b89607..9cc440d5ee 100644 --- a/P5/Source/Specs/provenance.xml +++ b/P5/Source/Specs/provenance.xml @@ -1,10 +1,7 @@ - + + + + provenance provenance contains any descriptive or other information @@ -28,35 +25,35 @@ concerning a single identifiable episode during the history of a manuscript, man - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -80,4 +77,4 @@ concerning a single identifiable episode during the history of a manuscript, man - \ No newline at end of file + diff --git a/P5/Source/Specs/ptr.xml b/P5/Source/Specs/ptr.xml index acebc97a7e..3396854320 100644 --- a/P5/Source/Specs/ptr.xml +++ b/P5/Source/Specs/ptr.xml @@ -1,11 +1,5 @@ - + pointer @@ -31,7 +25,9 @@ - + + + Only one of the @@ -49,4 +45,4 @@ attributes @target and @cRef may be supplied on . - \ No newline at end of file + diff --git a/P5/Source/Specs/pubPlace.xml b/P5/Source/Specs/pubPlace.xml index 21ee7e1a29..64f70e76e6 100644 --- a/P5/Source/Specs/pubPlace.xml +++ b/P5/Source/Specs/pubPlace.xml @@ -1,11 +1,5 @@ - + publication place @@ -55,4 +49,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/publicationStmt.xml b/P5/Source/Specs/publicationStmt.xml index 5316a8b5de..dd75c2f0c6 100644 --- a/P5/Source/Specs/publicationStmt.xml +++ b/P5/Source/Specs/publicationStmt.xml @@ -1,18 +1,12 @@ - + publication statement mention de publication 출판 진술 出版陳述 - Angaben zur Veröffentlichung + Angaben zur Veröffentlichung declaración de la publicación dichiarazione sulla pubblicazione groups information concerning the publication or distribution of an electronic or other text. @@ -21,7 +15,7 @@ $Id$ 전자 또는 기타 텍스트의 출판 또는 배포에 관한 정보를 모아 놓는다. 匯集電子文件或其他類型文件的出版或發行相關資訊。 電子テキストなどの出版や頒布に関する情報をまとめる。 - umfasst Angaben zu Veröffentlichung oder Vertrieb eines elektronischen oder sonstigen Textes. + umfasst Angaben zu Veröffentlichung oder Vertrieb eines elektronischen oder sonstigen Textes. agrupa la información concerniente a la publicación o distribución de un texto electrónico u otro texto. raggruppa le informazioni riguardo la pubblicazione o la @@ -31,19 +25,11 @@ $Id$ - - - - - - - - - - - - - + + + + + @@ -147,7 +133,7 @@ $Id$ 可用性、日付が、この順番で出現することが望ましい。

-

+

Wenn die Angaben zur Veröffentlichung mehrere Mitglieder der Klassen model.publicationStmtPart.agency oder model.publicationStmtPart.detail enthalten und nicht einen oder mehrere Absätze (p) bzw. unbestimmte Einheiten (ab), dann hat die Reihenfolge der Elemente eine Bedeutung, auf die zu achten ist. So müssen Elemente, die Angaben über den Veröffentlichungsort, diff --git a/P5/Source/Specs/publisher.xml b/P5/Source/Specs/publisher.xml index 7e850b1891..71307f9cc1 100644 --- a/P5/Source/Specs/publisher.xml +++ b/P5/Source/Specs/publisher.xml @@ -1,10 +1,7 @@ - + + + + publisher editorial éditeur @@ -78,4 +75,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/punctuation.xml b/P5/Source/Specs/punctuation.xml index c95640b945..c9275273e7 100644 --- a/P5/Source/Specs/punctuation.xml +++ b/P5/Source/Specs/punctuation.xml @@ -1,11 +1,5 @@ - + specifies editorial practice adopted with respect to punctuation marks in the original. @@ -14,13 +8,15 @@ $Id$ - + indicates whether or not punctation marks have been retained as content within the text. - + + + no punctuation marks have been retained @@ -35,7 +31,9 @@ $Id$ indicates the positioning of punctuation marks that are associated with marked up text as being encoded within the element surrounding the text or immediately before or after it. - + + + punctuation marks found at the start or end of a marked up text component are included within its surrounding element; @@ -72,4 +70,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/purpose.xml b/P5/Source/Specs/purpose.xml index 4675f2f3d0..a2484050f6 100644 --- a/P5/Source/Specs/purpose.xml +++ b/P5/Source/Specs/purpose.xml @@ -1,11 +1,5 @@ - + characterizes a single purpose or communicative function of the @@ -33,7 +27,9 @@ text. précise une intention particulière especifica un tipo particular de finalidad specifica un tipo particolare di scopo. - + + + didactic, advertising, propaganda, etc. @@ -84,7 +80,9 @@ etc. prédomine. especifica el alcance en que predomina este propósito. specifica il grado in cui lo scopo predomina. - + + +

Values should be interpreted as follows. this purpose is predominantthis purpose is intermediatethis purpose is weakextent unknown @@ -132,4 +130,4 @@ attribute is needed, in which case it may contain running prose

- \ No newline at end of file + diff --git a/P5/Source/Specs/q.xml b/P5/Source/Specs/q.xml index 9b0e344e18..a6a2975e8f 100644 --- a/P5/Source/Specs/q.xml +++ b/P5/Source/Specs/q.xml @@ -1,11 +1,5 @@ - + quoted @@ -71,7 +65,9 @@ parlato o pensato, oppure per caratterizzarlo con maggior precisione. kann verwendet werden, um anzuzeigen, ob die abgesetzte Textpassage gesprochen oder gedacht wird, oder um sie auf andere Weise detaillierter zu beschreiben. - + + + spoken @@ -229,4 +225,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/quotation.xml b/P5/Source/Specs/quotation.xml index 92ad6dd141..750b056e8a 100644 --- a/P5/Source/Specs/quotation.xml +++ b/P5/Source/Specs/quotation.xml @@ -1,11 +1,5 @@ - + quotation @@ -28,9 +22,7 @@ $Id$ - - - + @@ -57,7 +49,9 @@ On , either the @marks attribute should be used, or a paragraph of descri el texto. indica se le virglotette siano state mantenute o meno all'interno del testo. - + + + no quotation marks have been retained @@ -88,7 +82,7 @@ On , either the @marks attribute should be used, or a paragraph of descri - + + quotation @@ -75,4 +69,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/rb.xml b/P5/Source/Specs/rb.xml index d05c252eed..e8afce6844 100644 --- a/P5/Source/Specs/rb.xml +++ b/P5/Source/Specs/rb.xml @@ -1,11 +1,5 @@ - + ruby base @@ -18,23 +12,28 @@ - + - -

The word 你 好 nǐ hǎo + +

The word 你 好 nǐ hǎo (hello) is glossed in pinyin to provide a pronunciation guide.

- -

- - 你nǐ - 好hǎo - -

- - - + +

+ + + 你 + nǐ + + + 好 + hǎo + + +

+ + - \ No newline at end of file + diff --git a/P5/Source/Specs/rdg.xml b/P5/Source/Specs/rdg.xml index 5dae28b179..576fa2ecec 100644 --- a/P5/Source/Specs/rdg.xml +++ b/P5/Source/Specs/rdg.xml @@ -1,11 +1,5 @@ - + reading @@ -80,4 +74,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/rdgGrp.xml b/P5/Source/Specs/rdgGrp.xml index 72c65906b4..7105b228eb 100644 --- a/P5/Source/Specs/rdgGrp.xml +++ b/P5/Source/Specs/rdgGrp.xml @@ -1,11 +1,5 @@ - + reading group @@ -32,13 +26,13 @@ relationship or other affinity. - - - - - - - + + + + + + + @@ -103,4 +97,4 @@ relationship or other affinity. - \ No newline at end of file + diff --git a/P5/Source/Specs/re.xml b/P5/Source/Specs/re.xml index 064e19571f..87df3c273f 100644 --- a/P5/Source/Specs/re.xml +++ b/P5/Source/Specs/re.xml @@ -1,11 +1,5 @@ - + related entry @@ -35,16 +29,14 @@ $Id$ - - - - - - - - - - + + + + + + + +

The following example from Webster's New Collegiate Dictionary @@ -365,4 +357,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/recordHist.xml b/P5/Source/Specs/recordHist.xml index bd66ec0811..43ead0170f 100644 --- a/P5/Source/Specs/recordHist.xml +++ b/P5/Source/Specs/recordHist.xml @@ -1,11 +1,5 @@ - + recorded history @@ -28,14 +22,10 @@ revision status of the parent manuscript or object description itself. - - - + - - - + @@ -77,4 +67,4 @@ revision status of the parent manuscript or object description itself. - \ No newline at end of file + diff --git a/P5/Source/Specs/recording.xml b/P5/Source/Specs/recording.xml index a5efb58380..db050f7864 100644 --- a/P5/Source/Specs/recording.xml +++ b/P5/Source/Specs/recording.xml @@ -1,11 +1,5 @@ - + recording event @@ -36,12 +30,10 @@ a public broadcast. - - - - - + + + @@ -53,7 +45,9 @@ a public broadcast. Art der Aufnahme tipo de grabación tipo di registrazione. - + + + audio @@ -118,7 +112,7 @@ a public broadcast. Le Téléphone sonne - Marie Pezé est Docteur en psychologie, psychanalyste, expert judiciaire ; dirige + Marie Pezé est Docteur en psychologie, psychanalyste, expert judiciaire ; dirige la consultation « souffrance et travail » à l’Hôpital de Nanterre (92), auteure de ils ne mourraient pas tous mais tous étaient frappés, Editions Pearson. @@ -244,4 +238,4 @@ a public broadcast. - \ No newline at end of file + diff --git a/P5/Source/Specs/recordingStmt.xml b/P5/Source/Specs/recordingStmt.xml index d069238c92..793b732c6d 100644 --- a/P5/Source/Specs/recordingStmt.xml +++ b/P5/Source/Specs/recordingStmt.xml @@ -1,11 +1,5 @@ - + recording statement @@ -32,12 +26,8 @@ spoken text. - - - - - - + + @@ -70,4 +60,4 @@ distinct recordings made by hidden microphone in early February - \ No newline at end of file + diff --git a/P5/Source/Specs/redo.xml b/P5/Source/Specs/redo.xml index 0a8dad0d60..1ec1647624 100644 --- a/P5/Source/Specs/redo.xml +++ b/P5/Source/Specs/redo.xml @@ -1,11 +1,5 @@ - + indicates one or more cancelled interventions in a @@ -19,12 +13,16 @@ - + + + points to one or more elements representing the interventions which are being reasserted. - + + + @@ -41,4 +39,4 @@ nur piepſet iſt die Welt ſchon matt." is written the redundant l - \ No newline at end of file + diff --git a/P5/Source/Specs/ref.xml b/P5/Source/Specs/ref.xml index 1c6f9dd713..fc6502bad9 100644 --- a/P5/Source/Specs/ref.xml +++ b/P5/Source/Specs/ref.xml @@ -1,11 +1,5 @@ - + reference @@ -14,7 +8,7 @@ referencia référence riferimento - Referenz + Referenz defines a reference to another location, possibly modified by additional text or comment. 부가적인 텍스트 또는 해설로 수정될 수 있는, 다른 위치로 참조를 정의한다. 標明與其他位置互相參照的符號，或許包含附加的文字或註解。 @@ -24,7 +18,7 @@ modificada por un texto o comentario adicional. definisce un riferimento ad un'altra posizione, può essere modificata da un commento o testo ulteriore - definiert einen externen oder internen Verweis, der auch durch einen zusätzlichen Text oder Kommentar ergänzt werden kann. + definiert einen externen oder internen Verweis, der auch durch einen zusätzlichen Text oder Kommentar ergänzt werden kann. @@ -77,10 +71,10 @@

属性targetとcRefは、排他的に使用される。

-

Die target und cRef-Attribute schließen sich gegenseitig aus.

+

Die target und cRef-Attribute schließen sich gegenseitig aus.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/refState.xml b/P5/Source/Specs/refState.xml index 1106b17904..af152bf484 100644 --- a/P5/Source/Specs/refState.xml +++ b/P5/Source/Specs/refState.xml @@ -1,11 +1,5 @@ - + reference state @@ -29,7 +23,9 @@ $Id$ - + + + + references declaration Déclaration du système de références 참조 선언 參照宣告 - Angabe der Referenzstruktur + Angabe der Referenzstruktur declaración de referencias dichiarazione sui riferimenti specifies how canonical references are constructed for this @@ -21,7 +15,7 @@ $Id$ 표준 참조가 이러한 텍스트에 대해 어떻게 구성되는가를 명시한다. 標明本文件與某一個權威參照標準的關係。 標準的な参照の作られ方を示す。 - beschreibt, wie Standardreferenzen für diesen Text aufgebaut sind. + beschreibt, wie Standardreferenzen für diesen Text aufgebaut sind. indica cómo se han formado las referencias canónicas para este texto. specifica in che modo siano costruiti i riferimenti canonici per il testo. @@ -95,4 +89,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/reg.xml b/P5/Source/Specs/reg.xml index 234e9c4971..54c31d9bcc 100644 --- a/P5/Source/Specs/reg.xml +++ b/P5/Source/Specs/reg.xml @@ -1,11 +1,5 @@ - + regularization @@ -15,7 +9,7 @@ régularisation regularización regolarizzazione - Normalisierung + Normalisierung contains a reading which has been regularized or normalized in some sense. 어떤 면에서 정규화 또는 표준화된 해석을 포함한다. 標誌一般化或規格化處理過的文字。 @@ -26,7 +20,7 @@ normalizada en algún sentido. contiene una lettura è stata regolarizzata o normalizzata in qualche modo. - enthält eine normalisierte Schreibweise einer Textstelle. + enthält eine normalisierte Schreibweise einer Textstelle. @@ -107,4 +101,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/region.xml b/P5/Source/Specs/region.xml index 1dc01d63d3..791900f72a 100644 --- a/P5/Source/Specs/region.xml +++ b/P5/Source/Specs/region.xml @@ -1,10 +1,7 @@ - + + + + region région contains the name of an administrative unit such as a state, province, or county, larger @@ -31,35 +28,35 @@ $Id$ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -86,4 +83,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/relatedItem.xml b/P5/Source/Specs/relatedItem.xml index 3cf81f3a14..1248003de0 100644 --- a/P5/Source/Specs/relatedItem.xml +++ b/P5/Source/Specs/relatedItem.xml @@ -1,11 +1,5 @@ - + contains or references some other bibliographic item which is related to the present one in @@ -30,12 +24,10 @@ - - - - - - + + + + @@ -51,7 +43,9 @@ relatedItem element must be empty points to the related bibliographic element by means of an absolute or relative URI reference zeigt auf das in Beziehung stehende bibliografische Objekt durch eine absolute oder relative URI - + + + @@ -101,4 +95,4 @@ relatedItem element must be empty - \ No newline at end of file + diff --git a/P5/Source/Specs/relation.xml b/P5/Source/Specs/relation.xml index 51c10ca188..8ee3afd0d4 100644 --- a/P5/Source/Specs/relation.xml +++ b/P5/Source/Specs/relation.xml @@ -1,10 +1,7 @@ - + + + + relationship 관련성 人際關係 @@ -55,40 +52,38 @@ $Id$ - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + supplies a name for the kind of relationship of which this is an instance. 이것이 실례인 관련성 종류에 대한 이름을 제공한다. 提供該關係的確切名稱。 @@ -96,7 +91,9 @@ $Id$ fournit un nom pour le type de relation dont elle est une instance. proporciona un nombre para elipo de relación que representan. assegna un nome al tipo di relazione che rappresenta - + + + @@ -108,7 +105,9 @@ $Id$ dans une relation réciproque. identifica i partecipanti attivi in una relazione di non reciprocità, oppure tutti i partecipanti in una relazione di reciprocità - + + + supplies a list of participants amongst all of whom the relationship holds equally. @@ -116,7 +115,9 @@ $Id$ relación fournit une liste de participants entre lesquels la relation est réciproque. fornisce una lista di partecipanti tra i quali c'è una relazione paritaria - + + + @@ -127,7 +128,9 @@ $Id$ identifie les participants passifs dans une relation non mutuelle. identifica los participantes pasivos en una relación de no reciprocidad. identifica i partecipanti passiviall'interno di una relazione di non reciprocità. - + + + @@ -187,4 +190,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/remarks.xml b/P5/Source/Specs/remarks.xml index 23da683e5e..55fa6dec95 100644 --- a/P5/Source/Specs/remarks.xml +++ b/P5/Source/Specs/remarks.xml @@ -1,11 +1,5 @@ - + remarks @@ -30,13 +24,15 @@ $Id$ - - + + specifies the remark concerned. - + + + @@ -78,4 +74,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/rendition.xml b/P5/Source/Specs/rendition.xml index 3b345f24fb..4466d98b2d 100644 --- a/P5/Source/Specs/rendition.xml +++ b/P5/Source/Specs/rendition.xml @@ -1,11 +1,5 @@ - + rendition @@ -34,7 +28,9 @@ $Id$ where CSS is used, provides a way of defining pseudo-elements, that is, styling rules applicable to specific sub-portions of an element. - + + + styling applies to the first line of @@ -60,7 +56,9 @@ the target element contains a selector or series of selectors specifying the elements to which the contained style description applies, expressed in the language specified in the scheme attribute. - + + + @@ -69,7 +67,7 @@ the target element - + font-style: italic; diff --git a/P5/Source/Specs/repository.xml b/P5/Source/Specs/repository.xml index 476584b959..655bc1c9b3 100644 --- a/P5/Source/Specs/repository.xml +++ b/P5/Source/Specs/repository.xml @@ -1,11 +1,5 @@ - + repository diff --git a/P5/Source/Specs/residence.xml b/P5/Source/Specs/residence.xml index a284f06693..331f92b772 100644 --- a/P5/Source/Specs/residence.xml +++ b/P5/Source/Specs/residence.xml @@ -1,10 +1,7 @@ - + + + + residence 거주 住所 @@ -30,40 +27,38 @@ $Id$ - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + @@ -127,4 +122,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/resp.xml b/P5/Source/Specs/resp.xml index 5db6d520a0..bc3f971d9b 100644 --- a/P5/Source/Specs/resp.xml +++ b/P5/Source/Specs/resp.xml @@ -1,10 +1,7 @@ - + + + + responsibility 책임성 @@ -35,35 +32,35 @@ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -118,4 +115,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/respStmt.xml b/P5/Source/Specs/respStmt.xml index 58349a0684..ed5c86256f 100644 --- a/P5/Source/Specs/respStmt.xml +++ b/P5/Source/Specs/respStmt.xml @@ -1,11 +1,5 @@ - + statement of responsibility @@ -48,24 +42,16 @@ - - - - - - - - - + @@ -121,4 +107,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/respons.xml b/P5/Source/Specs/respons.xml index 73a5496334..286f8060f9 100644 --- a/P5/Source/Specs/respons.xml +++ b/P5/Source/Specs/respons.xml @@ -1,11 +1,5 @@ - + responsibility @@ -45,7 +39,9 @@ markup of particular element(s). indique l'aspect spécifique du balisage sur lequel porte la responsabilité. indica el aspecto específico del marcaje por el cual la responsabilidad está siendo asignada indica l'aspetto specifico della codifica per il qaule è attribuita la responsabilità - + + + responsibility is being assigned concerning the name of the element diff --git a/P5/Source/Specs/restore.xml b/P5/Source/Specs/restore.xml index c7e94547ab..fe5f8a234f 100644 --- a/P5/Source/Specs/restore.xml +++ b/P5/Source/Specs/restore.xml @@ -1,11 +1,5 @@ - + restore @@ -47,4 +41,4 @@ For I hate this - \ No newline at end of file + diff --git a/P5/Source/Specs/retrace.xml b/P5/Source/Specs/retrace.xml index dbd5275258..0e4d8201d0 100644 --- a/P5/Source/Specs/retrace.xml +++ b/P5/Source/Specs/retrace.xml @@ -1,11 +1,5 @@ - + contains a sequence of writing which has been retraced, for @@ -40,4 +34,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/revisionDesc.xml b/P5/Source/Specs/revisionDesc.xml index ef4590e766..0d4f5b0e38 100644 --- a/P5/Source/Specs/revisionDesc.xml +++ b/P5/Source/Specs/revisionDesc.xml @@ -1,11 +1,5 @@ - + revision description @@ -76,7 +70,7 @@ $Id$

直近の変更をリストの先頭に記録する。

-

Wenn an diesem Element gesetzt, sollte das status-Attribut den aktuellen +

Wenn an diesem Element gesetzt, sollte das status-Attribut den aktuellen Status des Dokuments widerspiegeln. An jedem change-Kindelement gibt das selbe Attribut den jeweiligen Status zum Zeitpunkt der Änderung an. Die change-Elemente werden der Konvention nach so angeordnet, dass die letzte Änderung am Anfang steht und die erste zum Schluss.

diff --git a/P5/Source/Specs/rhyme.xml b/P5/Source/Specs/rhyme.xml index bfc72d8e28..885aa09d79 100644 --- a/P5/Source/Specs/rhyme.xml +++ b/P5/Source/Specs/rhyme.xml @@ -1,11 +1,5 @@ - + marks the rhyming part of a metrical line. @@ -37,7 +31,9 @@ $Id$ fornisce un'etichetta che identifica quale parte dello schema rimico è rappresentata dalla stringa in questione - + + +

Within a particular scope, all rhyme elements with the same value for their label attribute are assumed to rhyme with each other. The scope is defined by @@ -72,33 +68,30 @@ $Id$ - - - - - Tyger! Tyger! burning bright - In the forests of the night, - What immortal hand or eye - Could frame thy fearful symmetry? - - - - - - - - "Hark! Lakshman! Hark, again that cry! - It is, — it is my husband's voice! - hasten, to his succour fly, - No more hast thou, dear friend, a choice. - He calls on thee, perhaps his foes - Environ him on all sides round, - That wail, — it means death's final throes! - Why standest thou, as magic-bound? - - + + + + Tyger! Tyger! burning bright + In the forests of the night, + What immortal hand or eye + Could frame thy fearful symmetry? + + + + + + + "Hark! Lakshman! Hark, again that cry! + It is, — it is my husband's voice! + hasten, to his succour fly, + No more hast thou, dear friend, a choice. + He calls on thee, perhaps his foes + Environ him on all sides round, + That wail, — it means death's final throes! + Why standest thou, as magic-bound? + + - diff --git a/P5/Source/Specs/role.xml b/P5/Source/Specs/role.xml index 461b88d12d..231dc45122 100644 --- a/P5/Source/Specs/role.xml +++ b/P5/Source/Specs/role.xml @@ -1,11 +1,5 @@ - + role @@ -30,7 +24,9 @@ $Id$ specifies the gender of the role. - + + +

Values for this attribute may be locally defined by a project, or they may refer to an external standard.

 @@ -71,4 +67,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/roleDesc.xml b/P5/Source/Specs/roleDesc.xml index 2d737564fb..9e98defb06 100644 --- a/P5/Source/Specs/roleDesc.xml +++ b/P5/Source/Specs/roleDesc.xml @@ -1,11 +1,5 @@ - + role description @@ -47,4 +41,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/roleName.xml b/P5/Source/Specs/roleName.xml index 343dd5722a..9ab4eea871 100644 --- a/P5/Source/Specs/roleName.xml +++ b/P5/Source/Specs/roleName.xml @@ -1,11 +1,5 @@ - + role name @@ -82,4 +76,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/root.xml b/P5/Source/Specs/root.xml index a3033d0869..4e423b3db4 100644 --- a/P5/Source/Specs/root.xml +++ b/P5/Source/Specs/root.xml @@ -1,11 +1,5 @@ - + root node @@ -25,9 +19,7 @@ $Id$ - - - + @@ -39,7 +31,9 @@ other analytic element. fournit l'identifiant de l'objet représenté par la racine ; cet objet peut être une paire nom-valeur ou tout autre élément analytique. proporciona el valor de la raíz, que puede ser una estructura de rasgos u otro elemento de análisis. assegna alla radice un valore, che può essere una struttura di tratti o altro elemento di analisi - + + + identifies the elements which are the children of the root node. @@ -49,7 +43,9 @@ other analytic element. fournit la liste des identifiants des éléments qui sont les enfants du nœud racine. proporciona una lista de identificadores de elementos que son hijos (descendientes) de la raíz. fornisce una lista di identificatori degli elementi figli del nodo radice - + + +

If the root has no children (i.e., the tree is trivial), then the children @@ -79,7 +75,9 @@ attribute should be omitted.

indique si la racine est ordonnée ou non. indica si la raíz es o no ordenada. indica se la radice è ordinata - + + +

The value true indicates that the children of the root are ordered, whereas false indicates the @@ -111,7 +109,9 @@ attribute should be omitted.

donne le degré sortant de la racine, c'est-à-dire le nombre de ses enfants. indica el grado en salida de la raíz, es decir, el número de hijos de esta. indica il grado in uscita della radice, cioè il numero dei suoi figli - + + +

The in degree of the root is always 0.

 @@ -146,4 +146,4 @@ attribute should be omitted.

- \ No newline at end of file + diff --git a/P5/Source/Specs/row.xml b/P5/Source/Specs/row.xml index 4d08795cad..075f38aa56 100644 --- a/P5/Source/Specs/row.xml +++ b/P5/Source/Specs/row.xml @@ -1,11 +1,5 @@ - + row @@ -24,15 +18,13 @@ $Id$ - - - - - - + + + + - @@ -61,4 +53,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/rs.xml b/P5/Source/Specs/rs.xml index 31ec5ef3dc..d8b144c9e1 100644 --- a/P5/Source/Specs/rs.xml +++ b/P5/Source/Specs/rs.xml @@ -1,11 +1,5 @@ - + referencing string @@ -56,4 +50,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/rt.xml b/P5/Source/Specs/rt.xml index 69aa85d21b..605f1aa137 100644 --- a/P5/Source/Specs/rt.xml +++ b/P5/Source/Specs/rt.xml @@ -1,11 +1,5 @@ - + ruby text @@ -21,14 +15,16 @@ - + supplies a pointer to the base being glossed by this ruby text. ルビテキストの対象へのポインタを示す。 - + + + - 大だい - 統とう - 領りょう + + 大 + だい + + + 統 + とう + + + 領 + りょう +

@@ -115,4 +120,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/rubric.xml b/P5/Source/Specs/rubric.xml index 903f2ebcac..e2c243539b 100644 --- a/P5/Source/Specs/rubric.xml +++ b/P5/Source/Specs/rubric.xml @@ -1,11 +1,5 @@ - + rubric @@ -59,4 +53,4 @@ manuscript or other object signals the beginning of a text division, often with - \ No newline at end of file + diff --git a/P5/Source/Specs/ruby.xml b/P5/Source/Specs/ruby.xml index 1097f0631b..0fcb7034e4 100644 --- a/P5/Source/Specs/ruby.xml +++ b/P5/Source/Specs/ruby.xml @@ -1,23 +1,17 @@ - + ruby container -ルビのためのコンテナ要素。 -contains a + ルビのためのコンテナ要素。 + contains a passage of base text along with its associated ruby gloss(es). -ルビ及びその対象となるテキストを含む。 - - - - - + ルビ及びその対象となるテキストを含む。 + + + + + @@ -36,10 +30,8 @@

- -

This fictional example shows the initialism TEI glossed letter-by-letter with an IPA transcription.

@@ -61,4 +53,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/s.xml b/P5/Source/Specs/s.xml index 97094b2d4a..e437d55a97 100644 --- a/P5/Source/Specs/s.xml +++ b/P5/Source/Specs/s.xml @@ -1,11 +1,5 @@ - + s-unit @@ -31,10 +25,10 @@ $Id$ - - + @@ -53,8 +47,17 @@ $Id$ - Quandpartez-vous ? - Demain. + + Quand + partez + - + vous + ? + + + Demain + . + @@ -93,4 +96,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/said.xml b/P5/Source/Specs/said.xml index 61a29696e2..9a6a556aca 100644 --- a/P5/Source/Specs/said.xml +++ b/P5/Source/Specs/said.xml @@ -1,11 +1,5 @@ - + speech or thought @@ -48,7 +42,9 @@ l'objet cité est dit oralement ou par signes. può essere utilizzato per indicare se la citazione in questione è stata pronunciata o firmata - + + +

@@ -89,7 +85,9 @@ à considérer comme comme étant du discours direct ou du discours indirect. può essere utilizzato per indicare se la citazione in questione è considerata come discorso diretto o indiretto - + + + true @@ -191,4 +189,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/salute.xml b/P5/Source/Specs/salute.xml index 586f534fc7..80c947b935 100644 --- a/P5/Source/Specs/salute.xml +++ b/P5/Source/Specs/salute.xml @@ -1,11 +1,5 @@ - + salutation @@ -62,4 +56,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/samplingDecl.xml b/P5/Source/Specs/samplingDecl.xml index edfe009fa1..02b4e14138 100644 --- a/P5/Source/Specs/samplingDecl.xml +++ b/P5/Source/Specs/samplingDecl.xml @@ -1,18 +1,12 @@ - + sampling declaration déclaration d'échantillonnage 표본 추출 선언 取樣宣告 - Angabe der Auswahlverfahren + Angabe der Auswahlverfahren declaración de muestra dichiarazione di campionatura contains a prose description of the rationale and methods used in selecting texts, or parts of a text, for inclusion in the resource. @@ -22,7 +16,7 @@ $Id$ 코퍼스 또는 텍스트 집단 구축에서 표본 추출에 사용된 원리와 방법에 대한 산문체 기술을 포함한다. 以篇章描述的方式說明建立文集或文選時文件取樣的原理與方法。 コーパス等を作成する際、テキストを標本化する原理や手法に関する、散文 による解説を含む。 - enthält eine Beschreibung der Kriterien und Methoden, + enthält eine Beschreibung der Kriterien und Methoden, nach denen die Texte für ein Korpus oder eine Sammlung zusammengestellt wurden. contiene una descripción en prosa sobre los fundamentos y métodos usados en textos de muestra en la creación de un corpus o una selección de textos. @@ -34,9 +28,7 @@ $Id$ - - - + @@ -76,14 +68,14 @@ $Id$

純粋な意味での標本化過程または体系的な資料の省略が、難しすぎて転記 できない、または充分な関心が得られていないと考えられているにしても、 当該要 素は、テキスト部分の体系的な取捨選択に関する情報の全てを 記録する。

- -

+ +

Dieses Element umfasst Informationen über das systematische Einbinden oder Auslassen von Textteilen. Dabei kann es sich um eine Beschreibung der Auswahlprozesse handeln oder um Angaben darüber, warum bestimmtes Material ausgelassen wurde, z. B. weil das Material zu schwierig zu transkribieren oder nicht interessant genug war.

- + diff --git a/P5/Source/Specs/schemaRef.xml b/P5/Source/Specs/schemaRef.xml index f93b1c609e..d636100c56 100644 --- a/P5/Source/Specs/schemaRef.xml +++ b/P5/Source/Specs/schemaRef.xml @@ -1,11 +1,5 @@ - + schema reference @@ -16,17 +10,17 @@ $Id$ - + - - + the identifier used for the customization or schema - - + + + + - @@ -34,9 +28,7 @@ $Id$ - - - \ No newline at end of file + diff --git a/P5/Source/Specs/schemaSpec.xml b/P5/Source/Specs/schemaSpec.xml index 8b3b87ce18..b2bf1c881c 100644 --- a/P5/Source/Specs/schemaSpec.xml +++ b/P5/Source/Specs/schemaSpec.xml @@ -1,11 +1,5 @@ - + schema specification @@ -39,8 +33,8 @@ $Id$ - - + + @@ -57,7 +51,9 @@ $Id$ conforment à ce schéma. especifica los puntos de acceso al esquema, es decir, qué elementos son los permitidos para ser usados como raíz de los documentos conforme al esquema mismo. specifica i punti di accesso allo schema, cioè quali elementi sono consentiti come radice dei documenti conformi allo schema stesso - + + + TEI @@ -109,7 +105,9 @@ $Id$ utiliser lors de la création d'objets dans un schéma . indica la lengua que se utiliza para la creación de objetos en el esquema en el caso en que los nombres de elementos o atributos esten disponibles en otras lenguas. indica la lingua da utilizzare per la creazione di oggetti nello schema nel caso in cui i nomi di elementi o attributi siano disponibili in più lingue - + + + documentation language @@ -130,7 +128,9 @@ $Id$ précise quelle langue utiliser lors de la création de la documentation. indica la lengua que se ha de utilizar para la creación de la documentación en el caso en que las descripciones de elementos, atributos, clases o macros esten disponibles en más lenguas. indica la lingua da utilizzare per la creazione della documentazione nel caso in cui le descrizioni di elementi, attributi, classi o macro siano disponibili in più lingue - + + +

Although multiple languages may be specified, the current TEI ODD processor is only capable of handling one.

diff --git a/P5/Source/Specs/scriptDesc.xml b/P5/Source/Specs/scriptDesc.xml index 41e9ae1346..7772ba6b5e 100644 --- a/P5/Source/Specs/scriptDesc.xml +++ b/P5/Source/Specs/scriptDesc.xml @@ -1,11 +1,5 @@ - + script description @@ -16,16 +10,10 @@ $Id$ - - - + - - - - - - + + @@ -48,4 +36,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/scriptNote.xml b/P5/Source/Specs/scriptNote.xml index 758f6afd04..56fe5e0278 100644 --- a/P5/Source/Specs/scriptNote.xml +++ b/P5/Source/Specs/scriptNote.xml @@ -1,11 +1,5 @@ - + describes a particular script distinguished within @@ -25,4 +19,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/scriptStmt.xml b/P5/Source/Specs/scriptStmt.xml index a5373939fa..675c624be0 100644 --- a/P5/Source/Specs/scriptStmt.xml +++ b/P5/Source/Specs/scriptStmt.xml @@ -1,11 +1,5 @@ - + script statement @@ -33,9 +27,7 @@ a spoken text. - - - + @@ -58,4 +50,4 @@ a spoken text. - \ No newline at end of file + diff --git a/P5/Source/Specs/seal.xml b/P5/Source/Specs/seal.xml index 7a86a8cff3..a3d3a40f01 100644 --- a/P5/Source/Specs/seal.xml +++ b/P5/Source/Specs/seal.xml @@ -1,10 +1,7 @@ - + + + + seal sceau contains a description of one seal or similar applied to the object described @@ -21,48 +18,44 @@ $Id$ - - - - - - + + + + - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + contemporary contemporain specifies whether or not the seal is contemporary with the @@ -74,7 +67,9 @@ $Id$ manuscrit auquel il est attaché. especifica si el sello es o no contemporáneo al objeto al que se ha aplicado. specifica se il sigillo è coevo o meno rispetto all'oggetto al quale è applicato - + + + @@ -104,4 +99,4 @@ Parchment tag on which is written: Woldorp Iohanne G.

- \ No newline at end of file + diff --git a/P5/Source/Specs/sealDesc.xml b/P5/Source/Specs/sealDesc.xml index 92199795e8..9a52b9b57c 100644 --- a/P5/Source/Specs/sealDesc.xml +++ b/P5/Source/Specs/sealDesc.xml @@ -1,11 +1,5 @@ - + seal description @@ -32,20 +26,14 @@ eventualmente con ulteriori elementi decoNote - - - + - - - - - - - - - - + + + + + + @@ -68,4 +56,4 @@ eventualmente con ulteriori elementi decoNote - \ No newline at end of file + diff --git a/P5/Source/Specs/secFol.xml b/P5/Source/Specs/secFol.xml index 5abad24f53..af4f1e1314 100644 --- a/P5/Source/Specs/secFol.xml +++ b/P5/Source/Specs/secFol.xml @@ -1,11 +1,5 @@ - + second folio @@ -43,7 +37,7 @@ $Id$ --> The element should not be used outside of msDesc. - + diff --git a/P5/Source/Specs/secl.xml b/P5/Source/Specs/secl.xml index ee6a262402..7472eb0b19 100644 --- a/P5/Source/Specs/secl.xml +++ b/P5/Source/Specs/secl.xml @@ -1,11 +1,5 @@ - + secluded text @@ -23,18 +17,23 @@ $Id$ one or more words indicating why this text has been secluded, e.g. interpolated etc. - + + + - - - Alphesiboea suos ulta est pro coniuge fratres, - sanguinis et cari vincula rupit amor. - - secl. Pescani + + + + Alphesiboea suos ulta est pro coniuge fratres, + sanguinis et cari vincula rupit amor. + + + secl. Pescani + - \ No newline at end of file + diff --git a/P5/Source/Specs/seg.xml b/P5/Source/Specs/seg.xml index 1154e5583d..0746828f36 100644 --- a/P5/Source/Specs/seg.xml +++ b/P5/Source/Specs/seg.xml @@ -1,5 +1,5 @@ - + arbitrary segment @@ -113,4 +113,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/segmentation.xml b/P5/Source/Specs/segmentation.xml index c898527318..1d2bac5412 100644 --- a/P5/Source/Specs/segmentation.xml +++ b/P5/Source/Specs/segmentation.xml @@ -1,11 +1,5 @@ - + segmentation @@ -30,9 +24,7 @@ $Id$ - - - + @@ -54,4 +46,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/sense.xml b/P5/Source/Specs/sense.xml index b5b714105b..649dec48e8 100644 --- a/P5/Source/Specs/sense.xml +++ b/P5/Source/Specs/sense.xml @@ -1,11 +1,5 @@ - + groups together all information relating to one word sense in a dictionary entry, for @@ -27,16 +21,14 @@ $Id$ - - - - - - - - - - + + + + + + + + @@ -47,7 +39,9 @@ $Id$ indique le niveau de ce sens dans la hiérarchie. la profundidad de anidamiente fornisce il grado di nidificazione del senso - + + + @@ -107,4 +101,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/sequence.xml b/P5/Source/Specs/sequence.xml index c2c397c3e3..6e847b05b1 100644 --- a/P5/Source/Specs/sequence.xml +++ b/P5/Source/Specs/sequence.xml @@ -1,11 +1,5 @@ - + indicates that the constructs referenced by its children form a sequence @@ -26,7 +20,9 @@ $Id$ if false, indicates that component elements of a sequence may occur in any order. - + + + @@ -48,4 +44,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/series.xml b/P5/Source/Specs/series.xml index b4a41cc747..37145a66a4 100644 --- a/P5/Source/Specs/series.xml +++ b/P5/Source/Specs/series.xml @@ -1,11 +1,5 @@ - + series information @@ -30,21 +24,19 @@ - - - - - - - - - - - - - - - + + + + + + + + + + + + + @@ -63,4 +55,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/seriesStmt.xml b/P5/Source/Specs/seriesStmt.xml index 3fed1411af..a3f0247abf 100644 --- a/P5/Source/Specs/seriesStmt.xml +++ b/P5/Source/Specs/seriesStmt.xml @@ -1,18 +1,12 @@ - + series statement mention de collection 연속간행물 진술 集叢陳述 - Angaben zu einer Publikationsreihe + Angaben zu einer Publikationsreihe declaración de serie dichiarazione sulla serie groups information about the series, if any, to which a publication belongs. @@ -21,7 +15,7 @@ $Id$ 연속 간행물에 대한 정보를 모아 놓는다. 若出版品隸屬於某叢書，則在此匯集該叢書的相關資訊。 出版されたシリーズの情報をまとめる。 - umfasst Angaben zu einer Publikationsreihe, zu der eine Veröffentlichung gehört. + umfasst Angaben zu einer Publikationsreihe, zu der eine Veröffentlichung gehört. agrupa información sobre la serie, si la hay, a la que pertenece una publicación. raggruppa le informazioni circa la serie alla quale @@ -32,25 +26,17 @@ $Id$ - - - + - - - - - - - - - - - - - - - + + + + + + + + + @@ -100,4 +86,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/set.xml b/P5/Source/Specs/set.xml index 7c0414a352..b6d62995c3 100644 --- a/P5/Source/Specs/set.xml +++ b/P5/Source/Specs/set.xml @@ -1,11 +1,5 @@ - + setting @@ -37,20 +31,14 @@ $Id$ - - - - - - - - - - - - - - + + + + + + + + @@ -168,4 +156,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/setting.xml b/P5/Source/Specs/setting.xml index 9de8088770..eea67bef97 100644 --- a/P5/Source/Specs/setting.xml +++ b/P5/Source/Specs/setting.xml @@ -1,11 +1,5 @@ - + describes one particular setting in which a language @@ -79,4 +73,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/settingDesc.xml b/P5/Source/Specs/settingDesc.xml index 915dd6d807..a9ef181e2d 100644 --- a/P5/Source/Specs/settingDesc.xml +++ b/P5/Source/Specs/settingDesc.xml @@ -1,83 +1,83 @@ - + - setting description - 무대 기술 - 背景描述 - description du contexte - descripción de realización - descrizione dello scenario - describes the setting or settings within which a + setting description + 무대 기술 + 背景描述 + description du contexte + descripción de realización + descrizione dello scenario + describes the setting or settings within which a language interaction takes place, or other places otherwise referred to in a text, edition, or metadata. - 언어적 상호작용이 발생하는 무대 또는 배경을 산문적 기술로서 또는 일련의 무대 요소로서 + 언어적 상호작용이 발생하는 무대 또는 배경을 산문적 기술로서 또는 일련의 무대 요소로서 기술한다. - 描述語言互動所發生的一個或多個背景，可用一段散文描述或是一系列的背景元素來表達。 - 言語交流が行われた状況設定を、散文または一連の要素settingに + 描述語言互動所發生的一個或多個背景，可用一段散文描述或是一系列的背景元素來表達。 + 言語交流が行われた状況設定を、散文または一連の要素settingに より示す。 - décrit le(s) contexte(s) dans lesquels se situe une + décrit le(s) contexte(s) dans lesquels se situe une interaction linguistique, soit sous la forme d'une description en prose, soit sous celle d'une série d'éléments décrivant le contexte. - describe en prosa, o mediante una serie de + describe en prosa, o mediante una serie de elementos de realización, la realización o realizaciones dentro de las cuales una interacción lingüística tiene lugar. - descrive lo scenario o gli scenari nei quali si + descrive lo scenario o gli scenari nei quali si svolge l'interazione linuistica, sia in forma di prosa descrittiva sia con elementi di scenario. - - - - - - - - - - - - - - - - - - - - -

Texts recorded in the + + + + + + + + + + + + + + + + + + +

Texts recorded in the Canadian Parliament building in Ottawa, between April and November 1988

- - - -

Pierre Mendès France, - Entretiens avec Jean Lacouture (1980-1981 )

 - - - -

文本錄於渥太華的加拿大國會大廈，介於1988年4月至11月間

 - - -

May contain a prose description organized as paragraphs, or a series of + + + + + + +

Pierre Mendès France, + Entretiens avec Jean Lacouture (1980-1981 )

+ + + + + + +

文本錄於渥太華的加拿大國會大廈，介於1988年4月至11月間

+ + + + +

May contain a prose description organized as paragraphs, or a series of setting elements. If used to record not settings of language interactions, but other places mentioned in the text, then place optionally grouped by listPlace inside standOff should be preferred.

- - -

Peut contenir un texte organisé en paragraphes ou une série d'éléments + + +

Peut contenir un texte organisé en paragraphes ou une série d'éléments setting.

- - -

段落レベルの散文、または一連の要素settingを含むかもしれない。

- - - - - - \ No newline at end of file + + +

段落レベルの散文、または一連の要素settingを含むかもしれない。

+ + + + + + diff --git a/P5/Source/Specs/settlement.xml b/P5/Source/Specs/settlement.xml index dbe0208625..28792f0ea5 100644 --- a/P5/Source/Specs/settlement.xml +++ b/P5/Source/Specs/settlement.xml @@ -1,10 +1,7 @@ - + + + + settlement lieu de peuplement contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. @@ -29,35 +26,35 @@ $Id$ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -87,4 +84,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/sex.xml b/P5/Source/Specs/sex.xml index ecf477a80b..979a3a80fa 100644 --- a/P5/Source/Specs/sex.xml +++ b/P5/Source/Specs/sex.xml @@ -1,10 +1,7 @@ - + + + + sex sexe specifies the sex of an organism. @@ -25,40 +22,38 @@ $Id$ - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + supplies a coded value for sex @@ -108,4 +103,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/shift.xml b/P5/Source/Specs/shift.xml index 51f6dba6e8..204651a541 100644 --- a/P5/Source/Specs/shift.xml +++ b/P5/Source/Specs/shift.xml @@ -1,11 +1,5 @@ - + shift @@ -24,7 +18,9 @@ utterances by any one speaker changes. - + + + @@ -43,7 +39,9 @@ paralinguistic feature. caractéristique paralinguistique. enunciado paralingüístico fenomeno paralinguistico - + + + speed of utterance. @@ -110,8 +108,10 @@ paralinguistic feature. caractéristique paralinguistique en question. especifica el nuevo estado del fenómeno paralingüístico especificado. specifica il nuovo stato del fenomeno paralinguistico specificato - - normal + + + + normal

Some possible values for this attribute are provided in section . The special value normal should be used to indicate that the feature concerned ceases to be remarkable at this point. In earlier versions of these Guidelines, a null value for this attribute was understood to have the same effect: this practice is now deprecated and will be removed at a future release. @@ -129,7 +129,6 @@ paralinguistic feature. - Elizabeth @@ -173,4 +172,4 @@ very loudly.

- \ No newline at end of file + diff --git a/P5/Source/Specs/sic.xml b/P5/Source/Specs/sic.xml index 4b52220db7..861abc25c1 100644 --- a/P5/Source/Specs/sic.xml +++ b/P5/Source/Specs/sic.xml @@ -1,11 +1,5 @@ - + Latin for thus or so @@ -107,4 +101,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/signatures.xml b/P5/Source/Specs/signatures.xml index a85faf4f06..4e1b79e727 100644 --- a/P5/Source/Specs/signatures.xml +++ b/P5/Source/Specs/signatures.xml @@ -1,11 +1,5 @@ - + signatures diff --git a/P5/Source/Specs/signed.xml b/P5/Source/Specs/signed.xml index 32fc5b8cd6..0d2c6415e4 100644 --- a/P5/Source/Specs/signed.xml +++ b/P5/Source/Specs/signed.xml @@ -1,11 +1,5 @@ - + signature @@ -64,4 +58,4 @@ dedicatory epistle, or other division of a text. - \ No newline at end of file + diff --git a/P5/Source/Specs/soCalled.xml b/P5/Source/Specs/soCalled.xml index 8b7341c2d3..3b117fa33f 100644 --- a/P5/Source/Specs/soCalled.xml +++ b/P5/Source/Specs/soCalled.xml @@ -1,11 +1,5 @@ - + so called @@ -54,4 +48,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/socecStatus.xml b/P5/Source/Specs/socecStatus.xml index 51c75f12c1..106dd22609 100644 --- a/P5/Source/Specs/socecStatus.xml +++ b/P5/Source/Specs/socecStatus.xml @@ -1,10 +1,7 @@ - + + + + socio-economic status statut socio-économique 사회-경제적 지위 @@ -30,40 +27,38 @@ $Id$ - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + identifies the classification system or taxonomy in use, for example by pointing to a locally-defined taxonomy element or by supplying a URI for an externally-defined system. identifie le système de classification ou la taxinomie utilisés. 사용 중인 분류 체계 또는 분류법을 식별한다. @@ -71,7 +66,9 @@ $Id$ 使われた分類システムを示す。 identifica el sistema de clasificación o de taxonomía empleado. identifica il sistema di classificazione o la tassonomia utilizzati - + + + identifies a status code defined within the classification system or taxonomy defined by the scheme attribute. @@ -85,7 +82,9 @@ $Id$ corrisponde a un codice relativo alla condizione socio-economica definito nel sistema di classificazione o tassonomia stabiliti dall'attributo source - + + + @@ -140,4 +139,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/sound.xml b/P5/Source/Specs/sound.xml index 3a943e8f3e..4361d3fadc 100644 --- a/P5/Source/Specs/sound.xml +++ b/P5/Source/Specs/sound.xml @@ -1,11 +1,5 @@ - + sound @@ -40,7 +34,9 @@ $Id$ spéciaux, etc. classifica il tipo di suono, ad esempio musica, effetto speciale, ecc. - + + + indicates whether the sound overlaps the surrounding speeches or interrupts them. @@ -53,7 +49,9 @@ $Id$ interrompt. indica se il suono si accavalla con le battute o se le interrompe - + + +

The value true indicates that the sound is heard between the surrounding speeches; the value false indicates that the sound overlaps one or more of the @@ -139,4 +137,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/source.xml b/P5/Source/Specs/source.xml index 8aacb9e2d5..24e9dfe8cd 100644 --- a/P5/Source/Specs/source.xml +++ b/P5/Source/Specs/source.xml @@ -1,11 +1,5 @@ - + source @@ -45,4 +39,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/sourceDesc.xml b/P5/Source/Specs/sourceDesc.xml index 165b4bf0ff..caa3e87ef8 100644 --- a/P5/Source/Specs/sourceDesc.xml +++ b/P5/Source/Specs/sourceDesc.xml @@ -1,11 +1,5 @@ - + source description @@ -14,7 +8,7 @@ $Id$ descripción de la fuente descrizione della fonte - Beschreibung der Quellen + Beschreibung der Quellen describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. @@ -24,25 +18,25 @@ $Id$ 전자 파일을 생성하거나 도출한 원전 텍스트에 대한 기술을 제시한다. 提供所製電子文件的一個或數個來源文件的書目描述。 電子テキストが作られた元テキストの情報を示す。 - beschreibt die Quelle, von der sich der elektronische Text ableitet. + beschreibt die Quelle, von der sich der elektronische Text ableitet. Üblicherweise eine bibliografische Beschreibung im Falle eines digitalisierten Textes oder eine Bezeichnung wie "born digital" für einen nur in elektronischer Form vorliegenden Text. proporciona una descripción del texto (o textos) fuente del que un texto electrónico deriva o ha sido generado. fornisce una descrizione relativa alla o alle fonti da - cui è derivato o generato un documento elettronico. + cui è derivato o generato un documento elettronico. - - - - - - + + + + + + @@ -78,4 +72,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/sourceDoc.xml b/P5/Source/Specs/sourceDoc.xml index 1954c104ce..eb79c801bb 100644 --- a/P5/Source/Specs/sourceDoc.xml +++ b/P5/Source/Specs/sourceDoc.xml @@ -1,18 +1,11 @@ - + contains a transcription or other representation of a single source document potentially forming part of a dossier génétique or collection of sources. - -dossier génétique（生成文書）、あるいは資料のコレクションの一部を潜在的に形成し得る単一の資料文書の翻刻やその他の表現を含む。 + dossier génétique（生成文書）、あるいは資料のコレクションの一部を潜在的に形成し得る単一の資料文書の翻刻やその他の表現を含む。 diff --git a/P5/Source/Specs/sp.xml b/P5/Source/Specs/sp.xml index e99461b992..104f1b6481 100644 --- a/P5/Source/Specs/sp.xml +++ b/P5/Source/Specs/sp.xml @@ -1,11 +1,5 @@ - + speech diff --git a/P5/Source/Specs/spGrp.xml b/P5/Source/Specs/spGrp.xml index 0376a3b5aa..7256ded5e2 100644 --- a/P5/Source/Specs/spGrp.xml +++ b/P5/Source/Specs/spGrp.xml @@ -1,11 +1,5 @@ - + speech group @@ -20,16 +14,12 @@ - - - - - - - - - - + + + + + + @@ -83,4 +73,4 @@ young man would present to his lady love. It makes me blush! - \ No newline at end of file + diff --git a/P5/Source/Specs/space.xml b/P5/Source/Specs/space.xml index 06930970fe..ac27f7d18c 100644 --- a/P5/Source/Specs/space.xml +++ b/P5/Source/Specs/space.xml @@ -1,11 +1,5 @@ - + space @@ -23,7 +17,7 @@ $Id$ - + @@ -43,7 +37,9 @@ $Id$ indique si l'espace est vertical ou horizontal. indica si el espacio es vertical u horizontal. indica se lo spazio è orizzontale o verticale - + + + the space is horizontal. diff --git a/P5/Source/Specs/span.xml b/P5/Source/Specs/span.xml index 60c8cda740..328b765562 100644 --- a/P5/Source/Specs/span.xml +++ b/P5/Source/Specs/span.xml @@ -1,11 +1,5 @@ - + associates an interpretative annotation directly with a span of text. @@ -67,7 +61,9 @@ The attributes @to and @from on may each contain only a single valueto, especifica el pasaje entero. indica l'inizio di un brano annotato; se non è accompagnato dall'attributo to indica l'inero brano - + + + gives the identifier of the node which is the end-point of the span of text being annotated. @@ -77,7 +73,9 @@ The attributes @to and @from on may each contain only a single valuespécifie la fin du passage annoté. especifica el final del pasaje que se anota. indica la fine del brano annotato - + + + @@ -109,4 +107,4 @@ The attributes @to and @from on may each contain only a single value - \ No newline at end of file + diff --git a/P5/Source/Specs/spanGrp.xml b/P5/Source/Specs/spanGrp.xml index a028678bc1..3752f75319 100644 --- a/P5/Source/Specs/spanGrp.xml +++ b/P5/Source/Specs/spanGrp.xml @@ -1,11 +1,5 @@ - + span group @@ -27,7 +21,7 @@ $Id$ - + @@ -55,4 +49,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/speaker.xml b/P5/Source/Specs/speaker.xml index 929d53dfbc..93ddbbaf92 100644 --- a/P5/Source/Specs/speaker.xml +++ b/P5/Source/Specs/speaker.xml @@ -1,17 +1,11 @@ - + locuteur 講者 - Sprecher + Sprecher contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment. forme particulière de titre ou de marque qui donne le diff --git a/P5/Source/Specs/specDesc.xml b/P5/Source/Specs/specDesc.xml index 67f15e8be5..745e1c1d88 100644 --- a/P5/Source/Specs/specDesc.xml +++ b/P5/Source/Specs/specDesc.xml @@ -1,11 +1,5 @@ - + specification description @@ -29,7 +23,9 @@ $Id$ - + + + identifier @@ -50,7 +46,9 @@ $Id$ que se está describiendo. assegna un identificatore all'elemento o alla classe per i quali deve essere fornita una descrizione - + + + @@ -61,8 +59,12 @@ $Id$ -

The value should match the ident of a documentary element (that is, a member of att.identified).

 -

Il valore dovrebbe essere lo stesso dell'ident di un elemento di documentazione (vale a dire, il membro di att.identified).

 + +

The value should match the ident of a documentary element (that is, a member of att.identified).

+ + +

Il valore dovrebbe essere lo stesso dell'ident di un elemento di documentazione (vale a dire, il membro di att.identified).

+ attributes @@ -81,7 +83,9 @@ $Id$ proporcionar una descripción. indica dei nomi di attributi per i quali devono essere fornite delle descrizioni - + + + @@ -156,4 +160,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/specGrp.xml b/P5/Source/Specs/specGrp.xml index 61e2a04a15..5b70adcaf4 100644 --- a/P5/Source/Specs/specGrp.xml +++ b/P5/Source/Specs/specGrp.xml @@ -1,11 +1,5 @@ - + specification group @@ -115,4 +109,4 @@ contains specifications for the elements - \ No newline at end of file + diff --git a/P5/Source/Specs/specGrpRef.xml b/P5/Source/Specs/specGrpRef.xml index 14adf6a8c1..3f722d77af 100644 --- a/P5/Source/Specs/specGrpRef.xml +++ b/P5/Source/Specs/specGrpRef.xml @@ -1,11 +1,5 @@ - + reference to a specification group @@ -29,7 +23,9 @@ $Id$ - + + + points at the specification group which logically belongs here. @@ -42,7 +38,9 @@ $Id$ corresponde a ese punto en cuestión. indica il gruppo di istruzioni che per logica corrisponde al punto in questione - + + + @@ -73,7 +71,7 @@ $Id$

- + @@ -129,4 +127,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/specList.xml b/P5/Source/Specs/specList.xml index 6c2be80d45..613b06ce2c 100644 --- a/P5/Source/Specs/specList.xml +++ b/P5/Source/Specs/specList.xml @@ -1,11 +1,5 @@ - + specification list @@ -26,9 +20,7 @@ $Id$ - - - + @@ -57,4 +49,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/sponsor.xml b/P5/Source/Specs/sponsor.xml index 8b637f6e59..3913a7df43 100644 --- a/P5/Source/Specs/sponsor.xml +++ b/P5/Source/Specs/sponsor.xml @@ -1,10 +1,7 @@ - + + + + sponsor commanditaire Förderer @@ -14,7 +11,7 @@ $Id$ 후원 조직 또는 기관의 이름을 명시한다. 標明贊助的組織或機構名稱。 支援を行う組織や団体の名前を示す。 - gibt den Namen einer Organisation oder Institution an, die als Förderer auftritt. + gibt den Namen einer Organisation oder Institution an, die als Förderer auftritt. especifica el nombre de la organización o institución responsable. indica il nome di un'organizzazione o istituzzione @@ -30,35 +27,35 @@ $Id$ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -100,7 +97,7 @@ $Id$

-

+

Förderer übernehmen die inhaltliche Verantwortung für ein Projekt. Sie sind zu unterscheiden von Geldgebern (siehe funder-Element), die nicht notwendigerweise die inhaltliche Verantwortung oder Betreuung übernehmen.

@@ -108,4 +105,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/stage.xml b/P5/Source/Specs/stage.xml index 544ee76cb1..80489bc92d 100644 --- a/P5/Source/Specs/stage.xml +++ b/P5/Source/Specs/stage.xml @@ -1,11 +1,5 @@ - + stage direction @@ -46,7 +40,9 @@ indica el tipo de acotación. indica il tipo di direttiva di scena beschreibt die Art der Regieanweisung. - + + + describes a setting. @@ -148,29 +144,35 @@ mehrere der oben angeführten Funktionen. -

If the value mixed is used, it must be the only value. Multiple values may however be supplied - if a single stage direction performs multiple functions, for example is both an entrance and a modifier.

-

Der Wert mixed kann nur alleine benutzt werden. Mehrere Werte können in Kombination + +

If the value mixed is used, it must be the only value. Multiple values may however be supplied + if a single stage direction performs multiple functions, for example is both an entrance and a modifier.

+ + +

Der Wert mixed kann nur alleine benutzt werden. Mehrere Werte können in Kombination eingesetzt werden, wenn eine einzelne Regieanweisung unterschiedliche Funktionen erfüllt, z. B. - sowohl einen Auftritt als auch eine Figurenbeschreibung.

 + sowohl einen Auftritt als auch eine Figurenbeschreibung.

+ A curtain being drawn. Music - Enter Husband as being thrown off his horse and falls. + Enter Husband as being thrown off his horse and falls. + Exit pursued by a bear. He quickly takes the stone out. To Lussurioso. - Having had enough, and embarrassed for the family. + Having had enough, and embarrassed for the family. + Disguised as Ansaldo. - Enter Latrocinio disguised as an empiric + Enter Latrocinio disguised as an empiric + At a window. Aside. - Behold. Here the vpper part of the Scene open'd; when @@ -178,8 +180,9 @@ two semicircular benches, one aboue another: who sate thus till the rest of the Prologue was spoken, which being ended, they descended in order within the Scene, whiles the Musicke plaid Our - Poet knowing our free hearts - + Poet knowing our free hearts + + La scène est dans une place de ville. @@ -223,4 +226,4 @@ by the stage direction.

- \ No newline at end of file + diff --git a/P5/Source/Specs/stamp.xml b/P5/Source/Specs/stamp.xml index 4e993a006e..a86282c4f3 100644 --- a/P5/Source/Specs/stamp.xml +++ b/P5/Source/Specs/stamp.xml @@ -1,10 +1,7 @@ - + + + + stamp cachet contains a word or phrase describing a stamp or similar device. @@ -25,35 +22,35 @@ $Id$ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + diff --git a/P5/Source/Specs/standOff.xml b/P5/Source/Specs/standOff.xml index 3436e774c9..06364cfc58 100644 --- a/P5/Source/Specs/standOff.xml +++ b/P5/Source/Specs/standOff.xml @@ -1,17 +1,12 @@ - + + - + Functions as a container element for linked data, contextual information, and stand-off annotations embedded in a TEI document. - - リンクト・データや文脈情報、TEI文書に埋め込まれたスタンドオフ・アノテーションをコンテナ化する要素として機能する。 + + リンクト・データや文脈情報、TEI文書に埋め込まれたスタンドオフ・アノテーションをコンテナ化する要素として機能する。 @@ -32,10 +27,11 @@ See the file COPYING.txt for details

This example shows an encoding of morphosyntactic features similar to the encoding system used by ISO 24611 (MAF).

- + - + + + @@ -61,28 +57,52 @@ See the file COPYING.txt for details - I - + + I + + + + - want - + + want + + + + - to - + + to + + + + - put up - + + put up + + + + - new - + + new + + + + - wallpaper - + + wallpaper + + + + @@ -91,36 +111,37 @@ See the file COPYING.txt for details

This example shows an encoding of contextual information which is referred to from the main text.

- + - - - - - Atlanta - - Georgia - United States of America - 33.755 -84.39 - - - - - Birmingham - - Alabama - United States of America - 33.653333 -86.808889 - - - - - - - - -

Moreover, I am congnizantcognizant of the interrelatedness of all communities and + + + + + + + Atlanta + + Georgia + United States of America + 33.755 -84.39 + + + + + Birmingham + + Alabama + United States of America + 33.653333 -86.808889 + + + + + + + + +

Moreover, I am congnizantcognizant of the interrelatedness of all communities and states. I cannot sit idly by in Atlanta and not be concerned about what happens in Birmingham. Injustice anywhere is a threat to justice everywhere. We are caught in an inescapable network of mutuality, tied in a single garment @@ -128,9 +149,9 @@ See the file COPYING.txt for details again can we afford to live with the narrow, provincial outside agitator idea. Anyone who lives inside the United States can never be considered an outsider anywhere in this country.

- - - + + + diff --git a/P5/Source/Specs/state.xml b/P5/Source/Specs/state.xml index 5c1846f337..6736230ef0 100644 --- a/P5/Source/Specs/state.xml +++ b/P5/Source/Specs/state.xml @@ -1,10 +1,7 @@ - + + + + state statut contains a description of some status or quality attributed to a person, place, or organization often at some specific time or for a specific date range. @@ -51,42 +48,42 @@ $Id$ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + + + @@ -124,9 +121,9 @@ $Id$ - - - + + + @@ -143,4 +140,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/stdVals.xml b/P5/Source/Specs/stdVals.xml index 20b8e4a325..c034363b42 100644 --- a/P5/Source/Specs/stdVals.xml +++ b/P5/Source/Specs/stdVals.xml @@ -1,11 +1,5 @@ - + standard values @@ -33,9 +27,7 @@ $Id$ - - - + @@ -62,4 +54,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/street.xml b/P5/Source/Specs/street.xml index 13472c54d1..0ff0d13124 100644 --- a/P5/Source/Specs/street.xml +++ b/P5/Source/Specs/street.xml @@ -1,11 +1,5 @@ - + contains a full street address including any name or number identifying a @@ -78,4 +72,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/stress.xml b/P5/Source/Specs/stress.xml index 59a9f9713f..f83183bc89 100644 --- a/P5/Source/Specs/stress.xml +++ b/P5/Source/Specs/stress.xml @@ -1,11 +1,5 @@ - + stress @@ -45,4 +39,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/string.xml b/P5/Source/Specs/string.xml index 93aad81c84..5dfd6bbc0a 100644 --- a/P5/Source/Specs/string.xml +++ b/P5/Source/Specs/string.xml @@ -1,11 +1,5 @@ - + string value @@ -55,4 +49,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/styleDefDecl.xml b/P5/Source/Specs/styleDefDecl.xml index cb5a058be8..4df4f508b0 100644 --- a/P5/Source/Specs/styleDefDecl.xml +++ b/P5/Source/Specs/styleDefDecl.xml @@ -1,11 +1,5 @@ - + style definition language declaration @@ -19,9 +13,7 @@ $Id$ - - - + @@ -36,4 +28,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/subc.xml b/P5/Source/Specs/subc.xml index 23939e7f55..c3c421a2b1 100644 --- a/P5/Source/Specs/subc.xml +++ b/P5/Source/Specs/subc.xml @@ -1,11 +1,5 @@ - + subcategorization @@ -28,7 +22,6 @@ $Id$ - @@ -73,4 +66,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/subst.xml b/P5/Source/Specs/subst.xml index e4ee36cd8c..13ae0d7bf1 100644 --- a/P5/Source/Specs/subst.xml +++ b/P5/Source/Specs/subst.xml @@ -1,11 +1,5 @@ - + substitution @@ -27,7 +21,7 @@ $Id$ - + @@ -72,4 +66,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/substJoin.xml b/P5/Source/Specs/substJoin.xml index 47eab419d9..6c77826e60 100644 --- a/P5/Source/Specs/substJoin.xml +++ b/P5/Source/Specs/substJoin.xml @@ -1,5 +1,5 @@ - + substitution join @@ -12,7 +12,7 @@ - + @@ -26,4 +26,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/summary.xml b/P5/Source/Specs/summary.xml index b72f02df49..273d19e4ec 100644 --- a/P5/Source/Specs/summary.xml +++ b/P5/Source/Specs/summary.xml @@ -1,11 +1,5 @@ - + contains an overview of the available @@ -49,4 +43,4 @@ fonts. - \ No newline at end of file + diff --git a/P5/Source/Specs/superEntry.xml b/P5/Source/Specs/superEntry.xml index d414afabf3..5a28e421cc 100644 --- a/P5/Source/Specs/superEntry.xml +++ b/P5/Source/Specs/superEntry.xml @@ -1,11 +1,5 @@ - + super entry @@ -30,12 +24,8 @@ $Id$ - - - - - - + + @@ -126,4 +116,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/supplied.xml b/P5/Source/Specs/supplied.xml index cf10b33aa8..1956d58582 100644 --- a/P5/Source/Specs/supplied.xml +++ b/P5/Source/Specs/supplied.xml @@ -1,11 +1,5 @@ - + supplied @@ -38,11 +32,13 @@ $Id$ 說明該文件當時必須補充的原因。 該テキストが付加された理由を示す。 donne la raison pour laquelle on a dû restituer le texte. - explica los motivos de dicha inserción. spiega i motivi di tale inserimento - + + + @@ -80,4 +76,4 @@ element is appropriate for which circumstance.

- \ No newline at end of file + diff --git a/P5/Source/Specs/support.xml b/P5/Source/Specs/support.xml index b03ddb462b..9c7b5f7488 100644 --- a/P5/Source/Specs/support.xml +++ b/P5/Source/Specs/support.xml @@ -1,11 +1,5 @@ - + support @@ -65,4 +59,4 @@ etc. which make up the physical support for the written part of a manuscript or - \ No newline at end of file + diff --git a/P5/Source/Specs/supportDesc.xml b/P5/Source/Specs/supportDesc.xml index 60e6e55ce5..28ef664bb7 100644 --- a/P5/Source/Specs/supportDesc.xml +++ b/P5/Source/Specs/supportDesc.xml @@ -1,11 +1,5 @@ - + support description @@ -49,7 +43,9 @@ $Id$ le matériau qui a principalement servi pour fabriquer le support. un nombre breve definido en el ámbito de un proyecto y referente al material que costituye la mayor parte del suporte. un nome breve definito nell'ambito di un progetto e riferito al materiale che costituisce la maggior parte del supporto - + + + diff --git a/P5/Source/Specs/surface.xml b/P5/Source/Specs/surface.xml index 70ee7aa2f3..f20cd80ba7 100644 --- a/P5/Source/Specs/surface.xml +++ b/P5/Source/Specs/surface.xml @@ -1,11 +1,5 @@ - + defines a written surface as a two-dimensional @@ -29,26 +23,20 @@ celui-ci. - - - - - - - + + + + + - - - - - - - - - - - - + + + + + + + + @@ -56,7 +44,9 @@ celui-ci. describes the method by which this surface is or was connected to the main surface - + + + glued in place @@ -73,7 +63,9 @@ celui-ci. indicates whether the surface is attached and folded in such a way as to provide two writing surfaces - + + + @@ -123,4 +115,4 @@ are also understood with reference to this same coordinate system.-->

- \ No newline at end of file + diff --git a/P5/Source/Specs/surfaceGrp.xml b/P5/Source/Specs/surfaceGrp.xml index 5962f5aa49..d172ffc034 100644 --- a/P5/Source/Specs/surfaceGrp.xml +++ b/P5/Source/Specs/surfaceGrp.xml @@ -1,11 +1,5 @@ - + surface group @@ -14,19 +8,17 @@ $Id$ wishes to treat as a single unit. - + - - - - - - - + + + + + @@ -51,4 +43,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/surname.xml b/P5/Source/Specs/surname.xml index eb308b00a0..6c0f50941b 100644 --- a/P5/Source/Specs/surname.xml +++ b/P5/Source/Specs/surname.xml @@ -1,11 +1,5 @@ - + surname @@ -46,4 +40,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/surplus.xml b/P5/Source/Specs/surplus.xml index b9e7f521e1..e60978c86b 100644 --- a/P5/Source/Specs/surplus.xml +++ b/P5/Source/Specs/surplus.xml @@ -1,11 +1,5 @@ - + surplus @@ -28,7 +22,9 @@ $Id$ repeated, interpolated etc. indique les raisons pour lesquelles on considère cette partie de texte comme superflue. - + + + @@ -39,4 +35,4 @@ Sydney Smith - \ No newline at end of file + diff --git a/P5/Source/Specs/surrogates.xml b/P5/Source/Specs/surrogates.xml index b6a26eadff..b7ae70e701 100644 --- a/P5/Source/Specs/surrogates.xml +++ b/P5/Source/Specs/surrogates.xml @@ -1,11 +1,5 @@ - + surrogates @@ -79,4 +73,4 @@ may exist in the holding institution or elsewhere. - \ No newline at end of file + diff --git a/P5/Source/Specs/syll.xml b/P5/Source/Specs/syll.xml index 61f673b947..c5ad5c2d89 100644 --- a/P5/Source/Specs/syll.xml +++ b/P5/Source/Specs/syll.xml @@ -1,11 +1,5 @@ - + syllabification @@ -57,4 +51,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/symbol.xml b/P5/Source/Specs/symbol.xml index 5b281f3657..b50ac1f1b2 100644 --- a/P5/Source/Specs/symbol.xml +++ b/P5/Source/Specs/symbol.xml @@ -1,11 +1,5 @@ - + symbolic value @@ -28,7 +22,9 @@ $Id$ - + + + supplies a symbolic value for the feature, one of a finite list that @@ -40,7 +36,9 @@ may be specified in a feature declaration. extraite d'une liste finie qui peut être spécifiée dans une déclaration de traits. proporciona el valor simbólico para un rasgo, uno de una lista finita que puede ser especificada en una declaración de rasgo. fornisce il valore simbolico del tratto, un valore da una lista che può essere specigicata in una dichiarazione di tratti. - + + + @@ -60,4 +58,4 @@ may be specified in a feature declaration. - \ No newline at end of file + diff --git a/P5/Source/Specs/table.xml b/P5/Source/Specs/table.xml index ab11d7c54b..f1202b38ca 100644 --- a/P5/Source/Specs/table.xml +++ b/P5/Source/Specs/table.xml @@ -1,11 +1,5 @@ - + table @@ -25,39 +19,27 @@ $Id$ - + - - - - - - + + + + - - - + - - - - - - + + - - - - - - + + @@ -73,11 +55,13 @@ $Id$ indica el número de filas en una tabla. indica il numero di righe della tabella. gibt die Anzahl der Tabellenzeilen an. - + + +

If no number is supplied, an application must calculate the number of rows.

-

Rows should be presented from top to bottom.

+

Rows should be presented from top to bottom.

Les rangées sont ordonnées de haut en bas

@@ -108,14 +92,17 @@ $Id$ indica il numero di colonne in ciascuna riga della tabella- gibt die Anzahl der Tabellenspalten an. - + + +

If no number is supplied, an application must calculate the number of columns.

-

Within each row, columns should be presented left to right.

+

Within each row, columns should be presented left to right.

 -

Si aucun nombre n'est fourni, une application doit calculer le nombre de colonnes.

Dans chaque rangée, les colonnes sont ordonnées de gauche à droite.

+

Si aucun nombre n'est fourni, une application doit calculer le nombre de colonnes.

+

Dans chaque rangée, les colonnes sont ordonnées de gauche à droite.

行中において、列は左から右への順番で示される。

@@ -239,4 +226,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/tag.xml b/P5/Source/Specs/tag.xml index 7ab9d5d2b3..c75eea817e 100644 --- a/P5/Source/Specs/tag.xml +++ b/P5/Source/Specs/tag.xml @@ -1,11 +1,5 @@ - + tag @@ -39,7 +33,9 @@ $Id$ indicates the type of XML tag intended indique quel type de balise XML est prévu. indica di quale tipo di marcatore XML si tratta - + + + a start-tag, with delimiters < and > is intended @@ -96,7 +92,9 @@ $Id$ es definido. fornisce il nome dello schema in cui è definito il nome - + + + TEI diff --git a/P5/Source/Specs/tagUsage.xml b/P5/Source/Specs/tagUsage.xml index 6289a27d35..c3d0b55d1b 100644 --- a/P5/Source/Specs/tagUsage.xml +++ b/P5/Source/Specs/tagUsage.xml @@ -1,11 +1,5 @@ - + element usage @@ -52,7 +46,9 @@ $Id$ indicado mediante una etiqueta. il nome (identificatore generico) dell'elemento indicato dal marcatore. - + + + specifies the number of occurrences of this element within the text. @@ -66,7 +62,9 @@ $Id$ determinado aparece en el texto. specifica il numero di occorrenze dell'elemento nel testo. - + + + with unique identifier @@ -89,7 +87,9 @@ $Id$ en el texto con un valor distintivo apara el atributo global xml:id. specifica il numero di occorrenze dell'elemento nel testo e che reca un valore distinto dall'attributo globale xml:id. - + + + @@ -131,4 +131,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/tagsDecl.xml b/P5/Source/Specs/tagsDecl.xml index 0b8997623a..d38e2655cd 100644 --- a/P5/Source/Specs/tagsDecl.xml +++ b/P5/Source/Specs/tagsDecl.xml @@ -1,11 +1,5 @@ - + tagging declaration @@ -29,7 +23,7 @@ $Id$ - + @@ -39,9 +33,11 @@ $Id$ indicates whether the element types listed exhaustively include all those found within text, or represent only a subset. - + + + -

TEI recommended practice is to specify this attribute. When +

TEI recommended practice is to specify this attribute. When the tagUsage elements inside tagsDecl are used to list each of the element types in the associated text, the value should be given as false. diff --git a/P5/Source/Specs/taxonomy.xml b/P5/Source/Specs/taxonomy.xml index 3badf02763..9fd403576c 100644 --- a/P5/Source/Specs/taxonomy.xml +++ b/P5/Source/Specs/taxonomy.xml @@ -1,11 +1,5 @@ - + taxonomy @@ -240,4 +234,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/tech.xml b/P5/Source/Specs/tech.xml index 44c3593e67..246531778d 100644 --- a/P5/Source/Specs/tech.xml +++ b/P5/Source/Specs/tech.xml @@ -1,11 +1,5 @@ - + technical stage direction @@ -41,7 +35,9 @@ meant for the actors. catégorise l'indication technique de mise en scène. classifica l'indicazione di scena tecnica. - + + + a lighting cue @@ -97,8 +93,9 @@ technical direction applies. identifie la ou les représentations auxquelles s'appliquent ces indications techniques. identifica la messa in scena o le messe in scena a cui si applicano le indicazioni tecniche. - - + + + @@ -119,4 +116,4 @@ technical direction applies. - \ No newline at end of file + diff --git a/P5/Source/Specs/teiCorpus.xml b/P5/Source/Specs/teiCorpus.xml index be5c7dc1b4..6bec188d40 100644 --- a/P5/Source/Specs/teiCorpus.xml +++ b/P5/Source/Specs/teiCorpus.xml @@ -1,11 +1,5 @@ - + TEI corpus @@ -56,7 +50,9 @@ La versión del esquema TEI La versione dello schema TEI gibt die Versionsnummer der TEI-Richtlinien an, gegen die dieses Dokument validiert wird. - + + +

Major editions of the Guidelines have long been informally referred to by a name made up of the letter P (for Proposal) followed by a digit. The current release is one of the many @@ -173,4 +169,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/teiHeader.xml b/P5/Source/Specs/teiHeader.xml index c6de7fdce7..4bdc2278c1 100644 --- a/P5/Source/Specs/teiHeader.xml +++ b/P5/Source/Specs/teiHeader.xml @@ -1,11 +1,5 @@ - + TEI header @@ -24,7 +18,7 @@ $Id$ 제공한다. 在所有符合TEI標準的文本起始的電子題名頁當中提供敘述性以及宣告性的資訊。 全てのTEI準拠テキストが伴う、電子版のタイトルページを構成する、記述 的・宣言的情報を示す。 - beinhaltet beschreibende und erklärende Metadaten, die einer digitalen Ressource oder einer Sammlung von Ressourcen vorangestellt sind. + beinhaltet beschreibende und erklärende Metadaten, die einer digitalen Ressource oder einer Sammlung von Ressourcen vorangestellt sind. proporciona información descriptiva y declarativa de una página de título electrónico prefijada como un texto conforme a TEI. fornisce informazioni descrittive e dichiarative che @@ -205,10 +199,10 @@ document.-->

document.-->

 -

Eines der wenigen Elemente, die verpflichtend für ein valides TEI-Dokument sind.

+

Eines der wenigen Elemente, die verpflichtend für ein valides TEI-Dokument sind.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.authority.xml b/P5/Source/Specs/teidata.authority.xml index 6720a61dbc..59a4da3a1d 100644 --- a/P5/Source/Specs/teidata.authority.xml +++ b/P5/Source/Specs/teidata.authority.xml @@ -1,12 +1,7 @@ - + - + defines attribute values which derive from an authority list, which may be an enumerated list defined in the document's schema, a list or taxonomy elsewhere in the document, or an online taxonomy, gazetteer, or other authority. @@ -18,7 +13,6 @@ See the file COPYING.txt for details

Attribute values with this datatype should either come from a value list in the attribute - specification (teidata.enumerated) or be a valid URI (teidata.pointer).

+ specification (teidata.enumerated) or be a valid URI (teidata.pointer).

 diff --git a/P5/Source/Specs/teidata.certainty.xml b/P5/Source/Specs/teidata.certainty.xml index 2797de8577..ab110e2d3e 100644 --- a/P5/Source/Specs/teidata.certainty.xml +++ b/P5/Source/Specs/teidata.certainty.xml @@ -1,9 +1,5 @@ - + defines the range of attribute values expressing a degree of certainty. diff --git a/P5/Source/Specs/teidata.count.xml b/P5/Source/Specs/teidata.count.xml index 7b428db4c4..fa8874ebcf 100644 --- a/P5/Source/Specs/teidata.count.xml +++ b/P5/Source/Specs/teidata.count.xml @@ -1,9 +1,5 @@ - + defines the range of attribute values used for a non-negative @@ -17,15 +13,15 @@ integer value used as a count. define la gama de valores de atributos para números enteros no negativos usados como un cálculo. definisce la gamma di valori di attributi usati per un numero intero non negativo impiegato come computo - - + + -

Any positive integer value or zero is permitted

+

Any positive integer value or zero is permitted

 -

非負整数値のみが許される。

+

非負整数値のみが許される。

 -

Seules des valeurs positives entières sont autorisées.

+

Seules des valeurs positives entières sont autorisées.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.duration.iso.xml b/P5/Source/Specs/teidata.duration.iso.xml index 49127a8f98..c0b7aea644 100644 --- a/P5/Source/Specs/teidata.duration.iso.xml +++ b/P5/Source/Specs/teidata.duration.iso.xml @@ -1,9 +1,5 @@ - + defines the range of attribute values available for representation of a duration in time @@ -15,45 +11,45 @@ See the file COPYING.txt for details define la gama de valores de atributos posibles para representar la duración en el tiempo usando formatos estàndards ISO 8601. - - + + - - - + + + - - a day and a half - + + a day and a half + - - a fortnight - + + a fortnight + - - - + + + - - une journee et demie - + + une journee et demie + - - une quinzaine - + + une quinzaine + - - - + + + -

A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the +

A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the last, which may have a decimal component (using either . or , as the decimal point; @@ -61,19 +57,19 @@ See the file COPYING.txt for details pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first time number-letter pair.

-

For complete details, see ISO 8601 Data elements and interchange formats — Information + <p>For complete details, see ISO 8601 <title>Data elements and interchange formats — Information interchange — Representation of dates and times.

 -

時間幅は、先頭文字Pに続いて、数値-文字のペア列で示される。 文字は単位を示している。Y(年)、M(月)、D(日)、H(時間)、M(分)、S(秒) +

時間幅は、先頭文字Pに続いて、数値-文字のペア列で示される。 文字は単位を示している。Y(年)、M(月)、D(日)、H(時間)、M(分)、S(秒) の順番になる。数値は符号のない整数である。但し、最後に10進数の 表記記号(小数点を示す.または,。後者が望 ましい)をとることはある。数値が0の場合、 数値-文字のペアは省略されることがある。 H(時間)、M(分)、 S(秒)が数値-文字のペアを作る場合、区切子 Tを先頭にして時間を示す数値-文字 のペアを示す必要がある。

-

詳細については、ISO 8601Data elements and interchange formats - Information interchange - + <p> 詳細については、ISO 8601<title>Data elements and interchange formats - Information interchange - Representation of dates and timesを参照のこと。

-

Une durée est exprimée par une suite de paires alphanumériques, précédée par la lettre P ; +

Une durée est exprimée par une suite de paires alphanumériques, précédée par la lettre P ; la lettre donne l'unité et peut être Y (année), M (mois), D (jour), H (heure), M (minute), ou S (seconde), dans cet ordre. Les nombres sont des entiers sans signe, à l'exception du dernier, @@ -82,7 +78,7 @@ See the file COPYING.txt for details alors la paire alphanumérique peut être omise. Si les paires alphanumériques H (heure), M (minute), ou S (seconde) sont présentes, alors le séparateur T doit précéder la première paire alphanumérique time.

-

Pour des détails complets, voir ISO 8601 Data elements and interchange formats — + <p>Pour des détails complets, voir ISO 8601 <title>Data elements and interchange formats — Information interchange — Representation of dates and times.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.duration.w3c.xml b/P5/Source/Specs/teidata.duration.w3c.xml index 368724d72c..749b12705a 100644 --- a/P5/Source/Specs/teidata.duration.w3c.xml +++ b/P5/Source/Specs/teidata.duration.w3c.xml @@ -1,9 +1,5 @@ - + defines the range of attribute values available for representation of a duration in time using W3C datatypes. @@ -14,45 +10,45 @@ See the file COPYING.txt for details valeurs d'attributs exprimant une durée temporaraire utilisant les types de données W3C define la gama de valores de atributos disponibles para la representación de un periodo de tiempo usando tipos de datos W3C - - + + - - - + + + - - a day and a half - + + a day and a half + - - a week - + + a week + - - - + + + - - une journée et demie - + + une journée et demie + - - une semaine - + + une semaine + - - - + + + -

A duration is expressed as a sequence of number-letter pairs, +

A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for @@ -63,11 +59,11 @@ See the file COPYING.txt for details number-letter pairs are present, then the separator T must precede the first time number-letter pair.

-

For complete details, see the W3C +

For complete details, see the W3C specification.

 -

+

時間幅は、先頭文字Pに続いて、数値-文字のペア列で示される。 文字は単位を示している。Y(年)、M(月)、D(日)、H(時間)、M(分)、S(秒) の順番になる。数値は符号のない整数である。但し、Sの場 @@ -77,14 +73,14 @@ See the file COPYING.txt for details 区切子Tを先頭にして時間を示す 数値-文字のペアを示す必要がある。

-

+

詳細については、 W3C specificationを参照のこと。

-

Une durée est exprimée par une suite de paires alphanumériques, précédée par la lettre P ; la lettre donne l'unité et peut être Y +

Une durée est exprimée par une suite de paires alphanumériques, précédée par la lettre P ; la lettre donne l'unité et peut être Y (année), M (mois), D (jour), H (heure), M (minute), ou S (seconde), dans cet ordre. Les nombres sont des entiers non signés à l'exception du dernier, qui peut comporter une décimale (en utilisant soit . soit , pour la virgule ; la dernière possibilité est préférable). Si un nombre est 0, alors @@ -92,7 +88,7 @@ See the file COPYING.txt for details (minute), ou S (seconde) sont présentes, alors le séparateur T doit précéder la première paire alphanumérique time.

-

Pour des détails complets, voir W3C +

Pour des détails complets, voir W3C specification.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.enumerated.xml b/P5/Source/Specs/teidata.enumerated.xml index 8a951c8229..65abcaf276 100644 --- a/P5/Source/Specs/teidata.enumerated.xml +++ b/P5/Source/Specs/teidata.enumerated.xml @@ -1,9 +1,5 @@ - + defines the range of attribute values expressed as a single XML name taken from a list of @@ -19,27 +15,27 @@ See the file COPYING.txt for details definisce la gamma di valori di attributi espressi come singola parola o token tratto da una lista di possibilità attestate - - + +

Attributes using this datatype must contain a single word which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

-

Typically, the list of documented possibilities will be provided (or exemplified) by a value +

Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a valList element.

 -

当該データ型は、妥当なXML名前 (詳細は +

当該データ型は、妥当なXML名前 (詳細は を参照のこと)である単語でなくてはならない。例えば、 属性値として空白文字、または数値で始まる名前をとることはできない。

-

典型例は、可能な記述またはその例のリストが、要素valList 中に属性定義として示されている。

+

典型例は、可能な記述またはその例のリストが、要素valList 中に属性定義として示されている。

-

Les attributs utilisant ce type de données doivent contenir un mot qui suit les règles de +

Les attributs utilisant ce type de données doivent contenir un mot qui suit les règles de définition d'un nom XML valide (voir ): par exemple ils ne peuvent pas contenir des blancs ni commencer par des chiffres.

-

Normalement, la liste des possibilités documentées est fournie (ou exemplifiée) par une liste +

Normalement, la liste des possibilités documentées est fournie (ou exemplifiée) par une liste de valeurs dans la spécification de l'attribut associé, exprimée par un élément valList.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.gender.xml b/P5/Source/Specs/teidata.gender.xml index 9207d6cf87..36823e05a2 100644 --- a/P5/Source/Specs/teidata.gender.xml +++ b/P5/Source/Specs/teidata.gender.xml @@ -1,11 +1,7 @@ - + + - + defines the range of attribute values used to represent the gender of a person, persona, or character. diff --git a/P5/Source/Specs/teidata.interval.xml b/P5/Source/Specs/teidata.interval.xml index f6b7eaf5d9..e50a413a56 100644 --- a/P5/Source/Specs/teidata.interval.xml +++ b/P5/Source/Specs/teidata.interval.xml @@ -1,24 +1,20 @@ - + defines attribute values used to express an interval value. - - - - - - - - - + + + + + + + + + -

Any value greater than zero or any one of the values +

Any value greater than zero or any one of the values regular, irregular, unknown.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.key.xml b/P5/Source/Specs/teidata.key.xml index a6dd428ed5..44a53ca6d3 100644 --- a/P5/Source/Specs/teidata.key.xml +++ b/P5/Source/Specs/teidata.key.xml @@ -1,58 +1,43 @@ - - - defines the range of attribute values expressing a coded value by means of an arbitrary + + + + + defines the range of attribute values expressing a coded value by means of an arbitrary identifier, typically taken from a set of externally-defined possibilities. - 임의의 확인소에 의해 부호화된 값을 표현하는 속성 값 범위를 정의하며, 이것은 일반적으로 외부 정의 - 확률의 집합에서 얻어진다. - 定義的屬性值範圍以隨機識別碼來表示一個編碼值，該識別碼通常來自一組外部定義的可能性 - 任意の識別子により属性値の範囲が定義される。典型例は、外部で定義され ているものから値がとられる。 - définit la gamme des valeurs d'attributs exprimant une - valeur encodée au moyen d'un identifiant arbitraire, typiquement emprunté à un ensemble de - possibilités définies extérieurement - define la gama de valores de atributos que expresan un - valor codificado a través de un identificador arbitrario obtenido, normalmente, de un conjunto + 임의의 확인소에 의해 부호화된 값을 표현하는 속성 값 범위를 정의하며, 이것은 일반적으로 외부 정의 + 확률의 집합에서 얻어진다. + 定義的屬性值範圍以隨機識別碼來表示一個編碼值，該識別碼通常來自一組外部定義的可能性 + 任意の識別子により属性値の範囲が定義される。典型例は、外部で定義され ているものから値がとられる。 + définit la gamme des valeurs d'attributs exprimant une + valeur encodée au moyen d'un identifiant arbitraire, typiquement emprunté à un ensemble de + possibilités définies extérieurement + define la gama de valores de atributos que expresan un + valor codificado a través de un identificador arbitrario obtenido, normalmente, de un conjunto de posibilidades definidas exteriormente. - definisce la gamma di valori di attributi che esprimono + definisce la gamma di valori di attributi che esprimono un valore codificato tramite un identificatore arbitrario tratto, di solito, da un insieme di - possibilità definite esternamente + possibilità definite esternamente - - - -

Information about the set of possible values for an attribute using this datatype may (but + + + +

Information about the set of possible values for an attribute using this datatype may (but need not) be documented in the document header. Externally defined constraints, for example that values should be legal keys in an external database system, cannot usually be enforced by a TEI system. Similarly, because the key is externally defined, no constraint other than a requirement that it consist of Unicode characters is possible.

- -

当該データ型で定義される属性値に関する情報は、(必須ではないが)当該 文書のヘダーに記述されるかもしれない。外部で定義されている制約、例 - えば、外部のデータベースシステムにあるキーの定義は、一般には、(そ のままでは)TEIシステムでは使うことができない。また、このキーは外部 - で定義されているので、ユニコード文字を使用するという制約以外の制約 を採用することも可能になる。

+ +

当該データ型で定義される属性値に関する情報は、(必須ではないが)当該 文書のヘダーに記述されるかもしれない。外部で定義されている制約、例 + えば、外部のデータベースシステムにあるキーの定義は、一般には、(そ のままでは)TEIシステムでは使うことができない。また、このキーは外部 + で定義されているので、ユニコード文字を使用するという制約以外の制約 を採用することも可能になる。

- -

Les informations sur le jeu de valeurs possibles pour un attribut utilisant ce type de - données peuvent (mais cela n'est pas nécessaire) être documentées dans l'en-tête TEI du document. - Des contraintes définies de façon externe, par exemple le fait que les valeurs doivent être - des clés valides dans une base de données externe, ne peuvent être appliquées habituellement par un - système TEI. De même, parce que la clé est définie de façon externe, aucune contrainte autre - que la nécessité d'être constituée de caractères Unicode n'est possible.

+ +

Les informations sur le jeu de valeurs possibles pour un attribut utilisant ce type de + données peuvent (mais cela n'est pas nécessaire) être documentées dans l'en-tête TEI du document. + Des contraintes définies de façon externe, par exemple le fait que les valeurs doivent être + des clés valides dans une base de données externe, ne peuvent être appliquées habituellement par un + système TEI. De même, parce que la clé est définie de façon externe, aucune contrainte autre + que la nécessité d'être constituée de caractères Unicode n'est possible.

diff --git a/P5/Source/Specs/teidata.language.xml b/P5/Source/Specs/teidata.language.xml index 260e1d749b..9f843256b5 100644 --- a/P5/Source/Specs/teidata.language.xml +++ b/P5/Source/Specs/teidata.language.xml @@ -1,9 +1,5 @@ - + defines the range of attribute values used to identify a particular combination of human @@ -19,261 +15,134 @@ See the file COPYING.txt for details definisce la gamma di valori di attributi usati per identificare una determinata combinazione di linguaggio e sistema di scrittura umani - - - - - - - + + + + + + + -

The values for this attribute are language tags as defined in BCP 47. Currently BCP 47 comprises RFC 5646 +

The values for this attribute are language tags as defined in BCP 47. Currently BCP 47 comprises RFC 5646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice.

-

A language tag, per BCP 47, is assembled from a sequence of components +

A language tag, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components - (variant and extension), which are repeatable. - - The IANA-registered code for the language. This is almost always the same as the ISO + (variant and extension), which are repeatable. The IANA-registered code for the language. This is almost always the same as the ISO 639 2-letter language code if there is one. The list of available registered language subtags can be found at . It is recommended - that this code be written in lower case. - - The ISO 15924 code for the script. These codes consist of 4 letters, and it is + that this code be written in lower case.The ISO 15924 code for the script. These codes consist of 4 letters, and it is recommended they be written with an initial capital, the other three letters in lower case. The canonical list of codes is maintained by the Unicode Consortium, and is available at . The IETF - recommends this code be omitted unless it is necessary to make a distinction you need. - - Either an ISO 3166 country code or a UN M.49 region code that is registered with IANA + recommends this code be omitted unless it is necessary to make a distinction you need.Either an ISO 3166 country code or a UN M.49 region code that is registered with IANA (not all such codes are registered, e.g. UN codes for economic groupings or codes for countries for which there is already an ISO 3166 2-letter code are not registered). The former consist of 2 letters, and it is recommended they be written in upper case; the list - of codes can be searched or browsed at . The latter consist of 3 digits; the list of codes can be found at . - - An IANA-registered variation. These codes are used to indicate + of codes can be searched or browsed at . The latter consist of 3 digits; the list of codes can be found at .An IANA-registered variation. These codes are used to indicate additional, well-recognized variations that define a language or its dialects that are not covered by other available subtags. - - An extension has the format of a single letter followed by a hyphen followed by + 2.2.5 -->An extension has the format of a single letter followed by a hyphen followed by additional subtags. These exist to allow for future extension to BCP 47, but as of this - writing no such extensions are in use. - - An extension that uses the initial subtag of the single letter + writing no such extensions are in use.An extension that uses the initial subtag of the single letter x (i.e., starts with x-) has no meaning except as negotiated among the parties involved. These should be used with great care, since they interfere with the interoperability that use of RFC 4646 is intended to promote. In order for a document that makes use of these subtags to be TEI-conformant, a corresponding - language element must be present in the TEI header. - + language element must be present in the TEI header.

-

There are two exceptions to the above format. First, there are language tags in the IANA registry that +

There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been grandfathered from previous specifications.

-

Second, an entire language tag can consist of only a private use subtag. These tags start +

Second, an entire language tag can consist of only a private use subtag. These tags start with x-, and do not need to follow any further rules established by the IETF and endorsed by these Guidelines. Like all language tags that make use of private use subtags, the language in question must be documented in a corresponding language element in the TEI header.

-

Examples include - - Shona - - Taiwanese - - Chinese written in traditional script as used in Hong Kong - - English as spoken in Sierra Leone - - Polish - - Spanish as spoken in Mexico - - Spanish as spoken in Latin America - +

Examples include ShonaTaiwaneseChinese written in traditional script as used in Hong KongEnglish as spoken in Sierra LeonePolishSpanish as spoken in MexicoSpanish as spoken in Latin America

-

The W3C Internationalization Activity has published a useful introduction to BCP 47, Language +

The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML.

 -

当該属性値は、 BCP 47 +

当該属性値は、 BCP 47 で定義されている言語タグになる。 現行のBCPには、RFC4646とRFC4647の内容が含まれている。 今後は、他のIETF文書も採用されるかもしれない。

BCP 47にある言語タグは、ハイフン (-、U+002D)で区切られた一連の 下位タグから構成されている。下位タグは、以下の順番 らなる。下位タグは、初めの1つは必須で、あとは選択的である。 - variantとextensionは複数回、他は1回のみ出現出現する。この下位タグ のグループは繰り返し可能である。 - - IANAの言語コード。この殆どは、該当言語が既にあれば、ISO 639の2文字 (以下、この場合の文字はラテン文字)言語コードと同じである。利用可能 + variantとextensionは複数回、他は1回のみ出現出現する。この下位タグ のグループは繰り返し可能である。 IANAの言語コード。この殆どは、該当言語が既にあれば、ISO 639の2文字 (以下、この場合の文字はラテン文字)言語コードと同じである。利用可能 な言語下位タグのリストは - にある。言語コードは、小文字で書かれることが推奨されている。 - - ISO 15924による文字を示すコード。4文字から構成され、冒頭文字は大文 字で、残り3文字は小文字で書かれることが推奨されている。このコード + にある。言語コードは、小文字で書かれることが推奨されている。 ISO 15924による文字を示すコード。4文字から構成され、冒頭文字は大文 字で、残り3文字は小文字で書かれることが推奨されている。このコード は、ユニコードコンソーシアムで管理され、 か - ら入手することができる。IETFでは、不要であれば当該コードを省略する ことを推奨している。 - - ISO 3166またはUN M.49による国または地域コード。このコードはIANAに 登録されている(但し全てではない。例えば、UNコードには経済圏や、 ISO - 3166の2文字コードで既に登録されているところは含まれていない)。 ISOコードは、2文字から構成され、大文字で書かれることが推奨されてい る。このコードは、 にある。 またUNコードは、3文字から構成されている。このコードは、 にあ る。 - - IANAにある登録値。このコードは、 他の下位タグでは対応できない、追加的であるがよく知られている、ある言語 + ら入手することができる。IETFでは、不要であれば当該コードを省略する ことを推奨している。 ISO 3166またはUN M.49による国または地域コード。このコードはIANAに 登録されている(但し全てではない。例えば、UNコードには経済圏や、 ISO + 3166の2文字コードで既に登録されているところは含まれていない)。 ISOコードは、2文字から構成され、大文字で書かれることが推奨されてい る。このコードは、 にある。 またUNコードは、3文字から構成されている。このコードは、 にあ る。 IANAにある登録値。このコードは、 他の下位タグでは対応できない、追加的であるがよく知られている、ある言語 や方言の種類を示すために使用される。 - - - いち文字、ハイフン、追加下位タグの順番で、拡張情報が示される。 これは、BCP 47が将来拡張された時のためある。現時点ではそのような 拡張はない。 - - - xXで始まる(すなわち、x-)下位タ + いち文字、ハイフン、追加下位タグの順番で、拡張情報が示される。 これは、BCP 47が将来拡張された時のためある。現時点ではそのような 拡張はない。 xXで始まる(すなわち、x-)下位タ グで示される拡張情報は、関連する団体間で決められた範囲の意味を持つ。 このコードは大文字で書かれるべきである。これは、RFC4646aで使われて いるタグとの相互運用性を保つためである。 このタグを使用してTEI準拠の文書を作成するには、要素 languageをTEIヘダー中に記述しなければならない。 - - +

-

上記記述形式には、2つの例外がある。ひとつは、ここにある言語タグは、 +

上記記述形式には、2つの例外がある。ひとつは、ここにある言語タグは、 IANAにある統語規則に違反しているものがある。 これはIANAでは昔の規定を継承しているからであ る。

-

ふたつめは、言語タグを、下位タグprivateだけで構成することができる ことである。x-で始まるタグの内容は、IETFにある規定に +

ふたつめは、言語タグを、下位タグprivateだけで構成することができる ことである。x-で始まるタグの内容は、IETFにある規定に も当該TEIガイドラインにある規定にも従う必要はない。他の言語タグと 同様に、このタグを使用した場合には、TEIヘダーにある要素 languageにこのタグを記述しなければならない。

-

言語コードには、以下のようなものがある。 - - ショナ語 - - 中国語、台湾 - - 中国語、繁体字、香港 - - 英語、シエラレオネ共和国 - - ポーランド語 - - スペイン語、メキシコ - - スペイン語、ラテンアメリカ - +

言語コードには、以下のようなものがある。 ショナ語中国語、台湾中国語、繁体字、香港英語、シエラレオネ共和国ポーランド語スペイン語、メキシコスペイン語、ラテンアメリカ

-

W3Cの国際化活動では、BCP 47の解説を以下に用意している。 +

W3Cの国際化活動では、BCP 47の解説を以下に用意している。 HTMLとXMLで使用される言語タグ。

 -

Les valeurs pour cet attribut sont les étiquettes de langue définies +

Les valeurs pour cet attribut sont les étiquettes de langue définies dans la norme BCP 47. Actuellement, la norme BCP 47 intègre les normes RFC 4646 et RFC 4647 ; à l'avenir, d'autres documents de l'IETF pourront leur succéder en tant que meilleure pratique.

-

Une étiquette de langue, pour la norme BCP 47, est formée par l'assemblage d'une +

Une étiquette de langue, pour la norme BCP 47, est formée par l'assemblage d'une suite de composants ou de sous-étiquettes reliés par un trait d'union (-, U+002D). L'étiquette est composée des sous-étiquettes suivantes, dans l'ordre indiqué. Chaque sous-étiquette est facultative, à l'exception de la première. Chacune ne peut avoir qu'une occurrence, sauf les quatrième et cinquième (variante - et extension), qui sont répétables. - - Code de langue enregistré par l'IANA. Il est presque toujours identique au code + et extension), qui sont répétables. Code de langue enregistré par l'IANA. Il est presque toujours identique au code de langue alphabétique ISO 639-2, s'il y en a un. La liste des sous-étiquettes de langue enregistrées est disponible à : . Il est recommandé - d'écrire ce code en minuscules. - - Code ISO 15924 pour l'écriture. Ces codes sont constitués de 4 lettres, et il est + d'écrire ce code en minuscules.Code ISO 15924 pour l'écriture. Ces codes sont constitués de 4 lettres, et il est recommandé d'écrire la première lettre en majuscule, les trois autres en minuscules. La liste canonique des codes est maintenue par le Consortium Unicode, et elle est disponible à : . L'IETF recommande - d'omettre ce code, sauf s'il est nécessaire pour établir une distinction. - - Soit un code de pays ISO 3166, soit un code de région UN M.49 enregistré par + d'omettre ce code, sauf s'il est nécessaire pour établir une distinction.Soit un code de pays ISO 3166, soit un code de région UN M.49 enregistré par l'IANA (tous les codes de ce type ne sont pas enregistrés : par exemple, ne sont pas enregistrés les codes UN pour des regroupements économiques ou les codes de pays pour lesquels il existe déjà un code de pays alphabétique ISO 3166-2). Le premier est constitué de 2 lettres, et il est recommandé de l'écrire en majuscules. La liste des codes est - disponible à : . Le second est constitué de 3 chiffres ; la liste des codes est disponible à : . - - Variante enregistrée par l'IANA. Ces codes sont utilisés + disponible à : . Le second est constitué de 3 chiffres ; la liste des codes est disponible à : .Variante enregistrée par l'IANA. Ces codes sont utilisés pour indiquer des variantes additionnelles et bien établies, qui définissent une langue ou ses dialectes et qui ne sont pas couverts par d'autres sous-étiquettes existantes. - - Une extension a la forme d'une lettre unique, suivie d'un trait d'union, lui-même suivi de sous-étiquettes additionnelles. Ces dernières existent pour tenir compte d'une future extension - de la norme BCP 47, mais à l'heure actuelle de telles extensions ne sont pas utilisées. - - Une extension utilisant la sous-étiquette initiale de la lettre + 2.2.5 -->Une extension a la forme d'une lettre unique, suivie d'un trait d'union, lui-même suivi de sous-étiquettes additionnelles. Ces dernières existent pour tenir compte d'une future extension + de la norme BCP 47, mais à l'heure actuelle de telles extensions ne sont pas utilisées.Une extension utilisant la sous-étiquette initiale de la lettre x (i.e., commençant par x-) n'a pas d'autre signification que celle négociée entre les parties impliquées. Ces sous-étiquettes doivent être utilisées avec beaucoup de prudence, car elles interfèrent avec l'interopérabilité que l'utilisation de la norme RFC 4646 vise à promouvoir. Pour qu'un document qui utilise ces sous-étiquettes soit conforme à la TEI, un élément language correspondant doit être présent dans - l'en-tête TEI. - + l'en-tête TEI.

-

Il y a deux exceptions au format ci-dessus. Premièrement, il y a des codes de langue dans +

Il y a deux exceptions au format ci-dessus. Premièrement, il y a des codes de langue dans le registre de l'IANA qui ne correspondent pas à la syntaxe ci-dessus, mais qui sont présents car ils ont été hérités de spécifications antérieures.

-

En second lieu, une étiquette complète de langue peut consister seulement en une sous-étiquette d'usage privé. Ces étiquettes commencent par x- ; il n'est pas +

En second lieu, une étiquette complète de langue peut consister seulement en une sous-étiquette d'usage privé. Ces étiquettes commencent par x- ; il n'est pas nécessaire qu'elles suivent les autres règles établies par l'IETF et acceptées par les présents Principes directeurs. Comme toutes les étiquettes de langue qui utilisent des sous-étiquettes d'usage privé, la langue en question doit être documentée dans un élément correspondant language dans l'en-tête TEI.

-

Les exemples incluent : - - Shona - - Taïwanais - - Chinois de Hong Kong écrit dans l'écriture traditionnelle - - Anglais parlé au Sierra Leone - - Polonais - - Espagnol parlé au Mexique - - Espagnol parlé en Amérique latine - +

Les exemples incluent :ShonaTaïwanaisChinois de Hong Kong écrit dans l'écriture traditionnelleAnglais parlé au Sierra LeonePolonaisEspagnol parlé au MexiqueEspagnol parlé en Amérique latine

-

La W3C Internationalization Activity a publié une introduction à la norme BCP 47 dont la lecture peut être utile : Language +

La W3C Internationalization Activity a publié une introduction à la norme BCP 47 dont la lecture peut être utile : Language tags in HTML and XML.

- + - + - \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.name.xml b/P5/Source/Specs/teidata.name.xml index 4d1547a933..131160bfcb 100644 --- a/P5/Source/Specs/teidata.name.xml +++ b/P5/Source/Specs/teidata.name.xml @@ -1,9 +1,5 @@ - + defines the range of attribute values expressed as an XML Name. @@ -17,20 +13,20 @@ See the file COPYING.txt for details definisce la gamma di valori di attributi espressi come identificatore o nome XML - - + + -

Attributes using this datatype must contain a single word which follows the rules defining a +

Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see ): for example they cannot include whitespace or begin with digits.

-

当該属性は、妥当なXML名前(詳細は を参照)である +

当該属性は、妥当なXML名前(詳細は を参照)である ひとつの単語をとる。例えば、空白文字を含まず、数字が先頭文字にこな いもの。

-

Les attributs utilisant ce type de données doivent contenir un seul mot, qui suit les règles +

Les attributs utilisant ce type de données doivent contenir un seul mot, qui suit les règles de définition d'un nom XML valide (voir ) : par exemple ils ne peuvent contenir de blancs ou commencer par des chiffres.

- \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.namespace.xml b/P5/Source/Specs/teidata.namespace.xml index be9efb9202..76bdde47eb 100644 --- a/P5/Source/Specs/teidata.namespace.xml +++ b/P5/Source/Specs/teidata.namespace.xml @@ -1,9 +1,5 @@ - + defines the range of attribute values used to indicate XML namespaces as defined by the W3C @@ -27,23 +23,23 @@ See the file COPYING.txt for details indicare i nomi degli spazi in XML come stabilito dalle raccomandazioni tecniche del W3C per gli spazi dei nomi in XML. - - + + -

The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier + <p>The range of syntactically valid values is defined by <ref target="https://www.ietf.org/rfc/rfc3986.txt">RFC 3986 <title>Uniform Resource Identifier (URI): Generic Syntax

-

当該データ値は、RFC 2396 Uniform Resource + <p> 当該データ値は、<ref target="https://www.ietf.org/rfc/rfc2396.txt">RFC 2396 <title>Uniform Resource Identifier (URI) Reference に定義されている。

-

La gamme des valeurs syntaxiquement valides est définie par RFC 3986 Uniform Resource Identifier + <p>La gamme des valeurs syntaxiquement valides est définie par <ref target="https://www.ietf.org/rfc/rfc3986.txt">RFC 3986 <title>Uniform Resource Identifier (URI): Generic Syntax .

- + diff --git a/P5/Source/Specs/teidata.namespaceOrName.xml b/P5/Source/Specs/teidata.namespaceOrName.xml index 98db1a8eca..ad6b4cb362 100644 --- a/P5/Source/Specs/teidata.namespaceOrName.xml +++ b/P5/Source/Specs/teidata.namespaceOrName.xml @@ -1,15 +1,8 @@ - - - defines attribute values which contain either an absolute namespace URI or a qualified XML name. + + + + defines attribute values which contain either an absolute namespace URI or a qualified XML name. - - defines attribute values which contain either the null string or an XML name. + + + + + defines attribute values which contain either the null string or an XML name. - - - - + + + + + + - -

The rules defining an XML name form a part of the XML Specification.

+ +

The rules defining an XML name form a part of the XML Specification.

 diff --git a/P5/Source/Specs/teidata.numeric.xml b/P5/Source/Specs/teidata.numeric.xml index 4e5e249e71..63fd557a91 100644 --- a/P5/Source/Specs/teidata.numeric.xml +++ b/P5/Source/Specs/teidata.numeric.xml @@ -1,9 +1,5 @@ - + defines the range of attribute values used for numeric values. @@ -17,52 +13,43 @@ See the file COPYING.txt for details definisce la gamma di valori di attributi usati per valori numerici - - - - - - + + + + + + -

Any numeric value, represented as a decimal number, in floating point format, or as a ratio.

-

To represent a floating point number, expressed in scientific notation, E +

Any numeric value, represented as a decimal number, in floating point format, or as a ratio.

+

To represent a floating point number, expressed in scientific notation, E notation, a variant of exponential notation, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3.

-

A value expressed as a ratio is represented by two integer values separated by a solidus (/) +

A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2.

 -

10進数を作る数値。

-

また、IEEE倍精度浮動小数点(64bit長)をとることもできる。例えば、 ±10⁻³²³ から ±10³⁰⁸など。

-

科学的数値を評点する際、指数表現は、属性値と して記述される。 +

10進数を作る数値。

+

また、IEEE倍精度浮動小数点(64bit長)をとることもできる。例えば、 ±10⁻³²³ から ±10³⁰⁸など。

+

科学的数値を評点する際、指数表現は、属性値と して記述される。 10進数による仮数部、続いて記号E、続いて指数 部がくる。 乗算記号と底(10)は省略される。仮数部と指数 部には負になるかもしれない。記号Eと指数部を 分けるために空白文字を入れる必要はない。例えば、3×10⁸ は 3E8と書かれる。

-

他の例として、以下のようなものがある。 - - 3E10 (光の速度(cm/秒)) - - 9.12E-31 (電子の質量(kg)) - - 4E11 (銀河系にある恒星の数(推定値)) - - -1.76E11 (電子の電荷(クローン)) - +

他の例として、以下のようなものがある。 3E10 (光の速度(cm/秒))9.12E-31 (電子の質量(kg))4E11 (銀河系にある恒星の数(推定値))-1.76E11 (電子の電荷(クローン))

-

仮数部と指数部を分ける記号はeまたは Eのどちらでもよいが、当ガイドラインでは +

仮数部と指数部を分ける記号はeまたは Eのどちらでもよいが、当ガイドラインでは Eを使うことを推奨する。これは、他の規格との 整合性を保ち、数学における定数との混同を避けるためである。

-

Toute valeur numérique, représentée en nombre décimal, notée en virgule flottante ou +

Toute valeur numérique, représentée en nombre décimal, notée en virgule flottante ou en fraction.

-

Pour représenter un nombre en virgule flottante, exprimé en notation scientifique, +

Pour représenter un nombre en virgule flottante, exprimé en notation scientifique, E notation, une variante de la notation exponentielle peut être utilisée. Dans ce format, la valeur est exprimée par deux nombres séparés par la lettre E. Le premier facteur, le significande (parfois appelé mantisse) @@ -70,8 +57,8 @@ See the file COPYING.txt for details multipliant la mantisse par 10 fois le nombre indiqué par l'entier. Ainsi la valeur représentée en notation décimale 1000.0 pourrait être représentée en notation scientifique 10E3.

-

Une valeur exprimée en fraction est représentée par deux nombres entiers séparés par une +

Une valeur exprimée en fraction est représentée par deux nombres entiers séparés par une barre oblique (/). Ainsi, la valeur représentée en notation décimale 0.5 pourrait être représentée en fraction par la chaîne de caractères 1/2.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.outputMeasurement.xml b/P5/Source/Specs/teidata.outputMeasurement.xml index d155d5ba5c..fd873f5fb3 100644 --- a/P5/Source/Specs/teidata.outputMeasurement.xml +++ b/P5/Source/Specs/teidata.outputMeasurement.xml @@ -1,9 +1,5 @@ - + defines a range of values for use in specifying the size of an object that is intended for @@ -18,42 +14,42 @@ See the file COPYING.txt for details definisce una gamma di valori da impiegare nello specificare le dimensioni di un oggetto da inserire in rete - - + + - -
- The TEI Logo - Stylized yellow angle brackets with the letters TEI in + +
+ The TEI Logo + Stylized yellow angle brackets with the letters TEI in between and text encoding initiative underneath, all on a white background. - -
- + +
+ - -
- Le logo TEI - -
- + +
+ Le logo TEI + +
+ -

These values map directly onto the values used by XSL-FO and CSS. For definitions of the +

These values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft.

 -

当該値は、XSLFOやCSSで使用される値になる。詳細は各規格を参照のこと。 現時点で一番詳細なリストは、 CSS3 working +

当該値は、XSLFOやCSSで使用される値になる。詳細は各規格を参照のこと。 現時点で一番詳細なリストは、 CSS3 working draftになる。

-

Ces valeurs peuvent être reportées directement sur des valeurs utilisées par XSL-FO et CSS. Pour les +

Ces valeurs peuvent être reportées directement sur des valeurs utilisées par XSL-FO et CSS. Pour les définitions des unités, voir ces spécifications ; à ce jour la liste la plus complète est dans un CSS3 working draft.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.pattern.xml b/P5/Source/Specs/teidata.pattern.xml index 452be97e57..7c9f38ed8f 100644 --- a/P5/Source/Specs/teidata.pattern.xml +++ b/P5/Source/Specs/teidata.pattern.xml @@ -1,9 +1,5 @@ - + + defines the data type used to express a point in cartesian space. @@ -13,11 +9,11 @@ See the file COPYING.txt for details - - - - - + + + + + @@ -29,4 +25,4 @@ See the file COPYING.txt for details

- \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.pointer.xml b/P5/Source/Specs/teidata.pointer.xml index e4caa5e874..aa2dd688b4 100644 --- a/P5/Source/Specs/teidata.pointer.xml +++ b/P5/Source/Specs/teidata.pointer.xml @@ -1,9 +1,5 @@ - + defines the range of attribute values used to provide a single @@ -18,10 +14,10 @@ resource, either within the current document or elsewhere. define una gama de valores de atributos usados para proporcionar un indicador de cualquier recurso, bien en el documento corriente o en otro. definisce la gamma di valori di attributi usati per indicare un unico puntatore rispetto a qualsiasi altra risorsa all'interno del documento corrente o altrove - - + + -

The range of syntactically valid values is defined by +

The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using @@ -36,7 +32,7 @@ resource, either within the current document or elsewhere.

-

+

当該属性値は、 RFC 3986 Uniform Resource Identifier (URI) Reference @@ -45,10 +41,10 @@ resource, either within the current document or elsewhere.

-

La gamme des valeurs valides syntaxiquement est définie parRFC 3986 +

La gamme des valeurs valides syntaxiquement est définie parRFC 3986 Uniform Resource Identifier (URI): Generic Syntax

- \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.prefix.xml b/P5/Source/Specs/teidata.prefix.xml index 9b65e7770d..b819c9d9f2 100644 --- a/P5/Source/Specs/teidata.prefix.xml +++ b/P5/Source/Specs/teidata.prefix.xml @@ -1,27 +1,18 @@ - + + - - defines a range of values that may function as a URI scheme name. + + defines a range of values that may function as a URI scheme name.

This datatype is used to constrain a string of characters to - one that can be used as a URI scheme name according to RFC 3986, section + one that can be used as a URI scheme name according to RFC 3986, section 3.1. Thus only the 26 lowercase letters a–z, the 10 - digits 0–9, the plus sign, the period, and the hyphen are + digits 0–9, the plus sign, the period, and the hyphen are permitted, and the value must start with a letter.

 diff --git a/P5/Source/Specs/teidata.probCert.xml b/P5/Source/Specs/teidata.probCert.xml index 86ca7d96d1..be4c9be6d1 100644 --- a/P5/Source/Specs/teidata.probCert.xml +++ b/P5/Source/Specs/teidata.probCert.xml @@ -1,18 +1,12 @@ - - - defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value. - - - - + + + + + defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value. + + + + + - diff --git a/P5/Source/Specs/teidata.probability.xml b/P5/Source/Specs/teidata.probability.xml index 8ca88a9656..6d97a6527d 100644 --- a/P5/Source/Specs/teidata.probability.xml +++ b/P5/Source/Specs/teidata.probability.xml @@ -1,9 +1,5 @@ - + defines the range of attribute values expressing a probability. @@ -17,20 +13,20 @@ See the file COPYING.txt for details definisce la gamma di valori di attributi che esprimono una probabilità - - + + -

Probability is expressed +

Probability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true.

 -

出現度は、0から1までの実数で表現される。0は 確実に偽、1は、 確実に真を示す。

+

出現度は、0から1までの実数で表現される。0は 確実に偽、1は、 確実に真を示す。

-

Le degré de probabilité est exprimé +

Le degré de probabilité est exprimé par un nombre réel entre 0 et 1 ; 0 représentant certainement faux et 1 certainement vrai.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.replacement.xml b/P5/Source/Specs/teidata.replacement.xml index b1631c6fbc..cc30f8807f 100644 --- a/P5/Source/Specs/teidata.replacement.xml +++ b/P5/Source/Specs/teidata.replacement.xml @@ -1,16 +1,12 @@ - + defines attribute values which contain a replacement template. - - + + -

+

- \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.sex.xml b/P5/Source/Specs/teidata.sex.xml index 8ee18792d3..5ecd568207 100644 --- a/P5/Source/Specs/teidata.sex.xml +++ b/P5/Source/Specs/teidata.sex.xml @@ -1,18 +1,14 @@ - + + - + defines the range of attribute values used to identify the sex of an organism. - 인간 또는 동물의 성을 식별하는 속성 값 범위를 정의한다. - 定義的屬性值範圍用以識別人類或動物的性別 - 人間または動物の性を示す属性値の範囲を定義する。 - définit la gamme des valeurs d'attributs employés - pour identifier le sexe d’un organisme. + 인간 또는 동물의 성을 식별하는 속성 값 범위를 정의한다. + 定義的屬性值範圍用以識別人類或動物的性別 + 人間または動物の性を示す属性値の範囲を定義する。 + définit la gamme des valeurs d'attributs employés + pour identifier le sexe d’un organisme. define la gama de valores de atributos usados para identificar el sexo de un organismo. definisce una gamma di valori di attributi usati per @@ -24,7 +20,7 @@ See the file COPYING.txt for details

Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard.

 -

Les valeurs de cet attribut peuvent être définies localement par un projet ou peuvent faire - référence à un standard externe.

+

Les valeurs de cet attribut peuvent être définies localement par un projet ou peuvent faire + référence à un standard externe.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.temporal.iso.xml b/P5/Source/Specs/teidata.temporal.iso.xml index adacbd23ff..73c20acd57 100644 --- a/P5/Source/Specs/teidata.temporal.iso.xml +++ b/P5/Source/Specs/teidata.temporal.iso.xml @@ -1,9 +1,5 @@ - + defines the range of attribute values expressing a temporal expression such as a date, a @@ -27,36 +23,34 @@ See the file COPYING.txt for details estándard internacional Elementos de datos y formatos de intercambio - Intercambio de información – Representación de fechas y horas. - - - - - - - - - - - - + + + + + + + + + + + + -

If it is likely that the value used is to be compared with another, then a time zone +

If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

-

For all representations for which ISO 8601:2004 describes both a basic and an +

For all representations for which ISO 8601:2004 describes both a basic and an extended format, these Guidelines recommend use of the extended format.

 -

当該属性値が他の値と比較される場合、時間帯は必ず示されるべきである。 またはdateTimeを使うべきである(訳注：この文は修正されるかもしれな い)。

-

ISO 8601:2004には基本形式と拡張形式がある。 本ガイドラインでは拡張形式を使うことを推奨する。

- +

当該属性値が他の値と比較される場合、時間帯は必ず示されるべきである。 またはdateTimeを使うべきである(訳注：この文は修正されるかもしれな い)。

+

ISO 8601:2004には基本形式と拡張形式がある。 本ガイドラインでは拡張形式を使うことを推奨する。

-

S'il est vraisemblable que la valeur utilisée soit destinée à être comparer à d’autres +

S'il est vraisemblable que la valeur utilisée soit destinée à être comparer à d’autres valeurs, alors une indication du fuseau horaire devrait toujours être incluse, et seule la représentation dateTime devrait être employée.

-

Pour toutes les représentations pour lesquelles l’ISO 8601:2004 décrit à la fois un format +

Pour toutes les représentations pour lesquelles l’ISO 8601:2004 décrit à la fois un format basique et un format étendu , ce guide d’encodage recommandande l’emploi du format étendu .

- - \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.temporal.w3c.xml b/P5/Source/Specs/teidata.temporal.w3c.xml index c79a6bc9a6..32be7ce762 100644 --- a/P5/Source/Specs/teidata.temporal.w3c.xml +++ b/P5/Source/Specs/teidata.temporal.w3c.xml @@ -1,9 +1,5 @@ - + defines the range of attribute values expressing a temporal @@ -20,33 +16,33 @@ See the file COPYING.txt for details Datatypes Second Edition du W3C. define la gama de valores de atributos que expresan un valor temporal del tipo fecha, hora, o combinación de ambas, de acuerdo con la especificación de W3C XML Schema Part 2: Datatypes Second Edition. - - - - - - - - - - - + + + + + + + + + + + -

If it is likely that the value used is to be compared with +

If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

 -

+

当該属性値が他の値と比較される場合、時間帯は必ず示されるべきである。 またはdateTimeを使うべきである(訳注：この文は修正されるかもしれな い)。

-

S'il est probable que la valeur utilisée doive être comparée à +

S'il est probable que la valeur utilisée doive être comparée à d’autres, alors une indication de fuseau horaire sera toujours incluse, et seule la représentation de dateTime sera employée.

- \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.temporal.working.xml b/P5/Source/Specs/teidata.temporal.working.xml index 494dc701de..80772bcdaa 100644 --- a/P5/Source/Specs/teidata.temporal.working.xml +++ b/P5/Source/Specs/teidata.temporal.working.xml @@ -1,19 +1,14 @@ - + + - + defines the range of values, conforming to the W3C XML Schema Part 2: Datatypes Second Edition specification, expressing a date or a date and a time within the working life of the document. - + + defines the range of attribute values used to express some @@ -13,11 +9,11 @@ See the file COPYING.txt for details exprimant une chaine de caracteres Unicode, y compris des espaces blancs. - - + + -

Attributes using this datatype must contain a single +

Attributes using this datatype must contain a single token in which whitespace and other punctuation characters are permitted.

- \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.truthValue.xml b/P5/Source/Specs/teidata.truthValue.xml index 50300365eb..de9fea7450 100644 --- a/P5/Source/Specs/teidata.truthValue.xml +++ b/P5/Source/Specs/teidata.truthValue.xml @@ -1,9 +1,5 @@ - + defines the range of attribute values used to express a truth @@ -16,29 +12,29 @@ value. define la gama de valores de atributos usados para expresar un valor cierto. definisce la gamma di valori di attributi usati per esprimere un valore di verità - - + + -

The possible values of this datatype are 1 or +

The possible values of this datatype are 1 or true, or 0 or false.

-

This datatype applies only for cases where uncertainty is +

This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: teidata.xTruthValue.

 -

+

曖昧な値が許されない場合に使われるデータ型になる。属性値が真偽値で ない場合、例えば"unknown"や"inapplicable"の場合には、当該データ型 の拡張版であるteidata.xTruthValueを使うべきである。

-

Ce type de données ne s'applique que dans les cas où l'incertitude est +

Ce type de données ne s'applique que dans les cas où l'incertitude est inappropriée ; c’est-à-dire si l'attribut concerné peut avoir une valeur autre que vrai ou faux, par ex. inconnu, ou inapplicable, il devrait alors y avoir la version étendue de ce type de données : teidata.xTruthValue.

- \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.unboundedCount.xml b/P5/Source/Specs/teidata.unboundedCount.xml index eacf8d4252..23a1a86dcc 100644 --- a/P5/Source/Specs/teidata.unboundedCount.xml +++ b/P5/Source/Specs/teidata.unboundedCount.xml @@ -1,16 +1,14 @@ - + defines the range of values used for a counting number or the string unbounded for infinity. - + + + diff --git a/P5/Source/Specs/teidata.version.xml b/P5/Source/Specs/teidata.version.xml index 2addc9bf52..e40b5847e9 100644 --- a/P5/Source/Specs/teidata.version.xml +++ b/P5/Source/Specs/teidata.version.xml @@ -1,9 +1,5 @@ - + defines the range of attribute values which may be used to @@ -11,10 +7,10 @@ See the file COPYING.txt for details définit la gamme des valeurs d'attribut exprimant un numéro de version TEI. - - + + -

The value of this attribute follows the pattern specified by +

The value of this attribute follows the pattern specified by the Unicode consortium for its version number (). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third @@ -23,7 +19,7 @@ See the file COPYING.txt for details

-

La valeur de cet attribut devrait suivre le format proposé par +

La valeur de cet attribut devrait suivre le format proposé par le Consortium Unicode pour identifier les versions (). Un numéro de version ne contient que des chiffres et des points. Le numéro initiale identifie le numéro majeur de la version. Un deuxième et @@ -31,4 +27,4 @@ See the file COPYING.txt for details facultative des versions mineures ou sous-mineurs.

- \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.versionNumber.xml b/P5/Source/Specs/teidata.versionNumber.xml index 95246f4f14..050a3e6dc7 100644 --- a/P5/Source/Specs/teidata.versionNumber.xml +++ b/P5/Source/Specs/teidata.versionNumber.xml @@ -1,16 +1,12 @@ - + defines the range of attribute values used for version numbers. - - + + -

+

- \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.word.xml b/P5/Source/Specs/teidata.word.xml index edd11ce673..c3c5ce0d0d 100644 --- a/P5/Source/Specs/teidata.word.xml +++ b/P5/Source/Specs/teidata.word.xml @@ -1,9 +1,5 @@ - + defines the range of attribute values expressed as a single @@ -16,26 +12,26 @@ See the file COPYING.txt for details define una gama de valores de atributos expresados como una única palabra o señal. definisce la gamma di valori di attributi espressi come singola parola o singolo token - - + + -

Attributes using this datatype must contain a single +

Attributes using this datatype must contain a single word which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

 -

+

当該データ型を使用する属性値は、ひとつの単語 になる。単語とは、文字、数字、句読点などの記号から構成されている。 空白文字は含むことができない。

-

Les attributs employant ce type de données doivent contenir un +

Les attributs employant ce type de données doivent contenir un mot simple ne contenant que des lettres, des chiffres, des signes de ponctuation, ou des symboles : ils ne peuvent donc pas inclure d’espace.

- \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.xTruthValue.xml b/P5/Source/Specs/teidata.xTruthValue.xml index b63a6ec2bb..f7a22cb2ce 100644 --- a/P5/Source/Specs/teidata.xTruthValue.xml +++ b/P5/Source/Specs/teidata.xTruthValue.xml @@ -1,9 +1,5 @@ - + extended truth value @@ -20,23 +16,23 @@ See the file COPYING.txt for details definisce la gamma di valori di attributi usati per esprimere un valore di verità potenzialmente sconosciuto - - - - - - - - + + + + + + + + -

In cases where where uncertainty is inappropriate, use the +

In cases where where uncertainty is inappropriate, use the datatype teidata.TruthValue.

 -

不明な場合がなければ、データ型teidata.TruthValueを使用する。

+

不明な場合がなければ、データ型teidata.TruthValueを使用する。

-

Dans le cas où l'incertitude n’est pas adaptée, employer plutot +

Dans le cas où l'incertitude n’est pas adaptée, employer plutot le type de données teidata.TruthValue.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.xmlName.xml b/P5/Source/Specs/teidata.xmlName.xml index 303bd567c7..857fa32f3c 100644 --- a/P5/Source/Specs/teidata.xmlName.xml +++ b/P5/Source/Specs/teidata.xmlName.xml @@ -1,16 +1,12 @@ - + defines attribute values which contain an XML name. - - + + -

The rules defining an XML name form a part of the XML Specification.

+

The rules defining an XML name form a part of the XML Specification.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/teidata.xpath.xml b/P5/Source/Specs/teidata.xpath.xml index 8ace6486cd..3d35e0cf1f 100644 --- a/P5/Source/Specs/teidata.xpath.xml +++ b/P5/Source/Specs/teidata.xpath.xml @@ -1,23 +1,19 @@ - + -defines attribute values + defines attribute values which contain an XPath expression. - - - - -

Any XPath expression using the syntax + + + + +

Any XPath expression using the syntax defined in .

-

When writing programs that evaluate XPath expressions, +

When writing programs that evaluate XPath expressions, programmers should be mindful of the possibility of malicious code injection attacks. For further information about XPath injection attacks, see the article at OWASP.

- - \ No newline at end of file + + diff --git a/P5/Source/Specs/term.xml b/P5/Source/Specs/term.xml index 9103e5d9f1..e1e2b4489b 100644 --- a/P5/Source/Specs/term.xml +++ b/P5/Source/Specs/term.xml @@ -1,11 +1,5 @@ - + term @@ -22,7 +16,7 @@ designación simbólica que se considera como un término técnico. contiene una parola singola, un'unità formata da più parole, o una designazione simbolica che è considerata come un termine tecnico - enthält ein einzelnes Wort, Mehrworttermini + enthält ein einzelnes Wort, Mehrworttermini oder symbolische Bezeichnungen, die als Fachbegriffe verstanden werden @@ -102,26 +96,25 @@ are deprecated and may be removed at a subsequent release.

-

Wenn dieses Element innerhalb eines index-Elements auftritt, so wird es als Lemma dieses +

Wenn dieses Element innerhalb eines index-Elements auftritt, so wird es als Lemma dieses Index-Eintrags angesehen. An anderer Stelle wird es einfach als Auszeichnung eines Fachbegriffs gewertet. Das term-Element kann mit einem entsprechenden gloss-Element über sein ref-Attribut verknüpft werden; alternativ kann die Verknüpfung auch über das target-Attribut am gloss-Element hergestellt werden.

-

+

Es wird keine Position im Theoriediskurs bezogen, ob Fachbegriffe atomare oder größere lexikalische Einheiten umfassen können; das term-Element kann für jedwede dieser Einheiten eingesetzt werden. Weiterhin wird keine Definition von "Fachbegriff" gegeben, sondern jeder praktische Einsatz sanktioniert.

-

+

So wie auch andere Mitglieder der Attributklasse att.canonical können term-Elemente im laufenden Text mit entsprechenden kanonischen Definitionen verknüpft werden; entweder mittels einer URI (über das ref-Attribut) oder mittels eines speziellen Codes (über das key-Attribut). Da sich die Attribute target und cRef gegenseitig ausschließen und mit dem ref-Attribut überlappen, sind diese als "veraltet" gekennzeichnet und können mit einer der folgenden Guideline-Auflagen entfernt werden.

- - + + + + + terrain terrain contains information about the physical terrain of a place. @@ -23,66 +20,50 @@ $Id$ - - - - - - + + - - - - - - - - - - + + - - - - - - - - - + + + + + - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + @@ -100,4 +81,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/text.xml b/P5/Source/Specs/text.xml index 28a761284d..c78792294d 100644 --- a/P5/Source/Specs/text.xml +++ b/P5/Source/Specs/text.xml @@ -1,11 +1,5 @@ - + text @@ -39,7 +33,7 @@ $Id$ - + @@ -48,7 +42,7 @@ $Id$ - + @@ -203,4 +197,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/textClass.xml b/P5/Source/Specs/textClass.xml index 4cfe3b7e5a..b61f8d5b26 100644 --- a/P5/Source/Specs/textClass.xml +++ b/P5/Source/Specs/textClass.xml @@ -1,11 +1,5 @@ - + text classification @@ -37,13 +31,11 @@ $Id$ - - - - - - - + + + + + @@ -110,4 +102,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/textDesc.xml b/P5/Source/Specs/textDesc.xml index f70abebee7..2bf1253613 100644 --- a/P5/Source/Specs/textDesc.xml +++ b/P5/Source/Specs/textDesc.xml @@ -1,11 +1,5 @@ - + text description @@ -32,9 +26,7 @@ situational parameters. - - - + @@ -85,4 +77,4 @@ situational parameters. - \ No newline at end of file + diff --git a/P5/Source/Specs/textLang.xml b/P5/Source/Specs/textLang.xml index 61e0b15ceb..51444f0849 100644 --- a/P5/Source/Specs/textLang.xml +++ b/P5/Source/Specs/textLang.xml @@ -1,11 +1,5 @@ - + text language @@ -55,7 +49,9 @@ $Id$ principal utilizada en el manuscrito. assegna un codice che identifica la lingua principale utilizzata nel manoscritto - + + + other languages @@ -74,7 +70,9 @@ $Id$ lenguas utilizadas en el manuscrito. uno o più codici che identificano eventuali altre lingue utilizzate nel manoscritto - + + + @@ -100,7 +98,7 @@ languages or writing systems used for the bibliographic or manuscript descriptio all other TEI elements, such information should be provided by means of the global xml:lang attribute attached to the element containing the description.

-

In all cases, languages should be identified by means of a standardized +

In all cases, languages should be identified by means of a standardized language tag generated according to BCP 47. Additional documentation for the language may be provided by a language element in the TEI header. @@ -110,4 +108,4 @@ element in the TEI header. - \ No newline at end of file + diff --git a/P5/Source/Specs/textNode.xml b/P5/Source/Specs/textNode.xml index 6e246b0eef..62ae02ec23 100644 --- a/P5/Source/Specs/textNode.xml +++ b/P5/Source/Specs/textNode.xml @@ -1,20 +1,16 @@ - + - indicates the presence + indicates the presence of a text node in a content model - - - - - + + + + + + + @@ -22,11 +18,11 @@ $Id$ - + - + - \ No newline at end of file + diff --git a/P5/Source/Specs/then.xml b/P5/Source/Specs/then.xml index 6ffd948f9b..4b3a8f3ebb 100644 --- a/P5/Source/Specs/then.xml +++ b/P5/Source/Specs/then.xml @@ -1,11 +1,5 @@ - + separates the condition from the default in an if, or @@ -21,7 +15,9 @@ the antecedent and the consequent in a cond element. - + + + @@ -55,4 +51,4 @@ human readability of the feature-system declaration.

- \ No newline at end of file + diff --git a/P5/Source/Specs/time.xml b/P5/Source/Specs/time.xml index 9431aba531..9fbfb9015b 100644 --- a/P5/Source/Specs/time.xml +++ b/P5/Source/Specs/time.xml @@ -1,11 +1,5 @@ - + time diff --git a/P5/Source/Specs/timeline.xml b/P5/Source/Specs/timeline.xml index 01102307de..44d5056362 100644 --- a/P5/Source/Specs/timeline.xml +++ b/P5/Source/Specs/timeline.xml @@ -1,5 +1,5 @@ - + timeline @@ -20,9 +20,7 @@ - - - + @@ -33,7 +31,9 @@ désigne le début de la frise chronologique, c'est-à-dire le moment où elle commence. indica el origen de la escala temporal, es decir, el momento en que inicia. indica l'origine della scala temporale, cioè il momento in cui ha inizio - + + +

If this attribute is not supplied, the implication is that the time of origin is not known. If it is supplied, it must @@ -52,7 +52,9 @@ spécifie l'unité de temps correspondant à la valeur de l'attribut interval de la frise chronologique ou des points temporels qui la constituent. especifica la unidad temporal correspondiente al valor del atributo interval (intervalo) de la escala temporal o de sus puntos constitutivos. specifica l'unità temporale corrispondente al valore dell'attributo interval della scala temporale o dei suoi punti costitutivi - + + + days @@ -95,7 +97,9 @@ spécifie la partie numérique d'un intervalle de temps. indica los componentes numéricos de un intervalo de tiempo. indica la componente numerica di un intervallo temporale - + + +

The value irregular indicates uncertainty about all the intervals in the timeline; the value regular indicates that all the intervals are evenly spaced, but the size of the intervals is not known; numeric values indicate evenly spaced values of the size specified. If individual points in time in the timeline are given different values for the interval attribute, those values locally override the value given in the timeline.

 @@ -136,4 +140,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/title.xml b/P5/Source/Specs/title.xml index 2f0cc50578..2a6e119827 100644 --- a/P5/Source/Specs/title.xml +++ b/P5/Source/Specs/title.xml @@ -1,10 +1,7 @@ - + + + + title titre Titel @@ -30,40 +27,38 @@ $Id$ - - The calendar attribute will be removed from this element + + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - + indicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material. @@ -84,7 +79,9 @@ $Id$ non pubblicato. gibt den bibliografischen Typ eines Titels an, d.h. ob er einen Artikel, ein Buch, eine Zeitschrift, eine Reihe oder unpubliziertes Material bezeichnet. - + + + analytic @@ -282,8 +279,10 @@ doit pas être utilisé.

acuerdo con alguna tipología funcional. classifica il titolo seguendo una tipologia conveniente. - klassifiziert den Titel entsprechend einer geeigneten Typologie. - + klassifiziert den Titel entsprechend einer geeigneten Typologie. + + + main title @@ -296,7 +295,6 @@ principal principal titolo Haupttitel - subordinate @@ -511,10 +509,9 @@ epistemology, methodology and history of Bibliothek herangezogen wird; Letzteres durch den Verweis auf ein XML-Element, das den kanonischen Titel enthält.

- - \ No newline at end of file + diff --git a/P5/Source/Specs/titlePage.xml b/P5/Source/Specs/titlePage.xml index 2e76307eb1..c772869bb2 100644 --- a/P5/Source/Specs/titlePage.xml +++ b/P5/Source/Specs/titlePage.xml @@ -1,11 +1,5 @@ - + title page @@ -37,8 +31,8 @@ $Id$ - - + + @@ -56,7 +50,9 @@ $Id$ tipología funcional. classifica il frontespizio in base a una tipologia funzionale - + + +

This attribute allows the same element to be used for volume title pages, series title pages, etc., as well as for the main @@ -141,4 +137,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/titlePart.xml b/P5/Source/Specs/titlePart.xml index a4e9c60f69..eaf2fd134d 100644 --- a/P5/Source/Specs/titlePart.xml +++ b/P5/Source/Specs/titlePart.xml @@ -1,11 +1,5 @@ - + title part @@ -42,7 +36,9 @@ indicated on a title page. beschreibt die Funktion dieses Titelbestandteils näher. especifica la función de tal subdivisión del título. specifica il ruolo di tale sezione o partizione all'interno del titolo - + + + main @@ -159,4 +155,4 @@ indicated on a title page. - \ No newline at end of file + diff --git a/P5/Source/Specs/titleStmt.xml b/P5/Source/Specs/titleStmt.xml index d7afe5f04a..71afeae093 100644 --- a/P5/Source/Specs/titleStmt.xml +++ b/P5/Source/Specs/titleStmt.xml @@ -1,11 +1,5 @@ - + title statement diff --git a/P5/Source/Specs/tns.xml b/P5/Source/Specs/tns.xml index 0d26a92827..df2fab5035 100644 --- a/P5/Source/Specs/tns.xml +++ b/P5/Source/Specs/tns.xml @@ -1,11 +1,5 @@ - + @@ -98,4 +92,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/trailer.xml b/P5/Source/Specs/trailer.xml index 40f438bf60..d0c6e77862 100644 --- a/P5/Source/Specs/trailer.xml +++ b/P5/Source/Specs/trailer.xml @@ -1,11 +1,5 @@ - + contains a closing title or footer appearing at the end of a division of a text. @@ -27,33 +21,31 @@ $Id$ - - - - - - - - - - - + + + + + + + + + Explicit pars tertia - + - In stead of FINIS this advice I send, - Let Rogues and Thieves beware of + In stead of FINIS this advice I send, + Let Rogues and Thieves beware of Hamans END.

From EEBO A87070

- + Explicit pars tertia @@ -78,4 +70,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/trait.xml b/P5/Source/Specs/trait.xml index 66504a0a6c..ed3827ca07 100644 --- a/P5/Source/Specs/trait.xml +++ b/P5/Source/Specs/trait.xml @@ -1,10 +1,7 @@ - + + + + trait trait distinctif contains a description of some status or quality attributed to a person, place, or organization typically, but not necessarily, @@ -50,35 +47,35 @@ $Id$ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + + - transcription description - describes the set of transcription conventions used, particularly for spoken material. - - - - - - - - - - - - - - supplies an identifier for the encoding convention, independent of any version number. - - - - - - supplies a version number for the encoding conventions + transcription description + describes the set of transcription conventions used, particularly for spoken material. + + + + + + + + + + + + + + supplies an identifier for the encoding convention, independent of any version number. + + + + + + supplies a version number for the encoding conventions used, if any. - - - - - - - - - - + + + + + + + + + + - \ No newline at end of file + diff --git a/P5/Source/Specs/transpose.xml b/P5/Source/Specs/transpose.xml index eccfcdf492..d0e790e907 100644 --- a/P5/Source/Specs/transpose.xml +++ b/P5/Source/Specs/transpose.xml @@ -1,11 +1,5 @@ - + describes a single textual transposition as an ordered list @@ -38,4 +32,4 @@ as indicated by the metamark.

- \ No newline at end of file + diff --git a/P5/Source/Specs/tree.xml b/P5/Source/Specs/tree.xml index 40b2592cc2..894814ae63 100644 --- a/P5/Source/Specs/tree.xml +++ b/P5/Source/Specs/tree.xml @@ -1,11 +1,5 @@ - + tree @@ -50,7 +44,9 @@ nodes of the tree. racine et des nœuds internes de l'arbre. establece el número máximo de hijos (descendientes) de la raíz y de los nodos internos del árbol. stabilisce il numero massimo di figli della radice e dei nodi interni dell'albero - + + + ordered @@ -66,7 +62,9 @@ partially ordered. indique si l'arbre est ordonné ou non ou s'il l'est partiellement. indica si el árbol es o no ordenado, o si es parcialmente ordenado. indica se l'albero è ordinato o parzialmente ordinato - + + + @@ -112,7 +110,9 @@ unordered. nombre de ses nœuds. proporciona el orden del árbol, es decir, el número de los nodos. indica l'ordine dell'albero, cioè il numero dei suoi nodi - + + +

The size of a tree is always one less than its order, hence there is no need for both a size and order @@ -236,4 +236,4 @@ there is an internal node, there must also be at least one leaf.

- \ No newline at end of file + diff --git a/P5/Source/Specs/triangle.xml b/P5/Source/Specs/triangle.xml index 3d2379cb77..8f8eccfba7 100644 --- a/P5/Source/Specs/triangle.xml +++ b/P5/Source/Specs/triangle.xml @@ -1,11 +1,5 @@ - + underspecified embedding tree, so called because of its @@ -28,16 +22,12 @@ $Id$ - - - - - - - - - - + + + + + + @@ -51,7 +41,9 @@ structure or other analytic element. fournit l'identifiant de l'objet représenté par le triangle ; cet objet peut être une paire nom-valeur ou tout autre élément analytique. asigna al triángulo un valor, que puede ser el identificador de una estructura de rasgos u otro elemento de análisis. assegna al triangolo un valore, che può essere l'dentificatore di una struttura di tratti o altro elemento di analisi - + + + @@ -89,4 +81,4 @@ structure or other analytic element. - \ No newline at end of file + diff --git a/P5/Source/Specs/typeDesc.xml b/P5/Source/Specs/typeDesc.xml index 1f08d51997..5a3288d839 100644 --- a/P5/Source/Specs/typeDesc.xml +++ b/P5/Source/Specs/typeDesc.xml @@ -1,11 +1,5 @@ - + typeface description @@ -19,16 +13,10 @@ $Id$ - - - + - - - - - - + + @@ -53,4 +41,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/typeNote.xml b/P5/Source/Specs/typeNote.xml index 7d9e6910be..31f2f0dfb2 100644 --- a/P5/Source/Specs/typeNote.xml +++ b/P5/Source/Specs/typeNote.xml @@ -1,11 +1,5 @@ - + typographic note @@ -30,4 +24,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/u.xml b/P5/Source/Specs/u.xml index 85cab0b1f2..41d21abb53 100644 --- a/P5/Source/Specs/u.xml +++ b/P5/Source/Specs/u.xml @@ -1,11 +1,5 @@ - + utterance @@ -28,7 +22,7 @@ $Id$ - + @@ -46,7 +40,9 @@ $Id$ 前の発話から当該発話への遷移(交替)の性質を示す。 indica la naturaleza de la transición entre un enunciado y el precedente. indica la natura del passaggio tra questo enunciato e il precedente - + + + smooth diff --git a/P5/Source/Specs/unclear.xml b/P5/Source/Specs/unclear.xml index 9c6a936f18..bea7fb9117 100644 --- a/P5/Source/Specs/unclear.xml +++ b/P5/Source/Specs/unclear.xml @@ -1,11 +1,5 @@ - + unclear @@ -32,7 +26,7 @@ - + @@ -97,12 +91,16 @@
-

One or more words may be used to describe the reason; + +

One or more words may be used to describe the reason; usually each word will refer to a single cause.

- -

Una o más palabras se pueden usar para describir la razón. Normalmente cada palabra se referirá a una causa concreta

-

Ein oder mehrere Wörter können verwendet werden, um den Grund zu beschreiben. In der Regel wird jedes Wort auf eine einzige Ursache verweisen.

- + + +

Una o más palabras se pueden usar para describir la razón. Normalmente cada palabra se referirá a una causa concreta

+ + +

Ein oder mehrere Wörter können verwendet werden, um den Grund zu beschreiben. In der Regel wird jedes Wort auf eine einzige Ursache verweisen.

+ Where the difficulty in transcription arises from damage, categorizes the cause of @@ -116,9 +114,11 @@ usually each word will refer to a single cause.

causa de un daño, categoriza, si puede ser identificada, la causa de tal daño. qualora la difficoltà nella trascrizione emerga da danneggiamento, indica la causa del danno qualora possa essere identificata. - basiert die Schwierigkeit bei der Transkription auf einer schadhaften Stelle am Textträger, + basiert die Schwierigkeit bei der Transkription auf einer schadhaften Stelle am Textträger, kann der Grund dafür hier genauer kategorisiert werden. - + + + damage results from rubbing of the leaf edges @@ -142,7 +142,7 @@ usually each word will refer to a single cause.

sur la surface de la feuille il danno è causato da macchie di umido sulla superficie del foglio - Schaden, versursacht durch Schimmel auf der Blattoberfläche + Schaden, versursacht durch Schimmel auf der Blattoberfläche damage results from smoke @@ -183,13 +183,14 @@ his attention elements may be closely allied in use. See section for discussion of which element is appropriate for which circumstance.

-

The hand attribute points to a definition of the hand +

The hand attribute points to a definition of the hand concerned, as further discussed in section .

- -

El mismo elemento se usa para todos los casos de incertidubre en la transcripción del contenido de un elemento, para material tanto escrito como hablado. Para otros aspectos relacionados con la certeza, incertidumbre y fiablilidad del etiquetado y transcripción, consultar el capítulo .

+ +

El mismo elemento se usa para todos los casos de incertidubre en la transcripción del contenido de un elemento, para material tanto escrito como hablado. Para otros aspectos relacionados con la certeza, incertidumbre y fiablilidad del etiquetado y transcripción, consultar el capítulo .

Los elementos damage, gap, del, unclear y supplied pueden estar estrechamente relacionados en su uso. Consulta la sección para ver una discusión sobre qué elemento es apropiado en qué circunstancias.

-

El atributo hand dirige a una descripción de la mano implicada; se discute de manera más detallada en la sección .

 +

El atributo hand dirige a una descripción de la mano implicada; se discute de manera más detallada en la sección .

+

Le même élément est utilisé pour tous les cas d'incertitude portant sur la transcription du contenu d'éléments, qu'il s'agisse de documents écrits ou oraux. Pour les autres @@ -205,15 +206,15 @@ concerned, as further discussed in section .

 -

+

Das Element wird für alle unsicheren Transkriptionen verwendet, egal ob es sich um geschriebenes oder gesprochenes Material handelt. Für andere Aspekte der Sicherheit, Unsicherheit und Zuverlässigkeit von Auszeichnung und Transkription, siehe Kapitel .

-

+

Die Elemente damage, gap, del, unclear und supplied werden oft im selben Kontext verwendet. Im Kapitel wird diskutiert, welches Element unter welchen Umständen geeignet ist.

-

+

Das hand-Attribut verweist auf eine Beschreibung der betreffenden Schreibhand (siehe hierzu Kapitel ).

@@ -221,4 +222,4 @@ concerned, as further discussed in section .

- \ No newline at end of file + diff --git a/P5/Source/Specs/undo.xml b/P5/Source/Specs/undo.xml index 6c5ac0c1fc..039e560921 100644 --- a/P5/Source/Specs/undo.xml +++ b/P5/Source/Specs/undo.xml @@ -1,11 +1,5 @@ - + indicates one or more marked-up interventions in a document @@ -18,12 +12,16 @@ - + + + points to one or more elements representing the interventions which are to be reverted or undone. - + + + @@ -45,4 +43,4 @@ underdotting, thus reinstating the words "just some" and - \ No newline at end of file + diff --git a/P5/Source/Specs/unicodeProp.xml b/P5/Source/Specs/unicodeProp.xml index bd101b5109..a8c61f32c3 100644 --- a/P5/Source/Specs/unicodeProp.xml +++ b/P5/Source/Specs/unicodeProp.xml @@ -1,278 +1,281 @@ - + + - - unicode property - provides a Unicode property for a character (or + + unicode property + provides a Unicode property for a character (or glyph). - - - - - - - - - - - specifies the normalized name of a Unicode + + + + + + + + + + + specifies the normalized name of a Unicode property. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - specifies the value of a named Unicode + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + specifies the value of a named Unicode property. - - - - - - - 人 - - -

A definitive list of current Unicode property names is provided in The Unicode + + + + + + + + + + + + 人 + + + + +

A definitive list of current Unicode property names is provided in The Unicode Standard.

- - -

Eine definitive Liste der aktuellen Unicode Eigenschaftsnamen wird vom Unicode Standard + + +

Eine definitive Liste der aktuellen Unicode Eigenschaftsnamen wird vom Unicode Standard bereitgestellt.

- - -

Une liste fermée des noms de propriétés Unicode est donnée dans la norme Unicode.

- - -

現行のユニコード基準名のリストは、ユニコード規格にある。

- - - - + + +

Une liste fermée des noms de propriétés Unicode est donnée dans la norme Unicode.

+ + +

現行のユニコード基準名のリストは、ユニコード規格にある。

+ + + + diff --git a/P5/Source/Specs/unihanProp.xml b/P5/Source/Specs/unihanProp.xml index 453c7689de..0095838acc 100644 --- a/P5/Source/Specs/unihanProp.xml +++ b/P5/Source/Specs/unihanProp.xml @@ -1,20 +1,19 @@ - + + - - unihan property - holds the name and value of a normative or + + unihan property + holds the name and value of a normative or informative Unihan character (or glyph) property as part of its attributes. - - - - - - - - - + - - - specifies the normalized name of a unicode + + + specifies the normalized name of a unicode han database (Unihan) property - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - specifies the value of a named Unihan + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + specifies the value of a named Unihan property - - - - - - - - - -

A definitive list of current Unihan property names is provided in the Unicode Han Database.

- - - - + + + + + + + + + + + +

A definitive list of current Unihan property names is provided in the Unicode Han Database.

+ + + + diff --git a/P5/Source/Specs/unit.xml b/P5/Source/Specs/unit.xml index 01a9b4aa1e..61d9cdcb1d 100644 --- a/P5/Source/Specs/unit.xml +++ b/P5/Source/Specs/unit.xml @@ -1,16 +1,10 @@ - + contains a symbol, a word or a phrase referring to a unit of measurement in any kind of formal or informal system. enthält ein Symbol, ein Wort oder eine Phrase, die sich auf eine Maßeinheit in einem formellen oder informellen System bezieht. - + 公式・非公式に関わらず、単位を表す記号や単語、語句を含む。 @@ -20,15 +14,16 @@ - +

Here is an example of a unit element holding a unitRef attribute that points to a definition of the unit in the TEI header.

- 3 ells - - - + + 3 + ells + + @@ -44,18 +39,21 @@ 2 - kg + kg + - 3minute + + 3 + minute + - 1, 2, 5, 7 - millimètres + 1, 2, 5, 7millimètres @@ -67,8 +65,7 @@

Light travels at 3×10^10 - - cm per second + cm per second .

 diff --git a/P5/Source/Specs/unitDecl.xml b/P5/Source/Specs/unitDecl.xml index 3e979a9c6a..63ab16e2df 100644 --- a/P5/Source/Specs/unitDecl.xml +++ b/P5/Source/Specs/unitDecl.xml @@ -1,10 +1,7 @@ - + + + + unit declarations provides information about units of measurement that are not members of the International System of Units. @@ -18,63 +15,63 @@ - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + - \ No newline at end of file + diff --git a/P5/Source/Specs/unitDef.xml b/P5/Source/Specs/unitDef.xml index ae46a30382..11fa36c2d4 100644 --- a/P5/Source/Specs/unitDef.xml +++ b/P5/Source/Specs/unitDef.xml @@ -1,10 +1,7 @@ - + + + + unit definition contains descriptive information related to a specific unit of measurement. @@ -14,64 +11,64 @@ - - - - - - + + + + + + - The calendar attribute will be removed from this element + The calendar attribute will be removed from this element as it will only be allowed on elements that represent dates with their content. This is because the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the + indicates one or more systems or calendars to which the date represented by the content of this element belongs. - 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. - 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel + 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. + 指明該日期表示所使用的曆法計算系統。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra + indica el sistema o calendario en que se muestra una fecha. - indica il sistema o calendario al quale la data + indica il sistema o calendario al quale la data appartiene. - - - - - - - @calendar indicates one or more + + + + + + + @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this element has no textual content. - - - + + + - - - - - Equivalent to a cubit or 24 daktyloi. - - - - - A basic unit of length equivalent to one finger (or the size of a thumb) in ancient Greece. - - + + + + + Equivalent to a cubit or 24 daktyloi. + + + + + A basic unit of length equivalent to one finger (or the size of a thumb) in ancient Greece. + + - + - \ No newline at end of file + diff --git a/P5/Source/Specs/usg.xml b/P5/Source/Specs/usg.xml index b36d90ac4c..f61d1c2596 100644 --- a/P5/Source/Specs/usg.xml +++ b/P5/Source/Specs/usg.xml @@ -1,11 +1,5 @@ - + usage @@ -28,7 +22,6 @@ $Id$ - @@ -43,7 +36,9 @@ $Id$ classe les informations sur l'usage en utilisant n'importe quelle typologie adaptée clasifica la información sobre el uso aplicando una tipología funcional. classifica le informazioni sull'uso secondo una tipologia funzionale. - + + + geographic diff --git a/P5/Source/Specs/vAlt.xml b/P5/Source/Specs/vAlt.xml index d836d0410c..40622dac4d 100644 --- a/P5/Source/Specs/vAlt.xml +++ b/P5/Source/Specs/vAlt.xml @@ -1,11 +1,5 @@ - + value alternation @@ -29,12 +23,8 @@ $Id$ - - - - - - + + @@ -62,4 +52,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/vColl.xml b/P5/Source/Specs/vColl.xml index 6f2bb26e5c..ad0a3f2818 100644 --- a/P5/Source/Specs/vColl.xml +++ b/P5/Source/Specs/vColl.xml @@ -1,11 +1,5 @@ - + collection of values @@ -30,15 +24,11 @@ $Id$ - - - - - - - - - + + + + + @@ -57,7 +47,9 @@ $Id$ données sous forme d'ensemble, de paquet ou de liste. indica la organización del valor o valores dados como conjunto o lista. indica il tipo di organizzazione di un dato valore come insieme, borsa o lista. - + + + indicates that the given values are organized as a set. @@ -195,4 +187,4 @@ organisées en liste. - \ No newline at end of file + diff --git a/P5/Source/Specs/vDefault.xml b/P5/Source/Specs/vDefault.xml index 4ec3347a7e..9d396b3508 100644 --- a/P5/Source/Specs/vDefault.xml +++ b/P5/Source/Specs/vDefault.xml @@ -1,11 +1,5 @@ - + value default @@ -43,12 +37,8 @@ condition matches, the value none is assumed. - - - - - - + + @@ -83,4 +73,4 @@ elements.

- \ No newline at end of file + diff --git a/P5/Source/Specs/vLabel.xml b/P5/Source/Specs/vLabel.xml index 531daeecc2..4321cb4129 100644 --- a/P5/Source/Specs/vLabel.xml +++ b/P5/Source/Specs/vLabel.xml @@ -1,11 +1,5 @@ - + value label @@ -28,9 +22,7 @@ $Id$ - - - + @@ -42,7 +34,9 @@ $Id$ fournit un nom pour le point de partage. proporciona un nombre para un punto de división. fornisce un nome per il punto di condivisione. - + + + @@ -94,4 +88,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/vMerge.xml b/P5/Source/Specs/vMerge.xml index e4f998ff28..a816cfbfd2 100644 --- a/P5/Source/Specs/vMerge.xml +++ b/P5/Source/Specs/vMerge.xml @@ -1,11 +1,5 @@ - + merged collection of values @@ -32,9 +26,7 @@ contenidos por sus hijos, considerando la organización especificada por el atri - - - + @@ -48,7 +40,9 @@ contenidos por sus hijos, considerando la organización especificada por el atri résultantes comme un ensemble, un paquet ou une liste. indica que la organización resultante de la fusión de valores se muestra como un conjunto, multiconjunto o como una lista. indica l'organizzazione dei valori risultanti dall'unificazione in un insieme, borsa o lista. - + + + indicates that the resulting values are organized as a set. @@ -130,4 +124,4 @@ with the set of values masculine, neuter and feminine.

- \ No newline at end of file + diff --git a/P5/Source/Specs/vNot.xml b/P5/Source/Specs/vNot.xml index 53bd40e940..4f5acb2cfe 100644 --- a/P5/Source/Specs/vNot.xml +++ b/P5/Source/Specs/vNot.xml @@ -1,11 +1,5 @@ - + value negation @@ -27,9 +21,7 @@ $Id$ - - - + @@ -72,4 +64,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/vRange.xml b/P5/Source/Specs/vRange.xml index 8487f76541..8554c44dcf 100644 --- a/P5/Source/Specs/vRange.xml +++ b/P5/Source/Specs/vRange.xml @@ -1,11 +1,5 @@ - + value range @@ -71,4 +65,4 @@ then each value must be subsumed by the vRange. - \ No newline at end of file + diff --git a/P5/Source/Specs/val.xml b/P5/Source/Specs/val.xml index 9b1819e57d..35d06c9b89 100644 --- a/P5/Source/Specs/val.xml +++ b/P5/Source/Specs/val.xml @@ -1,11 +1,5 @@ - + value @@ -49,4 +43,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/valDesc.xml b/P5/Source/Specs/valDesc.xml index 972416ed92..0400d7b88c 100644 --- a/P5/Source/Specs/valDesc.xml +++ b/P5/Source/Specs/valDesc.xml @@ -1,11 +1,5 @@ - + value description @@ -59,4 +53,4 @@ an attribute may take, additional to the information carried by the - \ No newline at end of file + diff --git a/P5/Source/Specs/valItem.xml b/P5/Source/Specs/valItem.xml index c4e228718c..b9df3d602c 100644 --- a/P5/Source/Specs/valItem.xml +++ b/P5/Source/Specs/valItem.xml @@ -1,11 +1,5 @@ - + documents a single value in a predefined list of values. @@ -24,12 +18,12 @@ $Id$ - - - - - - + + + + + + @@ -37,7 +31,9 @@ $Id$ specifies the value concerned. - + + + diff --git a/P5/Source/Specs/valList.xml b/P5/Source/Specs/valList.xml index 270a0d05f5..dedd50e909 100644 --- a/P5/Source/Specs/valList.xml +++ b/P5/Source/Specs/valList.xml @@ -1,11 +1,5 @@ - + value list @@ -44,7 +38,9 @@ $Id$ los valores especificados para los atributos. indica la possibilità di estendere la lista dei valori specificati per gli attributi - + + + open @@ -147,4 +143,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/variantEncoding.xml b/P5/Source/Specs/variantEncoding.xml index 6c8c8fc94e..0eb17a6da1 100644 --- a/P5/Source/Specs/variantEncoding.xml +++ b/P5/Source/Specs/variantEncoding.xml @@ -1,11 +1,5 @@ - + variant encoding @@ -23,7 +17,9 @@ $Id$ - + + + indicates which method is used to encode the apparatus of @@ -36,7 +32,9 @@ variants. der textkritische Apparat kodiert ist. indica el método seguido para codificar el aparato crítico de las variantes. indica il metodo adottato per codificare l'apparato di varianti. - + + + apparatus uses line numbers or other canonical reference scheme @@ -97,7 +95,9 @@ or external to it. innerhalb oder außerhalb des Textes erscheint. indica si el aparato aparece al interno o al externo del texto. indica se l'apparato compare all'interno del testo, o esternamente. - + + + @@ -155,4 +155,4 @@ parallel-segmentation method of apparatus markup.

- \ No newline at end of file + diff --git a/P5/Source/Specs/view.xml b/P5/Source/Specs/view.xml index aebc363a62..d38f3163a9 100644 --- a/P5/Source/Specs/view.xml +++ b/P5/Source/Specs/view.xml @@ -1,11 +1,5 @@ - + view @@ -128,4 +122,4 @@ a brownstone-- - \ No newline at end of file + diff --git a/P5/Source/Specs/vocal.xml b/P5/Source/Specs/vocal.xml index fb278b2858..8088b3ab7d 100644 --- a/P5/Source/Specs/vocal.xml +++ b/P5/Source/Specs/vocal.xml @@ -1,11 +1,5 @@ - + vocal @@ -28,9 +22,7 @@ $Id$ - - - + @@ -42,7 +34,9 @@ $Id$ répété. indica si el fenómeno es eventual o si se repite. indica l'eventuale ripetizione del fenomeno - + + + false

The value true indicates that the vocal effect @@ -92,4 +86,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/w.xml b/P5/Source/Specs/w.xml index 606d7f8867..7dc252abec 100644 --- a/P5/Source/Specs/w.xml +++ b/P5/Source/Specs/w.xml @@ -1,11 +1,5 @@ - + word @@ -93,7 +87,7 @@ $Id$ Actors Waiters : - + @@ -101,4 +95,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/watermark.xml b/P5/Source/Specs/watermark.xml index 8e4dec88ee..03cb8f3a80 100644 --- a/P5/Source/Specs/watermark.xml +++ b/P5/Source/Specs/watermark.xml @@ -1,11 +1,5 @@ - + watermark diff --git a/P5/Source/Specs/when.xml b/P5/Source/Specs/when.xml index 3f21a63129..e523ed4557 100644 --- a/P5/Source/Specs/when.xml +++ b/P5/Source/Specs/when.xml @@ -1,5 +1,5 @@ - + indicates a point in time either relative to other elements in the same timeline tag, or absolutely. @@ -12,7 +12,9 @@ - + + + supplies an absolute value for the time. @@ -22,7 +24,9 @@ contient une valeur temporelle absolue. proporciona un valor temporal absoluto indica un valore temporale assoluto - + + +

This attribute should always be specified on a when element which serves as the target for the origin attribute of a timeline.

@@ -42,7 +46,9 @@ especifica la unidad temporal en la que se expresa el valor interval, si este valor no es heredado del padre timeline. specifica l'unità temporale nel quale è espresso l'attributo interval, se questo non è ereditato dal genitore timeline - + + + days @@ -85,7 +91,9 @@ spécifie la partie numérique d'un intervalle de temps. especifica los componentes numéricos de un intervalo temporal. indica la componente numerica di un intervallo temporale - + + + identifies the reference point for determining the time of the current when element, which is obtained by adding the interval to the time of the reference point. @@ -95,7 +103,9 @@ identifie le point de référence pour déterminer la date ou l'heure de l'élément courant when : cette date ou cette heure s'obtiennent en ajoutant la valeur de l'intervalle à la date du point de référence. identifica el punto de referencia para la determinación del valor temporal del elemento when (cuando) en cuestión, obtenido añadiendo el intervalo al punto de referencia temporal. identifica il punto di riferimento per la determinazione del valore temporale dell'elemento when corrente, ottenuto aggiungendo l'intervallo al punto di riferimento temporale - + + +

This attribute should point to another when element in the same timeline. If no value is @@ -136,4 +146,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/width.xml b/P5/Source/Specs/width.xml index 62855f778f..71df9ba726 100644 --- a/P5/Source/Specs/width.xml +++ b/P5/Source/Specs/width.xml @@ -1,11 +1,5 @@ - + width @@ -47,4 +41,4 @@ facing the observer, and perpendicular to that indicated by the - \ No newline at end of file + diff --git a/P5/Source/Specs/wit.xml b/P5/Source/Specs/wit.xml index f153529f5f..8ba635db3f 100644 --- a/P5/Source/Specs/wit.xml +++ b/P5/Source/Specs/wit.xml @@ -1,11 +1,5 @@ - + wit @@ -69,4 +63,4 @@ interest.

- \ No newline at end of file + diff --git a/P5/Source/Specs/witDetail.xml b/P5/Source/Specs/witDetail.xml index f9b40b0762..ecb9d7db0d 100644 --- a/P5/Source/Specs/witDetail.xml +++ b/P5/Source/Specs/witDetail.xml @@ -1,11 +1,5 @@ - + witness detail @@ -56,7 +50,9 @@ detail refers. witDetail. indica la sigla o siglas relativas a los testimonios a los cuales se refieren los detalles indica la sigla o le sigle relative ai testimoni ai quali si riferiscono i dettagli - + + + describes the type of information given about the witness. @@ -67,7 +63,9 @@ detail refers. le témoin. describe el tipo de información dada sobre los testimonios. descrive il tipo di informazione fornita in merito al testimone - + + + @@ -90,4 +88,4 @@ detail refers. - \ No newline at end of file + diff --git a/P5/Source/Specs/witEnd.xml b/P5/Source/Specs/witEnd.xml index 3a163c4ffa..d5222d49ff 100644 --- a/P5/Source/Specs/witEnd.xml +++ b/P5/Source/Specs/witEnd.xml @@ -1,11 +1,5 @@ - + fragmented witness end @@ -28,7 +22,9 @@ witness. - + + + @@ -42,4 +38,4 @@ witness. - \ No newline at end of file + diff --git a/P5/Source/Specs/witStart.xml b/P5/Source/Specs/witStart.xml index 2c0569f149..56f68edf2c 100644 --- a/P5/Source/Specs/witStart.xml +++ b/P5/Source/Specs/witStart.xml @@ -1,11 +1,5 @@ - + fragmented witness start @@ -28,7 +22,9 @@ fragmentary witness. - + + + @@ -41,4 +37,4 @@ fragmentary witness. - \ No newline at end of file + diff --git a/P5/Source/Specs/witness.xml b/P5/Source/Specs/witness.xml index fc5c9f4550..8d625c45b0 100644 --- a/P5/Source/Specs/witness.xml +++ b/P5/Source/Specs/witness.xml @@ -1,11 +1,5 @@ - + witness @@ -36,7 +30,7 @@ referred to by a single sigil. - + @@ -67,4 +61,4 @@ may be empty.

- \ No newline at end of file + diff --git a/P5/Source/Specs/writing.xml b/P5/Source/Specs/writing.xml index d028c67a71..17cc4270cb 100644 --- a/P5/Source/Specs/writing.xml +++ b/P5/Source/Specs/writing.xml @@ -1,11 +1,5 @@ - + writing @@ -40,7 +34,9 @@ $Id$ fois ou progressivement. indica si el texto escrito aparece de repente o gradualmente. indica se il testo scritto appare in un'unica soluzione o gradualmente - + + +

The value true indicates the writing is revealed gradually; the value false that the @@ -103,4 +99,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/xenoData.xml b/P5/Source/Specs/xenoData.xml index 7448af8d57..8f6eb2b112 100644 --- a/P5/Source/Specs/xenoData.xml +++ b/P5/Source/Specs/xenoData.xml @@ -1,11 +1,5 @@ - + non-TEI metadata @@ -39,18 +33,26 @@ $Id$ have to be resolved accordingly.

- The description of a new world, called the blazing-world - The Duchess of Newcastle - 1667 - British Library, 8407.h.10 - utopian fiction + + + The description of a new world, called the blazing-world + The Duchess of Newcastle + 1667 + British Library, 8407.h.10 + utopian fiction + + - The Description of a New World, Called the Blazing-World, 1668 - Cavendish, Margaret (Lucas), Duchess of Newcastle - Women Writers Project - 2002-02-12 - utopian fiction + + + The Description of a New World, Called the Blazing-World, 1668 + Cavendish, Margaret (Lucas), Duchess of Newcastle + Women Writers Project + 2002-02-12 + utopian fiction + + @@ -59,72 +61,75 @@ $Id$ - +

In this example, the prefix rdf is bound to the namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#, the prefix dc is bound to the namespace http://purl.org/dc/elements/1.1/, and the prefix cc is bound to the namespace http://web.resource.org/cc/.

- - - - Applied Software Project Management - review - - - - - - - - - - - - - + + + + + Applied Software Project Management - review + + + + + + + + + + + + + +

In this example, the prefix dc is again bound to the namespace http://www.openarchives.org/OAI/2.0/oai_dc/, and the prefix oai_dc is bound to the namespace http://www.openarchives.org/OAI/2.0/oai_dc/.

- - - The colonial despatches of Vancouver Island and British + + + + The colonial despatches of Vancouver Island and British Columbia 1846-1871: 11566, CO 60/2, p. 291; received 13 November. Trevelyan to Merivale (Permanent Under-Secretary) - 1858-11-12 - Trevelyan - University of Victoria Humanities Computing and Media + 1858-11-12 + Trevelyan + University of Victoria Humanities Computing and Media Centre, and UVic Libraries - InteractiveResource - application/xhtml+xml - text - http://bcgenesis.uvic.ca/getDoc.htm?id=B585TE13.scx - This document is licensed under a Creative Commons … - (SCHEME=ISO639) en - Transcribed from microfilm and/or original documents, and + InteractiveResource + application/xhtml+xml + text + http://bcgenesis.uvic.ca/getDoc.htm?id=B585TE13.scx + This document is licensed under a Creative Commons … + (SCHEME=ISO639) en + Transcribed from microfilm and/or original documents, and marked up in TEI P5 XML. The interactive XHTML resource is generated from the XHTML using XQuery and XSLT. - repository: CO - coNumber: 60 - coVol: 2 - page: 291 - coRegistration: 11566 - received: received 13 November - Trevelyan, Sir Charles Edward - Merivale, Herman - Elliot, T. Frederick - Moody, Colonel Richard Clement - Lytton, Sir Edward George Earle Bulwer - Jadis, Vane - Carnarvon, Earl - British Columbia - British Columbia correspondence: Public Offices + repository: CO + coNumber: 60 + coVol: 2 + page: 291 + coRegistration: 11566 + received: received 13 November + Trevelyan, Sir Charles Edward + Merivale, Herman + Elliot, T. Frederick + Moody, Colonel Richard Clement + Lytton, Sir Edward George Earle Bulwer + Jadis, Vane + Carnarvon, Earl + British Columbia + British Columbia correspondence: Public Offices document (normally correspondence between government departments) - - + + @@ -132,49 +137,49 @@ $Id$ namespace http://www.loc.gov/mods/v3.

- - - Academic adaptation and cross-cultural + + + Academic adaptation and cross-cultural learning experiences of Chinese students at American universities - a narrative inquiry - - - - - Author - - Northeastern University - Hong - Zhang - - - - - Advisor - - Liliana - Meneses - - - text - doctoral theses - - - Boston (Mass.) - - Northeastern University - 2013 - - - eng - - - electronic - born digital - - - + a narrative inquiry + + + + + Author + + Northeastern University + Hong + Zhang + + + + + Advisor + + Liliana + Meneses + + + text + doctoral theses + + + Boston (Mass.) + + Northeastern University + 2013 + + + eng + + + electronic + born digital + + + @@ -184,7 +189,8 @@ $Id$ must be escaped as \n. To avoid the accidental insertion of newlines by software, the use of xml:space is recommended. Blocks of JSON should be wrapped in CDATA sections, as they may contain characters illegal in XML.

- + + <![CDATA[ { "features": [ @@ -257,7 +263,8 @@ $Id$ "@type": "Place" } ]]> - + +

Note: the example above has been trimmed for legibility. The original may be found linked from Arachosiorum Oppidum/Alexandria. The contributors, listed per the license terms, are R. Talbert, @@ -267,4 +274,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/xr.xml b/P5/Source/Specs/xr.xml index 49947b3b1c..aef29cce29 100644 --- a/P5/Source/Specs/xr.xml +++ b/P5/Source/Specs/xr.xml @@ -1,11 +1,5 @@ - + cross-reference phrase @@ -33,17 +27,15 @@ $Id$ - - - - - - - - - - - + + + + + + + + + @@ -57,7 +49,9 @@ $Id$ tipología funcional. indica il tipo di riferimento incrociato secondo una tipologia funzionale - + + + synonym @@ -223,4 +217,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/zone.xml b/P5/Source/Specs/zone.xml index f7487b0ac8..757ef47b5c 100644 --- a/P5/Source/Specs/zone.xml +++ b/P5/Source/Specs/zone.xml @@ -1,11 +1,5 @@ - + defines any two-dimensional area within a surface @@ -48,7 +42,9 @@ element. im msDesc-Element beschrieben ist oder durch die Koordinaten des surface-Elements selbst. Die Drehung wird in Bogengrad angegeben. - + + + 0 @@ -113,4 +109,4 @@ by its parent surface.

- \ No newline at end of file +